Re: Update for Windows Vista (KB938371) error code 80070057

"Rob" <robleblanc@live.com> wrote in message
news:79C72A69-66DD-4CB3-891C-1F308E023B4E@microsoft.com...

>

>> What a useless article--no deployment or file info.

>
> I suppose if I knew everything there was to know about windows updates I
> would already know how to
> solve this problem wouldn't I?

That was an editorial comment on the quality of that article, in particular its usefulness
for troubleshooting problems with installing its update, not a complaint about you citing it. ; )

>

>> Does it have an option for verbose logging? E.g. try starting it with
>> /? to list
>> your deployment options or just guess that /verbose will work.

>
> No the standalone update does not have that option

Did you try /verbose anyway? Or just -V ?
BTW what kind of update is it? If it's .msi you would try /L*vx KB938371_Verbose.log

>

>> Searched for what? There are numerous discussions which mention this
>> update.
>> Most seem to involve error code 0x80073712.

>
> Well since I don't know what this error code is I searched for something
> like "Windows Update KB938371 error 80070057"
> and variations of that. What else should I have searched for. Why would I
> pay attention to error code 0x80073712 when it is not
> the same as 80070057?

As I indicated if you had searched for just the update name and perhaps filtered
for answered posts by appending MVP you would have found whatever the suggestions
have been for that other code. Nobody knows much about it either, so you could apply
whatever suggestions were given for collecting diagnostics from those.

BTW that error code is really a hex string (even though in this particular case it might look like
a decimal number). In general you will find that there are more instances of error codes prefixed
by 0x than not. Also, adding "Windows Update" to your search is not likely to improve your
search results, at least in here. For example, in here it would be implicit or when mentioned at all
it would just as likely be referred to as WU or AU.

So I would try two searches: 0x80070057 MVP
and KB938371 MVP

>

>> This error code is even less descriptive:
>>
>> <cmd_output OS="XPsp2">
>> E:\>set /a c= 0x57
>> 87
>> E:\>net helpmsg %c%
>>
>> The parameter is incorrect.
>> </cmd_output>

>
> ^^^What does this even mean?^^^

That's the point. Not much. ; )

>
> I scanned the Windowsupdate.log file:
>
> * Update is not allowed to download due to regulation.
> 2008-03-18 16:34:12:863 992 a4c DnldMgr Regulation:
> {7971F918-A847-4430-9279-4A52D1EFE18D} - Update
> 8587921A-242E-466E-8600-B15C6792EB30 is "PerUpdate" regulated and can NOT
> download. Sequence 9334 vs AcceptRate 0.
> .
> .
> .
> 2008-03-18 16:34:54:082 992 a4c Agent ** END ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2008-03-18 16:34:54:082 992 a4c Agent *************
> 2008-03-18 16:34:54:082 992 a4c Report REPORT EVENT:
> {E75D6A21-22DA-4FF6-B2AD-5588ECD7E165} 2008-03-18 16:34:12:832-0600 1 182101 {3AFB21E2-E01E-49C7-A558-54CA0001F9DA} 501 80070057
> wusa Failure ContentInstall Installation Failure: Windows failed to install the following update
> with error 0x80070057: Update for Windows (KB938371).
>
> I certainly don't know what that means but maybe that puts it into context.

Indeed. The first message "PerUpdate" regulated and can NOT download." tells you that the server
is busy and you won't be able to get the update yet. I guess the message and code that you are reporting
is just a symptom of not being able to handle that event very cleanly.


But you implied that you downloaded the update, ran it manually and had a problem?
With what symptom? Hint: it would not be something in the WindowsUpdate.log
Look for the diagnostics from that attempt. E.g. search your drives for any files which
it changed that day; then sort them by Date Modified. That actually sorts them by Timestamp
as well, so then all you have to do is scroll to the time the update was run and see from the
files which were changed which ones are readable. E.g. drag them to an open Notepad window.


Good luck

Robert
---