Main Forum > General Computer Support
Windows Rollup KB4093118 Failed: 80004005 (SOLVED! FOR MANY UPDATE KB, FINALLY!)
dugadugadid:
Solved, 2 months later! After 3 dist upgrades!
So I finally solved this Windows / Update BUG, it and it was as simple as this; set peerdissvc (under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\) (aka branchcache as it is known under services.msc) from disabled back to manual, along with its dependency http, to manual. I'm quite sure setting branchcache to manual was all that was necessary for the fix to take place; I also had set "not configured" to alll changes I had made to "Background Intelligence Transfer Service" under group policy regarding peer caching. I had tried the latter before the last 3 distupgrades and it did not make any difference; so it seems windows update fails if you disable branchcache, which is typically only used by businesses anyway, so many people recommend to disable it, for security reasons also. What a headache; I spent at least a 80 hours, and weeks, and months trying to figure this one out; Windows update has turned into a bunch of bull***** with their ROLLUPS; one error on one of 130 little updates and the whole shebang goes down with the ship; dumbest idea ever for their update platform; they should change to individual updates and do it quick.
This is a MICROSOFT WINDOWS UPDATE BUG. You shouldn't have to enable or disable any built in windows service to get a "windows" update working. What a headache.
SO for all of you 80004005 victims out there; check your C:\Windows\Logs\CBS\cbs.log; search for "error" or "Failed execution" know very well whatever app is failing to install, be it IIS as quoted below-> they disabled IIS and it fixed their problem, or peerdist -> I had to set it from disabled TO manual, so make sure you fiddle with enabling or disabling the failing install service using services.msc or under the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\
Change the entry "start" to demand or auto, or disable if it was already enabled, reboot, then try your update.
0 Boot
1 system
2 Automatic
3 Demand (aka manual)
4 Disabled
Another user claimed the following:
I can also attest that IIS seemed to be the culprit for me.
I disabled the services World Wide Web Publishing Service, IIS Admin Service and some others for good measure, set them all to manual, rebooted, then tried to install SP1 RC Refresh and that finally succeeded.
I would get certain GUIDs in my CBS.log:
Code Block
2008-01-17 12:28:30, Error CSI 00000d42 (F) Failed execution of queue item Installer: Task Scheduler ({386b5911-b69e-4d2d-a3ab-796d2ec6af38}) with HRESULT 80041315 [Error,Facility=FACILITY_ITF,Code=4885 (0x1315)]. Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
Old component: Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
New component: Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6001.17128, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6001.17128, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;274
2008-01-17 12:28:41, Error CSI 00000f12 (F) Done with generic command 110 (0x0000006e); CreateProcess returned 0, CPAW returned S_OK
Url reservation add failed, Error: 6
Boggin:
Good to see you have found the cause and I've unlocked your other thread as requested.
I've exported and attached the Terminal Server registry item if you still want it.
I think I've done it right as this is the first time I've attached an exported reg item.
If you do decide to merge it, create a restore point first.
This is from Win 7 x64 SP1 Home Premium.
dugadugadid:
Thank you so much for your help and support! Much appreciated :cheesy:
Boggin:
You're welcome, but it was you who found the fix.
Navigation
[0] Message Index
[*] Previous page
Go to full version