Sign in to follow this  
Followers 0

Windows Defender

9 posts in this topic

Posted

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:

2dl34i.jpg

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?

Share this post


Link to post
Share on other sites

Posted

I presume that you checked services.msc and the Defender service is enabled and running?

Share this post


Link to post
Share on other sites

Posted

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.

Share this post


Link to post
Share on other sites

Posted

Click on Support Information button, I think it should provide error codes which you can google.

Share this post


Link to post
Share on other sites

Posted

I seem to have the exact same problem. :/

Share this post


Link to post
Share on other sites

Posted

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

2 people like this

Share this post


Link to post
Share on other sites

Posted

I thought you had to re-register DLL's to correct the problem.

Share this post


Link to post
Share on other sites

Posted

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.

1 person likes this

Share this post


Link to post
Share on other sites

Posted

Well that saves me from pulling my hair out, as this was bothering me recently

Thanks OP

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.