I'm using a newly installed copy of Win2k SP4 and although I can download
updates from Windows Update, I can't install them. it gives a general message
of "...... (name of update) fails!" and brings me to a summary window stating
that none of the installations were succefully completed.

If you refer to Trev's post at 12/29/2005 5:04 AM PST, you will see his
original problem (which corresponds exactly to mine... same updates were not
installing as well). I tried his solution that worked for him, and this
didn't work for me.

For reference, I was able to get from my WU log file, the info it spat out
as WU failed to install the already-downloaded 3 updates:

2005-12-29 23:30:07 844 204 COMAPI -- START -- COMAPI: Install [ClientId =
MicrosoftUpdate]
2005-12-29 23:30:07 844 204 COMAPI ---------
2005-12-29 23:30:07 844 204 COMAPI - Allow source prompts: Yes; Forced:
No; Force quiet: No
2005-12-29 23:30:07 844 204 COMAPI - Updates in request: 3
2005-12-29 23:30:07 844 204 COMAPI - ServiceID =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2005-12-29 23:30:07 844 204 COMAPI - Updates to install = 3
2005-12-29 23:30:07 844 204 COMAPI <<-- SUBMITTED -- COMAPI: Install
[ClientId = MicrosoftUpdate]
2005-12-29 23:30:07 660 464 Agent *************
2005-12-29 23:30:07 660 464 Agent ** START ** Agent: Installing updates
[CallerId = MicrosoftUpdate]
2005-12-29 23:30:07 660 464 Agent *********
2005-12-29 23:30:07 660 464 Agent * Updates to install = 3
2005-12-29 23:30:07 660 464 Agent * Title = <NULL>
2005-12-29 23:30:07 660 464 Agent * UpdateId =
{7E42BA28-C236-4B44-B6BA-C00ADD8DE5A3}.51
2005-12-29 23:30:07 660 464 Agent * Bundles 1 updates:
2005-12-29 23:30:07 660 464 Agent *
{6E2CE922-F9D8-43DE-92EE-6BAAC78729E2}.51
2005-12-29 23:30:07 660 464 Agent * Title = <NULL>
2005-12-29 23:30:07 660 464 Agent * UpdateId =
{B166A6A9-398B-4C81-B8DB-2043CF0672A1}.103
2005-12-29 23:30:07 660 464 Agent * Bundles 1 updates:
2005-12-29 23:30:07 660 464 Agent *
{F2FCA9BF-05AD-460A-977C-355CE5734118}.102
2005-12-29 23:30:07 660 464 Agent * Title = <NULL>
2005-12-29 23:30:07 660 464 Agent * UpdateId =
{279FE710-6AA0-4691-89F0-3B3012720B51}.101
2005-12-29 23:30:07 660 464 Agent * Bundles 1 updates:
2005-12-29 23:30:07 660 464 Agent *
{13625DC4-6D61-4812-A236-2E28FB385B3A}.101
2005-12-29 23:30:08 660 464 Agent WARNING: Failed to evaluate Installed
rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
0x80041017
2005-12-29 23:30:09 660 464 EEHndlr FATAL: MSI DLL version is 2.0. Version
3.1 is required.
2005-12-29 23:30:09 660 464 Agent WARNING: Failed to evaluate Installed
rule, updateId = {6248B8B1-FFEB-DBD9-887A-2ACF53B09DFE}.102, error =
0x80241001
2005-12-29 23:30:09 660 464 EEHndlr FATAL: MSI DLL version is 2.0. Version
3.1 is required.
2005-12-29 23:30:09 660 464 Agent WARNING: Failed to evaluate Installed
rule, updateId = {1403F223-A63F-F572-82BA-C92391218055}.102, error =
0x80241001
2005-12-29 23:30:09 660 464 Service WARNING: GetUserTokenFromSessionId
failed with hr 0x800706d3
2005-12-29 23:30:09 660 464 Agent * WARNING: Exit code = 0x80240020
2005-12-29 23:30:09 660 464 Agent *********
2005-12-29 23:30:09 660 464 Agent ** END ** Agent: Installing updates
[CallerId = MicrosoftUpdate]
2005-12-29 23:30:09 660 464 Agent *************
2005-12-29 23:30:09 660 464 Agent WARNING: WU client failed installing
updates with error 0x80240020
2005-12-29 23:30:09 844 340 COMAPI >>-- RESUMED -- COMAPI: Install
[ClientId = MicrosoftUpdate]
2005-12-29 23:30:09 844 340 COMAPI - Install call failed
2005-12-29 23:30:09 844 340 COMAPI - Reboot required = No
2005-12-29 23:30:09 844 340 COMAPI - WARNING: Exit code = 0x80240FFF;
Call error code = 0x80240020
2005-12-29 23:30:09 844 340 COMAPI ---------
2005-12-29 23:30:09 844 340 COMAPI -- END -- COMAPI: Install [ClientId =
MicrosoftUpdate]
2005-12-29 23:30:09 844 340 COMAPI -------------
2005-12-29 23:30:10 844 204 COMAPI WARNING: Operation failed due to earlier
error, hr=80240020


I also saw the topic "Update installation fails" by Harold Cataquet, and I
found my situation was similar to his in that I also could not manually start
my BITS service. When I did, it returned the following info (taken from the
event viewer):

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7003
Date: 29/12/2005
Time: 11:28:19 PM
User: N/A
Computer: PK
Description:
The Background Intelligent Transfer Service service depends on the following
nonexistent service: LanmanWorkstation

Now, I tried everything that was mentioned in that thread, and unfortunately
that didn't work, either.

After trying those things, I reinstalled Windows with a "clean install" (I
think), but without reformatting the hard drive. This didn't solve the
problem.

Then, I tried simply downloading those updates that WU needed itself from
the MS Download Center. I was able to do this and install them manually
without problem. Thus, I was able to access all the other Updates that are
available to me using WU. I downloaded them all using WU. When it came time
to install them, the exact same type of error occured, and installation
failed for all of them. If it will help, I will post the relevant section of
the WU log file (now refusing to install these other, 20 or so updates), but
I fear with so many failed installs it would be extremely large (haven't
actually looked yet).

Please, any help would be greatly appreciated! Thanks.

Tossy