Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows Update fails: 0x80070005. wuauclt handler: failed to spawn

153 views
Skip to first unread message

nzmike

unread,
Sep 7, 2004, 2:27:01 AM9/7/04
to
Hi,

I recently upgraqded my W2K SP4 (w/ all current updates) Compaq Evo N800v
laptop to XP Pro. I then installed SP1a and went to windowsupdate to get all
the newer patches, fixes and sticking plasters. It finds the downloads and
even downloads them but when I actually ask XP to install them it gives me
the "Updates were unable to be successfully installed" error on every single
one of them. The relevant section (for one of the updates) of the
WindowsUpdate.log is below.

The only thing I can think of is that during the install of XP Pro I got
that problem where it stops the install and gives this error: "GetIUMS not
found in MSDART.dll" about 80 times. I followed instructions I found on the
web for this where you just keep clicking OK and it eventually goes away.
The rest of the upgrade seems to have worked fine, the machine is fast and
stable, but I can't get the updates to install at all.

Can anyone help me solve this? I don't want to do a fresh reinstall of XP
as I have many client projects on the machine which I do not want (or have
time right now) to reinstall and reconfgure.

Cheers,

Mike


2004-09-07 16:13:11+1000 1056 618 WU client found 58 updates and 10
categories in search
2004-09-07 16:13:11+1000 1056 618 WU client finished Searching for update
2004-09-07 16:13:12+1000 1056 618 WU client calls back to search call
WindowsUpdate with code Call complete and error 0
2004-09-07 16:13:12+1000 1056 618 WU client completed and deleted call
{5A8F0ACD-7B86-4727-9489-D07425B7D110}
2004-09-07 16:13:12+1000 1056 6a0 prune update list before Install
2004-09-07 16:13:12+1000 1056 6a0 setting system restore point
2004-09-07 16:13:12+1000 1056 6a0 SRSetRestorePoint failed with
ERROR_SERVICE_DISABLED (expected behavior on client SKUs with SR turned off)
2004-09-07 16:13:13+1000 3808 d1c Error: 0x80070005. wuauclt handler: failed
to spawn COM server
2004-09-07 16:13:13+1000 1056 6a0 0x80070005: ERROR: Remote update handler
container process created (PID: 3808), but exited before signaling event
2004-09-07 16:13:13+1000 1056 6a0 WU client failed installing updates with
error 0x80070005
2004-09-07 16:13:13+1000 1056 6a0 Install call failed, error is 80070005
2004-09-07 16:13:13+1000 1056 6a0 Install complete for all calls, reboot NOT
needed
2004-09-07 16:13:13+1000 1056 6a0 WU client calls back to install call
{AE88D785-FA1C-4553-A870-C9F886708D05} with code Call failed and error
0x80070005
2004-09-07 16:13:13+1000 1056 6a0 WU client completed and deleted call
{AE88D785-FA1C-4553-A870-C9F886708D05}
2004-09-07 16:13:16+1000 1056 6a0 REPORT EVENT:
{692BC7D3-22EB-4818-A3E9-6F542B8A3047} 67 2004-09-07
16:13:11+1000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.

nzmike

unread,
Sep 7, 2004, 2:49:05 AM9/7/04
to
I looked at some other posts and Lucy (are you out there?!?!) recommeded
someone else to try the following REGSVR32 commands...

REGSVR32 C:\WINDOWS\system32\wuapi.dll
REGSVR32 C:\WINDOWS\system32\wuauclt.exe
REGSVR32 C:\WINDOWS\system32\wuaueng.dll
REGSVR32 C:\WINDOWS\system32\wucltui.dll

The three DLLs had no problems but when I did wuauclt.exe it told this:

"wuauclt.exe was loaded but the DLLRegisterServer entry point was not found.
wuauclt.exe does not appear to be a .DLL or .OCX file".

Hope that is of some help... updates still not do not work of course.


Mike

Press Enter

Click Start > Run > Type the follow command in the Open box.

"REGSVR32 C:\WINDOWS\system32\ wups.dll" (w/o quotes)

nzmike

unread,
Sep 8, 2004, 5:13:02 AM9/8/04
to
BUMP!!!

*PLEASE* can I have some help from a MSFT or someone... this is driving me
mad!!!

TIA...

Mike

Robert Aldwinckle

unread,
Sep 8, 2004, 5:44:10 PM9/8/04
to
Try a search?

http://groups.google.com/groups?q=80070005+OR+0x80070005++MSFT+OR+MVP++group:microsoft.*.windowsupdate&num=20&hl=en&lr=&ie=UTF-8&c2coff=1&scoring=d

It looks like we are waiting for someone to have this problem
who has enough initiative and savvy to take advantage of some
of the suggestions we have been making about diagnostics
in order to understand the symptom and provide all the rest
a canned solution.

Join the line or good luck!


Robert Aldwinckle
---


"nzmike" <nzm...@discussions.microsoft.com> wrote in message
news:E4CB2BDD-B1BA-42F2...@microsoft.com...

nzmike

unread,
Sep 8, 2004, 6:19:13 PM9/8/04
to
Did I try a search? Well, put it this way - Google shares have gone up
again so that could have something to do with it! I searched high and low,
looked on Experts Exchange etc etc and this newsgroup was the closest I came
hence my posts here. I'm not one of those people that just waits for help -
beleive me, I've tried everything short of a complete rebuild!

However... the link you provided did turn up another newsgroup to which
someone posted in the last day or two with a solution that helped someone
with a similair (but not identical) problem so I wil try that and post here
if it works.

Mike

Maurice N ~ MVP

unread,
Sep 8, 2004, 8:29:37 PM9/8/04
to
nzmike wrote:
> Did I try a search? Well, put it this way - Google shares have gone
> up again so that could have something to do with it! I searched high
> and low, looked on Experts Exchange etc etc and this newsgroup was
> the closest I came hence my posts here. I'm not one of those people
> that just waits for help - beleive me, I've tried everything short of
> a complete rebuild!
>
> However... the link you provided did turn up another newsgroup to
> which someone posted in the last day or two with a solution that
> helped someone with a similair (but not identical) problem so I wil
> try that and post here if it works.
>
> Mike
>
Howdy nzmike,
I noticed your 1st post of this morning, What caught my eye is that the System Restore service failed to make a restore point. As you may know, Sys Restore is invoked just before making updates.
Check on your Services. Insure System Restore service is not disabled.
Check your FREE space. Not enough space will also lead to its failure.

As a sidenote, Lucy is on leave. This is */the/* group for Windows Update issues.
--
Maurice N
MVP Windows - Shell / User
-----

krisc

unread,
Jan 22, 2005, 4:07:09 PM1/22/05
to
In my search of a solution for the same fault, I passed by your question
but didn't find an answer on the net. Or you still have the same problem,
or anyone who has the solution is hiding it.
I finally found a solution in this: Give 'Everyone' total control on the
COM+, DCOM and the installs run. As I didn't figure out yet which access
is really needed, I strongly suggest the delete that authorization as soon
as the installation is finished.

Spread the word because there are a lot of people wrestling with the same
problem out there. If, by the way, anyone knows what privilege should be
used, let me know, please.

0 new messages