Post Service Pack 2 Updates

I have been trying to get a machine to install post WinXP SP2 updates.
Service Pack 2 has been installed successfully, however all the updates that
have come out since refuse to install, either from the Windows Update site,
or by running them manually. Manual installation simply returns an error of
"The system cannot find the path specified" after Agreeing with the licensing
terms. This error is logged the same in Event Viewer Event ID 4373.

I've had a flick through the registry to see if there's anything obvious,
there isn't. And looking back through the Event Log the problem seems to have
existed for some weeks. Possibly since SP2 installation. At present the only
method of cure would seem to be a format and re-load.

Unfortunately the error messaging isn't very intuitive, and is rather
generic, it's clears what's wrong, but not clear, why and how to rectify it.
Web searches have revealed zip because of the generic nature of the error
message. Hence I ended up here...

"SmokeyMcPotHead" <> wrote in message
news:C928BD25-7FC8-4679-9914-...
>I have been trying to get a machine to install post WinXP SP2 updates.
> Service Pack 2 has been installed successfully, however all the updates that
> have come out since refuse to install, either from the Windows Update site,
> or by running them manually. Manual installation simply returns an error of
> "The system cannot find the path specified" after Agreeing with the licensing
> terms. This error is logged the same in Event Viewer Event ID 4373.


Does the Event Viewer show you the problem path?
Does it show up in any of the WU logs?
If not, I'd try using FileMon (from SysInternals)
to see if that problem appears any clearer.
(It certainly helps illuminate the summary messages
you get in the logs. <g>)

Tip: in order to break up the FileMon log what I would do is
activate maximum prompting in the security zone that you are using.
Another advantage to doing that is you can see clues about the
processing in the Status bar which you might otherwise miss
(because they occur too quickly). That also could help refine
your symptom description.


Good luck

Robert Aldwinckle
---


>
> I've had a flick through the registry to see if there's anything obvious,
> there isn't. And looking back through the Event Log the problem seems to have
> existed for some weeks. Possibly since SP2 installation. At present the only
> method of cure would seem to be a format and re-load.
>
> Unfortunately the error messaging isn't very intuitive, and is rather
> generic, it's clears what's wrong, but not clear, why and how to rectify it.
> Web searches have revealed zip because of the generic nature of the error
> message. Hence I ended up here...