Problems with 0x800A01AD in SP2

I'm having similiar problems as others. I installed WinXP SP2 and now Windows
Update gives me 0x800A01AD. I tried Lucy's fixes and got the below errors
when using REGSVR32. Any ideas? Turning off AV software (Trend Micro) doesn't
help, neither do reboots or restarting Windows Update in Services.

Thanks,

Tim

"Lucy [MSFT]" wrote:

> Hello,
>
> Thanks for posting the log file. It looks like the required service
> "Automatic Update" is failing to start. Let's verify. Please register the
> following Files:
>
> Click Start > Run > Type the follow commands in the Open box (one at a time,
> in sequence):
>
> REGSVR32 C:\WINDOWS\system32\wuapi.dll

DllRegisterServer in c:\windows\system32\wuapi.dll failed.
Return code was "0x80070005

> REGSVR32 C:\WINDOWS\system32\wuauclt.exe

C:\WINDOWS\system32\wuauclt.exe was loaded, but the DllRegisterServer entry
point was not found.
C:\WINDOWS\system32\wuauclt.exe does not appear to be a .DLL or .OCX file.

> REGSVR32 C:\WINDOWS\system32\wuaueng.dll

Works fine

> REGSVR32 C:\WINDOWS\system32\wucltui.dll

Works fine

> REGSVR32 C:\WINDOWS\system32\wups.dll

