Problems with 1.35.706 update...

[fb0r]

Hi!

Running Windows Defender 1.1.1593.0 w/engine 1.1.3604.0 and definition
version 1.35.563.0.

I'm having problems with the latest Windows Defender update (1.35.716) here.

I get error code 0x80070643 in the WD GUI when trying to update definitions
from inside Defender.

Windows Update downloads work perfectly fine except for the Windows Defender
update. Defender update via Windows Update fails. Error code 0x80508007 from
its command line installer in the Windows Update log.

I've tried uninstalling and reinstalling Defender. Still no luck with the
latest update.

Tried rolling back to 1.0.0 definitions via "MpCmdRun -removedefinitions
-all" and then updating Defender from the WD GUI. Again fail. Same error code
as before, 0x80070643.

Tried downloading the manual installer for the 1.35.716 update. Fail upon
launch with no given error message. Installation simply halts after a brief
copying of files. Update not performed.

Tried booting into safe mode and using the manual 1.35.716 installer again.
Fail. No error message and no joy.

So I reverted to 1.0.0 definitions via command line again (MpCmdRun.exe) and
a manual install of the previous update (1.35.563) works perfectly fine! Very
interesting.



Beginning to run out of ideas as to what could be wrong. Cheers & thanks for
any new angles on it.

 

[JohnBurns]

I have the same problem - did you find an answer? t

 

[Spleen]

I have EXACTLY this problem too! But, having uninstalled and tried to
reinstall WD, I am now stuck at definitions 1.0000.

FbOr (or anyone else!!), how did you manually roll back to last weeks defs?

Thanks guys

 

[JohnBurns]

I would like to know how to roll back to last weeks defs also. However, for
now I am going to uninstall WD until Microsoft sees fit to fix this problem.

 

[Spleen]

Hi John

I really should learn to read Theres some fella who posts links to a
EXE files under the signatures sub-folder. Click on his thread for the defs
1.35.563.0 and run the .exe (or download it or whatever).

BOTTOM LINE - there seems to be a problem with the file itself.

 

[fb0r]

Correct. Look in the microsoft.private.security.spyware.signatures group, top
post.

Download the files in the first (signature v. 1.35.24.0 & engine v.
1.1.3604.0) and second link (signature v. 1.35.563) and install signature &
engine update first and then the incremental update to the 1.35.563
definitions.

And, no, still no luck sorting the problem out. Nearing midnight here so I
have no time to try out other solutions right now as I have work to do
tomorrow.

Hopefully it's just a problem with the definitions file and MS will have it
sorted soon.

/Cheers

 

[Bill Sanderson]

I'd recommend going to the security portal and getting the latest defs
there.

www.microsoft.com/security/portal

look on the right for Windows Defender definitions.

This is the best location for the latest possible definitions--if there is a
problem, the fix should be here first.

 

[John Navas]

I'd recommend going to the security portal and getting the latest defs
there.

www.microsoft.com/security/portal

look on the right for Windows Defender definitions.

This is the best location for the latest possible definitions--if there is a
problem, the fix should be here first.

It isn't there yet. The manual definition update also fails.

 

[fb0r]

Manual updater to version 1.35.745 is up for DL at Microsoft Malware
Protection Center as of this morning (local time) and installs fine. It's
probably going to be propagated to Windows Update soon.

Problem is now solved for me. Thanks!

/Cheers

 

[Joan Archer]

Problem solved for me now, just done the update and it's installed OK.