cyberhash

Are you using the new versions that you have downloaded from the site, as there was issues with previous builds on windows 10 ?? 8.0.319 for v8 is fine on windows and you should make sure that's the version you are trying to install. If this is the version you are trying then its not ESS causing the problems. Are you overclocking or using a software suite that came with your motherboard to overclock ?

If the program quarantines anything that you don't believe is a virus or malware, then go to quarantine and submit a sample(right click on item) and it can be looked at. If it's found not to be dangerous then it will be excluded.

@jcd2150 & ilmara , have you tried using the eset uninstall tool before installing the new version ?? Not sure if this is works with windows 10, but worth a try hxxp://download.eset.com/special/ESETUninstaller.exe

Installed/activated and updated fine

got a direct link ?? as any of the beta pages i go to still show v 9.0.111

Glad you managed to get your problem sorted Sometimes learning the hard way is the best as you NEVER forget lol . You now probably know more about networks than 80% of the people online working out your problem.

You are correct I do have file and printer sharing enabled. I think I've corrected the svchost connection as it is not showing any more in the Troubleshooting Wizard. However the DHCP error is still showing in the event Viewer. I'm not having any issues with connections to the Internet or the other computer on my home network so I guess everything is working as it should. This svchost stuff is way over my head. Thank you for your time taken to reply and offer your solution, I appreciate it. You are welcome Don't have v9 beta running myself so cant advise as to why DHCP is showing on your event viewer if everything is working ok. As your pc would not have an ip address on your network if it could not make DHCP requests and communicate properly.

It was promised to us for this week, obviously it didn't happen. They don't say anything now and prefer to remain silent. Was stated that v8 and v9 beta installers would be updated after the 20th and before the 29th, we are in the middle of that time period nothing is late yet

@kuro yes its a known problem and done the same with all of us that were using 10240 & v9. It's not only you

Looks ugly , have you checked windows to see if any of your fonts are corrupt ????? as im running the same setup as yourself and have no issues whatsoever and the font displayed on my log viewer looks different and i have not changed anything (all defaults when installing ESS). Have attached a pic for you to look at

@Jack Sounds like your problem was related to a file association problem in windows if it was clicking on links within emails that was giving you problems. Nothing to do with what Eset product you installed. If i noticed this post earlier i could have told you how to fix it

Just a guess that your router has network file/printer/usb sharing enabled and its trying to communicate to svchost on your pc to allow it to be used, and because the firewall is blocking it then it cant issue a connection to it. Probably why its showing 39 blocking events for the 2 items. Personally i just allow all processes under svchost to communicate freely to prevent any problems, using (interactive) mode on the firewall to first check what the process is

@HITMAN wait for the new version available in the next few days

10 is up and running and stable, but it does smell of both windows 7 and 8.1. Look some places and you have the old control panel from win 7, and use another method to reach it and its got the metro style look with half the options not available. Also new edge browser has very poor compatibility with a lot of sites. Yeah Microsoft have made massive update failures in the past , but they do fix them quickly. Don't know if any of you seen the post regarding Symantec and them forcing (by mistake ahem) an alpha/beta update to Norton that was not to everyone's taste hxxp://www.theregister.co.uk/2015/07/20/win10_norton_snafu_update/ At least we know when we are testing and running beta stuff with ESET Personally i don't believe that build 10240 of win 10 that's doing the rounds will be the one we see released on the 29th.

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public Times they are a-changin'. Look at Microsoft, all open and humble. Yeah sure, but I am not saying that its only positive. If ESET needs to move the release date forward....there is always a few people that might react like "but you said it was going to be released now buuuuu" By keeping the release info secret until a few days before they plan to release it they prevent these people from feeling let down and disappointed and post their anger on social media or whatever. But personally I don't complain, I know how this works, even if they say October right now, I know that no date is set in stone I don't know about open and humble. I think they seem to think that they do everything right all the time, and if they get some negative feedback, they only come up with a bad excuse. It will be very interesting to see how their automatic WU system works out with Win10 if MS plan to keep the current "high" quality on their updates. WU works fine on 10 already had 2 security updates and 2 updates for windows defender

Ran this test myself to see what effect it had on my system. With ESS 8.0.312 Installed, win 7 x64. 2 Pics attached show no real difference between having ESS active or temporarily disabled. Think your problem could be driver related or something else running in the background that is not happy running along side EAV/ESS ?????

Any chance of having V9 having the same choices when configuring firewall when installing and first running. Much prefer the old way like v7 & v8 , where you could choose "Interactive" policy when first setting it up and then remembering the rules for each application launch.

Installed v9.0.114 of ESS (When installed it shows 9.0.111 ????) on win 10 pro x64 build 10240. Exactly the same problem as with previous builds of V9 on windows 10. Install works fine but totally blocks any internet access whatsoever and therefore cant even activate the beta. Internet access can only be gained by uninstalling ESS, temporarily disabling does not work. Any logs i can provide you with or anything else to help resolve this problem ???

I would presume one of the versions will be Win 10 compatible on release date. Even if v9 beta is not finished by then, they might even update v8 to work in the interim ?

Installed v9 beta on win 10 x64 build 10162. Cant get any internet access whatsoever even when everything is temporarily disabled via gui. Worked fine on build 10130 .......... Everything was working fine before installing v9 beta ........ MS problem or ESET ??

Cheers for that, just wanted to make sure it was reported and fixed

Like Marcos stated above, v2 of eset products were lightweight and done the job that they needed to do BACK when they were released. Time has moved on and so has the talent of crafting new code to infect pc's. I too loved the simplicity of v2 layout and options ...... but new & more options are needed in today's world. The GUI is no more complex than any other A/V product that i have tried, and i have tried (nearly) them all Performance wise, i would be surprised if ESET's products did not rank in the top 3 (if not top) , for low system impact.

Hi, Not a major problem as such, but needs to be fixed Uninstalled V9 Beta, with all modules/defs up to date as of today 29/06/15. Uninstall seemed to go fine , but leaves behind Epfw NDIS Lightweight Filter and with no internet access available until uninstalled manually.

Same here for me . Stuck at 11461 , hxxp://www.virusradar.com/en/update/infoshows 11463 is latest. Maybe an issue with update server. Maybe the update server is playing in the masters golf competition

Was just a thought that something else was running, and didn't like the way eset was accessing files at the start of a scan and causing the freezing. Saying that, with what you described in your original post. Your problem seems to be with the GUI itself and not the actual scan. If its freezing before even managing to press the scan button. Bad video card drivers perhaps ?