Works fine
>
> Any errors registering any of the files? If so, please post the error
> message
>
> Next, try Stopping and Restarting the Automatic Update service
>
> Click Start >Run
> Type "Services.msc" (w/o quotes)
> Press OK
> Find "Automatic Update"
> Stop and restart the service.
>
> Do you get an error message?
>
>
> Thanks,
> Lucy [MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.

Also, registering MSXML.dll, MSXML2.dll, MSXML3.dll didn't work. And I
downloaded the MSXML Parser 3.0 SP4 and it didn't help either.

Thanks

"tim_darklighter" wrote:

> I'm having similiar problems as others. I installed WinXP SP2 and now Windows
> Update gives me 0x800A01AD. I tried Lucy's fixes and got the below errors
> when using REGSVR32. Any ideas? Turning off AV software (Trend Micro) doesn't
> help, neither do reboots or restarting Windows Update in Services.
>
> Thanks,
>
> Tim
>
> "Lucy [MSFT]" wrote:
>
> > Hello,
> >
> > Thanks for posting the log file. It looks like the required service
> > "Automatic Update" is failing to start. Let's verify. Please register the
> > following Files:
> >
> > Click Start > Run > Type the follow commands in the Open box (one at a time,
> > in sequence):
> >
> > REGSVR32 C:\WINDOWS\system32\wuapi.dll
>
> DllRegisterServer in c:\windows\system32\wuapi.dll failed.
> Return code was "0x80070005
>
> > REGSVR32 C:\WINDOWS\system32\wuauclt.exe
>
> C:\WINDOWS\system32\wuauclt.exe was loaded, but the DllRegisterServer entry
> point was not found.
> C:\WINDOWS\system32\wuauclt.exe does not appear to be a .DLL or .OCX file.
>
> > REGSVR32 C:\WINDOWS\system32\wuaueng.dll
>
> Works fine
>
> > REGSVR32 C:\WINDOWS\system32\wucltui.dll
>
> Works fine
>
> > REGSVR32 C:\WINDOWS\system32\wups.dll
>
> Works fine
> >
> > Any errors registering any of the files? If so, please post the error
> > message
> >
> > Next, try Stopping and Restarting the Automatic Update service
> >
> > Click Start >Run
> > Type "Services.msc" (w/o quotes)
> > Press OK
> > Find "Automatic Update"
> > Stop and restart the service.
> >
> > Do you get an error message?
> >
> >
> > Thanks,
> > Lucy [MSFT]
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
>

Tim,

Unless you give us any details all we can do is take stabs at solutions
which have solved incidents which included this symptom in the past.

A long time ago another poster discovered (for who knows what reason)
that he could avoid it after clearing his TIF. ;o

Here's a Google Groups search which may help you if you would prefer
to stay on that tack.

<
http://groups.google.com/groups?q=80...UTF-8&c2coff=1 >

Note that you could also click on Sort by date. That would get you closer
to current thinking about a particular symptom but then you might have to
wade through several redundant or incomplete threads to find unique
and successful ideas.


Good luck

Robert Aldwinckle
---


"tim_darklighter" <> wrote in message
news:E6A2B4EA-C493-4BCA-B398-...
> Also, registering MSXML.dll, MSXML2.dll, MSXML3.dll didn't work. And I
> downloaded the MSXML Parser 3.0 SP4 and it didn't help either.
>
> Thanks
>
> "tim_darklighter" wrote:
>
>> I'm having similiar problems as others. I installed WinXP SP2 and now Windows
>> Update gives me 0x800A01AD. I tried Lucy's fixes and got the below errors
>> when using REGSVR32. Any ideas? Turning off AV software (Trend Micro) doesn't
>> help, neither do reboots or restarting Windows Update in Services.
>>
>> Thanks,
>>
>> Tim
>>
>> "Lucy [MSFT]" wrote:
>>
>> > Hello,
>> >
>> > Thanks for posting the log file. It looks like the required service
>> > "Automatic Update" is failing to start. Let's verify. Please register the
>> > following Files:
>> >
>> > Click Start > Run > Type the follow commands in the Open box (one at a time,
>> > in sequence):
>> >
>> > REGSVR32 C:\WINDOWS\system32\wuapi.dll
>>
>> DllRegisterServer in c:\windows\system32\wuapi.dll failed.
>> Return code was "0x80070005
>>
>> > REGSVR32 C:\WINDOWS\system32\wuauclt.exe
>>
>> C:\WINDOWS\system32\wuauclt.exe was loaded, but the DllRegisterServer entry
>> point was not found.
>> C:\WINDOWS\system32\wuauclt.exe does not appear to be a .DLL or .OCX file.
>>
>> > REGSVR32 C:\WINDOWS\system32\wuaueng.dll
>>
>> Works fine
>>
>> > REGSVR32 C:\WINDOWS\system32\wucltui.dll
>>
>> Works fine
>>
>> > REGSVR32 C:\WINDOWS\system32\wups.dll
>>
>> Works fine
>> >
>> > Any errors registering any of the files? If so, please post the error
>> > message
>> >
>> > Next, try Stopping and Restarting the Automatic Update service
>> >
>> > Click Start >Run
>> > Type "Services.msc" (w/o quotes)
>> > Press OK
>> > Find "Automatic Update"
>> > Stop and restart the service.
>> >
>> > Do you get an error message?
>> >
>> >
>> > Thanks,
>> > Lucy [MSFT]
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no rights.
>>

Robert -

Thanks for the Google groups. I'll start wading through those for ideas. As
far as details go, would appending the last 15 or so lines of my
WindowsUpdate.log help? Lucy seemed to be able to help Spaz with his problem
because he sent that to her.

I'm not sure what other details to give, but if any certain log files (or
the like) would help just ask. WU (v5) only gave out after installing SP2
(over WinXP Pro SP1). I can load up the WU website but upon clicking either
Express or Custom Install, it stalls for a minute or two and gives me the
error page. The support idea the website gives (editing WU permissions in
regedit for different users) didn't help.

I can only say that I've tried registering all of the MDXML.dll's, I've
tried registering the WUxxx.dll's, and I've tried turning off firewall and
antivirus software, and clearing my TIFs didn't help either. (These are the
common fixes that I've seen so far and have not worked in my case.)

Thanks,

Tim

"tim_darklighter" <> wrote in message
news:A540B218-21FF-4B27-B7BD-...
> Robert -
>
> Thanks for the Google groups. I'll start wading through those for ideas. As
> far as details go, would appending the last 15 or so lines of my
> WindowsUpdate.log help? Lucy seemed to be able to help Spaz with his problem
> because he sent that to her.

