Microsoft Enterprise Platforms Support: Windows Server Core Team
EPS Team Blogs
Product Team Blogs
I've seen several reports now of the following error (or something similar):
!! 0xc0000034 !! 142/53007 (_0000000000000000.cdf-ms)
Note If you restart the computer, you experience the same error message.
If you're hitting one of these errors, you have a few options depending on the OS you're using.
Option 1 (Win7 client only): Use a system restore point to recover the system
Option 2 (Win7 client and 2008 R2 server): Delete the poqexec entry
NOTE: I've seen several people that have called in and said that they cant find the values referenced in this blog once they have booted into WinRE. Please remember that when you are booted into WinRE you are booted into a RAMDRIVE. This means that when you open the registry editor you are actually seeing the hives from WinRE and NOT the ones from Windows. When you need to make sure you are loading the system hive from your Windows drive and not WinRE.
If this does not get your installation up and running there is another available workaround posted in the forums here: http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/1c9a7151-b48c-4a98-aae7-a4b82682ea8e#bcabda57-7338-499f-aee2-d708e76df315
It is not recommended that you edit the pending.xml but this may get your machine booted properly. If you are desperate, feel free to try this at your own risk. I wrote about why you want to be careful with this here: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
If you're planning on opening an issue with SP1 for this, please try and gather the following information before you call, it will greatly help us in working on the issue:
Hope this helps.
Joseph Conway Senior Support Escalation Engineer Microsoft Enterprise Platforms Support
Even after doing this fix the system is still in unstable stage.
Impossible to install Win7 SP1 thereafter. It will say that some Windows Update components are missing. Trying to fix this with System Update Readiness Tool doesn't success. The only way to really fix all the mess done by the update is to do what Microsoft call a "in-place system update" which - to say the least - really pissed off us.
This is unacceptable that deploying SP1 via Automatic update or WSUS broke our systems.
Don't you test in your labs before saying to your customers that the update is ready for widespread deployment and fail proof?
"...when you open the registry editor you are actually seeing the hives from WinRE and NOT the ones from Windows."
When loading registry hives from an offline system, i always use the format:
> reg load HKLM\offline_SYSTEM C:\Windows\system32\config\SYSTEM
That way it remains obvious what hives have been manually loaded, and i never forget the crucial step:
> reg unload RootKey\offline_<HIVE>
Failing to do this will result in hive corruption so bad that you will have to restore from a backup.
Before the official fix was released by Microsoft, I used the pending.xml suggested fix on 20 different computes. I just tried to install the Windows 7 Professional SP1 manually after undoing the change. I am now getting a Catastrophic Failure E_Unexpected. Any help would be appreciated in getting the Windows 7 SP1 fix resolved.
In your instructions for option 2 when deleting the poqexec entry, the registry keys are different between the command line version and the GUI version
Command line "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager"
Should these not be the same?
Specifically, one is deleting the value from the CurrentControlSet and the other is deleting it from the ControlSet001.