Noticing a problem with updates on one of my pc's , Both are XP Home with
SP2 , the one thats working fine is fully patched the other thats having
problems has no patches (Only used for testing) , On the latter it showed a
0X8024400e error when attempting to update, After a Reboot it opens and
displays that it hasnt been updated for 20 days , If I click update it shows
there is no new definition or engine updates available.
Signature Version is 1.0.0.0 1/25/2006 at 7:29PM
Tried a repair install using the add/remove screen and it was still the same
when it restarted. The system tray icon is always present showing the WD icon
and the orange shield
If I open the definition folder:
C:\Documents and Settings\All Users\Application Data\Microsoft\Windows
Defender\Definition Updates\{E87CCCC9-697F-489C-8CF1-DAE7CBEC417F}
It has mpasbase.vdm and a size of 329 kb and then the mpasdlta.vdm with a
size of 9kb
The other machine has mpasbase.vdm at 1,510 kb and mpasdlta.vdm at 128kb
If I delete both mpasbase.vdm and mpasdlta.vdm from the pc thats having a
problem and also delete the same files from the backup folder which is
located in the same area it still shows that there is no updates available,
Copying the files from the working version to the other machine doesnt help
either, it still shows the original install signature version on the main
screen and displays the orange shield in the system tray, It looks like it
may need to update info in the registry as well as the definition files to
remove that alert and system tray icon.
I then deleted its WD Service using a command prompt but it really doesnt
like that as it will then not load giving a invalid handle error
Finally I
went to add/remove screen and performed a repair install again and its now
working and the system tray icon has gone.:
Old value: HKLM\SOFTWARE\Microsoft\Windows Defender\Signature
Updates\ASSignatureVersion = 1.0.0.0
New value: HKLM\SOFTWARE\Microsoft\Windows Defender\Signature
Updates\ASSignatureVersion = 1.13.1272.4
Not sure what step did the trick but will remove it and try again if I can
re-create the error, hopefully it provides some clues to the MS team about
what's causing it.
Andy