Definition Update for Windows Defender - KB2267602 (Definition 1.213.5087.0) - Error 0x80070643

I’m not really sure why this discussion is being up-voted like it is, but judging from the vote count, it must be mtcdnp’s report that the troubleshooter doesn’t work that’s responsible for generating all the enthusiasm. Of course I didn’t really want to spoil the party by finding something that actually does work, but I did just happen to stumble upon a method that appears to fix this problem completely, and in a heck of a hurry – without ever having to touch the registry or use some external download to do the dirty work for you.

I had just reproduced this issue for a third time in order to confirm that Windows Defender would actually start up if Avast was disabled, since this would allow Windows 8.1 users to turn off Windows Defender in the Settings tab and thus resolve the issue.

After reproducing the issue, I disabled the Avast shields “permanently” with the Avast shields control (right-click on the Avast icon, and select Avast shields control > Disable permanently), and I found that this did in fact allow me to turn on Defender.

Then I just left Windows Defender turned on and went back and enabled all of the Avast shields with the shields control – and this turned off Windows Defender as expected. But when I closed the Windows Defender UI and then tried to reopen it, I got the familiar “This app has been turned off and isn’t monitoring your computer” message. That message normally means that Windows Defender has been properly disabled. So I checked the registry, and sure enough, the DisableAntiSpyware and DisableAntiVirusDWORDs actually had been updated to the proper value of 1.

Then it suddenly dawned on me that I had just inadvertently replicated the fix proposed by hughie55 in the following windows discussion thread – but in a highly condensed form that didn’t even require rebooting between steps:

http://answers.microsoft.com/en-us/windows/forum/windows\_10-update/definition-update-for-windows-defender-kb2267602/d4edd314-a438-4ac2-b7a9-dc1c45a1ef62

So now I’m fairly confident that we might be able to generalize this uber-simple fix to some other AV products as well. In my case, I was able to just turn off the third-party AV app (Avast Free); start Windows Defender; and then turn the third-party app back on while Windows Defender was still turned on. But in other cases, you might need to repeat this procedure a couple of times, or maybe reboot between steps. Anyhow, people who aren't really dead set on waiting for Microsoft to fix this issue might want to just go ahead and give this fix a try.

GreginMich

Hey JJ,

You ARE THE MAN!!!

Thanks Worked for me!

AK

Thanks for the feedback, André Kennedy. This really isn’t a Windows Update issue, as the OP quickly discovered. It’s just a case where Windows Defender doesn't get switched off in the registry when the third-party AV app is installed. So you have to either reinstall the third-party app; use the shortcut method that I’ve described above; or turn Defender off in Group Policy. People with the Home edition of Windows 10 can just download and run the Turn_Off_Windows_Defender.reg  file to disable Windows Defender in the Group Policy registry key:

http://www.tenforums.com/tutorials/5918-windows-defender-turn-off-windows-10-a.html

GreginMich

Sau khi tải windows update troubleshooter và sửa lỗi thì tôi đã thành công. Cám ơn rất nhiều.

Bing translation:

After downloading the windows update troubleshooter fixes and then I was successful. Thank you very much.