Hi all,

I, too, have been struggling with one of these this morning. One a site with identical machines (put in as a greenfield network), 5 of the machines took the update like a champ, whereas one has failed. Upon failure it reverts back to the PreSP1 state by means of a rollback, however this takes time.

The symptoms the customer sees is that the update appears to freeze at 70% for some time, then begins to rollback after about an hour. I've verified this with my own testing.

In order to get this far, I've also completed on this machine:

• Installation of the SUR tool, which reported zero errors.
• Perform a cleanup of the .NET Frameworks using the cleanup tool and reinstalled .NET Framework 4 Client
• Ran a full, non  SP1 Windows Update, which located a number of minor patches. An interesting one that I noted was an updated Graphics Chipset driver for the Intel G35(I think) chipset.
• Clean reboot, of course

Luckily, while the install is running, you can browse to the C$ share of the machine and check the CBS logfile.

Here is an annotated version of what I found around the time of the failure:

----

2011-03-11 15:19:27, Info                  CSI    00000415 Calling generic command executable (sequence 29 (0x0000001d)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [52]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_TCPIP"

-> LAST TIME THAT THE GUI WAS UPDATED TO SHOW A NEW PROGRESS PERCENTAGE.

2011-03-11 15:19:27, Info                  CBS    Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 70.

2011-03-11 15:24:26, Info                  CSI    00000416 Done with generic command 29 (0x0000001d); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:48 [48]"Trying to install MS_TCPIP ...

...done.

"]
2011-03-11 15:24:26, Info                  CSI    00000417@2011/3/11:04:54:26.432 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-TCPIP, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;427187855
2011-03-11 15:24:26, Info                  CSI    00000418 End executing advanced installer (sequence 614)
    Completion status: S_OK

2011-03-11 15:24:26, Info                  CSI    00000419 Begin executing advanced installer phase 38 (0x00000026) index 576 (0x00000240) (sequence 615)
    Old component: [ml:300{150},l:298{149}]"Microsoft-Windows-RasServer, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
    New component: [ml:300{150},l:298{149}]"Microsoft-Windows-RasServer, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2011-03-11 15:24:26, Info                  CSI    0000041a Calling generic command executable (sequence 30 (0x0000001e)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [53]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_RasSrv"
2011-03-11 15:29:16, Info                  CSI    0000041b Done with generic command 30 (0x0000001e); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:49 [49]"Trying to install MS_RasSrv ...

...done.

"]
2011-03-11 15:29:16, Info                  CSI    0000041c Calling generic command executable (sequence 31 (0x0000001f)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [56]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_Steelhead"
2011-03-11 15:29:19, Info                  CBS    Startup: Changing logon timeout to a sliding window timeout: 900000
2011-03-11 15:34:06, Info                  CSI    0000041d Done with generic command 31 (0x0000001f); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:52 [52]"Trying to install MS_Steelhead ...

...done.

"]
2011-03-11 15:34:06, Info                  CSI    0000041e@2011/3/11:05:04:06.373 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-RasServer, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;828485001
2011-03-11 15:34:06, Info                  CSI    0000041f End executing advanced installer (sequence 615)
    Completion status: S_OK

2011-03-11 15:34:06, Info                  CSI    00000420 Begin executing advanced installer phase 38 (0x00000026) index 577 (0x00000241) (sequence 616)
    Old component: [ml:296{148},l:294{147}]"Microsoft-Windows-RasBase, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
    New component: [ml:296{148},l:294{147}]"Microsoft-Windows-RasBase, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2011-03-11 15:34:06, Info                  CSI    00000421 Calling generic command executable (sequence 32 (0x00000020)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [54]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_NDISWAN"
2011-03-11 15:39:32, Info                  CSI    00000422 Done with generic command 32 (0x00000020); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:50 [50]"Trying to install MS_NDISWAN ...

...done.

"]
2011-03-11 15:39:32, Info                  CSI    00000423 Calling generic command executable (sequence 33 (0x00000021)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [53]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_RASMAN"
2011-03-11 15:44:35, Info                  CSI    00000424 Done with generic command 33 (0x00000021); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:49 [49]"Trying to install MS_RASMAN ...

...done.

-> THINGS START TO GO WRONG HERE IT SEEMS ..... STARTS TO TIMEOUT AND DETECT TIMEOUTS

"]
2011-03-11 15:44:35, Info                  CSI    00000425 Calling generic command executable (sequence 34 (0x00000022)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [51]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_PPTP"
2011-03-11 15:49:07, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Previous global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStateStageDrivers
2011-03-11 15:49:07, Info                  CBS    Clearing HangDetect value
2011-03-11 15:49:07, Info                  CBS    Saved last global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Setting HangDetect value to 1
2011-03-11 15:49:07, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:07, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Setting HangDetect value to 2
2011-03-11 15:49:07, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.

->THIS RESTART NEVER HAPPENS...2011-03-11 15:49:07, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info                  CBS    Setting HangDetect value to 3
2011-03-11 15:49:07, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:07, Info                  CBS    Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:07, Info                  CBS    Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:07, Info                  CBS    Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:07, Info                  CBS    Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:08, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:08, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info                  CBS    Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info                  CBS    Setting HangDetect value to 4
2011-03-11 15:49:08, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:08, Info                  CBS    Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:08, Info                  CBS    Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:08, Info                  CBS    Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:08, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info                  CBS    Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info                  CBS    Setting HangDetect value to 5
2011-03-11 15:49:08, Info                  CBS    Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:08, Info                  CBS    Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:08, Info                  CBS    Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:43, Info                  CSI    00000426 Done with generic command 34 (0x00000022); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:47 [47]"Trying to install MS_PPTP ...

->....YET THIS COMPONENT COMPLETES SUCCESSFULLY.

...done.

"]
2011-03-11 15:49:43, Info                  CSI    00000427 Calling generic command executable (sequence 35 (0x00000023)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [52]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_PPPOE"

-> WHY IS IT INITIATING A SYSTEM SHUTDOWN HERE....?

2011-03-11 15:49:46, Info                  CBS    Startup: A system shutdown was initiated while waiting for startup to complete
2011-03-11 15:49:46, Info                  CBS    Startup: Attempting to terminate the startup thread.
2011-03-11 15:49:46, Info                  CBS    Failed a critical portion of startup processing. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
2011-03-11 15:49:46, Info                  CBS    Ending the TrustedInstaller main loop.
2011-03-11 15:49:46, Info                  CBS    Starting TrustedInstaller finalization.

-> THESE DON'T LOOK GOOD!!

2011-03-11 15:49:46, Info                  CBS    Failed to unload the COMPONENTS hive. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2011-03-11 15:50:52, Info                  CBS    Starting TrustedInstaller initialization.
2011-03-11 15:50:53, Info                  CBS    Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f\cbscore.dll
2011-03-11 15:50:56, Info                  CSI    00000001@2011/3/11:05:20:56.382 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x73d25d7d @0x73d0205a @0x701c99 @0x701236 @0x77c475a8)
2011-03-11 15:50:56, Info                  CSI    00000002@2011/3/11:05:20:56.392 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x73d67183 @0x73d64013 @0x701c99 @0x701236 @0x77c475a8)
2011-03-11 15:50:56, Info                  CSI    00000003@2011/3/11:05:20:56.392 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x731f4bb0 @0x731f548e @0x701327 @0x701245 @0x77c475a8)
2011-03-11 15:50:56, Info                  CBS    Ending TrustedInstaller initialization.
2011-03-11 15:50:56, Info                  CBS    Starting the TrustedInstaller main loop.
2011-03-11 15:50:56, Info                  CBS    TrustedInstaller service starts successfully.
2011-03-11 15:50:56, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2011-03-11 15:50:56, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2011-03-11 15:50:56, Info                  CBS    SQM: Requesting upload of all unsent reports.
2011-03-11 15:50:56, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2011-03-11 15:50:56, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info                  CBS    Blocked system sleep; prior state: 0x80000000
2011-03-11 15:50:56, Info                  CSI    00000004 CSI Store 723760 (0x000b0b30) initialized
2011-03-11 15:50:56, Info                  CBS    Session: 30138275_3387440894 initialized by client SP Coordinater Engine.
2011-03-11 15:50:56, Info                  CBS    Startup: current ExecuteState is CbsExecuteStateResolvePending
2011-03-11 15:50:56, Info                  CBS    Disabling LKG boot option
2011-03-11 15:50:56, Info                  CBS    Startup: Initializing driver operations queue.
2011-03-11 15:50:56, Info                  CBS    Startup: Initializing advanced operation queue.
2011-03-11 15:50:56, Info                  CBS    Startup: Waiting for SC autostart event
2011-03-11 15:50:56, Info                  CBS    Startup: BlockTime: 10800000ms, BlockTimeIncrement: 900000ms
2011-03-11 15:50:56, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
2011-03-11 15:50:59, Info                  CBS    Startup: SC autostart event signaled
2011-03-11 15:50:59, Info                  CBS    Clearing HangDetect value
2011-03-11 15:50:59, Error                 CBS    Startup: A possible hang was detected on the last boot. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
2011-03-11 15:50:59, Info                  CBS    Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:50:59, Info                  CBS    Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending

->ROLLBACK STARTS HERE

2011-03-11 15:50:59, Error                 CBS    Startup: No progress detected while needing to process the advanced operation queue, rolling back and cancelling the transaction. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:59, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2011-03-11 15:50:59, Info                  CBS    Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Rollback.
2011-03-11 15:51:01, Info                  CSI    00000005 Rolling back transactions...

2011-03-11 15:51:01, Info                  CSI    00000006 Creating NT transaction (seq 1), objectname [6]"(null)"
2011-03-11 15:51:01, Info                  CSI    00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x1f8
2011-03-11 15:51:02, Info                  CSI    00000008 Performing 2387 operations; 2387 are not lock/unlock and follow:

----

After this point, it's the rollback operation continuing.

Due to the two or three attempts to install, this customer's CBS log file is around the 35MB mark, but I think this is the relevant information here.

While the solution in this threat seems to get around it being stuck, it also appears to prevent an installation at a later date, so I'm hesitant to try this right now. I'm hoping this sheds a little light on the situation, or at least my situation.

Look forward to any info on this subject!

Cheers,

Dave

Okay, Ive got something that might help. (first time posting on TN btw, I read the fourms ALOT!)

I have a client that installed SP1 across their domain thanks to the WSUS implementation on SBS..

Anyway. out of all the users we originally thought only users with Asus laptops were affected, then we had a Dell fail.

Turns out, the only thing these machines have in common is they all ran Windows Anytime Upgrade, out of all the machines (3) that we upgraded using WAU , ALL of them failed to install SP1.

the fix for removing 000.cdf.ms rolled back the sp1 install fine and the user could login

Just trying to install SP1 from my usb key now to see if it is related to WSUS

ill let you know shortly.

Okay, Back.

The USB install throws errors about missing windows components, the solution to that is of course an in place upgrade, Ive not done this as the media the customer has is

1) a restore disk

2) Win 7 home (needs pro, hence WAU)

