Update on torn state systems

Rarely do I completely delete a posting but I am going to in this case.  If you have a torn state C34 install, we have a supported workaround.

Please use the new information for this located here: https://blogs.technet.com/b/joscon/archive/2011/05/10/supported-workaround-for-torn-state-installations-on-windows-7-sp1.aspx

--Joseph

Comments

• Anonymous
  January 01, 2003
  Yup, glad this was posted today.  Thanks for adding it here Susan.

• Anonymous
  January 01, 2003
  @Billy, if you deleted the checkpoint in the pending.xml then you are in a torn state.

• Anonymous
  January 01, 2003
  The currently supported solution is posted in the blog and thats a rebuild.  

• Anonymous
  January 01, 2003
  If the script ran and SP1 installed, thats all there is to it.  The script enables the installer to get past the issue that causes the SP1 installer to fail.  So, in short, if you're showing SP1 installed, then you're fine.

• Anonymous
  January 01, 2003
  Thanks for the catch Kelvin

• Anonymous
  January 01, 2003
  @Nick; Thanks.  Rest assured that these comments are being seen.  I know in the end that might not mean much but it's all I have right now. --Joseph

• Anonymous
  January 01, 2003
  @Per;  You should be able to do the script

• Anonymous
  January 01, 2003
  An update that prevents a "0xC0000034" error message when you try to install Windows 7 SP1 or Windows Server 2008 R2 SP1 is available: support.microsoft.com/.../en-us

• Anonymous
  January 01, 2003
  The comment has been removed

• Anonymous
  January 01, 2003
  The comment has been removed

• Anonymous
  January 01, 2003
  RV; An inplace should suffice as its really just rebuilding the Windows directory.  You could then use something like USMT to do a hardlink migration (USMT hardlinks that is) and move the user data back to the old directories.  It's covered here:technet.microsoft.com/.../dd883247(WS.10).aspx And, you're welcome RV.  I'm glad that this is providing value to some of you even though I know this isnt the outcome to this that all of you were hoping for. --Joseph

• Anonymous
  January 01, 2003
  @Billy; if you want to try something for me on a machine, can you do the following: dism /online /remove-package /packagename:Package_for_KB976932~31bf3856ad264e35~amd64~6.1.1.17514 reboot and attempt to reinstall SP1 normally.

• Anonymous
  April 25, 2011
  I have never seen Microsoft so thoroughly side step its obligation to fix an issue but they have. Microsoft not fully testing the WSUS rollout of SP1 caused the failed SP1 installs. Your own support services told techs and end users to use the pending.xml "fix". Now after what 4 weeks you’re telling us that Microsoft is not willing to accept the blame by either providing a solution or sending checks to those end users who will now be paying me to fix your mess. Way to go Microsoft, time to turn off updates! You have completely destroyed any trust that was remaining in patch management with this latest and I key on that word, LATEST failed patch.

• Anonymous
  April 25, 2011
  Agreed.  We have also turned off all updates from WSUS. I don't want more destroyed machines with no fix from Microsoft. "Rebuild the machines" is not an acceptable "fix".

• Anonymous
  April 25, 2011
  The comment has been removed

• Anonymous
  April 26, 2011
  "But at this time rebuilding the OS is the only Microsoft supported solution" were you serious when you wrote this? Rebuild 75 clients? save  data on 75 clients and put it back? r u coming to do all this on my  30 customer each having more than 50 clients?

• Anonymous
  April 26, 2011
  I also agree that this is an unacceptable resolution. So can we send the bill to MS for the time it takes us to rebuild all of these machines? This is another reason to not trust the "security focused" (MS words, not mine) Microsoft solutions. Thanks once again for another lovely Vista like experience..

• Anonymous
  April 26, 2011
  How am going to get my customer to trust Microsoft products in the future?

• Anonymous
  April 26, 2011
  Hey Joseph, First, I am sorry that you are the "fall guy" for Microsoft on this one (at least public).   I and others do appreciate these updates. I have to say, I find this extremely dissapointing and lacking from Microsoft.   I have many sites that had this issue, and my small company is the one to bare the cost of repairing our customers systems while the big MS sit happy with their licence sales. I tell you what.    How about you send me the email of the person in Microsoft that I can send the bill to for all this work that the WSUS version of this update has caused?   Then you dont need to convince me that a version of the installer isn't needed to fix this. Microsoft should release an inplace upgrade build that people in this state can use. Thanks for listening (again) Nick

• Anonymous
  April 26, 2011
  The comment has been removed

• Anonymous
  April 28, 2011
  While I go to dozens of clients with dozens of machines to fix these issues for free, who is going to make my mortgage payment?  I certainly can't be making money while I'm fixing these for free.  Just like BP's response to the gulf disaster, I think Microsoft needs to respond with a similar program as the fixing of this issue essentially puts me and my clients temporarily out of business unless you can come up with a better solution.  The handling of this has been poor and the solution is no solution at all.  

• Anonymous
  April 28, 2011
  Will running an in-place upgrade do what's required to get the machines out of a torn state or do we have to wipe and install?  I know rebuilding about 30 machines isn't a monumental task for many admins that read this blog, but it's a considerable chunk of time for just myself and an assistant at our company, staggered over weeks and coordinating schedules with users to get their machines and keep them for the needed time. Also, thanks for all of your communication joscon.  Obviously, this is a frustrating situation for everyone, yourself included, but we'd be worse off without your posts and answers.  I hope those watching at Microsoft will acknowledge the attention you have paid and continue to pay to this issue.

• Anonymous
  May 03, 2011
  So what are you people going to do about this? Still wait for fix? Try the earlier posted workaround by Kelvin Aston or just giveup and reinstall OS? I really want this fixed and i simply cannot reinstall all the systems i have in torn state, period. Feels like i am refreshing this blog too often and hoping for solution.

• Anonymous
  May 04, 2011
  The comment has been removed

• Anonymous
  May 04, 2011
  @joscon YAY!!!!!! I gotta reload!!!!  YAY!!!!!!!!!!!!!!!!!

• Anonymous
  May 05, 2011
  How do you know if you are in a torn state? I just have the support.microsoft.com/default.aspx problem and the fix doesn't resolve it

• Anonymous
  May 05, 2011
  And for us who did the regedit fix (remove everything from SetupExecute )?

• Anonymous
  May 05, 2011
  Ah ok, I didn't do that. I had C019003 error first. I followed steps to resolve that (chkdsk sorted it), then I got (and still have) the C0000034 error. I tried the Script.vbs, and it ran, but it didn't say it had removed any POQ nodes and doesn't appear to have made any difference. I am backing up my files and will re-install 7. So far it only seems to have happened to 1 pc on our wsus network, but there are some that haven't done sp1 yet.

• Anonymous
  May 06, 2011
  Hi again, I've run the script on one of our machines that have been in a "torn" state via the regedit fix. The script successfully ran and i got into windows. But how do I know that the machine is fixed (not in torn state)? There was no indication that the Service Pack 1 installation continued or anything like that Two machines did not have pending.xml but rather pending.xml.(lots of numbers & letters) //Per

• Anonymous
  May 06, 2011
  Well it showed as SP1 installed before as well so that's why I'm a but confused. I didn't get the regular window that said that SP1 was successfully installed.