Hmm. With most updates, the thing I try in this situation is to 1)
uninstall the update, if it shows as installed, and 2) download the update
as a separate package and save it to the desktop, then run that. If that
fails, there is a log file which may be worth reading through to see if
there are clues to what failed.
OK - so I'm going here:
http://www.microsoft.com/downloads/...e0-e72d-4f54-9ab3-75b8eb148356&displaylang=en
OK - downloaded to the desktop, and double-clicked. It opens UI, and I
choose a quick scan--not enough time tonight for a full scan. As it runs, I
see that in %windir%\debug there are two text files open, mrt and mrteng.
OK - nothing found, exit the UI.
mrteng shows that I've run the June version of this file three times
now--once when it arrived via AU, once yesterday when I responded to your
message, and once tonight.
mrt shows that I've been running this product since May of 2005, and every
run has a return code of zero, which I suspect is good, but boring for the
antimalware folks.
Neither of these has install/uninstall stuff. I can't spot a log file
related to the MRT except those noted above.
OK: 1) does %windir%\debug exist, and can you create and delete files in
it?
2) can you delete %windir%\system32\mrt.exe ?
Having done that, can you run the download I linked to above--and does it
place the current version in that location? (and if that works, does the
looping update quit, perhaps after another iteration?)
This is all I can see to look for--perhaps there are registry entries
associated with this critter, but I don't have a reference to them handy.
Can you imagine any app or settings on your system, changed since second
Tuesday of May, that might prevent access to the above locations?
--