New information on error code 0xc0000034

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:

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): .

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


Comments (92)
  1. Susan;

    No worries, fire away, I write the blog so Microsoft can get feedback.  I'm not involved with the WSUS side of our business (as you already know but others might not know) so I dont really know about those decisions and history as to what changed there so I cant intelligently speak to those decisions.

    However, I do know that call volume helps to add fuel to the fire on a hot issue.  Especially when you have the install base we have, it can be hard to see if something is a smaller isolated incident or something much worse.  A one day spike in call volume here could be caused by anything and if those calls stop or slow to a small trickle, then it really does appear to be a "blip" on the radar.  Now, I am not saying thats the case with the C34's but its also true that we didnt see many calls on this internally (and your reasons noted are extremely valid as to why).  I realize based on the feedback that this is more than a blip, but I chose to personally invest the time to be vested in SP1 issues at release so I have a closer perspective to these issues than many.

    As for call volume we didnt get, please gather that data and send it to me so I can get it to the right people and give more impact to this story (number of machines would be helpful as well if possible).  

    Hell, if you didnt call us for support on this issue and want to make sure you're counted just +1 the thread so I can add them up.


  2. 1.  Yes, you can hit this without WSUS

    2.  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.

    3.  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

    4.  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.

  3. Thanks Drew, thats a good collection of all of the information out there.

  4. @Jay;  In your case I would reinstall.  I dont know when, or if, we'll have a fix for the torn state systems.

  5. Correct, if you've done the pending.xml hack, this will not help you out of the torn state.

  6. @Chucko;  Still considering options there, but no news for now.

  7. No, the vbs script allows for the service pack to finish completing properly on machines that are in a C34 state.

  8. 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.


  9. @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.


  10. @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.

  11. 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.

  12. @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.

  13. 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.

  14. @Lars/Roger:  Right now the script will resolve any new C34 states.  I would recommend restarting the machines installed via WSUS rather than shutdown as that seems to allow most WSUS installations to install based on user feedback.

  15. @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).

  16. Anonymous says:

    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?

  17. @ 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.

  18. 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).

  19. @Matt; then you should be fine running the script.  Let me know the results please.

  20. @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.

  21. @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.

  22. I posted about this today.  Our only supported method for torn state systems at this time is a rebuild.

  23. @Hamlet;  Sorry, not at this time.

  24. @Sam;  No one said we're leaving you in an unsupported state, I said we're looking into options for those particular problems.  I dont know what, if any, options there will be.  

    But, to give you my personal take on this since this is my blog….many people are in a torn state because they followed a users newsgroup post.  Most people did not call into Microsoft for support on these issues.  So, to say Microsoft didnt support you on your issue isnt quite accurate.  

    This isnt to say that I dont understand your point, I do.  But, I know how many cases were opened on this issue internally and to say that it was not a high number would be a gross understatement.

  25. @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.

  26. Anonymous says:

    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"

  27. @Matt;  Our script is safe if you're currently in a C34 state.

  28. ffwiki says:

    joscon, do you work on a Method to fix Windows in a faulty state after the pending.xml workaround?

  29. Matt says:

    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?

  30. ffwiki says:

    @Matt: you should avoid deleting the checkpoints in the pending.xml file.

    the script does other stuff, which is official safe.

  31. Matt says:

    Thanks for the reply.  I've not touched it yet so it is completely fresh from the attempted SP1 install.

  32. Matt says:

    Will do.

  33. lars says:

    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…

  34. Roger says:

    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?

  35. Drewfus says:

    You might find this blog post an interesting read:…/quick-tip-fatal-error-c0000034.html

  36. John Jennings says:

    Hey Joseph –

    What if we did the pending.xml fix? (I would've waited for your fix, but his came out first, and I had a boss that was literally drooling down the back of my neck)

    How can we install SP1? Fix for the fix? SP1 updated binary? Completely screwed?


    John J.


  37. John Jennings says:

    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.

  38. John Jennings says:

    Le Sigh. Thanks Joseph.

  39. tom says:

    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).

  40. In…/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 in…/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"?

  41. Chucko says:

    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.

  42. Haven't done anything yet, what to do? says:

    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?

  43. Haven't done anything yet, what to do? says:

    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……/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.

  44. sam says:

    @joscon – Please convey to your superiors/team that the reason many of our machines are in a "Torn State" is because of a faulty/untested/lemon of a service pack from Microsoft. That you are not committing to help us get our machines back to a supported state is bullshit.

    Our machines, in a completely supported environment by Microsoft, failed after installing SP1. When I get to work at 8 am, see almost all the machines are down, and call MS Support to wait on hold for an hour – what am I supposed to do?

    Option A) Let my +200 users wait while the computers are down? (200 users x $20 an hour = a hell of a lot of money) There is *NO* information from Microsoft online regarding the error, the problem, or any possible fix – and I'm still on hold.

    Option B) Google the error, find something that appears to fix the problem, and get my users up and running.

    Those of us who chose Option B need to be supported. To leave us hanging because we tried to fix a problem with your faulty product is unconscionable.

  45. susan says:

    I do not want to shoot the messenger here but please, do not throw out the 'we didn't get calls'.  In this day and age of bing, google, blogs, twitter we use the tools that we are accustomed to.  We search for an answer.  We do not call in because when we call support we go to the first line level and it costs these consultants money to deal with the issue and is vastly ineffiicent to do so.  So we go to the tools we find effiicient these days — forums and searching.  

    While I will grant you that this was a side effect of bad information the original root cause was the change in Windows 7 sp1 behavior in WSUS so that it no longer deploys all by itself but comes down with other patches.  Someone in Microsoft made the WSUS deployers beta testers and didn't tell us.

    So while the "torn state" problem was due to bad advice, it was advice needed to get these machines back in order because someone in Microsoft made the decision to let WSUS release updates like this.  They needed their machines working.  They went to a Microsoft forum where we in the community tell people to go and ask for help.  

    The reason you don't have cases is that customers impacted by this are primarily WSUS servers and a lot of SBS boxes and we don't call support.  Your enterprise customers may not use WSUS and certainly don't have it set for automatic install of service packs on workstations.

    And why do we have that?  Because someone else at Microsoft in the SBS team unfortunately made that the default setting in SBS's WSUS deployment.  Now I will kick myself a bit for not getting out an alert that this might happen, but the ONLY place that Microsoft  "announced" it was going to be on  an obsure KB that lists the content of what might be on MU and WSUS.

    I deeply appreciate your candor and honesty on this blog, an I apologize for the terseness of this response, but please, do not equate lack of phone calls and cases to lack of bodies.

    We do not call.  If you'd like me to get head counts from the people I personally know were impacted and did not call in and set up cases, please let me know.

  46. chucko says:

    I,  for one, followed the first iteration of the KB975484 release, and was a good soldier and only performed the exact instructions to remove the poqexec entry.  I did nothing else, and even commented to the tech that was with me that I wanted to fix this the Microsoft way, not with a bunch of unsupported hacks.

    But these PC's are still in a "Torn State".

    I'm hoping for a positive resolution.  

  47. lars says:

    Susan! Thank's! Exactly my view of this! This is not good for our and MS reputation in the SBS market…

  48. PGL says:

    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

  49. susan says:

    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 I will keep the info confidential, but would like to get a greater idea of the impact.

    Thank you in advance for this info.…/error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspx…/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx…/new-information-on-error-code-0xc0000034.aspx

  50. Wolfgang says:

    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?

  51. Steve Jones says:

    Thank you for this post..  I wish I had found it YESTERDAY, when I was looking for solutions.  Luckily, the impact for me (so far) has just been at home with 2 machines which are backed up by a HomeServer, and are in the process of restoring to Wednesday's backup, so I should be OK.  

    I did spend several hours yesterday investigating, and trying various things with the pending.xml file, and as such, based on what I've learned today, if not for my HomeServer backups, I'd be in trouble with the rest of the gang here.

    I have my home systems setup for 100% immediate approval and deployment on my WSUS for this exact reason – I want to be "cutting edge and dangerous" at home, to see the worst of what I might have to support at work, and I accept this risk, but I feel for all the SMB customers who have minimal IT staff and just have the same settings because the guy who set the server up KNEW that otherwise, no updates would EVER be installed.

    First and foremost, I want to thank you for having such honesty in a blog.  Sharing this information is good for all of us, and it's unusual these days – Most companies would forbid it because it "airs the dirty laundry" in public, but with a problem like this, any information that can be shared, early and honestly, will help EVERYONE get through to a root cause and fix ASAP.  

    Because I appreciate the honesty, I dont want to appear to be "piling on" with the admins here who are stuck because we followed "unofficial" help found on 3rd party blogs, but at the same time, at that moment, it was the best, and likely ONLY information available, and I will second the notion that calling Microsoft at the first sign of trouble, no matter how serious, is NOT how we usually operate.  On the contrary, my method would typically be to start googling, and look to see if there's a technet article in the first 2 pages or so of results.  If so, I go there first, but if not, I'll listen to advice given by those who have already fought the battle I'm in, whether they're from Microsoft or not.  I would hate to believe that Microsoft wouldn't try their best to help those affected users.  

    In past OS's, a situation like this was often fixed by simply reapplying the newest service pack again, which would replace all non SP files with the latest ones.  Is this not the case anymore, and if so, why not??  It seems like a "torn" system should be easy to fix by reapplying the SP and letting it re-do it's copies.  Afterall, the SP is largely a compilation of hotfixes, some of which may have already been installed by any particular customer anyway, so certainly reinstalling the SP can't HURT, right??   Is there something in SP1 that prevents it, and if so, why?  Is there a registry hack that could be done to trick the system into thinking that SP1 hasn't been installed, so that it can be redone?

    Thanks again for the blog, the info, and especially the fix..  


  52. susan says:

    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.

  53. DaveA says:

    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.

  54. Wolfgang says:

    @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.

  55. stephane says:


    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 ?

  56. Mark M. says:

    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?

  57. A tech says:

    As requested, a +1 for "we couldn't be bothered to wait on hold for MS support".

    Testing didn't reveal a problem but we had a fairly high rate of 0xc0000034 the morning after deployment via WSUS. We've now declined the update and will wait for MS to fix the problem. Yet another reason for small business to distrust MS I'm afraid.

    I'll add a +1 for the "How does one set the "exclusive" option for an update in WSUS 3.2?" and how do we "force a reboot" questions. You may have users that are trained to do exactly what you want, but we need to rely on stuf "just working".

  58. fejesjoco says:

    3 torn machines here.

  59. susan says:

    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.

  60. susan says:

    Got word back.  We don't control the exclusive flag.  Only Microsoft  does.

  61. Wolfgang says:

    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.

  62. Jason says:

    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.

  63. susan says:

    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.

  64. susan says:

    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?


  65. susan says:

    (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.  

  66. Bitbucket says:

    Add me to the list of people who have a lot of computers in the so called "torn" state.  Like others, I had to get my machines up and running quickly and there was no fix from Microsoft yet.  I used the method of editing out the line in Pending.xml.  As far as I know, there is no fix for this yet and it's been weeks.

    Anyone know when a fix is coming?

  67. Bitbucket says:

    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.

  68. mike says:

    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.

  69. Ben says:

    Hi Joseph,

    Today (April 3rd) I shot my machine to hell with SP1 and got the C34, spent hours trying to find a solution by myself, then got access to another pc and found first "torn" fixes and now this, I never applied the torn fixes and now the POQ-Node Removing vbs and I'm all relieved.

    BUT, what I don't understand is this: On March 16th you started this post/thread, which was now about two weeks ago which makes is plausible to say that MS knew about this very serious problem at this point. Why is my Windows still offered this potentially fatally faulty SP two weeks later, and why is it not pulled out of WindowsUpdate until the cause and a solution has been found? Why keep risking further damage, especially random torn systems which I understand you still cannot fix today?

    Had someone acted responsibly and pulled the plug on SP1 via WindowsUpdate two weeks ago, at least I would not have had to spend hours on this today.

    Thanks for listening and (hopefully) passing this on to responsible ones.


  70. Ben says:

    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)



  71. Drewfus says:

    @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.

    1. Could Ben have got the C34 condition on his non-WSUS machine due to existing pending updates?

    2. 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?

    3. Are you in a position or aware if MSFT intends releasing information that explains the root cause, or causes, of the code 0xc0000034 issue?

    4. 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?

  72. Drewfus says:

    2. If the size of the service pack isn't the issue, then your almost implying that installing *other* updates could result in the same or related condition, if pending updates exist. No? If yes, then the probability of success is lower for any update on a system with pending updates, regardless of size or nature of the new update. The difference might be minute in practice, but this does hint at a slight brittleness in the servicing architecture. No reasonable person could suggest that the code should be perfect in this regard, but isn't that a good reason for the service pack to suggest to the user in this case that "It is recommended that the system be restarted to clear the pending update queue before proceeding with the service pack installation. Do you want to restart now? Y|N".

    3. The KB says:

    "This issue can occur when a user attempts to install the Service Pack, does not restart the machine to complete the installation, installs other updates and then restarts the machine. This issue can also occur if the Service Pack is installed simultaneously with other updates when using WSUS."

    So is the user or admin doing something wrong? The article does not explicitly or implicitly (IMO) state the user or WSUS admin is doing something wrong, so where is the fault? If the fault isn't administative then it must be in the servicing stack for allowing updates to proceed when the servicing stack is not able to process these updates with an extremely high probability of success. Without a thorough root cause analysis to read, that is the conclusion i'm drawing from the KB article.

    4. Fair enough, but again if existing pending updates can cause the C34 condition, then potentially this could affect *any* machine installing SP1. Also, having a machine offline does amount to data loss, whatever the cause.

  73. Bitz says:

    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.

  74. B says:

    Windows 7 deletes all System Restore Points upon reboot:…/en-us

    Interesting… wonder if that's the trigger for the lack of no restore points reported by everyone?

  75. jay says:


    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?


  76. NYCDrew says:

    @Bitz  "No service pack before this one has behaved in this manner"

    Actually, this same problem has been happening since Vista Sp1:…/4491fe25-be44-430e-a384-fb58c5da5ad0

    At least in XP, WU wouldn't let you install the SP's with any other updates.

  77. Bitz says:

    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.

  78. jay says:

    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.


  79. BitBucket says:

    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.

  80. FYI: According to…/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

  81. Neikius says:

    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.

  82. Phil D. says:


    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…

  83. susan says:

    Bitbucket, Neikius and Phil?

    Can you ping me at 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.

  84. Dave says:

    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?

  85. Jesper Johag says:

    We had about 70 computers with this issue before I stopped the update. 50 of them "fixed" with the pending.xml-hack. (This was at the time when that was the only known solution.)

    Now we have problems with ForeFront on a (for now) unknown number of computers (may be up to 1500). People reporting that their computer warns them that antivirus program is missing.

    The information here is somewhat depressing:…/fcs-v1-march-2011-update.aspx

    I cite: "We have received reports of an installation issue with our March update of Forefront Client Security when the option of 'install updates and shutdown' is used. "

    The "installation issue" is that ForeFront antimalware agent gets removed from system.

    I have used automatic updates on all our clients and servers since SUS v 1.0 without any problems, until now. ;^)

  86. Tim Birchall says:

    1. Hyper-v VM Server 2008R2

    2. Hyper-v does not support USB

    3. 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?

  87. Tim Birchall says:

    Thought I would share this in case anyone else runs into this issue.

    Since the error centered around the backup part of the script

    (Script.vbs(25, 1) msxml3.dll: The parameter is incorrect.

    Line 25: …

    Within notepad I made a backup (copy) of  the pending.xml file

    (File>Open>Browse to Pending.xml>right click copy>right click paste> result "copy-pending.xml")

    Then I removed the backup portions of the script.

    Added the Wscript.quit line after the load command.

    Now the new script looks like this:

    Dim xmlDoc, node, nodeList, fileName, backupFileName, numberOfPOQNodes

    Set xmlDoc = CreateObject("Microsoft.XMLDOM")

    If Wscript.Arguments.Count = 0 Then

    WScript.echo("Error! No XML file specified.")


    End If

    fileName = WScript.Arguments(0)

    If Not xmlDoc.Load(fileName) Then


    End If

    Set nodeLIst = xmlDoc.documentElement.selectNodes("POQ")

    numberOfPOQNodes = nodeList.Length

    For Each node in nodeList



    Set smlDoc = Nothing

    WScript.echo(numberOfPOQNodes & "POQ nodes removed. Script completed.")

    Ran the new script and this worked without a hitch!

    The server is now up and running.

  88. Bitbucket says:

    Still no resolution to the Torn State?

  89. andreas says:

    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?

  90. GrumblyG says:

    Anything more on a fix for torn systems?

    We have 16 systems withthis issue also and cannot at this time rbuild all of them.

  91. shyam mainali says:

    i am try to boot my laptop than i cant boot always so this error why

Comments are closed.

Skip to main content