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

Thank you so much.

ayuda

plis

I can not update . I always get this message

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

after I have installed the Norton antivirus software

What shall I do ?

@ dirismaurice

This helped other users with the same issue:

Uninstall Norton with the help of the Norton Removal tool: https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

Reboot.

Then disable Windows Defender completely (select either option 1 or option 2, depending on your Windows edition), see: Windows Defender - Turn On or Off in Windows 10

And then reinstall your Norton product.

========

Also see http://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_start/error-0x80070643/fc94fa4c-ead9-4270-92b1-a75ca210089f

========

Later EDIT:

For users with other AV's, see these lists for the specific AV removal tools:

List of anti-malware product removal tools

Uninstallers (removal tools) for common Windows antivirus software

Just to be clear, although the original source of the fix that Jsssssssss is referring to involved a PC with Norton installed, this fix should be generally applicable. The latest reports of this issue have been with McAfee products.

http://answers.microsoft.com/en-us/protect/forum/protect\_defender-protect\_updating/definition-update-for-windows-defender-kb2267602/ee5a7851-9ff4-4c0b-a3c9-bbcb2ef2c8d0

http://answers.microsoft.com/en-us/protect/forum/protect\_defender-protect\_updating/definition-update-for-windows-defender-kb2267602/ee5a7851-9ff4-4c0b-a3c9-bbcb2ef2c8d0

The intermediate cause appears to be a failure to update the DisableAntiSpyware and DisableAntiVirusDWORD values in the Windows Defender registry key. When I reproduced this registry error state with Avast Free installed, I observed three errors – Error 0x8007139f when trying to start the service in the UI; Error 577 when trying to start the service in services.msc; and Error 0x80070643 with Defender's definition updates:

http://answers.microsoft.com/en-us/protect/forum/protect\_defender-protect\_start/windows-defender-error-code-0x8007139f/93096739-16ce-471b-8716-1776f0c69f89?page=2

The presence of the underlying error state can easily be confirmed just by running this registry query (copy, paste, and enter this line at the command prompt):

reg query "hklm\software\microsoft\windows defender" /v DisableAntispyware

If you have a third-party AV app installed, then the return value should be 0x1 (disabled True). In cases where 0x0 (disabled False) is returned, the value is incorrect. The essential fix would then be to uninstall the AV app, run the app’s cleanup tool, and then reinstall; which would hopefully disable Windows Defender by setting the DisableAntiSpyware and DisableAntiVirus DWORDs to the proper value of 1. But since there are reports of this failing to resolve the issue, the safest bet would be to use the combination fix cited by Jsssssssss.

However, on the test machine, setting the DisableAntiSpyware DWORD to the value of 1 in the Polices registry key (with the Ten Forums Turn_Off_Windows_Defender.reg  file) was sufficient to resolve the update issue and prevent the Defender UI from appearing, since this setting overrides the DisableAntiSpyware DWORD setting in the Windows Defender registry key. But this didn’t change the value of the corresponding DWORD in the Windows Defender key (the underlying issue) or resolve the Error 577 issue (on the test machine).

So whether the combination fix has any real advantage over the short fix would depend on whether it’s actually restoring the correct values to the DisableAntiSpyware and DisableAntiVirus DWORDs in the Windows Defender key and resolving the Error 577 issue. The point being that the outcomes of the combination fix and the short fix would be the same for casual observers; and that we would need to check the DWORD values in the Windows Defender key, and also check the status of the Windows Defender service with services.msc, in order to be sure that the combination fix was completely resolving the underlying issues.

GreginMich