and my copy of win7 on usb is Enterprise.

So for now Ive barred this machine from installing SP1 and will see if a better solution is posted.

2 users here have gotten up and running with SP1 by formatting, installing 7, then SP1 then running WAU.. so looks like the issue MIGHT be there.

(edit) Corrected bad wording

It is time to stop publishing SP1.

This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.

The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.

 

On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.

Company machines are less affected, but they failed too.

And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.

 

Please: Stop SP1, tame that bitch, release SP1a.

 

hi ,

what people need to do is understand what they are talking about , .... and follow instructions ! half of the comps are infected with who knows what and then they wonder they cant install anything ?

there are people who install it on vista , .....

now if people first take a look at whats inside sp 1 , maybe they would see that its not that whats causing problems , ...

on the other hand are all the computers that have no problem what so ever , ...

1000 plus and only two errors , one due memory burned and one due to power loss , .... both fixed within the hour , ...

but there is no forum for people who have managed to succeed , ... !!

oh and both under all four seven versions !

have a nice day

Your users seem to differ from mine: Only those running Windows 7 tried to install SP1, none of the XP and Vista users tried to run Sp1. None of the affected machine got viruses. None of the affected machines got hardware problems. The worst the affected machines have are two or three toolbars, Google toolbar (thanks google, I think bundled with java), Yahoo toolbar (thanks adobe flash), Ask-toolbar (thanks PDF creator).

