problem with Windows Update, not related to WGA

I support about 9 or 10 computers on a small LAN, all running XP Pro.
Two of the computers always fail to install updates. The updates
download but always fail with an error code that is never listed in
the KB.

The only thing unique about these two computers is that they were set
up to allow Symantec WinFax Pro fax sharing server to run and allow
connections from other clients to that service.

The modifications involved making some changes to the settings for
certain DCOM rights.

I even tried to update to WGA and that install failed and now the
computer is acting very strange with Explorer (shell) locking up and
other issues which may or may not be related to WGA failing to
install.

In addition, after the computer has been up for a day or so, maybe
less, there is a svchost listing in Task Manager that shows using
almost all available CPU and when I shut down Windows Update service,
that entry goes away. Something has the WU all bound up but I don't
know what.

I'd like to get information that would enable me to troubleshoot the
issue... I really need these two computers to get back on track with
updates, etc... when I download the updates and apply them manually,
they always work so it is just a problem with WU from what I can tell.

I'd appreciate any help...

>T G <> wrote:

>I support about 9 or 10 computers on a small LAN, all running XP Pro.
>Two of the computers always fail to install updates. The updates
>download but always fail with an error code that is never listed in
>the KB.
>
>The only thing unique about these two computers is that they were set
>up to allow Symantec WinFax Pro fax sharing server to run and allow
>connections from other clients to that service.
>
>The modifications involved making some changes to the settings for
>certain DCOM rights.
>
>I even tried to update to WGA and that install failed and now the
>computer is acting very strange with Explorer (shell) locking up and
>other issues which may or may not be related to WGA failing to
>install.
>
>In addition, after the computer has been up for a day or so, maybe
>less, there is a svchost listing in Task Manager that shows using
>almost all available CPU and when I shut down Windows Update service,
>that entry goes away. Something has the WU all bound up but I don't
>know what.
>
>I'd like to get information that would enable me to troubleshoot the
>issue... I really need these two computers to get back on track with
>updates, etc... when I download the updates and apply them manually,
>they always work so it is just a problem with WU from what I can tell.
>
>I'd appreciate any help...


in further researching the issue, I see errors such as "failed with hr
= 80200013" when WU tries to download the update.

I tried to install the WGA package and it downloaded fine but errored
right away during installation with:
2005-08-07 18:15:17 2860 b28 AUClnt FATAL: Error:
0x80070005. wuauclt handler: failed to spawn COM server
2005-08-07 18:15:18 3816 498 Handler FATAL:
0x80070005: ERROR: Remote update handler container process created
(PID: 2860), but exited before signaling event
2005-08-07 18:15:18 3816 498 Agent * WARNING:
Exit code = 0x80070005
2005-08-07 18:15:18 3816 498 Agent *********
2005-08-07 18:15:18 3816 498 Agent ** END **
Agent: Installing updates [CallerId = WindowsUpdate]
2005-08-07 18:15:18 3816 498 Agent *************
2005-08-07 18:15:18 3816 498 Agent WARNING: WU
client failed installing updates with error 0x80070005
2005-08-07 18:15:18 2916 d1c COMAPI >>-- RESUMED
-- COMAPI: Install [ClientId = WindowsUpdate]
2005-08-07 18:15:18 2916 d1c COMAPI - Install
call failed
2005-08-07 18:15:18 2916 d1c COMAPI - Reboot
required = No
2005-08-07 18:15:18 2916 d1c COMAPI - WARNING:
Exit code = 0x80240FFF; Call error code = 0x80070005

Does this provide any information that would be helpful?

>T G <> wrote:

