Jump to content



Photo

Windows Defender


  • Please log in to reply
8 replies to this topic

#1 ManMountain

ManMountain

    Neowinian

  • Joined: 01-November 01
  • Location: Scotland
  • OS: Windows 8.1 Pro MC x64
  • Phone: LG Nexus 5

Posted 10 March 2013 - 09:53

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:

Posted Image

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?


#2 Buendia

Buendia

    Neowinian

  • Joined: 09-February 09

Posted 10 March 2013 - 10:48

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

#3 OP ManMountain

ManMountain

    Neowinian

  • Joined: 01-November 01
  • Location: Scotland
  • OS: Windows 8.1 Pro MC x64
  • Phone: LG Nexus 5

Posted 10 March 2013 - 11:01

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.

#4 Buendia

Buendia

    Neowinian

  • Joined: 09-February 09

Posted 10 March 2013 - 12:52

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

#5 gkl

gkl

    Neowinian

  • Joined: 04-August 05
  • Location: Latvia

Posted 10 March 2013 - 13:16

I seem to have the exact same problem. :/

#6 OP ManMountain

ManMountain

    Neowinian

  • Joined: 01-November 01
  • Location: Scotland
  • OS: Windows 8.1 Pro MC x64
  • Phone: LG Nexus 5

Posted 10 March 2013 - 13:23

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...itions/adl.aspx

#7 wahoospa

wahoospa

    Neowinian

  • Joined: 05-July 07
  • Location: South Carolina

Posted 10 March 2013 - 13:52

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

#8 OP ManMountain

ManMountain

    Neowinian

  • Joined: 01-November 01
  • Location: Scotland
  • OS: Windows 8.1 Pro MC x64
  • Phone: LG Nexus 5

Posted 10 March 2013 - 13:57

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.

#9 +-T-

-T-

    Trapmaster

  • Tech Issues Solved: 1
  • Joined: 03-December 01
  • Location: Western Australia & Scotland

Posted 10 March 2013 - 14:26

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

Thanks OP