Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


superssjdan last won the day on May 27 2014

superssjdan had the most liked content!

About superssjdan

  • Rank

Profile Information

  • Gender
  • Location
  • Interests
    Anime,Church Music,all things Pc Security

Recent Profile Visitors

1,167 profile views
  1. I have to say it's been running quite well.I can see no signs of any memory leak with v9.Web surfing is snappy.You can't even tell it's there.Yet more proof you have to take most a/v testing results with a grain of salt.I'm quite satisfied.Will keep my eyes out for any issues and will report back should I notice any.Great job development team.
  2. Sorry for not posting back sooner,but here is a piece of info from what I did with a few peoples machines with the installation stalling at installing drivers.I found that uninstalling,rebooting, and reinstalling the NIC drivers did the trick.
  3. That's great news.Glad to hear all is well.The few systems I had worked on I couldn't find traces in system folder or registry as I suspected that might be the problem.Just goes to show,ESET support is always the first and best option.Thanks for reporting back.
  4. After that you could run CCleaner and check off any registry entries left behind by Checkpoint/zone alarm.Make sure any folders in program files x86,program data,user related to checkpoint/zone alarm are deleted.
  5. Based on my distant past experience with zone alarm,it doesn't uninstall very cleanly at all.It may be worth your time to try running the tool located hxxp://www.bleepingcomputer.com/download/zonealarm-uninstall-tool/ and rebooting when finished.I play several MMO's and have never had a single issue with Eset and any of them.
  6. It may be a shot in the dark,but it may be worth opening an elevated command prompt and running the system file checker by typing sfc/scannow and let it complete.If there are issues that can't be fixed by the sfc,reopen an elevated command prompt and copy and paste the following command and allow to complete DISM /Online /Cleanup-Image /RestoreHealth.You can also try running the Microsoft .NET framework repair tool located here hxxp://www.microsoft.com/en-us/download/details.aspx?id=30135 I only mention all this,due to my having worked on 4 Eset windows 8.1 x64 installs which had this problem and found in these 4 cases,after having done the above,was able to get Eset to install without issue.I wish I had more time to troubleshoot further as to maybe the root causes of the issues.Unfortunately I only do tech related stuf,computer repairs,installs,malware removal in my spare time.I am a manager in a supermarket of all things.Think it's time to get back to school.Tech related work is so much more gratifying.
  7. I have heard from several people with this same exact issue.I would urge you both to contact support https://www.eset.com/us/support/contact/s2/?art=soln2955&seg=home If users take the time to report this to support and supply them with the necessary logs upon request, this issue may be able to be fixed quickly. As always, with Eset, support is free of charge for licensed users. Their tech agents are quite simply the best at what they do. Please do report back to thread upon resolution of your cases, as it may be beneficial to others.
  8. Merry Christmas and Happy New year to the Entire Eset family as well as all the forum helpers and end users.May your holidays be productive,enjoyable, and malware free.
  9. I also have a 150/150 fiber FIOS connection,however I am not having the problem you are seeing.I use win 8.1 x64 and use ESS along with WSA and Adguard.I have not tinkered with any settings other than setting up exceptions for WSA and Adguard.
  10. It's always been a pet peeve of mine why everytime a new OS is beta'd/previewed and introduced and all these people download it and expect all their software to work.I have seen this in each and every forum I participate in(no need to mention names).It's not the devs job to get their software working with preview/beta software.It's only their obligation to get it working with final code.Code can change immensely and frequently during a development cycle.To expect a development team to participate in such a rollercoaster is unrealistic and unwarranted.When you run preview/beta software,you do so understanding that there are limitations and that some things most likely will NOT work.It's like playing Russian roulette.It's something you have to learn to deal with if you want to be the first one to run something.I would certainly hope this does not turn into a flood like I have seen elsewhere.It's a preview.I am 1000% sure that ESET,and others, will be compatible when code is final.No point in doing it before then as it is huge waste of development resources.
  11. Hello, Just follow the directions in this KB article and you should be good to go.hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2289&actp=search&viewlocale=en_US&searchid=1412071981857
  12. If there is one thing that sets Eset apart from the rest of the pack,it's support without a doubt.It is a beta,and as such.i would certainly expect issues.That's the whole purpose of beta testing..to have come to light issues which the testing lab cannot replicate.I would certainly advise patience.Not every issue will be squashed quickly.Some will take longer than others as I am sure you will know.Just be sure to use the built in support form or hxxp://www.eset.com/int/beta/form
  13. It's been flagged at Sucuri sitecheck as hosting malicious code,and now has been detected as a malicious site by 3/58 at virustotal for the cue-splitter page.I'd stay away for the moment.
  14. I,for one,would not trust any website owner,authorized reseller or otherwise,with a page that is in various states of neglect.Quite a few areas have not been updated in a long time,and some of the coding is quite poor.Definitely would not purchase anything from them.Better to be safe than sorry.There are far more reputable places to do business.
  • Create New...