ManMountain Posted March 10, 2013 Share Posted March 10, 2013 Since March 9th, on my Windows 8 x64 Pro Media Center install, Windows Defender has been unable to complete any scans here. It returns an error code 0x800106ba showing the following screen: It would appear I am not alone in experiencing this issue: http://answers.micro...9e-47bdfe3d2c0b http://answers.micro...663a3e47?page=1 http://answers.micro...9f-6c19d12a3a30 http://answers.micro...84-e18dd78d634a I have installed NOD32 and done a complete scan, my system is not infected in any way. I just wondered if any fellow Neowinians are also affected by what appears to be either a software glitch in Windows Defender or in one of it's definition updates to cause this issue? Link to comment Share on other sites More sharing options...
Buendia Posted March 10, 2013 Share Posted March 10, 2013 I presume that you checked services.msc and the Defender service is enabled and running? Link to comment Share on other sites More sharing options...
ManMountain Posted March 10, 2013 Author Share Posted March 10, 2013 The service is set as automatic, it's enabled and running. The issue is that no matter which scan type I select, approximately when 90% complete through scan, I will get the error that the service has stopped. Link to comment Share on other sites More sharing options...
Buendia Posted March 10, 2013 Share Posted March 10, 2013 Click on Support Information button, I think it should provide error codes which you can google. Link to comment Share on other sites More sharing options...
gkl Posted March 10, 2013 Share Posted March 10, 2013 I seem to have the exact same problem. :/ Link to comment Share on other sites More sharing options...
ManMountain Posted March 10, 2013 Author Share Posted March 10, 2013 Microsoft have released a definition update which fixes the problem. It will roll out via Windows update soon or you can grab the latest definition from here http://www.microsoft.com/security/portal/definitions/adl.aspx AndyAmo and -T- 2 Share Link to comment Share on other sites More sharing options...
wahoospa Posted March 10, 2013 Share Posted March 10, 2013 I thought you had to re-register DLL's to correct the problem. Link to comment Share on other sites More sharing options...
ManMountain Posted March 10, 2013 Author Share Posted March 10, 2013 No, it would appear that a definition update released on the 8th/9th broke Defender and all scans thereafter would fail. Applying the latest definition fixes it and it's working perfectly again. goretsky 1 Share Link to comment Share on other sites More sharing options...
-T- Member Posted March 10, 2013 Member Share Posted March 10, 2013 Well that saves me from pulling my hair out, as this was bothering me recently Thanks OP Link to comment Share on other sites More sharing options...
Recommended Posts