(interleaved reply)
"Klintus Fang" <Klintus
> wrote in message
news

F744905-CCFA-4E1E-BE42-...
> curiously. I also have vista ultimate 64-bit and I am also having a problem
> with these same three updates.
>
> but for me. windows update simply fails to install them every time it
> tries.
> it gives me a different error code for each one
Please start new threads for new symptoms
and avoid confusing your problems with others' old ones.
> and tells me to search for information on the error code,
> but there is no record anywhere in the available information
> explaining what these error codes mean.
>
> KB955020: Error Code: 80070570
> KB951978: Error Code: 8007370B
> KB952709: Error Code: 8007370B
>
>
> It seems the error for me is that windows update is failing to download
> these three updates. It doesn't SAY that it failed to download the updates,
> but each time I try to download and install them the download % never goes
> above 0%.
What specific symptoms are you using to make your assumption?
Use the WindowsUpdate.log to find out for sure. (Ref KB902093)
BTW if it looks as if you *have* downloaded these updates and
these codes are actually associated with _install_ attempts you
can also try searching your harddrive for diagnostics created by
the install attempts.
Tip: in addition to the hex codes search for the decimal equivalents
of the last half. Sometimes you can even get an independent clue
from that by assuming that that decimal number represents a system
error message. To test that idea you could use a cmd window and
enter a net helpmsg command. Using your first code and my OS
as an example:
<cmd_output OS="XPsp2">
E:\>set /a c = 0x570
1392
E:\>net helpmsg %c%
The file or directory is corrupted and unreadable.
</cmd_output>
Is that what that code shows in your OS too?
If so, you can see that you would still need to find
the context of where it appears in some other diagnostic
to have any hope of knowing *which* file or directory
was being referred to.
Tip: if the problem appears to be happening during an install
you can eliminate WU/AU entirely from the scenario by
downloading and trying to install the update manually.
In that case, you may get more knowledgeable assistance
with whatever problems you encounter on that tack
by posting to a newsgroup which specializes in whatever
product the update is for. Also, on that tack it is usually
much easier to enable verbose logging which can help
your diagnosis wherever you report it. Another possibility
for supplementing any diagnostics is running ProcMon
and correlating its trace with whatever diagnostics you
do find.
>
> On a possibly unrelated path, I have been getting system hangs lately.
> Where the machine just completely freezes. With no blue screen or error
> message in the system log. The only pattern to my system freezes is that
> they always occur a few seconds after Windows Defender reports to the System
> Log that it is about to start an AntiSpyWare scan.
Again, this seems unrelated to WU/AU so you're more likely
to find more knowledgeable assistance in another newsgroup
which specializes in your OS.
HTH
Robert Aldwinckle
---