>
>>T G <> wrote:
>
>>I support about 9 or 10 computers on a small LAN, all running XP Pro.
>>Two of the computers always fail to install updates. The updates
>>download but always fail with an error code that is never listed in
>>the KB.
>>
>>The only thing unique about these two computers is that they were set
>>up to allow Symantec WinFax Pro fax sharing server to run and allow
>>connections from other clients to that service.
>>
>>The modifications involved making some changes to the settings for
>>certain DCOM rights.
>>
>>I even tried to update to WGA and that install failed and now the
>>computer is acting very strange with Explorer (shell) locking up and
>>other issues which may or may not be related to WGA failing to
>>install.
>>
>>In addition, after the computer has been up for a day or so, maybe
>>less, there is a svchost listing in Task Manager that shows using
>>almost all available CPU and when I shut down Windows Update service,
>>that entry goes away. Something has the WU all bound up but I don't
>>know what.
>>
>>I'd like to get information that would enable me to troubleshoot the
>>issue... I really need these two computers to get back on track with
>>updates, etc... when I download the updates and apply them manually,
>>they always work so it is just a problem with WU from what I can tell.
>>
>>I'd appreciate any help...
>
>
>in further researching the issue, I see errors such as "failed with hr
>= 80200013" when WU tries to download the update.
>
>I tried to install the WGA package and it downloaded fine but errored
>right away during installation with:
>2005-08-07 18:15:17 2860 b28 AUClnt FATAL: Error:
>0x80070005. wuauclt handler: failed to spawn COM server
>2005-08-07 18:15:18 3816 498 Handler FATAL:
>0x80070005: ERROR: Remote update handler container process created
>(PID: 2860), but exited before signaling event
>2005-08-07 18:15:18 3816 498 Agent * WARNING:
>Exit code = 0x80070005
>2005-08-07 18:15:18 3816 498 Agent *********
>2005-08-07 18:15:18 3816 498 Agent ** END **
>Agent: Installing updates [CallerId = WindowsUpdate]
>2005-08-07 18:15:18 3816 498 Agent *************
>2005-08-07 18:15:18 3816 498 Agent WARNING: WU
>client failed installing updates with error 0x80070005
>2005-08-07 18:15:18 2916 d1c COMAPI >>-- RESUMED
>-- COMAPI: Install [ClientId = WindowsUpdate]
>2005-08-07 18:15:18 2916 d1c COMAPI - Install
>call failed
>2005-08-07 18:15:18 2916 d1c COMAPI - Reboot
>required = No
>2005-08-07 18:15:18 2916 d1c COMAPI - WARNING:
>Exit code = 0x80240FFF; Call error code = 0x80070005
>
>Does this provide any information that would be helpful?

No one has any suggestions or ideas about this issue? I'd really
appreciate any ideas...

On Sun, 07 Aug 2005 16:59:47 -0400, T G <> wrote:

>I support about 9 or 10 computers on a small LAN, all running XP Pro.
>Two of the computers always fail to install updates. The updates
>download but always fail with an error code that is never listed in
>the KB.
>
>The only thing unique about these two computers is that they were set
>up to allow Symantec WinFax Pro fax sharing server to run and allow
>connections from other clients to that service.
>
>The modifications involved making some changes to the settings for
>certain DCOM rights.
>
>I even tried to update to WGA and that install failed and now the
>computer is acting very strange with Explorer (shell) locking up and
>other issues which may or may not be related to WGA failing to
>install.
>
>In addition, after the computer has been up for a day or so, maybe
>less, there is a svchost listing in Task Manager that shows using
>almost all available CPU and when I shut down Windows Update service,
>that entry goes away. Something has the WU all bound up but I don't
>know what.
>
>I'd like to get information that would enable me to troubleshoot the
>issue... I really need these two computers to get back on track with
>updates, etc... when I download the updates and apply them manually,
>they always work so it is just a problem with WU from what I can tell.
>
>I'd appreciate any help...

Had this same problem for a year or so with one of my Work LAN
computers, in my case I had foolishly installed Norton IS 2005 - big
mistake - when the problem surfaced had something to do with SP2 also,
was around that time it went tits up. Got rid of Norton but not the
problem which looks very similar as I recall to yours. Spent many
hours reading usenet and tinkering but nothing ever fixed it. Like you
I just dloaded and installed updates manually having decided it was
not worth the headache trying to fix updates any longer. Eventually I
did a full re-install that cured it.

Hope you find another way but don't hold your breath.

8-)

Jonah