Jump to content

[BUG] Problems with Eset and Windows 10 Creator Update


Recommended Posts

Hi, i'm new in this forum and use eset product for long years. Last day I formatted my pc with creator update iso, so i installed all my software include eis. But after a restart, eis doesn't boot and it completely block my pc. I use the uninstaller tool from recovery mode and after that i tried to figure out what the problem is. It took me some time but i managed to run eset. I noticed that eset, with the new creators update, has some problem with the windows module that determinate if an antivirus/firewall is installed. Infact when i reboot the pc the windows defender security center gives me an error that it can't start the malware module, after some time it recognizes eset and the error disappear. If i press the button that relaunch windows defender malware module it locks eset and block my pc like before unless, i deactivate the malware module and after that eset start again and the problem is fixed. The real problem is that with a fresh install if i install eset and reboot the pc, it can be possible that the pc will block because of this problem and for unskilled user it's a really big problem. Thank you and sorry for my english.

Link to comment
Share on other sites

  • Administrators

It sounds like an issue with your Windows 10 Security Center. ESET products have been tested with Creator Update and users haven't reported issues like this either. With ESET installed, Defender can activate automatically only after license expiration when the product reports as outdated.

Link to comment
Share on other sites

6 minutes ago, Marcos said:

It sounds like an issue with your Windows 10 Security Center. ESET products have been tested with Creator Update and users haven't reported issues like this either. With ESET installed, Defender can activate automatically only after license expiration when the product reports as outdated.

Ok, infact it happens at first install. I tried with another pc of mine after creator update. I think the problem is that at the first install, after insert activation code, eset update itself for the first time, and after that it can't deactivate the windows defender module well (it runs my cpu to 60%) and also i can't stop the first scan, because it's block everything. I managed to run it deactivating windows defender and after a reboot it's running well. I know it's strange, but also with the other computer i did the same things, Install OS, Install drivers; Install Eset (before install other applications) and i had the same issue until i fix like this, because if i don't turn off windows defender in the first reboot it's completely lock my pcs. May be other people doesn't have this problem but because i had with not just one, but two pcs i think it's good to report the problem i had. Thank you :).

Link to comment
Share on other sites

  • 3 weeks later...

My PC has also updated with Windows 10 Creator a few days ago. I am now finding, on running a scan with Eset, I am being told "No threats found" but the log shows "Error Opening [4]" on every folder.

Anyone have any idea what the problem is. My computer is operating fine otherwise.

I'm using a Lenovo Ideacentre.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...