Tuesday night WSUS pushed SP1 out to my win7 machines -- had one x64 laptop boot into "Fatal error C0000034 applying update operation 282 of 116278". I've done so much to the machine at this point I don't know if I remember the exact order of things, but I think the following is close: Used http://answers.microsoft.com/en-us/windows/forum/windows_7-system/fatal-error-c0000034-on-boot-after-service-pack-1/5f7127e8-9887-4f01-aaa5-9729b69544b7 to get it booting again, ran sfc /scannow and the readiness tool (http://www.microsoft.com/downloads/en/details.aspx?FamilyId=914fbc5b-1fba-4bae-a7c3-d2c47c6fcffc&displaylang=en). Re-ran SP1 installation which then appeared to install correctly, but after a reboot system does not report SP1 as being installed and windows update continues to report that SP1 needs to be installed. Attempts to re-install SP1 now fail: complete SP1 installation package (windows6.1-KB976932-X64.exe from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda) says "The Windows 7 Service Pack Installation cannot proceed until your computer is restarted.", and windows update fails with error code 80070BC9.
Any help would be greatly appreciated. Thanks.
We have the exact same issue on a significant number of HP desktops running Windows 7 Pro 64 Bit. We are at the exact same point where SP1 won't install, uninstall or show as installed correctly. It disabled loads of PC's this morning after being pushed by WSUS.
For those impacted on this thread can you find these logfiles on your system and send them via skydrive to e_bitzie-at-hotmail.com?
1. Registry hives. COMPONENTS, and SYSTEM
2. CBS log directory
6. “Dir /s /b” Directory listing of c:\windows\winsxs
Please this is a high priority at Microsoft and they need to see these log files. And ping me at susan-at-msmvps.com
Experienced pretty much the same issue:
Had three Win 7/64 Ultimate systems receive SP1 via WSUS last night. Results were as follows;
System 1: Dell Precision M6500 Laptop / OEM Win 7-64 Ultimate Installation / Failed with "Fatal Error C0000034 applying update operation 291 of 122443"
System 2: Dell Latitude E6510 Laptop / OEM Win 7-64 Ultimate Installation / Failed with "Fatal Error C0000034 applying update operation 282 of (failed to record this)
System 3: Dell Precision T3400 Workstation / Self Installed Win7-64 Ultimate / Service Pack 1 installed without errors.
I used the remedy posted by poster "thisWoot" at the link below to get systems 1 and 2 back to a bootable state. They are now apparently functioning fine except that: SP1 appears to have been rolled back with the result that the System Information screen indicates that SP1 is installed; Control Panel / Programs and Features shows that SP1 is not installed (no entry for SP1 which typically shows as KB976932); and, just to add to the fun, WSUS thinks SP1 is installed.
I have not attempted an SP1 reinstall on either of the failing systems but would expect a failure along the lines of the original poster.
For what it's worth, all the above systems were running Symantec SEP 11.0.5 and all have Symantec BESR 2010 SP2 installed.
I spent the better part of six hours messing around with this today. I can only say that I am glad we ran into this SP1 issue before shifting any further systems from XP.
As an aside, I ran SP1 direct from Windows Update on a Win 7/64 Ultimate VM hosted by a Hyper-V 2008 R2 system. This ran without problems.
I thought I would add an update:
As I eluded to above, this machine appears to be in a "torn" state similar to those that followed the "pending.xml" fix in http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/1c9a7151-b48c-4a98-aae7-a4b82682ea8e. SP1 will neither uninstall or install. WSUS reports it has having a failed update.
I am still awaiting a resolution...
Recently there was an issue where Win7 sp1 was put on WSUS and then due to default settings in SBS, it was automatically applied. Depending on if it was installed with other updates, in some cases it failed miserably leaving you with a "C34" error (see blogs below for references).
Many of you then googled and found references to editing the pending.xml file which got you immediately back in business, but put the system in what is now called a 'torn' state, i.e. 1/2 rtm, 1/2 sp1.
To get a feel of the true impact I'd like to find out the following. Can you please email me at susan-at-msmvps.com with the following information?
How many PCs under your control were impacted?
How many MS support cases did you open?
Thank you in advance for this info.