New information on error code 0xc0000034

Artikkeli
03/16/2011

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 and Windows 2008 R2. The information in this post applies to Windows 2008 R2 and Windows 7 ONLY and should not be used on other Windows installations.

The KB is located here: https://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 registry or pending.xml workarounds noted in the following blog entry and are in a torn state (ie. system will not update to SP1): https://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.

IMPORTANT: The Windows 7 / Windows Server 2008 R2 Service Pack 1 updates available on WSUS have been revised to ensure that these updates are installed exclusively. We are making this change in response to the issue described in KB975484 . Previously, Service Pack 1 could be installed at the same time as other updates. While this change does not fully resolve the issue, it will help prevent it from occurring. Note that users must also reboot their computers after installing Service Pack 1 and before scanning for or installing other updates.

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

Comments

Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003

Yes, you can hit this without WSUS
Kinda. It's not that its too big, but if you have other updates that have pending files, its best to reboot before installing the service pack to make sure they're cleaned up.
It's covered in the KB. Basically its what I have already said, you can hit a problem with prior pended updates and a cooresponding shutdown event that can lead to this
No. Intel's flaw was an architecurally based flaw that caused potential data loss and hardware degradation (NOTE: my summation, see Intel's documentation for actual info). While I know that this isnt optimal, the fact is that these issues are fairly small in total and dont affect the broader Microsoft OS install base. The SB flaw affected ALL Intel motherboards.

