Failed Windows Update Installations

Much thanks for posting the log and the Event Viewer info, Marty.
Perhaps *someone* can figure out why the Trusted Installer Module is so
fragile <eg>

> 2007-08-30 04:48:13:360 1364 9c DnldMgr FATAL:
> DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with
> 0x80080008.

0x80080008 CO_E_SERVER_STOPPING
It appears that the BITS service may have stopped here due to some
unknown reason and the DnldMgr failed to d/l the update.

[martyp]

MowGreen - Thank you for your reply. Some clarification requested.

After chunks of log text, you've provided some comments.
For example:

"0x80080008 CO_E_SERVER_STOPPING
It appears that the BITS service may have stopped here due to some
unknown reason and the DnldMgr failed to d/l the update."

= = = = =

"Methinks this is where the issue is. The Update server doesn't recognize
that the SelfUpdate components are installed. It checks and states they
are."

= = = = =

"0x80004002 E_Nointerface
In XP this would mean that the ActiveX component is not installed
properly/damaged/corrupted.
This *usually* occurs from 3rd party software, specifically, AVs or
security suites and security programs [Spybot, etc.]"

= = = = =

Are these simply observations?

Is the only action item the following:

"You could attempt to register these files at an Elevated Command Prompt
after stopping the WU service."

Appreciate your effort.

Marty

[martyp]

You're mowst welcome. The comments were just 'thinking out loud'
musings, Marty.
Not having installed Vista yet, I appreciate your posting the WU log and
Event Viewer message since it helps me get a grasp on how Vista updates.
Suggest you give the registering the .dll files a shot.
Not sure if it will resolve the updating issue, but it certainly won't
hurt anything

[martyp]

MowGreen:

Your comment "In XP this would mean that the ActiveX component is not installed properly/damaged/corrupted" is supported by a colleague who is a long-time, accomplished software developer. He said that it *appears* there's a COM component that is not registered or registered incorrectly. Finding that puppy is the hard part. Re-registering wu*.dlls has not resolved this issue. In summary, it's the old needle in a haystack, and I'm very frustrated in my efforts to find the needle.

Bottom line: I'll keep trucking along with Vista (32) hoping that the culprit is publicly identified or Vista's forthcoming SP1 comes to the rescue. With the sheer amount of postings on the Web relating to Windows Update issues, it would be nice if the process could be made more bullet-proof. But then again, it would be nice if I were tall and handsome!

Enjoy the weekend.

Marty

I wonder if installing the BITS Repair Tool is relevant to this, Freudi?
These entries appeared earlier in the log and the BITS state files may
have just been temporarily repaired:
SetNotifyInterface and the later error, E_Nointerface, might be related.

* Marty, what is the installed antivirus software ? *

See if this is present in the Application Event log:OR, just go ahead and install KB920520 from the link on the KB article :
http://support.microsoft.com/kb/940520
It automates the manual steps laid on in the KB and *should* not do
anything untoward to the OS.

[martyp]

Thanks for your suggestion, Freudi. Sorry to say the results are the same, which is to say installs continue to fail with 80004002 (Some Updates Were Not Installed).

Marty

[martyp]

Sort of a "catch 22," MowGreen. I would if I could! Since it's an .msu file it can't be installed by Windows Update. Or, for chuckles, the fix can't be a fix because what's broken doesn't allow the fix to try to fix it! Unless I'm missing something...

I'm using Kaspersky Internet Security. Rebooted with it totally disabled. Most recent chunk of windowsupdate.log follows...

