kb935807

[aptlinc1]

You can click help for this failed update and follow the steps for clearing
the software distribution and download caches after stopping windows update.
After clearing the caches start windows update.
Then go to
http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=KB935807&DisplayLang=en
and click run it on your computer.
Restart your computer.

On the start menu click windows update. On the left click update history and
it will tell you that kb935807 has installed succesfully.

However, windows update will still tell you that you still need this update.

My feeling is that it has updated but because it wasn't updated by the
normal windows update method in Vista it doesn't get catalogued in those
floders.

Maybe that glitch can also be fixed when they fix this update glitch.

 

[Robert Aldwinckle]

"aptlinc1" <aptlinc1@discussions.microsoft.com> wrote in message
news:4BB78D0D-46B2-496B-8EEF-88140E2CDFAE@microsoft.com...
> You can click help for this failed update and follow the steps for clearing
> the software distribution and download caches after stopping windows update.
> After clearing the caches start windows update.
> Then go to
> http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=KB935807&DisplayLang=en
> and click run it on your computer.
> Restart your computer.
>
> On the start menu click windows update. On the left click update history and
> it will tell you that kb935807 has installed succesfully.
>
> However, windows update will still tell you that you still need this update.
>
> My feeling is that it has updated but because it wasn't updated by the
> normal windows update method in Vista it doesn't get catalogued in those
> floders.


Instead of speculating try some analysis.

E.g. you can get the list of modules involved in the update from here:

http://www.microsoft.com/technet/security/bulletin/ms07-038.mspx

(Hint: Expand down to the File Information bullet.)

Next, when you run the update are you getting a request to reboot?
Then there is a subset of those modules which are currently in use
and have to be copied (or copies of them renamed) during a boot.
You can get a list of those by finding a registry value called
PendingFileRenameOperations
just before allowing the reboot. You may also be able to find even
more detailed clues about the same modules in the Event Viewer's
Application log.

Do you have any third-party security packages installed?
Are they active? More significantly will they be active when you reboot?
Then perhaps they will try to inhibit the copy/rename procedure,
(e.g. protecting you from a Trojan trying to install itself)?
You know that you don't want that "protection" so disable it.
BTW if this is in fact what has been happening I would appreciate
knowing if the security package logs (or could log) its activities.


>
> Maybe that glitch can also be fixed when they fix this update glitch.


I doubt there is a "glitch". I think the real problem is documenting
how to do updates carefully so they can be done successfully.


HTH

Robert Aldwinckle
---