Its the following update that seems to get stuck at checking for necessary space,

http://www.microsoft.com/downloads/details.aspx?familyid=CCDD3D35-BE5C-4C43-8FFA-BB8570A7321C&displaylang=en

 

Its stuck at that for 4 hours if not more on alot of computers, took me a long time to narrow it down to why the updates time out after running half a day. Installing a bunch of critical updates and this one is among them.

 

Checked the winupdate log and it doesnt tell me anything.

 

2007-04-25 10:54:27 1496 5e0 Misc   = Process: C:\WINNT\system32\svchost.exe
2007-04-25 10:54:27 1496 5e0 Misc   = Module: C:\WINNT\system32\wuaueng.dll
2007-04-25 10:54:27 1496 5e0 Service *************
2007-04-25 10:54:27 1496 5e0 Service ** START **  Service: Service startup
2007-04-25 10:54:27 1496 5e0 Service *********
2007-04-25 10:54:29 1496 5e0 Agent   * WU client version 5.8.0.2469
2007-04-25 10:54:29 1496 5e0 Agent   * SusClientId = '<NULL>'
2007-04-25 10:54:29 1496 5e0 Agent   * Just imaged
2007-04-25 10:54:29 1496 5e0 Agent   * Base directory: C:\WINNT\SoftwareDistribution
2007-04-25 10:54:29 1496 5e0 Agent   * Access type: No proxy
2007-04-25 10:54:29 1496 5e0 Agent   * Network state: Connected
2007-04-25 10:55:15 1496 5e0 Agent ***********  Agent: Initializing Windows Update Agent  ***********
2007-04-25 10:55:15 1496 5e0 Agent ***********  Agent: Initializing global settings cache  ***********
2007-04-25 10:55:15 1496 5e0 Agent   * WSUS server: <NULL>
2007-04-25 10:55:15 1496 5e0 Agent   * WSUS status server: <NULL>
2007-04-25 10:55:15 1496 5e0 Agent   * Target group: (Unassigned Computers)
2007-04-25 10:55:15 1496 5e0 Agent   * Windows Update access disabled: No
2007-04-25 10:55:19 1496 5e0 DnldMgr Download manager restoring 0 downloads
2007-04-25 10:55:19 1496 5e0 AU ###########  AU: Initializing Automatic Updates  ###########
2007-04-25 10:55:19 1496 5e0 AU   # AU disabled through User preference
2007-04-25 10:55:19 1496 5e0 AU   # AU is disabled, not initializing any handlers

 

Does anyone have any ideas what to do? This update refuses to install on alot of computers. Only once I tried to run all the critical updates one by one did I find this bottleneck. Otherwise it just gets stuck at the point of installing updates and I get a timeout error after 4-5hours (thats when using software delivery).

Any possibility you can remove that update from the list?  I know it's more managable on a single PC...with custom install options...just wondered if you used WSUS or something similar where you might be able to postpone installation of a patch because it's causing errors.

On these machines....has WMP been disabled, or otherwise patched already?  I've seen patches get stuck if they run "into themselves"....an already patched program.  (tends to happen to me if I don't sleep well)

Only other thing I can guess at, is something within Windows on those machines is blocking the install.  Something's keeping Windows/install manager from updating.  Gonna be a pain figuring out what they all have in common.

If you need to clear out the updates that a workstation has already downloaded create a new batch file and paste the following into it.

net stop "Automatic Updates"
del /f /s /q %windir%\SoftwareDistribution\*.*
net start "Automatic Updates"
wuauclt.exe /detectnow

The last line is optional. It tells the workstation to check for new updates.

I know this works on Windows XP, Server 2003 and Windows Vista. I'm not sure about Windows 2000.

 

Turns out its nothing wrong with the patch or more likely the computer, tried removing it from the package got same results.

 

After some work i found a process that was beeing run in the background by a program used to stop/start services (Third party junk), ending it made that MS-patch and others work like a charm.

 

Was a really annoying problem, but in the end im glad I managed to fix it. Learned alot in the process.

 

Thx for your help anyway =)

1. Double click on the self extracting Service Pack 2 installation file.
• Take note of where the files are being extracted to "ie: G:\f08f4e9b56a1c1ad94\i386\"
2. After all the files have been extracted the installer will begin.
• Do not click on "I Agree" or "Next" until after you have performed the following steps
3. Double click on "My Computer" on the desktop.
• Navigate to the location of the temporary files for the Service Pack installer.
• ie: G:\f08f4e9b56a1c1ad94\i386\
• Go one step further by entering the "update" directory.
• G:\f08f4e9b56a1c1ad94\i386\update\
4. Now here you will see both the installer file "update.exe" which is already running, as well as our culprit "FixCCS.exe
5. Right click on "FixCCS.exe" and chose "rename"
• Rename "FixCCS.exe" to something like "FixCCS_disable.exe"
6. After you have accepted the changes, you can proceed through the installation as normal.
• You will immediately notice that since you renamed "FixCCS.exe" it will not be loaded by the Service Pack 2 installer. Thus, your CPU will run like normal and will not be running at 100%
• You will also notice that the installer quickly runs through "Running necessary processes before install"
7. Finally, the installer will complete and you will be given the option to "restart later" via a checkbox. I suggest just restarting immediately, so you can begin downloading the latest updates from Microsoft.

this is for ppl that read this later

This does work!  However, if you are already at this point in the install, you can proceed by first stopping the FixCCS.exe process in Task Manager and the install will continue in about a minute.