2007-09-03 19:48:33:642 1412 4b8 Handler Attempting to create remote handler process as Primary-PC\Marty in session 1
2007-09-03 19:48:35:251 3924 b4c Misc =========== Logging initialized (build: 7.0.6000.381, tz: -0400) ===========
2007-09-03 19:48:35:251 3924 b4c Misc = Process: C:\Windows\system32\wuauclt.exe
2007-09-03 19:48:35:235 3924 b4c AUClnt FATAL: Error: 0x80004002. wuauclt handler: failed to spawn COM server
2007-09-03 19:48:35:376 1412 4b8 Handler FATAL: 0x80004002: ERROR: Remote update handler container process created (PID: 3924), but exited before signaling event
2007-09-03 19:48:35:392 1412 4b8 Agent * WARNING: Exit code = 0x80004002
2007-09-03 19:48:35:392 1412 b7c AU >>## RESUMED ## AU: Installing update [UpdateId = {05B30505-9F04-4382-BB49-19062335D5BA}]
2007-09-03 19:48:35:392 1412 4b8 Agent *********
2007-09-03 19:48:35:392 1412 b7c AU # WARNING: Install skipped
2007-09-03 19:48:35:392 1412 4b8 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2007-09-03 19:48:35:392 1412 b7c AU Install call completed.
2007-09-03 19:48:35:392 1412 4b8 Agent *************
2007-09-03 19:48:35:392 1412 b7c AU # WARNING: Install call failed, reboot required = No, error = 0x80004002
2007-09-03 19:48:35:392 1412 4b8 Agent WARNING: WU client failed installing updates with error 0x80004002
2007-09-03 19:48:35:392 1412 b7c AU #########
2007-09-03 19:48:35:392 1412 b7c AU ## END ## AU: Installing updates [CallId = {1F582633-DBC2-4657-BB66-08545179D89C}]
2007-09-03 19:48:35:392 1412 b7c AU #############
2007-09-03 19:48:35:392 1412 b7c AU Install complete for all calls, reboot NOT needed
2007-09-03 19:48:36:485 1412 f30 AU UpdateDownloadProperties: 0 download(s) are still in progress.
2007-09-03 19:48:36:485 1412 f30 AU Can not perform non-interactive scan if AU is interactive-only
2007-09-03 19:48:36:485 1412 f30 AU AU setting pending client directive to 'Install Complete Ux'
2007-09-03 19:48:36:485 1412 f30 AU Changing existing AU client directive from 'Progress Ux' to 'Install Complete Ux', session id = 0x1
2007-09-03 19:48:36:485 2796 ef8 CltUI AU client got new directive = 'Install Complete Ux', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, return = 0
2007-09-03 19:48:36:517 2796 ef8 CltUI AU client got new directive = 'Shutdown', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, return = 0
2007-09-03 19:48:36:642 1412 f88 AU AU received handle event

[martyp]

I don't understand the "pardon." The download is an .msu file, exactly what my Windows Update will download, but won't install (and the root of my problem).

Regarding <whistle>, does it represent something positive or negative?

Marty

[martyp]

MowGreen:

>>KB 940520 has a BITS repair tool that helps you clean up your BITS database if it seems to be corrupted.

Executed repair tool. No change.


Freudi:

>>You've tried the manual download and execution of the downloaded file from the above link for your Vista version already?

Yes - failed with "some updates were not installed"


>> It represents the potential cause of the issue you're seeing.

Booted with KIS totally disabled. No difference.

Thank you both for your continued interest. At least SP1 will contain cumulative updates. Who knows - maybe it'll fix whatever else prevents downloaded updates from being installed successfully.

[martyp]

Well, my friends, Windows Update is fixed.

At a high level, it is critical that the wu*.* files in \%windir%\System32 are original Vista files. For some reason, during the normal course of events, several of the files became corrupted. But we can't stop there.

There are also wu*.dll.mui files in \%windir%\System32\en-US [for those with English-US installations] that must be original Vista files. For some reason, too, a few of these became corrupted.

Both of these restoration steps are critical because if you only restore original wu*.* files to \%windir%\System32, the user interface can present itself without text - just some background graphics. Correcting the wu*.dll.mui files enables full text and graphics.

Thank you MowGreen and Ferdi for your attempts to help, and I hope that others experiencing Windows Update problems with the same symptoms will benefit from what I've learned.

[martyp]

MowGreen:

As I wrote in my previous post, all is well now. Downloads and installations are up-to-date, including KB938194 that you referred to.

Thanks again.

Marty