Only a hand full (less than ten) of the SP1-completely-fail users are among those who dig deeper into the system, and their wording is: "Well, it was acting strange before, I needed to reinstall anyway." - and they do so and solve their problem that way and don't ask me to help.

I wanted to add my name to the list of users affected:  I've got a Win 7 x64 laptop who tried to install SP1 using the shutdown method.  I pretty much get the same error described here  except it's on operation 291.  Today I did successfully update 2 Win 7 32 bit laptops, but I did that through Windows Updates and not the shutdown & install method.  Of note is that even on these two that were successful, the first time the PCs tried to install the SP, they both failed.  The two 32 bit PCs are brand new Dell's not touched by a user yet, the 64 bit is 'new' Dell but has been used by a user for about 2 weeks now.  Before I left work I left my PC shutting down and installing updates, I dread returning in the morning.  :-/

 

To the point,  I can't find any of the items in the pending.xml that have been cited.  I've looked for  0000000000000000.cdf-ms, delete, deletefile, "checkpoint", "point", "0000" "pt-pt" as cited by jadedhero.

 

I've tried the method's listed here: http://support.microsoft.com/kb/975484/en-us  and all have failed. 

I have no system-restore points listed, and the Reg Key they recommend to delete wasn't there to begin with. 

I can't find the "reboot.xml" file referenced by a previous poster.

