Jump to content

Recommended Posts

Posted

I have just upgraded to Windows 10 Build 1607 (Anniversary Update). While upgrade edevmon.sys was creating BSODs so I removed ESET and upgraded to Build 1607. But when I tried to install it again, (using installer downloaded via eset official site) crashes started all over again. I was forced to uninstall ESET to get system running all over again.

I am getting SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error.

Caused by: edevmon.sys

 

I am attaching screenshot that gives more detail about error.

 

Kindly help, so that I can again start using ESET.

post-13237-0-94070800-1470666949_thumb.png

  • Administrators
Posted

I'm afraid that a minidump won't help. We'd need to get at least a kernel or better complete memory dump from BSOD. BSOD would occur on system startup if edevmon is registered in the system but the actual driver file does not exist on a disk.

  • 4 weeks later...
Posted

Same problem with 1067 and Eset Andpoint Antivirus for Business 6.4.2014.2

If we activate the media controll (USB controll) -> do a restart -> bluescreen with same driver.

 

Please fix.

Posted (edited)

I don't know if ESET is causing this but I have a problem with the 1067 update now for a week or so.  Update loads up but will not or can not install them.  Kind of holds my computer hostage as it keeps uploading but not installing.  KOR-

 

Adding:  My Wi-Fi connection is also dropping and perhaps because of Windows trying to update.  Don't know but thought I would mention it.  KOR-

Edited by KOR
Posted

Hi Kor im running win 10 x64 same build no with eset smart security 9 for few weeks now with no problems. 

  • Administrators
Posted

Open the Windows features setup and temporarily disable Hyper-V.

Posted

Hey Marcos.  I can't seem to find the Hyper-V in Windows features.  I will keep looking.  KOR-

Posted

It does not seem to be there.  Looked and typed the Hyper-V and it states not found.  KOR-

Posted

It is in Control Panel > Programs & Features > Turn Windows Features on/off.

This is on Win 10 Pro. Maybe Home doesn't have it ?

Posted

Right, it is NOT in Win 10 Home.  KOR-

Posted

Hey Chevrolet, are you saying you took ESET V9 off and you are getting Windows updates with no problems?  KOR-

Posted

Yes i have installed updates just fine with eset smart security 9 installed and without installed no problems

Posted

You may have disabled a required windows update service in services. Restore services to defaults and have another try and rule out what you need and dont in services

Posted

Blackviper site has win 10 service configurations so you know what to set as, his tweaked version of config will also update fine from microsoft if you want to use that for a bit of extra proformance.

Posted

If eset is uninstalled and you are blocked also check windows firewall rules for svchost.exe. it will be needed to access the net to get updates so make sure its not blocked or something

Posted

In automatic firewall mode eset will allow svchost.exe to access win update without you doing anything. If your in intractive mode allow svchost.exe

  • Administrators
Posted

The best would be if you could configure the OS to generate complete memory dumps and then reproduce the crash. The only known crash on Windows 10 AU is caused by changes made to AU and occurs after enabling Device Control provided that a Hyper-V service is running. This will be addressed in future builds.

  • 2 weeks later...
Posted

After the windows 10 anniversary update, every time I insert a USB flash drive, the computer crashes.

Extremely frustrating

  • Administrators
Posted

Please configure Windows to generate complete memory dumps and reproduce the crash. When done, compress the dump, upload it to a safe location and pm me the download link. The only known BSOD on Windows 10 are caused by changes in Windows 10 AU when a Hyper-V service is running.

Posted

The best would be if you could configure the OS to generate complete memory dumps and then reproduce the crash. The only known crash on Windows 10 AU is caused by changes made to AU and occurs after enabling Device Control provided that a Hyper-V service is running. This will be addressed in future builds.

Hello,

 

Yes, after disabling device control, ESET is running fine. Waiting for this bug to be fixed. Thanks!!!

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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