King Grub

Support might not work on weekends, so hopefully you will get help soon. I had that happen to my installation back in version 10. I was just about to reinstall Windows anyway, so I didn't bother messing with it. Worked fine afterwards.

I am playing Monster Hunter World on PS4 (just finished the campaign) and Final Fantasy Royal Edition on PC. Eagerly awaiting Far Cry 5 at the end of the month.

It is happening this very moment.

Happening here too, in Sweden. I am sure we are all on different ISPs, so it's definitely an ESET thing. So not on your or my end, just wait it out and they'll fix it. It's the weekend so it might take some hours if we are unlucky.

It's not a bug. It takes a few minutes for all security products to register with the Security Center. That goes for all security products and it has always been that way. The difference now is that ESET actually tells you that it isn't registered yet instead of saying it is when it isn't.

You might have downloaded and installed the stand-alone antivirus - Nod32 - instead of the complete security suite that includes a firewall. The license for the security suite can be used to activate the stand-alone antivirus as well.

So far so good!

Thanks Marcos! The last time it was logged was yesterday when I posted the screenshots above, so I will monitor it in the upcoming days. It usually happens once every 24-48 hours or so.

No, I an not a n00b. Trust me, I run a very tight ship here, and the issue is not on my computer. This happens, as I wrote earlier in this very thread, on new Windows 10 installations with Nod32 as the first program installed after basic drivers and Windows updates.

No, it has never happened on startup. And Internet is fine when this happens - I am always connected to things like IRC, and when Internet goes down for even a second, it shows in those logs with a disconnect. The problem is not on my PC.

This is what it looks like.

The latest version is 10.1.210.0. You can download and isntall it manually if you aren't up to date. I haven't bothered thinking about this error, since it is kind of a non-issue. Sometimes when it checks for a program update (not a regular definitions update) it can't connect to the server and it gives this error. This happens with the latest version as well, on multiple computers with completely unrelated IPs or ISPs, and on completely fresh Windows 10 installations where Nod32 is the first program installed after basic drivers and Windows Update. It fixes itself next time it the program update runs and it connects.

Same here, and several people I know experience the same thing. It is not on your end.

Suprisingly, it looks like a legit deal. It's not a third party seller, but Amazon itself that sells it for that price on the UK site. The problem is that you have to use Kaspersky afterwards. (j/k)

Don't turn it off. It is the Windows Firewall service that is running, and that should not be turned off.

Same for Trend Micro users!

You are a hero! I hope it gets fixed soon. I am sorry I couldn't be bothered with logs and dumps.

Ah. I have disabled the password and login screen since I am the only one who has physical access to my PC. Tech support, no matter which company, almost never seem to do this. Even when the issue is easliy reproducible and it is obvious that the problem lies with the product, not the users.

Pressing CTRL+ALT+DELETE will make it possible to get into Safe Mode. I found no other way; selecting Restart from the Start menu while pressing Shift didn't work. Once in Safe Mode with networking, you can download the ESET uninstall tool and get rid of it that way. After that the PC works as usual again.

Someone else with the exact same problem: And he tested on 2 PCs. Have you tried running the web installer on a Creators Update machine? Three different persons with the same exact issue in 2 days is not a fluke and points to an issue with the installation process itself, not the users.

This issue does not cause a BSOD, so I there are no memory dumps to send. The system just becomes super unresponsive, and you have to either do a hard reset with the reset button (which makes it reboot normally, but it freezes again when the desktop appears) or reboot into safe mode. Neither of which produces a memory dump. I just arrived at work an hour ago, so it'll be quite some time until I get home to my PC, but I will be able to fix a log tonight, though. I don't have any special drivers, and those I do have - video card for example, and all the latest. No yellow question marks in the Device Manager. Windows updated fully. And no errors or warnings in the Event Viewer except the 3-4 DCOM ones during boot which everyone has on Windows 10. I run a very tight ship.

Hi! It does react to the Start button, but not to any further action from the start menu. For example, trying to restarting the computer from there just hangs it. Task Manager works by pressing Ctrl+Alt+Del, and it is from there that I had to reboot into Safe Mode with networking, download the ESET uninstall tool and run it to be able to use the computer. If I had been a "normal" computer user I would probably have been stuck at the freezing stage. I don't have a Lenovo notebook. It's a custom built desktop with a clean install of Windows, no bloatware. The ESET gui looks just like the pictures posted above, but in English. I tried to install it again after removing the first frozen installation with the uninstall tool, but the same thing happened again. I am not trying a third time for the time being. This is using the web installer by the way, since the full installation packages have not been updated to the latest version yet. I have not tried to use one of those yet. I usually use the offline installers, but I wanted to avoid having to update the program after installation this time.

Hello! I tried to do a fresh install of the latest version yesterday and got the exact same results as the thread starter! Exactly!

I don't have any good advice; I just wanted to say that I hope you get things fixed without any more issues. Getting hacked sucks!

Yeah, 10241 just came through fine.