I'm really not looking forward to going back to the office in the morning.  Any help that you could provide would be much appreciated. 

 

@thiswoot, the solution hasn't worked yet, but your sticking around here and helping is greatly appreciated.  Are you still watching the forums?

 

Thanks in advance

I wanted to add my name to the list of users affected:  I've got a Win 7 x64 laptop who tried to install SP1 using the shutdown method.  I pretty much get the same error described here  except it's on operation 291.  Today I did successfully update 2 Win 7 32 bit laptops, but I did that through Windows Updates and not the shutdown & install method.  Of note is that even on these two that were successful, the first time the PCs tried to install the SP, they both failed.  The two 32 bit PCs are brand new Dell's not touched by a user yet, the 64 bit is 'new' Dell but has been used by a user for about 2 weeks now.  Before I left work I left my PC shutting down and installing updates, I dread returning in the morning.  :-/

To the point,  I can't find any of the items in the pending.xml that have been cited.  I've looked for  0000000000000000.cdf-ms, delete, deletefile, "checkpoint", "point", "0000" "pt-pt" as cited by jadedhero.

I've tried the method's listed here: http://support.microsoft.com/kb/975484/en-us  and all have failed. 

I have no system-restore points listed, and the Reg Key they recommend to delete wasn't there to begin with. 

I can't find the "reboot.xml" file referenced by a previous poster.

I'm really not looking forward to going back to the office in the morning.  Any help that you could provide would be much appreciated. 

@thiswoot, the solution hasn't worked yet, but your sticking around here and helping is greatly appreciated.  Are you still watching the forums?

Thanks in advance

::Edit::

I found that I was looking at the wrong drive.  On the 64 bit computer I'm working with there were the C:\, D:\, X:\ and one other drive.  C: was the factory dell partition, D:\ was the OS install partition and X: was the Recovery environment.  I had been trying all of these steps on the X:\, When I changed to the D:\ I was able to find the section of the pending.xml that thiswoot referenced (and I found the reboot file).  I removed the lines, and rebooted.  It gave messages about failing and rolling back the SP, but when I go to windows update it shows SP1 as successfully applied.  Is anyone else seeing this?

It is time to stop publishing SP1.

This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.

The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.

 

On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.

Company machines are less affected, but they failed too.

And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.

 

Please: Stop SP1, tame that bitch, release SP1a.

 

hi ,

what people need to do is understand what they are talking about , .... and follow instructions ! half of the comps are infected with who knows what and then they wonder they cant install anything ?

there are people who install it on vista , .....

now if people first take a look at whats inside sp 1 , maybe they would see that its not that whats causing problems , ...

on the other hand are all the computers that have no problem what so ever , ...

1000 plus and only two errors , one due memory burned and one due to power loss , .... both fixed within the hour , ...

but there is no forum for people who have managed to succeed , ... !!

oh and both under all four seven versions !

have a nice day

And until you call in, it won't happen.  They are getting cases on this.  And furthermore some machines go through just fine.

Posting here is not enough.  Call 1-800-Micrsoft and open a case.  State that you are having problems with a service pack.

They will issue a fix once they understand what the problem is but without data points of "why" they can't fix.

It is time to stop publishing SP1.

This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.

The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.

On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.

Company machines are less affected, but they failed too.

And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.

Please: Stop SP1, tame that bitch, release SP1a.

YEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!

