I spent the week trying to install updates for .net and live writer , and it took me finally clicking on custom install and unclicking all but one and dling one at a time to get it to respond correctly
they're all installed now, but it took forever for some of them to dl and install,.

Thanks for the advice, Wulfin1.... unfortunately no updates via Automatic Update will install... all fail no matter how I do it.

I'm sure there's a reason (I can't fathom) and an answer to this dilemma (I can't find), so hopefully yrag or someone more knowledgeable than I will have an explanation and a resolution.

Try holding your tongue to the left instead of to the right.

Have you spilled blood for it?

yes check time and date and and run a full antivirus scan too.

Nasty

yarg...tried one update but it failed to install again, the error report is as follows:


* Updates to install = 1
2008-04-26 15:30:07:765 1368 a04 Agent * Title = Root Certificates Update
2008-04-26 15:30:07:765 1368 a04 Agent * UpdateId = {D24FE7DE-266B-4260-BBF2-59824AF246CF}.101
2008-04-26 15:30:07:765 1368 a04 Agent * Bundles 1 updates:
2008-04-26 15:30:07:765 1368 a04 Agent * {C1292657-6E08-4BD7-A3E6-8725BB43B40C}.101
2008-04-26 15:30:12:000 1368 a04 Handler Attempting to create remote handler process as HOME-D923F24026\starkers in session 0
2008-04-26 15:30:12:171 3804 628 Misc =========== Logging initialized (build: 7.0.6000.381, tz: +1000) ===========
2008-04-26 15:30:12:171 3804 628 Misc = Process: C:\WINDOWS\system32\wuauclt.exe
2008-04-26 15:30:12:171 3804 628 AUClnt FATAL: Error: 0x80004002. wuauclt handler: failed to spawn COM server
2008-04-26 15:30:12:187 1368 a04 Handler FATAL: 0x80004002: ERROR: Remote update handler container process created (PID: 3804), but exited before signaling event
2008-04-26 15:30:12:187 1368 a04 Agent * WARNING: Exit code = 0x80004002
2008-04-26 15:30:12:187 1368 a04 Agent *********
2008-04-26 15:30:12:187 1368 a04 Agent ** END ** Agent: Installing updates [CallerId = MicrosoftUpdate]
2008-04-26 15:30:12:187 1368 a04 Agent *************
2008-04-26 15:30:12:187 1368 a04 Agent WARNING: WU client failed installing updates with error 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI - Install call failed
2008-04-26 15:30:12:187 2812 e5c COMAPI - Reboot required = No
2008-04-26 15:30:12:187 2812 e5c COMAPI - WARNING: Exit code = 0x80240FFF; Call error code = 0x80004002
2008-04-26 15:30:12:187 2812 e5c COMAPI ---------
2008-04-26 15:30:12:187 2812 e5c COMAPI -- END -- COMAPI: Install [ClientId = MicrosoftUpdate]
2008-04-26 15:30:12:187 2812 e5c COMAPI -------------
2008-04-26 15:30:12:250 1368 460 Report REPORT EVENT: {5F68AF90-0CD7-424E-BF68-229CA10803F6} 2008-04-26 15:30:07:250+1000 1 162 101 {D24FE7DE-266B-4260-BBF2-59824AF246CF} 101 0 MicrosoftUpdate Success Content Download Download succeeded.
2008-04-26 15:30:12:937 2812 ecc COMAPI WARNING: Operation failed due to earlier error, hr=80004002

Hope that helps find a fix... cos it's all Greek to me.

May I humbly suggest that you perform a clean install of XP. Repair installs do not correct all problems, and can in fact cause them. I suggest this since it is honestly the fastest and simplest method of resolving your problem.

The problem very likely lies with some dll's and registry keys missing from your system or improperly created/registered. This likely was not fixed with the repair install since it overwrote only parts of the system.

That being said, if you still wish to attempt a repair otherwise, you should look into wether the appropriate services are running to enalbe windows update to perform the required tasks. Most often this can be an issue with the BITS service. You will have to force install the proper files/dll's and then register them with the system manually. This process will likely take more time than simply performing a clean install.

In my biz, time is money and the fastest solution that fully resolves the problem is often the best one.

yrag... all the registry items are there but 4 are different:

"Asynchronous"=dword:0x0000001(1)

"Impersonate"=dword:0x0000001(1)

"Safe"=dword:0x0000001(1)

"MaxWait"=dword:00000258(600)

I did export them just in case, but the editor will not allow me to change the values to those you posted... can type them in OK but nothing happens when tying to apply.

Damned blasted puters....



You may humbly suggest if you like... cos if things don't improve real soon, I'll be doing just that, though not so humbly. Being it's not that long ago thatI did it, there's quite likely to be a few... er, a lot of curse words going on during the process.

At this point a clean install might be best as said already. you`ll do alot of work just to do it any ways

You're either in a limited user account or it's a security app or both. List the apps installed.

Why do so many techs just wipe the drive? I have never understood that. I always do a complete image and then restore the customer's data after the reinstall. Why wouldn't you?

Hmm... I can see your point. Though I would say the two statements are different. The problem is work ethic and quality of work.