New information on error code 0xc0000034

New information on error code 0xc0000034

  • Comments 6
  • Likes

We have updated the KB that deals with this error to include a new script to get users out of the 0xc0000034 condition and allows SP1 to install properly. This fix will only work for users who are currently in a 0xc0000034 state after applying Service Pack 1 for Windows 7. This script is NOT for use on Windows 2008 R2.

The KB is located here: http://support.microsoft.com/kb/975484

I want to use this post specifically as a means to track how this is working for users and what issues (if any) you might encounter when running the script. 

Please note, this will NOT WORK for users who have used the pending.xml workaround or have used the SetupExecute registry entry noted in the following blog entry and are in a torn state (system will not update to SP1): http://blogs.technet.com/b/joscon/archive/2011/03/09/error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspx

NOTE: It SHOULD work on machines that deleted and recreated the SetupExecute value and are still getting the 0xC0000034 error on boot.

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:

  • \Windows\system32\config\COMPONENT and SYSTEM (files)
  • \Windows\Logs\CBS\*
  • \Windows\servicing\sessions\sessions.xml
  • \Windows\winsxs\poqexec.log
  • \Windows\winsxs\pending.xml
  • > dir /s /b %windir%\winsxs > %computername%_winsxs.txt
  • \Windows\WindowsUpdate.log

Joseph Conway
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • What is the reason for this issue? KB doesn't mention it. How can we prevent it from happening?

  • Thanks for the info.

    It would, however, be more helpful to supply the full paths to the files that you want, rather than just the file names.  That would save us mere mortals some time digging around to find them.

  • \Windows\system32\config\COMPONENT and SYSTEM  (files)

    \Windows\Logs\CBS\*

    \Windows\servicing\sessions\sessions.xml

    \Windows\winsxs\poqexec.log

    \Windows\winsxs\pending.xml

    > dir /s /b %windir%\winsxs > %computername%_winsxs.txt

    \Windows\WindowsUpdate.log

  • @Drewfus: Thanks for clarifying the paths for the files. Live blog has been updated.

  • What is the use of this post? I want the more details of this..Can u give the Explanation?

    blogs.technet.com/.../askcore

  • Hello, what can I do if error 0xc0000034 , 243/98576 occure on my friends computer? Its booting but windows doesnt come up...

    He bought computer recently from ebay and it has original windows and recovery disk. (_0000000000000000.cdf.ms).

    How and where can I try following  informations?

       \Windows\system32\config\COMPONENT and SYSTEM (files)

       \Windows\Logs\CBS\*

       \Windows\servicing\sessions\sessions.xml

       \Windows\winsxs\poqexec.log

       \Windows\winsxs\pending.xml

       > dir /s /b %windir%\winsxs > %computername%_winsxs.txt

       \Windows\WindowsUpdate.log