tmuster2k 22 Posted October 5, 2017 Share Posted October 5, 2017 Just tried to help customer recover system because new build of 6.6.2052 crashed system. Tech was testing this build on his laptop which had 6.5 previous. He is on the Windows 10 Spring Creators update of 1703. The install failed with 1603 Error code. After reboot it now is in startup repair loop.Used a WINPE disk to manually remove ESET drivers from windows/system32/drivers and confirmed ESET Security is not present in program files. Also used WINPE to remove ESET registry items. Rebooted system and same. No safemode options are working either. I even had him run through process of going into recovery console command prompt to move REGBACKUP to config but same. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,259 Posted October 5, 2017 Administrators Share Posted October 5, 2017 By "crashed system" do you mean BSOD? If so, we'd need to get a kernel or better complete memory dump from the crash to determine the cause and to confirm or deny that it was caused by ESET. At the moment I'm not aware of any recent crashes caused by ESET. Link to comment Share on other sites More sharing options...
tmuster2k 22 Posted October 9, 2017 Author Share Posted October 9, 2017 was not able to get dump as tech was ok with re-image of machine. Have not had anymore come in so hope it was a 1 off. Link to comment Share on other sites More sharing options...
Recommended Posts