I have an update for those of you with systems in a torn state. To clarify, torn state systems are those on which the unsupported workaround of deleting the checkpoint from the pending.xml file was used after getting the 0xC0000034 error during SP1 installations. Even though it was not recommended by Microsoft, many customers used it and ended up in a torn state that currently requires them to rebuild the machine, which is very painful. So, based on customer feedback, we have created a supported workaround to get out of that torn state without having to rebuild the machine. that I would like for those of you who have been actively watching my posts to test, The steps are as follows:
Please note: If you have a 64-bit installation of Windows the proper architecture value for the manifest is amd64 (not x64)
My ask is that a couple of you with torn state machines try this and let me know the feedback you have on the steps above. Note that these are not the same steps as we’ve seen from other posts for recovering from torn state that have driver issues with graphics cards. If you encounter one of those issues, those are in addition to the torn state and not indicative of a torn state.
Let me know the results
--Joseph
I'm wondering if a regular uninstall/reinstall from control panel would work at that point.
@joscon: Will do, soon as I can get access to one of my torn machines.
It worked.
The command I used in step 6a for my x64 system was:
DISM /online /remove-package /packagename:
Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514
@Joe; Awesome, glad that's working. Anyone else having issues with these steps now?
I have the same problem with my computer.
First of all I went to the first link and there are multiple files to download, which ones should i download.
Second, i have bought a new HDD and reinstalled OS and attached my old HDD which had that problem as a external Hard Disk.
Can i apply changes directly on the hard disk and put the hard disk back to boot up back in to my old system or will have to apply the fix in command prompt only?
and please can you explain the steps as if you are explaining to a dummy, i am not too familiar with where to go and what to do.. sorry for asking this questions but i need get my old computer back and not too sure that i understand all the steps correctly.
Thank you for the help.
--Taizoon
@zooooon;
1: Download the version of the service pack that matches the architecture of your installation. x86 for 32bit and x64 for 64bit systems
2: If you have a new HDD then why dont you migrate your user settings? It would be cleaner and faster and would save you a lot of hassle. That being said, you really should be running these commands against the local drive and not an offline drive so if you want to do these steps you should go ahead and remove the new drive, boot back into the old drive and then follow the steps.
I've made this as step by step as I can really. Once you have the proper version of the service pack you should be gtg.
Finally got a chance to run the steps on one of my broken x64 machines and it worked as well. Thanks Joscon for sticking with us. :-) you are da bomb.
No problem Brenda, glad to help.
We'll try these today. I posted regarding running inplace upgrades on the last blog entry, but that may all be moot. Thanks again!
So....
For me, I had to change the ad264 to ad364 AND change x64 to amd64
So, Step 6 was:
DISM /online /remove-package /packagename:Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514
This needs a script :)
This may sound a li'l dumb but I am not able to make out my torn machines.. Is there a way from which I can confirm that this one is a torn machine..?
I had a few machines which became torn at that time.. most of them have been re-imaged.. some i did not install SP.. some left torn.. so is there a way that i can know easily which one is what and stop playing Mr. Doom vs Batman on the machines?
Thanks for the resolution.. Joseph..!!
@Rahul;
No there isnt a way to determine torn state on the machines unfortunately.
Awesome, thank you very much for this, you are a legend.
BTW. I also had to use amd64 in step 6A.
No problem, glad that worked for you. I'll update the blog for amd64 since thats getting hit a lot.
@Rahul: All of my torn machines were identifiable by the list of installed updates under control panel - programs and features. Comparing a suspected torn system to a known good one in this way might reveal something for you. I'm seeing a very large number of updates all having a date of 3/10/2011 on my torn machines. Absence of this may not necessarily prove anything, though.