This method works without Safe Mode, without backups, without System Restore, without DISM, and without a Windows 7 DVD repair disc.

INSTRUCTIONS:

01. Reboot your computer while it's starting up.

02. When your computer starts up again, choose the option "Launch Startup Repair" 

 --> PIC: http://notebooks.com/wp-content/uploads/2011/01/Recov-1.jpg

03. When the Startup repair starts, click cancel.

04. After you click cancel it will show a box. Click "Don't Send" 

 --> PIC: http://i52.tinypic.com/xgjriw.png

05. Click the link "View advanced options for recovery and support"

06. In the new window click Command Prompt at the bottom.

 --> PIC: http://i51.tinypic.com/50imu8.png

07. In Command Prompt type this and press enter: %windir%\system32\notepad.exe

08. Notepad will open. In notepad go to File-->Open.

09. Change the type of files notepad views from .txt to All Files (see pic)

 --> PIC: http://i51.tinypic.com/35nd74z.png

10. Now in Notepad, go to C:\Windows\winsxs\ (or whichever drive Windows is installed on)

11. In that folder, find pending.xml and make a copy of it

12. Now open the original pending.xml (it will load really slow because the file is huge)

13. Press CNTRL+F and search for the following exactly: 0000000000000000.cdf-ms

14. Delete the following text (yours will be a little different):

<Checkpoint/>

<DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>

<MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>

--> PIC: http://i54.tinypic.com/adzpzp.png

Your PC might not have all 3 sections of code (<Checkpoint>, <DeleteFile>, <MoveFile>). Just make sure you delete section "Checkpoint" and whatever other sections have "000000000000000.cdf-ms". They will be right next to eachother.

15. Save the file, close notepad, close command prompt, restart your computer.

Once your computer starts up, do a normal startup (it may stall for 5-10 minutes at the "starting windows" screen, but leave it going) and the Service Pack will install some more stuff and restart a few times and then everything should be working! For some people, it reverts everything and cancels the service pack installation. For other people, the service pack installation completes. Either result is fine.

If you have any problems with the steps let me know or message me on Windows Messenger - thiswoot@hotmail.com

Feel free to send me a donation through paypal if this was helpful.  :)

The same commonality here - the only failed installations were those who used Shutdown to install the updates

Your are the man!!

We are an IT support company and we has a shock this morning.

But this fix it awesome.

Yes this works.  Thanks - salvaged a 64 bit AMD processor laptop

I have uploaded all the files but SYSTEM hive. They are in my public skydrive: http://cid-495f78ba5c771cf6.office.live.com/browse.aspx/.Public

A big thanks to thiswoot. We have 40 Win 7 64-bit computers. The calls starting coming at 7am this morning. Six of them had this C0000034 error from the SP1 update overnight. It apparently only happened to users who tried to run the update on their own and not wait for automatic updates in the middle of the night. There's no way I could have figured this out on my own. You saved my butt! Thank you!

We had today the same issue this morning that some customers gave us a call reporting machines not working anymore and hanging at "... step 282 of ..."

the solution from thiswoot worked for 3 of the affected machines - thank you for that, because of people like you other people can at least work again with their machines!

what I can confirm is that only 64Bit machines where affected and that it seems to be true that the problems only occured at machines that were shut down yesterday with the install updates and shutdown-option (one of our customers has a workstation that should run 24/7 - this one installed the sp1 correctly, although theres nearly exactly the same software on it like on the many others that crashed today).

Altough I´ve a problem with that solution and that is simply that the installation goes on until stating installation error - reverting changes - then users can login normally - the first one sees the sp1-install indicating that there was an installation error and that sp1 was not installed correctly although under computer properties it says windows 7 pro SP 1

So it would be great to find an answer to the question if theres now allright with the machines or not (although most functions needed in daily business life seem to work correctly as I could see on the first of the 3 "repaired" machines)

btw: I also tried the solution with the dism-command - it worked on none of the affected machines

I haven´t tried the method with applying an old registry-backup to the system (which in particular seems to be the same as the method removing the poqexec-key from registry) - but as it seems it leads to an 3/4 installed sp1 not able to reapply the update manually

Today I´m really embarrassed on microsoft since I called them in the afternoon looking at the dead computers of our customers letting me tell from ms that they want plenty of € before they help me to get things back running (although the ms worker told me that they´ve plenty of problems with sp1)!