UPDATED BLOG INFORMATION FOR THIS ISSUE IS NOW LOCATED HERE: http://blogs.technet.com/b/joscon/archive/2011/03/16/new-information-on-error-code-0xc0000034.aspx
This blog is being left up for information only
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:
• Registry hives. COMPONENT, and SYSTEM• CBS log directory• Sessions.xml• Poqexec.log• Pending.xml• “Dir /s /b” Directory listing of c:\windows\winsxs
Additionally, I would like anyone who has a machine "in state" and can get logs off from WinRE to grab their \Windows\winsxs\FileMaps\$$.cdf-ms and the WindowsUpdate.log file.
Hope this helps.
Did Option 2 and now I'm getting a config_initialization_failed bluescreen at boot.
Try using Startup repair in WinRE to see if it gets you by that error.
Tired it too on 2 systems and got BSODs
Tried repair: no errors found
Tried sfc /scannow: no errors found
i have ~15 affected PCs
All are German Installations
All are x64
Some updated SP1 successfully
Add the following as a last line to the Option 2:
Reg unload HKLM\BaseSystem
Boot with the win7 install DVD with CMD
Verify the date of the registry hives: system, software under
After than rename the current hives
ren system system.old
ren software software.old
copy system C:\windows\system32\config\system
copy software C:\windows\system32\config\software
Reboot the System.
Now the system starts properly.
So this is the same like here?
Can you change the "applies to" so that Windows 7 is mentioned there, too?
We're working on new content for it now Andre.
Hmm... Cannot install, uninstall or repair W7 x64 SP1 after using any of the solutions presented here...
Have 5 windows 7 Pro machines down with same failure received with auto Update of SP 1
If you have a solid way to reproduce this issue, please post your exact OS+Application+etc+SP1 build steps so that the folks at Microsoft can investigate.
What is a solid reproduction of failure? Is 5 examples enough?
Windows 7 pro, Auto Update of Service Pack 1, Fatal Error C0000034 applying update 282 of 116,496
affected machines will not restart and error messages all exactly the same.
Have a case open with Microsoft now.
That's not the case for many people, most are installing this is just fine.
@John - as joscon mentions only certain folks are seeing this issue. Thus, it would help to know what is unique about the particular installs hitting the problem. i.e. what other than the base OS (and installed from what media), features, etc. are present. What is the minimum amount of configuration from the base Win7 install which is required to reproduce this issue? If such a factor can be isolated and the issue reproduced this makes for a much quicker resolution.
Also, if you are working with Microsoft now, try providing a disk2vhd created image of a machine that if upgraded to SP1 will reproduce the issue on demand.
It is surprsing that the development team of a corporation as huge as MS repeating a mistake from Vista SP1 to Win7 SP1 as evident from Andre's KB... I seriously dont know what to say..!! I am concerned in wanting to kw if this is hitting the Server versions as well (2008 R2).. ??
ok, the KB article was updated to Windows 7, too.