I think that capturing a context by timestamp makes more sense.
E.g. "so many lines" may truncate the start of a context.
It seems that V5 is much more verbose than V4 so I doubt that
its old rules of thumb will be as useful and suspect that even 20 lines
won't be sufficient any more as a minimum.

Also, the diagnostics seem to be spread out into more files.
My approach is to search for all changed files on the day the problem
occurred, then sort by Date Modified. Often there are more files with
readable clues than just those which have an extension of .log (e.g. .xml and .txt)


>
> I'm not sure what other details to give, but if any certain log files (or
> the like) would help just ask. WU (v5) only gave out after installing SP2
> (over WinXP Pro SP1). I can load up the WU website but upon clicking either
> Express or Custom Install, it stalls for a minute or two and gives me the
> error page. The support idea the website gives (editing WU permissions in
> regedit for different users) didn't help.

There seems to be a new technique which does not involve RegEdit
but instead involves a command-line tool called sc. (Enter sc /?
for syntax help with that.) If you have more than one machine you might
try queries with that tool on both systems to see if there were any
significant differences.


>
> I can only say that I've tried registering all of the MDXML.dll's, I've
> tried registering the WUxxx.dll's, and I've tried turning off firewall and
> antivirus software, and clearing my TIFs didn't help either. (These are the
> common fixes that I've seen so far and have not worked in my case.)

Notice that those suggestions were made to V4 users so the symptom
may imply something quite different now for V5 users.


>
> Thanks,
>
> Tim
>


Good luck

Robert
---

Robert -

Instead of going through the files and such manually, I just decided to
rollback SP2 until more people have installed it. Chances are someone else
will have the same symptoms as I have.

On a lighter note, WU on SP1 (still V5) works fine...

Thanks for all of the help,

Tim Hathway

"Robert Aldwinckle" wrote:

> "tim_darklighter" <> wrote in message
> news:A540B218-21FF-4B27-B7BD-...
> > Robert -
> >
> > Thanks for the Google groups. I'll start wading through those for ideas. As
> > far as details go, would appending the last 15 or so lines of my
> > WindowsUpdate.log help? Lucy seemed to be able to help Spaz with his problem
> > because he sent that to her.
>
> I think that capturing a context by timestamp makes more sense.
> E.g. "so many lines" may truncate the start of a context.
> It seems that V5 is much more verbose than V4 so I doubt that
> its old rules of thumb will be as useful and suspect that even 20 lines
> won't be sufficient any more as a minimum.
>
> Also, the diagnostics seem to be spread out into more files.
> My approach is to search for all changed files on the day the problem
> occurred, then sort by Date Modified. Often there are more files with
> readable clues than just those which have an extension of .log (e.g. .xml and .txt)
>
>
> >
> > I'm not sure what other details to give, but if any certain log files (or
> > the like) would help just ask. WU (v5) only gave out after installing SP2
> > (over WinXP Pro SP1). I can load up the WU website but upon clicking either
> > Express or Custom Install, it stalls for a minute or two and gives me the
> > error page. The support idea the website gives (editing WU permissions in
> > regedit for different users) didn't help.
>
> There seems to be a new technique which does not involve RegEdit
> but instead involves a command-line tool called sc. (Enter sc /?
> for syntax help with that.) If you have more than one machine you might
> try queries with that tool on both systems to see if there were any
> significant differences.
>
>
> >
> > I can only say that I've tried registering all of the MDXML.dll's, I've
> > tried registering the WUxxx.dll's, and I've tried turning off firewall and
> > antivirus software, and clearing my TIFs didn't help either. (These are the
> > common fixes that I've seen so far and have not worked in my case.)
>
> Notice that those suggestions were made to V4 users so the symptom
> may imply something quite different now for V5 users.
>
>
> >
> > Thanks,
> >
> > Tim
> >
>
>
> Good luck
>
> Robert
> ---
>
>
>