Anonymous
January 01, 2003
Thanks Drew, thats a good collection of all of the information out there.
Anonymous
January 01, 2003
@Jay; In your case I would reinstall. I dont know when, or if, we'll have a fix for the torn state systems.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@Chucko; Still considering options there, but no news for now.
Anonymous
January 01, 2003
No, the vbs script allows for the service pack to finish completing properly on machines that are in a C34 state.
Anonymous
January 01, 2003
Ben; Thanks for the feedback. We know the most common conditions that lead to the service pack getting into this state, namely a push from WSUS with other updates already pending, coupled with a shutdown event. We're still looking at options for those in torn state but we do have good content on how to handle the problem in the event it should occur at some point. I'm glad that you were able to get out of the issue properly and will make sure that others see your comments. --Joseph
Anonymous
January 01, 2003
@John; I dont have a good answer for those systems right now. Some users have reported being able to get SP1 installed after using the pending.xml workaround but many are in torn states. If you're one of those in the torn state your only current options are a rebuild or parallel installation. Once I have more information on other possible options I will post them here. --Joseph
Anonymous
January 01, 2003
@Ottmar; Great question. No the changes to that article have nothing to do with the C34 issue. That was repackaged and re-release of the files to fix a small dependency issue. The two were'nt related.
Anonymous
January 01, 2003
It wouldn't be because of this error Shyam, this issue has been resolved. Most likely you're seeing a problem accessing the BCD store. You can ask this on the support forums and someone there can help you.
Anonymous
January 01, 2003
@Stephane: Yes, the standalone should be fine. Additionally, marking the service pack exclusive in WSUS and setting the installations to reboot should also prevent this from happening.
Anonymous
January 01, 2003
Jay; You're probably also in a torn state now because the registry that you ran the script against wasnt the same as the registry with the problem because you moved it.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@Steve; Thanks for the comment, I appreciate it. I try to keep this as open and honest as possible, as well as allowing everyone to voice their concerns and complaints in a way that you'll know gets heard (if only by me at times).
Anonymous
January 01, 2003
Thank you for your answer, joscon. We just restored a backup and applied the Method 1. Then, the SP1 continued with the rest of the steps. The problem is that one of our DC has the same problem. Could you explain what the script does? Do we need to re-install any specific update? Maybe uninstall and then install again SP1?
Anonymous
January 01, 2003
@ ALL: Ok, so I was talking with the product group today and while you dont have the ability to mark the service pack exclusive yourselves, what you can do is install ONLY the service pack when you push it via WSUS, it will have the same affect.
Anonymous
January 01, 2003
Thanks Ben, again I appreciate the feedback. Rest assured that the product group does read this feedback and take it seriously, so this isnt falling on deaf ears (even if the outcome isnt what you might prefer).
Anonymous
January 01, 2003
@Matt; then you should be fine running the script. Let me know the results please.
Anonymous
January 01, 2003
@John; Unfortunately no. Torn states are very random in where the actual problem occurs. That's why this isnt just a simple one fix to rule them all type scenario.
Anonymous
January 01, 2003
@Andreas; Yes, the exclusive tagged SP1 installer should not result in C34 issues on your installations. As always, you should test the installer inside of your environment and then roll it out to your larger infrastructure.
Anonymous
January 01, 2003
I posted about this today. Our only supported method for torn state systems at this time is a rebuild.
Anonymous
January 01, 2003
@Hamlet; Sorry, not at this time.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@Hamlet: The script basically modifies the way the pending operations queue is processed when the machines enters the C34 state @ffwiki: I dont have anything new for the pending.xml workaround right now. I'll let you know if that changes.
Anonymous
January 01, 2003
Hello, Joseph. We already recreated SetupExecute entry and W2K8 R2 booted successfully. But SP1 installation has failed and does not allow us to install. Is there any way we can resume/restart the installation of Service Pack 1? We have "C:Windowswinsxspending.xml.01cbe013a8260ae4"
Anonymous
January 01, 2003
@Matt; Our script is safe if you're currently in a C34 state.
Anonymous
March 17, 2011
joscon, do you work on a Method to fix Windows in a faulty state after the pending.xml workaround?
Anonymous
March 17, 2011
Hi joscon, I've just noticed that the KB mentions modifying the pending.xml file. Is this what we should be avoiding, or is using your script safe?
Anonymous
March 17, 2011
@Matt: you should avoid deleting the checkpoints in the pending.xml file. the script does other stuff, which is official safe.
Anonymous
March 17, 2011
Thanks for the reply. I've not touched it yet so it is completely fresh from the attempted SP1 install.
Anonymous
March 17, 2011
Will do.
Anonymous
March 18, 2011
I applied the fix to a machine yesterday, and it worked fine. However, I am about to enable this update in WSUS for approx 20 machines, now. Can we expect a fix to be launced, either an updated SP1 or a hotfix to apply prior to approving SP1? I would like to avoid the need to travel to the customer site Monday morning to fix broken machines...
Anonymous
March 18, 2011
Lars is right! I would like to ask the same question. Unfortunately I'm responsible for about 200 client machines and I'm scared to update these using our WSUS mechanism. Are there plans to create a revised version of SP1 anytime soon?
Anonymous
March 19, 2011
You might find this blog post an interesting read: grandstreamdreams.blogspot.com/.../quick-tip-fatal-error-c0000034.html
Anonymous
March 21, 2011
The comment has been removed
Anonymous
March 21, 2011
Joseph - Thanks for your first initial response, very timely! Just out of curiosity, do you know what's torn? Is it possible that re-appending the changes to the pending.xml file and re-starting the installation might do the trick? Or is that file removed once the roll-back/failed install is done? Thanks again, John J.
Anonymous
March 21, 2011
Le Sigh. Thanks Joseph.
Anonymous
March 22, 2011
At least the stand-alone installer has been working fine for us, and I've been able to update our WIM images to SP1. I think I'll not be approving the WSUS SP1 update, and install manually instead (we only have about 10 Win7 machines and about 5x 2008R2 VMs).
Anonymous
March 22, 2011
In blogs.technet.com/.../new-information-on-error-code-0xc0000034.aspx you've recommended restarting the machine after SP1 has been installed/offered via WSUS. Does the change documented insupport.microsoft.com/.../en-us for March 15 for Windows 7 SP1 ("Packages have been updated to address a known issue") have anything to do with the "C34 problem"?
Anonymous
March 22, 2011
What is MS going to do to help us fix the PC's that are in a "Torn State"? I'm sure hoping that the response to all of this is not an OS reload.
Anonymous
March 22, 2011
I haven't tried any solution yet, and I've tried to read as thoroughly as I could...but still couldn't come to a conclusion. Is that because there isn't one? I see the Microsoft article with the .vbs script...but that will still leave it in a torn state, correct?
Anonymous
March 22, 2011
OK, awesome, thanks for all the help. Just in case someone else out there hasn't done any "fix" yet and is wondering what the best thing to do is...support.microsoft.com/.../975484 and run that .vbs script. This worked for me and apparently I am not in a torn state as well. I will say that I had TrueCrypt on the system and I couldn't ever access the D: drive (or C:) drive where Windows was installed (instead I had the X: drive...which won't work). I used the TrueCrypt recovery CD for the laptop, decrypted the drive, booted to the Windows 7 CD, then followed the steps in the KB article.
Anonymous
March 23, 2011
The comment has been removed
Anonymous
March 23, 2011
The comment has been removed
Anonymous
March 23, 2011
The comment has been removed
Anonymous
March 24, 2011
Susan! Thank's! Exactly my view of this! This is not good for our and MS reputation in the SBS market...
Anonymous
March 24, 2011
I agree with Chucko. I followed the first iteration of the KB975484 release and had to use option 2 on multiple 64-bit Windows 7 systems. I hope and trust that Microsoft will find a solution to get these PCs out of the torn state, or at least tell me when they have given up all hope and that I will have to reinstall from scratch. I am a small business owner without an "IT department" and it will take me several hours per PC to "reset them." I am willing to devote the time to do this, but I will not do so until I have clear instructions from Microsoft that they have no other solution. Thanks. --PGL
Anonymous
March 24, 2011
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 urls below and this blog 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. Can you please email me back with the following information? How many PCs under your control were impacted? How many MS support cases did you open? Email it to susan-at-msmvps.com I will keep the info confidential, but would like to get a greater idea of the impact. Thank you in advance for this info. blogs.technet.com/.../error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspx blogs.technet.com/.../why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx blogs.technet.com/.../new-information-on-error-code-0xc0000034.aspx
Anonymous
March 25, 2011
I apologize if this question was asked before. What if I didn't approve SP1 on my WSUS yet but of course plan to do in the future. Will there be a new SP1 without that problem or will there be a security patch which I should install on all clients before rolling out SP1 on my WSUS?
Anonymous
March 25, 2011
The comment has been removed
Anonymous
March 25, 2011
To Wolfgang - you need to ensure that Win7 sp1 is approved all by itself so that it and only it can be installed. If you let it install with other updates chances are this issue will still occur.
Anonymous
March 25, 2011
I had it happen on one machine that I told to install updates and shutdown. Its x64 Win7pro using WSUS for updates. The vbs script did repair it. But I am curious. The description says the POQ operations appear twice in the pending file, so the second one fails. And the VBS script removes all (2 in my case) POQ nodes. So doesn't that mean the POQ instructions are never run, instead of run once, which I assume is what you would want to do.
Anonymous
March 25, 2011
@susan: Thank you for your answer. Unfortunately that means I can't ever roll out SP1 via WSUS. I can never be sure that all of my 80+ Win7 Worstations in the domain are at a 100% patchlevel.
Anonymous
March 28, 2011
Hello, Thanks for the attempted fix. I have a couple of machine hit by the issue. Hopefully, none where servers. The first machine ended up in thorn state since I really had to get it working. I reinstalled it completely. The second machine is a bit different: it's the machine from our demo room and it has a software installed for ensuring it always remains in the same (comodo time machine). I tried to fix it using the script but, unfortunately, there seem to be no "pending.xml" file in the winsxs folder. I was able to get it back in working state by restoring a snapshot (using CTM) and I'm back in pre-SP1 state. Questions: I have a farm of 2008R2 servers that haven't been upgraded to SP1. Is installing the "standalone" SP1 safe ? It'll be tedious work but stull less than rebuilding them or backing them up, restoring the latest snapshot and the the data back on them. Or can we expect a fixed release of SP1 soon ? Finaly, I have a snapshot of the demo room machine that fails when installing SP1. I have a snapshot of that state (through CTM). Would it be helpful for me to contact our local support (I'm in Switzerland) for providing that image ?
Anonymous
March 28, 2011
Regarding "marking the service pack exclusive" in WSUS. From the GUI (Version: 3.2.7600.226) I don't see the ability to set an approved "hotfix" exclusive? I haven't found any "hits" in the WSUS help or Technet documentation on the ability to set "exclusive" option for an update. How does one set the "exclusive" option for an update in WSUS 3.2?
Anonymous
March 29, 2011
The comment has been removed
Anonymous
March 30, 2011
3 torn machines here.
Anonymous
March 30, 2011
To MarkM. I'm asking around on that setting of exclusive as well. I'm not sure that's something we as WSUS admins can do. I see "exclusive" and "mandatory" as flags that Microsoft put in, not something I can control? Still checking, will report back.
Anonymous
March 30, 2011
Got word back. We don't control the exclusive flag. Only Microsoft does.
Anonymous
March 30, 2011
I am kinda amazed that something as big and important as a service pack isn't "exclusive" by default. The only thing I can think of that would make it possible to set the exclusive flag is to connect to the WSUS internal SQL Express database. But afaik any setting you change will be reset on the next synchronisation with Microsoft. What I don't understand is why MS isn't releasing a fixed SP1 or maybe a preliminary patch that would fix this problem.
Anonymous
March 31, 2011
I have a similar question to the most recent posts. It is very tricky, you might have to modify the GPO to allow reboots, and to control the install behavior you would need to have a very clean set of approvals that only includes an approval for Windows 7 SP1, and you’d for sure need to set an installation deadline on the approval for SP1. Please let us know if Micorosoft is working on an improved installed or testing a hotfix.
Anonymous
March 31, 2011
Tell the product team to post up exact step by step instructions please. The audience that got nailed the most with this didn't set up WSUS , the Small Business Server setup did it for them. Our default WSUS are set to automatically approve security updates, critical and definition updates, and service packs on workstations. If you have a functioning WSUS that is auto approving definition updates you can't guarantee that the only thing being deployed is Windows 7 sp1.
Anonymous
March 31, 2011
Furthermore as many c34s as we had, does the product team really want to take the risk of this not happening to some other large entity that isn't aware of this issue and doesn't install it all by itself? Really?
Anonymous
March 31, 2011
(sorry me again) I have forefront in my office. I get def updates all the time. I have no way short of unapproving all updates to ensure that SP1 will be deployed all by itself. The only way I can see that this is possible is building a specific WSUS patching OU, moving the computer into that OU for purposes of applying the service pack and then ensuring that only that sp got approved for that patch grouping. But one has to be warned that that will break the integration of WSUS in the SBS 2008/SBS 2011 console so it would need to be communicated how to do this and then how to put it back. Unless I'm blind and missing an easier way to do this, it's not as easy as they are implying here. WSUS doesn't push patches, the clients pull them.
Anonymous
April 01, 2011
The comment has been removed
Anonymous
April 01, 2011
I should have mentioned that trying to use a System Restore Point was futile. Apparently the attempted installation of SP1 wiped out ALL restore points, so that's not an option.
Anonymous
April 01, 2011
I had the C34 state and am now in the torn state. When I used the Pending.xml change I checked the folder listed in the XML file and found there were zero (as in NO) files in that folder. The instructions in the XML file were to move files from that folder to their final homes. The error itself occured on the second reboot of the server so I suspect that all the files had been moved on the first pass but the pending.xml file wasn't updated before the second restart. This was the only WSUS update being done at the time and I was logged in as Local Administrator and restarted as soon as the update requested the restart.
Anonymous
April 03, 2011
The comment has been removed
Anonymous
April 04, 2011
Joseph, thanks for the answer, but I must stress this: MS should, knowing that such an error can occur, just pull SP1 out of Windows Update (is, or is that not different from WSUS, because this occured on a stand-alone-desktop only locally administrated) until you have found a way to make sure nobody gets into that mess in the first place. Having a fix is fine and good, but the fix is to prevent a fix being necessary. Pulling SP1 from WSUS until such a solution is found, is the only responsible way of going about it, (imho) Greetings, Ben
Anonymous
April 05, 2011
@Ben joscon indicated above "We know the most common conditions that lead to the service pack getting into this state, namely a push from WSUS with other updates already pending, coupled with a shutdown event." Taken at face value, that suggests the issue is at least as much related to WSUS than SP1, so maybe it's WSUS that needs the hotfix more than service pack. However i note you had the problem on a standalone machine. You have a point about MSFT pulling the SP from WU until the issue is rectified, but to some extent that would be making assumptions about the source, or root cause of the problem. Joseph, a few questions on this.

Could Ben have got the C34 condition on his non-WSUS machine due to existing pending updates?
Why does the service pack install when pending updates exist? Isn't a SP too big and fundamental to risk queueing up with other updates? Shouldn't the installer ideally prompt the user to restart first?
Are you in a position or aware if MSFT intends releasing information that explains the root cause, or causes, of the code 0xc0000034 issue?
What is fundamentally different about this issue with SP1 and the silicon issue discovered in the Sandy Bridge chipsets that resulted in Intel withdrawing the products and issuing an update, asap? Shouldn't MSFT essentially be doing with SP1 what Intel did with their new chipsets?

Anonymous
April 05, 2011
The comment has been removed
Anonymous
April 05, 2011
I'd argue the admin isn't doing anything wrong. No where has the admin been told that no longer is service packs exclusive like they were in the past. So regardless of the fact that we had this SP as flagged to auto approve it was honestly expected that Win7 sp1 would behave like all other service packs before this and install all by itself. No service pack before this one has behaved in this manner.
Anonymous
April 05, 2011
Windows 7 deletes all System Restore Points upon reboot: support.microsoft.com/.../en-us Interesting... wonder if that's the trigger for the lack of no restore points reported by everyone?
Anonymous
April 06, 2011
HI. I had the same error with 0xc0000034, the first thing we trayed was to the solution with renaming files in system32config. Ex. ren default default.old and then copy default c:windowssystem32config. This helpt us to boot windows normally, but still no luck installing servicepack. We then ran the script from microsoft, and was able to install the servicepack. Servicepack is now listed as installed when you look in installed updates, but when you search for updates it still wants to install it, and if you try so it comes error 80070BC9. If you hit pause+break its not listed as servicepack 1. If i try to uninstall the servicepack i got error message: An error has occurred. Not all of the updates were successfully uninstalled. Any idea what I can do? JAY
Anonymous
April 06, 2011
@Bitz "No service pack before this one has behaved in this manner" Actually, this same problem has been happening since Vista Sp1: social.technet.microsoft.com/.../4491fe25-be44-430e-a384-fb58c5da5ad0 At least in XP, WU wouldn't let you install the SP's with any other updates.
Anonymous
April 06, 2011
Vista was the same. While prior versions may have c34'd, this is the first that is not marked as exclusive and thus potentially more c34's.
Anonymous
April 07, 2011
Joscon thanks for your reply, We trayed to move back the files to get back to the first error(0xc0000034) before we ran the script, but then windows just would not start up, hang on black screen. We then replaced the system files again and ran script, so probably yes we are in torn state. Do you think there will come a solution for "torn state" soon? do not have time to wait much longer so will probably go for a reinstall. Jay
Anonymous
April 07, 2011
Microsoft better have a fix for the torn state. I have 122 machines in that state right now and don't have the manpower to re-install all of them. It took me months to deploy Windows 7 and now Microsoft has come in and kicked over my sand-castle with a buggy SP1 deployment. Come on Microsoft. Fix this already. Don't hang us out to dry.
Anonymous
April 07, 2011
FYI: According to support.microsoft.com/.../en-us KB976932 aka SP1 for Windows 7 and Windows Server 2008 R2 will be marked as exclusive install in WSUS starting 12th April 2011
Anonymous
April 08, 2011
Yipee, as of 7. april this still managed to break 2 systems. And cause our localized ms tech page had the solution no3 that was broken (registry rollback way) I have 2 torn systems here now.
Anonymous
April 08, 2011
@BitBucket I hear you man, and Microsoft wonders why businesses are leary of installing their products before the first service pack. Well now we all get to be leary of installing a Service Pack too! I am still waiting on a fix for the torn states on our computers...
Anonymous
April 08, 2011
Bitbucket, Neikius and Phil? Can you ping me at susan-at-msmvps.com and I'll set you up with a free support case. Especially you bitbucket. I need your 122 broken machines to showcase to Microsoft this issue needs attention.
Anonymous
April 10, 2011
Echoing others on this forum: I wish I had read this much earlier. Failed PCs throughout my client base including my own internal organization. As a service provider, this will cost me (and my clients) dearly. I wonder who I can invoice for this little gem?
Anonymous
April 13, 2011
The comment has been removed
Anonymous
April 13, 2011

Hyper-v VM Server 2008R2
Hyper-v does not support USB
running notepad and saving the scipt to c: produces the error Script.vbs(25, 1) msxml3.dll: The parameter is incorrect. Have any ideas on how to work around this issue?

Anonymous
April 13, 2011
@Jesper You've seen and read blogs.technet.com/.../fcs-upcoming-solution-for-installation-issues-with-march-2011-update.aspx as well, true?
Anonymous
April 14, 2011
The comment has been removed
Anonymous
April 25, 2011
Still no resolution to the Torn State?
Anonymous
May 06, 2011
Hello Joscon, any news from companies deploying Windows 7 SP1 after April, 12th, where the SP was marked exklusive? Will the update work now if we would start with a fresh SP rollout?
Anonymous
May 06, 2011
Anything more on a fix for torn systems? We have 16 systems withthis issue also and cannot at this time rbuild all of them.
Anonymous
March 27, 2013
The comment has been removed

Jaa

New information on error code 0xc0000034

Comments

Lisäresursseja