Windows 7 Ultimate SP1 installation fails with error code c0000034
Locked
-
Thursday, February 24, 2011 12:12 PM
I've seen several entries regarding sp1 instalation errors, but none with this one: falat error c0000034 applying update operation
Machine is x64 (intel core i7), with 8gb mem
tried installing sp1 via windows update. there were three patches to install, one of them, sp1
did the two first, before, and then tried sp1.
It failed while rebooting (not remember the code, sorry), but i was able to do a system restore to pre-sp1.
them, got the full SP1 media from msdn, and did install it in offilne mode. Setup looked faster (of course?) and in reboot, this fatal error c0000034 appeared. But this time, no option for system restore.
if i try to enter in safe mode, i get stuck on driver loading (last loaded is classpnp.sys)
if i try to run, as seen in other threads, the sfc tool, i get a "there is a system repair pending which requires a boot to complete..." Of course, reboot just gets me to the 34 error.
As i cannot get to Windows, no InPlace setup is available...
So, i read about DISM could be used as a before-last resourt... How? I'm not sure what this error is, so i'm a bit lost about getting something out of DISM to correct it.
Any help?
Answers
-
Tuesday, March 29, 2011 12:40 AM
Your machine is most likely now in whats known as a torn state (meaning no future updates will install properly). Had you done the script in the KB article, the service pack would have installed properly and you wouldnt be in that state. I speak more about it here: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
--Joseph [MSFT] http://blogs.technet.com/b/joscon/- Marked As Answer by Susan BradleyMVP, Editor Tuesday, March 29, 2011 1:00 AM
-
Thursday, March 31, 2011 2:04 AMOwner
thiswoot,
Thank you for posting and wanting to help other users, but unfortunately, I had to delete your post. We have found that the steps in this post while allowing you to recover from the non-bootable state, leaves the machine in an unserviceable state, with SP1 partially installed. There is not a known way to recover a machine from this state at this time, so we recommend that people follow the steps in the KB article which allow you recover the system with Windows SP1 installed successfully. So as not to leave customers in state which is not serviceable, your post was removed.
KB article with steps to resolve the issue:
975484 Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;EN-US;975484We also have a blog post on the issue with more details of why the deleted steps should not be attempted:
Thanks-Tony Mann
IT Pro Audience Manager for Web Forums- Marked As Answer by Susan BradleyMVP, Editor Thursday, March 31, 2011 3:16 AM
All Replies
-
Thursday, February 24, 2011 3:49 PM
//
// MessageId: STATUS_OBJECT_NAME_NOT_FOUND
//
// MessageText:
//
// Object Name not found.
//
#define STATUS_OBJECT_NAME_NOT_FOUND ((NTSTATUS)0xC0000034 L)boot from the Windows 7 DVD or Windows Recovery Environment (F8)[1] and run the command prompt and run this:
DISM /image:C:\ /cleanup-image /revertpendingactions
(replace C: with the drive where you installed Windows 7)
This reverts all pending operations. Now you should go back to Windows 7 RTM.
Have you used Driver Sweeper to remove the ATI Inbox drivers? Yes, check this:Windows 7 Service Pack 1 fails to install with 0x800f0a13 or 0x800f0826
If not, Please run the Windows Explorer and go to the folder "C:\Windows\Logs\CBS\" and copy all files to your document folder, also copy the setupapi logs from the folder C:\Windows\Inf and the file "C:\Windows\winsxs\poqexec.log" to your document folder (otherwise you can't upload it), zip all files into 1 ZIP and upload the zip to your SkyDrive [2] and post a link here.
[1] http://windows.microsoft.com/en-US/windows7/What-are-the-system-recovery-options-in-Windows-7
[2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Thursday, February 24, 2011 4:36 PM
Hi,
no driver sweeper used
I've run dism, but got error 2, which i read somewhere else (by you, think) it is error not found, and it did nothing to stop pending actions
i've placed all the log files refered in this and other threads regarding installation (poqexec.log, cbs.log, setupapi, dism.log, ...) in here:
http://cid-1a5c47239c51c0aa.office.live.com/self.aspx/.Public/W7Sp1Logs.zip
For what is worth, i do not have any full system backup of the down machine, but have a different, pre-sp1 x64 w7 ultimate one available if needed to get some files.
thanks for all your help
miguel
- Edited by Miguel Saraiva Thursday, February 24, 2011 4:37 PM added info
-
Thursday, February 24, 2011 5:53 PM
also, trying to boot with f8 and Last known good configuration, enters the same error, trying to apply update operation, and repair does not find anything wrong, and just says to restart after a while.
miguel
-
Thursday, February 24, 2011 6:23 PM
2011-02-23 16:15:50, Info CBS Failure in poqexec.exe while processing updates. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE]
2011-02-23 16:15:50, Error CBS Shtd: Failed while processing non-critical primitive operations queue. Non-critical primitives will be retried from SMSS. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE]//
// MessageId: STATUS_TRANSACTION_NOT_ACTIVE
//
// MessageText:
//
// The requested operation was made in the context of a transaction that is no longer active.
//
#define STATUS_TRANSACTION_NOT_ACTIVE ((NTSTATUS)0xC0190003 L)1cbd37244f44df3: 74c, c0190003 , 7b75, 0, CreateFile ;\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.5.7601.17514_hu-hu_5e9bd461d23f97af_wuaueng.dll.mui _297f975d
so this CreateFile command failed because the transaction is closed.
This can be fixed the the system readiness tool. But the problem is that you need to return to RTM.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Thursday, February 24, 2011 6:29 PM
any brute force method exists to stop the system to try to update on boot, instead of using the dism? dism does not work
thanks
-
Thursday, February 24, 2011 6:56 PMrename the pending.xml from the WinSxS folder. this forces Windows to stop the installation.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/- Edited by Andre.Ziegler Friday, February 25, 2011 10:18 PM only rename
-
Thursday, February 24, 2011 7:24 PM
Hi Andre
How would you go about deleting that file from the command prompt?
Thanks in advance
-
Thursday, February 24, 2011 8:06 PM
delete/rename the pending.xml from the WinSxS folder. this forces Windows to stop the installation.
i did that but system gets stuck on starting windows screen.. any other solution
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Thursday, February 24, 2011 9:00 PM
delete/rename the pending.xml from the WinSxS folder. this forces Windows to stop the installation.
i did that but system gets stuck on starting windows screen.. any other solution
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
I have same problem and same result.... -
Thursday, February 24, 2011 10:48 PM
i did that but system gets stuck on starting windows screen.. any other solution
what do you mean with stuck?
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Friday, February 25, 2011 3:45 AM
Reboot and press F8 right after the Bios Screen.
Select Windows Recovery Environment [this should be the top option].
Select keyboard option and login for your account.
=> Open the "Command Prompt"
=> find your Windows directory (my PC was on D:)
=> cd to Windows\WinSxS folder
=> type in this command move pending.xml pending.old
=> exit command prompt
=> run "System Restore"
=> select the option for Service Pack 1
=> exit and reboot
That fixed my system...
-
Friday, February 25, 2011 5:45 AM
He probably means the same thing as I see. Tried using DISM, no luck. Tried renaming pending.xml, rebooted & system hangs at Windows Startup logo. When I try F8 Safe Mode, it takes about the same time to hang & it always stops at CLASSPNP.SYS so I suspect the same is happening when I try to boot normally. With pending.xml in place, I also get the C0000034 fatal error.
I really need to get this machine running again but cannot afford the time to reinstall all the applications & they are obviously unharmed. What are my options? If I reinstall off the installation disc, will my current installation be properly repaired or will it wipe everything out? Is my data drive (D:, a separate physical drive containing my User Profiles, accomplished with a minimal unattend.xml) in any danger?
-
Friday, February 25, 2011 8:12 AM
Totaly same result...He probably means the same thing as I see. Tried using DISM, no luck. Tried renaming pending.xml, rebooted & system hangs at Windows Startup logo. When I try F8 Safe Mode, it takes about the same time to hang & it always stops at CLASSPNP.SYS so I suspect the same is happening when I try to boot normally. With pending.xml in place, I also get the C0000034 fatal error.
-
Friday, February 25, 2011 12:40 PM
I have the same error as everyone else. FATAL ERROR C0000034.
I tried the DISM thing and I also tried renaming pending.xml. Neither worked.
My computer wont boot into safe mode and I have no system restores available. When I renamed pending.xml, I stopped getting the error, but now Windows just stalls at the startup screen.
I also tried going to Last Good Configuration, and that didnt work either.
What should I dooooooooooooooo?
-
Friday, February 25, 2011 12:54 PM
I have the same error as everyone else. FATAL ERROR C0000034.
I tried the DISM thing and I also tried renaming pending.xml. Neither worked.
My computer wont boot into safe mode and I have no system restores available. When I renamed pending.xml, I stopped getting the error, but now Windows just stalls at the startup screen.
I also tried going to Last Good Configuration, and that didnt work either.
What should I dooooooooooooooo?
Totaly same as I... You can reinstall your PC or wait for fix (like me). Now I am running Linux (ubuntu) Live CD..... -
Friday, February 25, 2011 1:05 PM
Well, i tried all possibilities and suggestions. Brute forcing removing pending.xml did not work. I also tried removing "temporary" fix folders,
The result was booting, and stalling in a black screen. no messages. F8 Safe modes did not work either.
So, for me, clean install. Moved everything into an OLD folder. This way, all drivers and so on are readily available (install pointing to system32\driverstore)
I did weight the option of wating for some fix for this, but by the time someone gets some answer, i already have everything installed and running (and a freshly installed computer is a must :)
So, thanks a lot for André Ziegler for all help, and for his massive work analysing all the log files that many people put in skydrive.
Regards, and best of luck for all (and for me. i still have two machines waiting for sp1)
Now it's time for all the SDK, API, Frameworks and so and so... A calm friday :)
Miguel
- Proposed As Answer by Andre.Ziegler Friday, February 25, 2011 2:24 PM
-
Friday, February 25, 2011 2:22 PM
I THINK I FOUND A WAY TO FIX IT!!
I WILL POST AN UPDATE IN 45 MINS...
-
Friday, February 25, 2011 2:26 PM
I THINK I FOUND A WAY TO FIX IT!!
I WILL POST AN UPDATE IN 45 MINS...
Oh yes... I am waiting... :) -
Friday, February 25, 2011 2:37 PMdo this please to help other users.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Friday, February 25, 2011 3:08 PMYes please ! Same problem there in France on several virtual Windows 7 64 bits in french
-
Friday, February 25, 2011 3:13 PM
I am trying the solution from Tim Hoover...It's long to restore at the end.
I'll keep you aware.
But I think that this problem is really critical for Microsoft...
-
Friday, February 25, 2011 3:37 PMThanks for the steps, but I don't have that ID in my file...
-
Friday, February 25, 2011 3:45 PM
Indeed, I found other ways to find that part. Line 1697, char 142 marks the end of the section in my case. The start can be found using the end part of the preceding tag.
Holy shit, it worked. I'm in. Do you like beer?
PS: it didn't work right away. I got a few errors and reverts, then another reboot. Now, I can login. There's no way that I'm trying this update again soon.
-
Friday, February 25, 2011 4:12 PMok, I bookmark this. Can someone with the c0000034 test this and verify it?
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Friday, February 25, 2011 4:16 PM
I tried the instructions from Tim Hoover above, and this is what followed:
After renaming the pending.xml file, System Restore almost finished running, and then said it could not complete successfully (choosing the SP1 install restore point). I went ahead and closed the window, allowing the computer to restart itself. Voila! It booted normally, and appears to have rolled back the service pack. I will wait until a fix is found for this issue before attempting a re-install.
If that had not worked, thiswoot's suggestion was my next bet. Though you may be able to simplify the proceedure thusly:
F8 when your computer boots and chose "Repair your computer"
Set the keyboard layout and login with your administrator password
Choose Command Prompt from the menu
Type: C: and hit enter
Type: notepad.exe c:\windows\winsxs\pending.xml
Resume with step 11 from thiswoot's post. :-) My apologies if this doesn't work, but that's how I open files in Notepad while in the Windows environment.
Cheers,
Mög
-
Friday, February 25, 2011 4:18 PM
PLEASE paste all the blue selection here http://pastebin.com/.
my pending.xml is a bit different
I need to know specific lines to delete... the "blue selection" I useless for me....
- Edited by javurmar Friday, February 25, 2011 4:28 PM ....
-
Friday, February 25, 2011 4:31 PM
Same problem for me...
I can find ._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\File
But lines after seems differents...
-
Friday, February 25, 2011 4:33 PM
-
Friday, February 25, 2011 4:42 PM
I did it by removing several lines starting with <SetFileinformation.... and with the tons of AAAAA...FFF..II...AAA..BBBB letters.
I imagine that it removes the blocking lines...
I will see if it is stable and if I can restart SP1 update :)
Yes I am crazy.
This is what I removed thanks to windiff :
http://pastebin.com/00MRcbnx
-
Friday, February 25, 2011 5:11 PM
It has worked for me.
But I know this is absolutely not explainable...and not sure at all.
-
Friday, February 25, 2011 5:18 PMlol nice job
-
Friday, February 25, 2011 5:24 PMYESSSS ... My windows is working too. But I can not explain too what lines I had deleted...
-
Friday, February 25, 2011 5:26 PMYou saved my data/time everythink... THX
-
Friday, February 25, 2011 6:26 PM
This Worked Many Many thanks you are a life saver.
-
Friday, February 25, 2011 8:27 PM
Unfortunately too late for me. I got online with a MS tech last night & ended up wiping my system install. I haven't lost data (yet) but now I have to reconfigure & reinstall all my applications & user profiles. I figure the grand total time lost will be a full week, including 2-3 days remaining to get it to a useful state.
I don't know if I should try to install SP1 before or after I get my machine to a useful state again. It was 100% stable & up-to-date right before the failed SP1 attempt. Given that SP1 is *supposed* to be minimal, I'm tempted to install it before migrating my old User Profiles. What a nightmare.
-
Saturday, February 26, 2011 1:51 AM
i retyped the whole URL from my phone (on which i was reading this given my PC crashed) just to thank this guy.
You sir (or ma'am) are a genius! Thank you!
-
Saturday, February 26, 2011 2:02 AM
glad you got it working polymorphicPinapple, ron325, javurmar!!!
-
Saturday, February 26, 2011 6:01 AM
I attempted Tim Hoover's suggested method to no avail. I have also found that the entries:
<DeleteFile path="\SystemRoot\WinSxS\FileMaps\program_files_x86_reference_assemblies_microsoft_framework_v3.0
and:
<DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
are not present in my pending.xml file.
I removed:
<Checkpoint/><MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
and rebooted, but it seems to hang at the "starting windows" screen as many other members have reported supra.Any assistance would be greatly appreciated,
Thanks,
Pete
-
Saturday, February 26, 2011 6:06 AM
Wait about 5 minutes (literally) at the "starting windows" screen before giving up and rebooting.I removed:
<Checkpoint/><MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
and rebooted, but it seems to hang at the "starting windows" screen as many other members have reported supra.Any assistance would be greatly appreciated,
Thanks,
Pete
-
Saturday, February 26, 2011 6:11 AM
Yes, it is working beautifully now.
Thank you again for your assistance!
What do you suspect that the issue was?
-
Saturday, February 26, 2011 1:10 PMThank You very much dear sir!!! i have only one question - what should i do now - should i replace the altered original pending.xml, with "back up" version, or was that only a precaution?
-
Saturday, February 26, 2011 3:31 PMenderock - Yes the backup was only precaution. You can either delete it or leave it. Do NOT rename it to pending.xml. It could mess stuff up.
-
Saturday, February 26, 2011 3:32 PM
god damn! that worked like a charm. thank you soooo much.
- steve
-
Saturday, February 26, 2011 5:27 PMThank you so much thiswoot. This worked perfectly.
-
Saturday, February 26, 2011 10:43 PMThanks thiswoot . Worked like champ. Appreciate ur help
-
Saturday, February 26, 2011 11:39 PMExcellent!! Thank you. Worked for me on two different pcs.
-
Sunday, February 27, 2011 1:57 AM
thiswoot,
Not only are you a lifesaver, you're a genius to boot! Thank you very, very much for providing this fix. I, once again, am a happy man...
Roberre
-
Sunday, February 27, 2011 9:47 AM
Hello Tim,
I tried using your method, however, there was no pending.xml file in my WinSxS folder --- do you have any other suggestions?
Thanks....
-
Sunday, February 27, 2011 9:49 AM
Hello,
I tried to use your method to fix my system, however, when I reached Step #11 - there was no pending.xml file in my Winsxs folder. Do you have any other suggestions?
Thank you...
-
Sunday, February 27, 2011 10:42 AM
Really thanks Thiswoot for the easy steps!
It worked for me! You're a hero!
-
Sunday, February 27, 2011 11:49 AM
Hello,
I tried to use your method to fix my system, however, when I reached Step #11 - there was no pending.xml file in my Winsxs folder. Do you have any other suggestions?
Thank you...
1. Make sure you view All Files instead of .txt files
http://i51.tinypic.com/35nd74z.png
2. If it's still not there, look for a pending.xml file with a bunch of random numbers at the end.
ex. pending.xml.01cb7d8fb9079780
If you find the pending.xml with random numbers, make a copy of it and rename the original to just pending.xml without the numbers, then follow the steps from step 12.
- Proposed As Answer by TexRyk Friday, March 11, 2011 7:20 PM
-
Sunday, February 27, 2011 5:10 PM
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
-
Sunday, February 27, 2011 5:11 PM
Yes it worked!
-
Sunday, February 27, 2011 7:41 PM
This worked perfectly for me, thank you very, very much for your kind efforts and hard work.
Instead of using the notepad aspect of your solution I used my Ubuntu dual boot option and accessed the folders and Pending.XML file through that. I supposed the Ubuntu live CD would be just as effective. But, ultimately it was down to the solution you posted here that worked for me. Thank you again. :¬)
-
Sunday, February 27, 2011 7:59 PM
I'm one of those.
Editing that large xml with notepad was a pain, but it seems to be working, my affected computer booted alright and is currently reinstalling the service pack as if nothing happened.
Thx a real lot @thiswoot, I don't know how u figured that out but it's great. U saved my day!
-
Sunday, February 27, 2011 8:16 PM
OMG i love you you saved my laptop
tho it did take some time to find it and the file was in drive E or something
but thank you SOOOOOO much i will forever worship you!!!!!!
-
Sunday, February 27, 2011 8:38 PMAs the others have said.....Thank you!
-
Sunday, February 27, 2011 8:52 PM
Marvellous ! great ! Many thanx.
What i figured out that changing the pending.xml in such a way that it fails the update process prior to getting it stuck is the key to this solution.
Because now after the logon, it says Update failed to install and in details is shows invalid parameter.
I must say even the destroying the proper syntax of this xml file would also do the trick.
any how saved one of my client big time because no backup, not able to boot in any safe mode, dism command also failinig with error=2, no past images or restore points, this the only DC with no ADCs and other options entailed redeployment of whole infrastructure i-e AD, Exchange, SharePoint with considerable data loss.
Update process is smooth, problem originated because of electric failure during the update process.
Shahid Roofi- Proposed As Answer by Shahid Roofi Sunday, February 27, 2011 8:52 PM
-
Sunday, February 27, 2011 9:41 PM
Same error here but my machine has been acting terribly just prior to that. Such as "Unleashing mode" errors, crashed within minutes when logged into like WoW with blue screens. After dl SP1 everything pretty much stopped. I can't boot up, I get stucked on the same fatal error 282 out of ( forgot the number).
Now I am trying woot's tutorial but when I opened the notepad, it shows 3 hard drives and my supposly C drive is now on D.
I am so lost I have been trying to fix my machine for days and nothing is working. Repair doesn't and tells me my computer can not be repaired, sp1 deleted my restore points and when i tried to make an restore to the 24th of this month, that is when all stopped and I get hung up on the fatal error code.
I, as well don't have a backup disk, well I have one from last july but not sure how to work it. And dl an recovery disk, same thing nothing works. I don't know how to reinstall W7 since I don't have a disk.
What can I do? Any help would be so appreciated.
-
Sunday, February 27, 2011 9:43 PM
How did you repair your clients PC, via remote controlled programs?
-
Sunday, February 27, 2011 10:03 PM
boot with any win7 DVD or window 2008 R2 DVD, and choose repair option on startup. use command prompt option down the road.
browse to c:\windows\winsxs folder and open pending.xml in notepad (takes a while)
then try to make the changes in the file as suggested in this blog.
Works like a charm.
Shahid Roofi- Proposed As Answer by Shahid Roofi Sunday, February 27, 2011 10:03 PM
-
Sunday, February 27, 2011 11:25 PM
Ok I did all this ( I hope I did it correct ) and it did a system restore as well ( one I have tried previously and didnt seem to work ). I did change the boot up back to regular w7 and not from the disk.
Via blue welcome screen it did some windows updates and once done and desktop showed up, i got this error
http://i52.tinypic.com/2v9651z.jpgThank you in advance
-
Monday, February 28, 2011 6:44 AM
Ok I did all this ( I hope I did it correct ) and it did a system restore as well ( one I have tried previously and didnt seem to work ). I did change the boot up back to regular w7 and not from the disk.
Via blue welcome screen it did some windows updates and once done and desktop showed up, i got this error
http://i52.tinypic.com/2v9651z.jpgThank you in advance
If you are able to log into Windows (which is what it looks like), I wouldnt worry about the SP1 installation being unsuccessful. Just wait until Microsoft fixes the problem and install it again.
-
Monday, February 28, 2011 7:28 AM
WOW! This saved my computer! I thought I was going to have to wipe and reinstall! I started with Error c000009a; then after trying to trouble shoot got the c0000034 error - and just about lost it all; then I found this forum and this other forum http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/error-code-c000009a-problems-applying-update-to/365bb5ac-065f-422e-901b-843496ff1245
that notepad.exe in cmd prompt saved the whole process for me! Thank you ALL so much!!!
-
Monday, February 28, 2011 7:39 AM
LOL at your long way around
just do notepad exe, open reboot.xml
<?xml version='1.0' encoding='utf-8'?>
<PendingTransaction Version="3.1">
<POQ>
<DeleteKeyValue path="\Registry\Machine\COMPONENTS" name="PendingRequired"/>
</POQ>
</PendingTransaction>copy that out and drop it into your pending.xml
few restarts done by sp1 and the computer will revert to previous settings, walla your in windows again. have a good day
-
Monday, February 28, 2011 8:27 AM
you rock man! It worked;
Also for those of you getting the C000009A Error - hit ctrl F again and type in amd64_microsoft-windows-e..atibility.resources_31bf3856ad364e35_pt-pt_ if it doesn't find it type in atibility.resources_31bf3856ad364e35_pt-pt_
Once your search finds this line of code find the first '<' that appears before it. Type in '!' right after the '<'
save the file and close notepad and the command prompt and restart your computer and go through normal install just as thiswoot posted.
Thanks again! You saved my computer!!!
-
Monday, February 28, 2011 5:29 PM
Yes it does and thanks so much...
but now I am back to another problem which was the original one such as when I log into any game, watch a youtube clip etc, it gives me the blue screen of death and I don't know why.
-
Monday, February 28, 2011 6:23 PM
Yes it does and thanks so much...
but now I am back to another problem which was the original one such as when I log into any game, watch a youtube clip etc, it gives me the blue screen of death and I don't know why.
It might be a problem with your video card or ram.
In the Windows search bar search for Windows Memory Diagnostic and run a memory scan. If thats not the problem try updating your video card drivers.
Also search for the blue screen error message on google.
-
Monday, February 28, 2011 8:17 PM
Cheers guys - two days of searching the web for a solution to this issue and have now fixed thanks to you :)
-
Tuesday, March 01, 2011 6:04 AM
Yes I did upgrade my drivers a few weeks back, but I guess I have a bad card it's an Nvidia GT220 and I have heard it is bad. I have called "Cyberpower" where I bought my PC from today and after charging me $32, they are sending me a W7 OEM... and I may have to go for a clean install.
Thank you very much for your help though :)
-
Tuesday, March 01, 2011 12:36 PMwhat causes this kind of problem? Microsoft should fix this, i've already xperienced this error twice, at first i had my PC reformatted, and now it's d same error again,,, just want 2 ask, is the "LAUNCH STARTUP REPAIR" is built only w/ certain brand of PCs, cause i cant find it in my LENOVO laptop, i pressed F8 as my PC boot, but it only shows this SAFE MODE SAFE MODE WITH NETWORKING SAFE MODE WITH COMMAND PROMPT LAST GOOD CONFIGURATION START WINDOWS NORMALLY pls help thanks
-
Tuesday, March 01, 2011 1:33 PM
what causes this kind of problem? Microsoft should fix this, i've already xperienced this error twice, at first i had my PC reformatted, and now it's d same error again,,, just want 2 ask, is the "LAUNCH STARTUP REPAIR" is built only w/ certain brand of PCs, cause i cant find it in my LENOVO laptop, i pressed F8 as my PC boot, but it only shows this SAFE MODE SAFE MODE WITH NETWORKING SAFE MODE WITH COMMAND PROMPT LAST GOOD CONFIGURATION START WINDOWS NORMALLY pls help thanks
Try pressing the reboot button on your PC while windows is on the black "starting windows" screen. Then once it starts up again, dont press F8. Just let it start up and see if "Launch Startup Repair" is one of the options.
Here's how you can do the same thing though with the Windows 7 DVD instead:
- Put the Windows 7 installation disc in the DVD drive, and then restart the computer.
- Press a key when you are prompted to restart from the disc.
- In the Install Windows window, select a language, a time, a currency, a keyboard input method or other input method, and then click Next.
- In the Install Windows window, click Repair your computer.
- In the System Recovery Options window, click the version of the Windows 7 operating system that you want to repair, and then click Next.
- In the System Recovery Options window, click Command Prompt.
Once you finish that, go to step 07 from my original post with the solution. -
Tuesday, March 01, 2011 3:02 PM
Thank you very very much! I helped me too!
But suddenly appeared new problems:
1) Bluetooth manager stopped working at all.
2) Printers in the network are not working.
3) Windows update menu is crasged. I can see only the book picture and ... nothing.
Do you know how to solve those problems?
-
Tuesday, March 01, 2011 5:19 PM
I have one big problem. When I try to save the pending.xml after having made the adjustments mentioned above, the notepad.exe freezes. At first I thought it was just processing so I let the computer be. But after 15 mins I finally gave up and restarted the computer. Tried it a couple of times now (tested Save, Save as and exiting and clicking save when prompted) but everytime ends the same way.
So frustrated knowing this is the final step from getting my computer back on track. Panicing, what to do?
-
Tuesday, March 01, 2011 6:14 PM
I have one big problem. When I try to save the pending.xml after having made the adjustments mentioned above, the notepad.exe freezes. At first I thought it was just processing so I let the computer be. But after 15 mins I finally gave up and restarted the computer. Tried it a couple of times now (tested Save, Save as and exiting and clicking save when prompted) but everytime ends the same way.
So frustrated knowing this is the final step from getting my computer back on track. Panicing, what to do?
At the top of notepad click Format and make sure "Word Wrap" is not checked. It makes notepad go a lot slower. By restarting your computer while it was saving, you couldve corrupted pending.xml, so delete pending.xml and make a copy of the backup you made earlier and name it pending.xml. Then open it. I would leave the file saving for 20-30 minutes this time. If it takes longer than that, you could burn a linux live cd and edit the file thru there. But first try turning off "Word Wrap" in notepad and leaving it for 20-30 minutes.
Vladimir - Im not sure. I dont use bluetooth, but my printer and windows update still work normally. What errors are you getting?
-
Tuesday, March 01, 2011 6:45 PMI did this and it worked but now when I boot to the desktop all I get is a black screen. I can safe boot with a screen. The only time I see nothing is when I go to the desktop. And I can't load the task manager either. Can someone help? Some how my system restore got cut off and I would hate to have to redo my whole system just because of windows!!! I have a laptop.
-
Tuesday, March 01, 2011 7:12 PMI also get a message that says failure to display security and shutdown options.
-
Tuesday, March 01, 2011 7:19 PM
I have one big problem. When I try to save the pending.xml after having made the adjustments mentioned above, the notepad.exe freezes. At first I thought it was just processing so I let the computer be. But after 15 mins I finally gave up and restarted the computer. Tried it a couple of times now (tested Save, Save as and exiting and clicking save when prompted) but everytime ends the same way.
So frustrated knowing this is the final step from getting my computer back on track. Panicing, what to do?
At the top of notepad click Format and make sure "Word Wrap" is not checked. It makes notepad go a lot slower. I would leave the file saving for 20-30 minutes. If it takes longer than that, you could burn a linux live cd and edit the file thru there. But first try turning off "Word Wrap" in notepad and leaving it for 20-30 minutes.
Vladimir - Im not sure. I dont use bluetooth, but my printer and windows update still work normally. What errors are you getting?
I'm so unbelievably frustrated now. Now when I try opening the pending file I receive: "the file is courrupted or unreadable". That goes for all the other pendingfiles as well with numbers following the name. Felt so close and now I just feel further away. And the copy I made is apparently blank sigh.. so now I'm screwed??? Or can someone upload theirs? Or they are personal for each computer?
I'm goin crazy here, I can't lose the files on my OS drive.
Btw the OS drive has become E:\ instead of C:\. Is this relevant at all to the problem??
Additionally, when trying to start windows now it doesn't hang up on the fatal error code thingie. Instead it comes up some text about checking C:\ and that one of your disks needs to be checked for consistency. It then tries running a ckhdisk but seems to fail:
"autochk can not run due to an error caused by a recently installed software package"
It tells me to try to do system restore from control panel. Unspecified error (766f6c756d62e63 3f1) is also mentioned.After awhile it continues on to a black screen where only the mouse cursor appears and then nothing more happens...
I'd appreciate any help terribly much!
-
Tuesday, March 01, 2011 7:46 PM
I did this and it worked but now when I boot to the desktop all I get is a black screen. I can safe boot with a screen. The only time I see nothing is when I go to the desktop. And I can't load the task manager either. Can someone help? Some how my system restore got cut off and I would hate to have to redo my whole system just because of windows!!! I have a laptop.
Boot into safe mode and login to the account you usually use. Then search for msconfig.exe and open it. Under the Startup tab, click disable all and apply. Then see if youre able to boot into windows normally. If so, you can re-add some of the stuff to msconfig that you normally use. -
Tuesday, March 01, 2011 8:03 PMYou're added on messenger!
-
Tuesday, March 01, 2011 8:28 PM
I did this and it worked but now when I boot to the desktop all I get is a black screen. I can safe boot with a screen. The only time I see nothing is when I go to the desktop. And I can't load the task manager either. Can someone help? Some how my system restore got cut off and I would hate to have to redo my whole system just because of windows!!! I have a laptop.
Boot into safe mode and login to the account you usually use. Then search for msconfig.exe and open it. Under the Startup tab, click disable all and apply. Then see if youre able to boot into windows normally. If so, you can re-add some of the stuff to msconfig that you normally use.
Nope no go still a black screen. I noticed in safe mode the banner at the top says sp1 and I think thats part of the problem. I'm running the 64 bit home premium does that make any diff? -
Tuesday, March 01, 2011 11:44 PM
I give up. I got past the original problem. Once the pending.xml was fixed the chkdsk went about and it started fixing and recovering orphaned files. When it finished it rebooted but after the starting windows screen there was just a blue screen and reboot. Error message mentioned "STOP: c000021a (Fatal System Error)"
Googling it says something about faulty sp installation can be the cause. So I take it that I'm pretty much screwed now? I don't mind reinstalling everything, however I would wanna save my files before make the format and clean install. I figure I can do the notebook.exe approach and manually copy important files over to my other hdd but is there a faster and more efficient way to do this? I'm not that experienced with computers. I don't have a external cabinet to put this drive into another computer and copy the files.Any suggestions? So many hours for nothing today :( Still very grateful for all the help I've received here today!
-
Wednesday, March 02, 2011 12:31 AM
DUDE YOU ARE THE MAN!!!!!!!!!! I spent a day in a half trying to get my laptop back on and in 5 minutes of searching I found this remedy. It took a little time to find the .cdf-ms line but after I removed that and waited 20 mins to restart- it loaded and tried to reinstall SP1 update then it failed but it allowed me back to my files, folders, pics and music. I am copying all of my data to an external HDD right now and I plan on installing a fresh new copy of Win7 in a few days just in case this happens again. You have just saved my life THANK YOU SO MUCH!!!!!!!!!!!!!!!!!!!!!!!
This guys is AMAZING!!!!!!!!!!!!
-
Wednesday, March 02, 2011 8:06 AM
^^thanks so much it actually worked.
It still shows that I need to update this SP1 but I'm afraid to do so.
Is it really necessary? Would Microsoft be able to help me?
Thanks,
Daniel -
Wednesday, March 02, 2011 10:50 AM
I can only show my problems.
How can I attach the snapshots or video?
-
Wednesday, March 02, 2011 4:07 PMI'd just like to say Tim Hoover & @thiswoot should be commended for their effort here. It's unimaginable that a company as big as Microsoft would allow such a catastrophic service pack hit the market to cause so many problems. That @thiswoot has stuck around this forum to try and help as many as he can is something Microsoft should take notice of because they certainly haven't helped many with these problems like he did. Thank you again to Tim Hoover & @thiswoot for this fix.
-
Wednesday, March 02, 2011 4:38 PMthis process worked great for us! thanks!! Mark
-
Thursday, March 03, 2011 5:10 AMThiswoot, you are a saint and a genius. Your fix worked. You saved me and my data and now I'd like to have your babies.
-
Friday, March 04, 2011 7:23 PMThanks for the fix, thiswoot! I looked through half a dozen of the 75+ threads on this, most of them with nothing more than some unhelpful "blame the user" solution before I found one where someone had linked to this fix. Worked great, no reinstall needed!
-
Saturday, March 05, 2011 2:31 AMHooray! Thank you.
-
Saturday, March 05, 2011 2:13 PM
A big THANK YOU from Germany.
-
Saturday, March 05, 2011 7:22 PM
I'm not sure I have the same problem* because my screen doesn't display the error number (just several "0"s, followed with "...")! I do have the same section in the pending file, however, except that it says:
"(...) PendingRenames\17e628ea97d5cb0121450000d801940e. (...)"
So can anyone tell me if I should try this fix / if it's "reasonably safe" and/or "reasonably likely it'll work"?
* My computer crashed when the power plug got disconnected, then installed some updates when rebooting... and hasn't been able to start Windows (Windows 7, 64-bit) ever since. I tried to "restore to an earlier version" (or something like that), with the only option being before some critical update from March 5 [not sure how that could've been SP1... I *thought* I had installed it on this computer some days ago, but who knows??!]. I didn't check before how many updates the computer was trying to install, but at least now it's 116,948, and there's a fatal error at update operation 282.
Sorry, I'm afraid that's about all I know. Sorry for being so ignorant about computers! :o((
Thanks a million for each and every piece of advice!!!
-
Saturday, March 05, 2011 9:58 PMThanks so much, thiswoot!! ... I'm currently working at logging into Windows Messenger (I keep getting error messages, possibly because of the computer I'm using now). I'll get in touch asap. :o/
-
Sunday, March 06, 2011 3:45 AM
Thank you! It works for me.YEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!
This method works without Safe Mode, without backups, without System Restore, without DISM, and without a Windows 7 DVD repair disc.
INSTRUCTIONS:
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Startup Repair"
03. When the Startup repair starts, click cancel.
04. After you click cancel it will show a box. Click "Don't Send"--> PIC: http://i52.tinypic.com/xgjriw.png
05. Click the link "View advanced options for recovery and support"
06. In the new window click Command Prompt at the bottom.--> PIC: http://i51.tinypic.com/50imu8.png
07. In Command Prompt type this and press enter: %windir%\system32\notepad.exe
08. Notepad will open. In notepad go to File-->Open.
09. Change the type of files notepad views from .txt to All Files (see pic)--> PIC: http://i51.tinypic.com/35nd74z.png
10. Now in Notepad, go to C:\Windows\winsxs\ (or whichever drive Windows is installed on)
11. In that folder, find pending.xml and make a copy of it
12. Now open the original pending.xml (it will load really slow because the file is huge)
13. Press CNTRL+F and search for the following exactly: 0000000000000000.cdf-ms
14. Delete the following text (yours will be a little different):<Checkpoint/><DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/><MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
--> PIC: http://i54.tinypic.com/adzpzp.png
Your PC might not have all 3 sections of code (<Checkpoint>, <DeleteFile>, <MoveFile>). Just make sure you delete section "Checkpoint" and whatever other sections have "000000000000000.cdf-ms". They will be right next to eachother.
15. Save the file, close notepad, close command prompt, restart your computer.
Once your computer starts up, do a normal startup (it may stall for 5-10 minutes at the "starting windows" screen, but leave it going) and the Service Pack will install some more stuff and restart a few times and then everything should be working! For some people, it reverts everything and cancels the service pack installation. For other people, the service pack installation completes. Either result is fine.
If you have any problems with the steps let me know.
- Proposed As Answer by xxxek Tuesday, April 19, 2011 12:19 PM
-
Sunday, March 06, 2011 8:47 AM
Hello everybody!
Finally I solved all problems! I would like to share the way of doing that.
1) Thanks thiswoot for his GREAT offer! I did exactly as he wrote and my Windows 7 Ultimate N x64 finally launched.
2) Many of services, menus and options were hurted and did not work. I download from MSDN site the new DVD, Windows 7 Ultimate 7 x64 WITH SP1. You all must download appropriated OSes.
3) I chose option for updating Windows and after day and night ... EVERYTHING IS WORKING FINE!!!
Thanks you thiswoot and you guys for the help!
-
Monday, March 07, 2011 11:54 AM
Hi everybody...
Just a question....
I have the same problem but a different error code...
My installation of SP1 stalls with error c0190003 trying to update amd64.... something
So, I have an intel processor. Why do I need the amd64 files?
What if, right after download finishes and before restarting, I just delete all the folders named amd64xxxx from WinSxS folder and then restart?
Could that just do all other updates and finish? Would it just skip (file not found) all the deleted updates and continue?
Thanks in advance for any responses,
Mars
-
Monday, March 07, 2011 2:22 PM
amd64 is the codename of the 64Bit consumer Windows because AMD sold the first 64Bit consumer CPU (Athlon64)So, I have an intel processor. Why do I need the amd64 files?
"A programmer is just a tool which converts caffeine into code"
Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221 -
Monday, March 07, 2011 3:50 PM
Hmmm.... Thanks Andre... I knew it was kind of a stupid suggestion and that I was missing some important information :p
Anyway, I seem to have solved the issue quite simply....I just downloaded and run the System Update Readiness Tool
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=914fbc5b-1fba-4bae-a7c3-d2c47c6fcffc
note: The above is for Win7 64bit
I restarted and reinstalled the SP1 through Windows Update... something peculiar happened...
The first time SP1 appeared in Windows Update it was only about 90-100MB. I clearly remember that...
After the System Update Readiness Tool, the SP1 was reported about 150MB.
Anyway, it installed like a charm. Restarted and done.
Mars
-
Monday, March 07, 2011 4:32 PMI love you...Your method saved my work when I was flipping out thinking I was screwed. I can't thank you enough!
-
Monday, March 07, 2011 7:44 PM
You Simply ROCK my friend !!! I normally turn off MS updates because of the terrible track record they have, for producing very poor updates. Going all the way back to Win95.... I like to check every few months and make sure there are no bugs then update. But I installed Win7 64 about three weeks ago worked very well then SP1 was pushed out and during the part where is says " DON'T TURN OFF YOUR COMPUTER DURING THIS UPDATE" the system rebooted and thats all she wrote! This fixed it up !
Thank you Thank you Thank you!
PS I've turned off my updates.....
G. :)
-
Tuesday, March 08, 2011 12:28 AM
my pending.xml does not have the "000000000000000.cdf-ms" section in it, or any other even similar to that, section.
NOTE: Before finding yor post i had installed windows 7 in the other partition of my harddrive.
In the one partition the Winsxs Directory has "rebbot.xml" and "poqexec.txt" documents
the other partition the Winsxs Directory has nothing but various subdirectories
There is, alhough, a 3rd, small partition (33.6MB) called BOOT where the "pending.xml" file can be found in the Winsxs Directory but as i said no "000000000000000.cdf-ms" in there.
Any suggestions?
-
Tuesday, March 08, 2011 2:33 AM
Hi, I did exactly as you recommended and it worked perfectly. I do not know if I shouldtry installing the service pack again, or if I should take some kind of action before proceeding.
Any suggestions?
Anyway, thank you!;-)
-
Tuesday, March 08, 2011 5:43 PMI also do not have "000000000000000.cdf-ms" in my pending.xml file. This is the 32bit version. I ran the readiness tool and everything before running the service pack update. I did notice that it did not shutdown properly doing the shutdown process. This is probably what caused the issue.
-
Tuesday, March 08, 2011 9:12 PM
Same error here but my machine has been acting terribly just prior to that. Such as "Unleashing mode" errors, crashed within minutes when logged into like WoW with blue screens. After dl SP1 everything pretty much stopped. I can't boot up, I get stucked on the same fatal error 282 out of ( forgot the number).
Now I am trying woot's tutorial but when I opened the notepad, it shows 3 hard drives and my supposly C drive is now on D.
I am so lost I have been trying to fix my machine for days and nothing is working. Repair doesn't and tells me my computer can not be repaired, sp1 deleted my restore points and when i tried to make an restore to the 24th of this month, that is when all stopped and I get hung up on the fatal error code.
I, as well don't have a backup disk, well I have one from last july but not sure how to work it. And dl an recovery disk, same thing nothing works. I don't know how to reinstall W7 since I don't have a disk.
What can I do? Any help would be so appreciated.
Same for me. Didn't work!
I can't access c: anymore (it will format). I just can access x: which is called Boot.
There I can find a 'pending.xml' but it doesn't contain any mentioned strings...Any chance to rescue my files??? I just need to rescue my data and then I can reinstall windows...
Thanks!
-
Tuesday, March 08, 2011 9:19 PM
Anyone with problems can add me on Windows Messenger and I will help
thiswoot@hotmail.com
-
Wednesday, March 09, 2011 3:55 AM
I also had many of the above problems with Sp1, however I don't use Windows Restore, but use Roxio Back on Track. I was able to restore back before I unsuccessfully installed SP1. Should I wait until Microsoft fixes this (maybe never), or do as one did and buy or download Win7 with with SP1 already installed? Thanks.
- Proposed As Answer by TexasTrucker Tuesday, March 29, 2011 9:42 PM
- Unproposed As Answer by TexasTrucker Tuesday, March 29, 2011 9:42 PM
-
Wednesday, March 09, 2011 4:17 AM
I also had many of the above problems with Sp1, however I don't use Windows Restore, but use Roxio Back on Track. I was able to restore back before I unsuccessfully installed SP1. Should I wait until Microsoft fixes this (maybe never), or do as one did and buy or download Win7 with with SP1 already installed? Thanks.
hi ,from the moment you use roxio or any other third party software the risks of malfunctions are greater , ...
check as to why it did not work , did you follow instructions ? updated and patched before the SP ? firewall or other security software (and hardware) like norton , mcafee off ? full admin rights ?
it would be a waste of time to rebuy win seven just for that reason , ... if you have the money , go for the ultimate version if you can use it
have a nice day
Scan with OneCare + Support ENDING for windows Vista & XP ! + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR + Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! -
Wednesday, March 09, 2011 7:26 AMThanks WOOT your the man worked first time ... Bloody Microsoft
-
Wednesday, March 09, 2011 9:11 AM
I expect you're getting used to being congratulated, thiswoot, but your fix worked for me too! Many thanks.
Incidentally, I'd also like to shake warmly by the throat, the person who gave the 'go-ahead' at Microsoft to push out this service pack. Judging by the volume of people having problems, it's clearly defective and ought to be withdrawn.
Al -
Wednesday, March 09, 2011 12:27 PM
works. excellent.
Any sign of Microsoft to fix this, when is it safe to turn Windows Updates back on?
http://learnerps-dotnet.blogspot.com -
Wednesday, March 09, 2011 1:08 PM
This issue just occurred on my Windows 7 Pro 64-Bit PC this morning. I was about to peform a recovery when I read this article. Upon making the changes thiswoot detailed and rebooting, my PC performed a service pack roll back and booted right up. Very nice instructions thiswoot.
Pro -
Wednesday, March 09, 2011 3:02 PMWindows update ran last night on my PC and SP1 was installed. It crashed with exactly the same error. I was certain that I was going to have to reformat but I tried this and it worked like a charm. It rolled back my SP1 install which I will now wait for a while before I try it again. Thanks guys. This was outstanding. You just have to be very careful in following the instructions.but they were very clear. I was lucky that my situation was exactly like the one in the post.
-
Wednesday, March 09, 2011 3:06 PMthiswoot's solution worked for me. It ended up reverting the changes. Thanks!
-
Wednesday, March 09, 2011 3:56 PMAwesome you rock. I am grateful to you for your detailed explanation and screenshots.
-
Wednesday, March 09, 2011 6:09 PMThis also worked for me. Thanks!!!!!!!
-
Wednesday, March 09, 2011 6:14 PMOMG! thiswoot! You are a god! My battery ran out while my Windows update was configuring and I had a fatal error. I work from my laptop and I thought I was screwed, but I followed ur steps and it worked like a charm! Ur a life saver!!! xxx
-
Wednesday, March 09, 2011 7:15 PMHi have the same problem and have been trying to do the fix however, when I try to go to View Advanced Options, a login screen appears asking for my user name and password. When I enter the user name and password it doesn't recognize them and I cant get to the command prompt. I have also tried going in through Safe Mode and it stalls. What can I do to get around this??
Thanks in advance -
Wednesday, March 09, 2011 7:26 PMHi, I have the same problem but here is an additional one. When I access the start-up repair screen and then chose View Advanced Options, first a drop down asking for the language / keyboard appears so of course I choose English... the a login screen appears with my user name already on there (I can't change it) and it wants my password. When that is entered it gives me a message saying the user name or password is wrong and I know it isn't. Does anyone have any suggestions to get around this?
Thanks in advance!! -
Wednesday, March 09, 2011 7:31 PM
Hi, I have the same problem but here is an additional one. When I access the start-up repair screen and then chose View Advanced Options, first a drop down asking for the language / keyboard appears so of course I choose English... the a login screen appears with my user name already on there (I can't change it) and it wants my password. When that is entered it gives me a message saying the user name or password is wrong and I know it isn't. Does anyone have any suggestions to get around this?
Thanks in advance!!
You are being prompted for the credentials for your local account. You may be on a domain, if so those credentials won't work. Use the username and password that was setup on the PC originally.
Pro -
Wednesday, March 09, 2011 7:34 PM
Hi, I have the same problem but here is an additional one. When I access the start-up repair screen and then chose View Advanced Options, first a drop down asking for the language / keyboard appears so of course I choose English... the a login screen appears with my user name already on there (I can't change it) and it wants my password. When that is entered it gives me a message saying the user name or password is wrong and I know it isn't. Does anyone have any suggestions to get around this?
Thanks in advance!!If you know how to take your hard drive out of your computer, you can plug your hard drive into a different computer and edit pending.xml from there (starting from step 8). Also if you have a boot disc, you can boot into Linux or something and edit the file from there. If you need help message me on Windows Live - thiswoot@hotmail.com
First try to do what ProSeriesNewb said above. If that doesnt work, do what I said.
-
Wednesday, March 09, 2011 8:04 PMWorked perfectly. You saved my day!!!!
-
Wednesday, March 09, 2011 8:36 PM
Another satisfied customer :)
I tried a few other methods before I found your post, followed your instructions and got the machine back up. The one issue I have is that after rebooting, it appeared to be installing SP1, then it came up with an error: Failure Configuring Service Pack - Reverting Changes. It came back up to a login prompt and I logged in OK however it shows that SP1 is installed. I think things may not be exactly right, though at least we can login and use the computer. I may just reimage with our new Win7SP1 image to be safe.
Thanks...
-
Wednesday, March 09, 2011 9:36 PMThiswoot, you just saved the day. At least half a dozen PCs had this problem at our site, and your solution worked for all of them. Thanks!
-
Wednesday, March 09, 2011 10:00 PMCrisis Averted Thanks To You!
-
Wednesday, March 09, 2011 10:40 PM
I don't have string "0000000000000000.cdf-ms" in my file, nor the alternative pending.******* file.
What should I do? I tried "Last Known Good," but it stops at 'Starting Windows.' What lines can I delete?
-
Wednesday, March 09, 2011 11:18 PM0xC0000034
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
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft -
Wednesday, March 09, 2011 11:45 PM
0xC0000034
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
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for MicrosoftThanks a lot .. I performed this, without the second step (it said not found). I rebooted (circular reboots without loading any Windows 7 icon). Did it again, it found it this time, and now it's doing circular reboots (no icon).
Any other options? I cannot believe this happened.
It's a bluescreen, config_initialization_failed. The Windows drive seems to be moved to drive D. Could that have something to do with it?
My install is totally screwed ...
-
Thursday, March 10, 2011 12:38 AM
Message me on Windows Messenger and I will try to help - thiswoot@hotmail.com0xC0000034
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
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for MicrosoftThanks a lot .. I performed this, without the second step (it said not found). I rebooted (circular reboots without loading any Windows 7 icon). Did it again, it found it this time, and now it's doing circular reboots (no icon).
Any other options? I cannot believe this happened.
It's a bluescreen, config_initialization_failed. The Windows drive seems to be moved to drive D. Could that have something to do with it?
My install is totally screwed ...
-
Thursday, March 10, 2011 1:44 AM
Hey, It really works!
Thank you!!
You maked my day!
-
Thursday, March 10, 2011 3:01 AM
HI,
I tried ProSeries NewB and your suggestions. I tried a boot disk but my 'puter wouldn't load it even after chainging the bios boot order. I now have the hard drive in another computer. When I try to change the win.sxs file in notepad, I can't save the changes. I get a message saying the file name or path do not exist and the the SaveAs dialogue menu opens with the path open to the file. When I try to save it again I get the same message. Any suggestions would be appreciated. I don't want to have to wipe the drive clean and reload everything....
Thanks again in advance!!
-
Thursday, March 10, 2011 3:56 AM
Try making a copy of pending.xml from your old hard drive to your desktop on your working computer. Then edit it from your desktop (with notepad) and save it. Then rename pending.xml on broken computer hard drive to pending2.xml and move the pending.xml from on your desktop to that folder.HI,
I tried ProSeries NewB and your suggestions. I tried a boot disk but my 'puter wouldn't load it even after chainging the bios boot order. I now have the hard drive in another computer. When I try to change the win.sxs file in notepad, I can't save the changes. I get a message saying the file name or path do not exist and the the SaveAs dialogue menu opens with the path open to the file. When I try to save it again I get the same message. Any suggestions would be appreciated. I don't want to have to wipe the drive clean and reload everything....
Thanks again in advance!!
-
Thursday, March 10, 2011 4:11 AMI still get the C00009a issue,,how do i turn into into a c0000034 issue so that i enjoy everyone's company here.
-
Thursday, March 10, 2011 5:46 AMHI I have tried that now as well. I can copy the file to the computer but reload the changed file. I can't change the file name It won't allow me to make changes... says I don't have the necessary permissions. I checked security and the only user listed with the permissions to alter the file is "Trusted Installer". I have tried to modify permissions for adminstrators and even the system and it won't allow a change. What can I try next?
Thanks again :-)- Edited by ffiire Thursday, March 10, 2011 5:58 AM
-
Thursday, March 10, 2011 5:57 AM
HI I have tried that now as well. It won't allow me to make changes... says I don't have the necessary permissions. I checked security and the only user listed with the permissions to alter the file is "Trusted Installer". I have tried to modify permissions for adminstrators and even the system and it won't allow a change. What can I try next?
Thanks again :-)Try this:
http://helpdeskgeek.com/windows-7/windows-7-how-to-delete-files-protected-by-trustedinstaller/
Except dont delete it obviously
-
Thursday, March 10, 2011 7:40 AM
Thanks that worked!! And then the file edit worked as well. The computer is back up and running! Thanks for all your help. I really appreciate it
Fred
-
Thursday, March 10, 2011 8:20 AMPerfect, thank you very much.
-
Thursday, March 10, 2011 8:22 AM
I had FOUR customers calling in today with exactely that problem since SP1 got rolled out with auto update.
Thank you.
http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/608ecca8-b815-4ff6-8f3c-a828518434a7/
did not work...
To Microsoft: Cannot keep up with the quality level you set with Win7 ?
-
Thursday, March 10, 2011 8:39 AM
thiswoot, you are a champ!
Had the error on 4 out of 5 new identical machines this morning.... the one that worked with the sp1 update, guess what it had a newer Bios...
the other 4 fixed with the suggestion of the pending.xml alteration - updating the bios of these as we speak...
UPDATE: updated the latest bios and it now installs sp1 flawlessly. So thats something else to check guys...
- Edited by Avantegarde-a-clue Thursday, March 10, 2011 10:26 AM
- Proposed As Answer by Avantegarde-a-clue Thursday, March 10, 2011 10:33 AM
- Unproposed As Answer by Avantegarde-a-clue Thursday, March 10, 2011 10:34 AM
-
Thursday, March 10, 2011 8:41 AMSehr guter Beitrag! Hat bestens funktioniert!
-
Thursday, March 10, 2011 9:00 AM
Works !
I have about 10pc's in my company. They all failed this morning after the service pack 1 for windows 7 x64 systems.
I wonder on a global scale what financial damage this service pack caused. Isn't a service pack made for fixing issues instead of creating new ones.
So now what? Tomorrow windows installs it again and the company stops working again? Is there a fixed update in the making???
-
Thursday, March 10, 2011 9:02 AM
hi tim
i did that but system gets stuck on starting windows screen.. any other solution
-
Thursday, March 10, 2011 9:49 AM
I applied sp1 trough wsus.. 2 systems failed this morning.
The fix won't work , I can't find the 000000000string in the file...anyone another working solution?
thanks
-
Thursday, March 10, 2011 10:03 AM
Today, ALL PCs with Windows 7 Pro 64bit gives the C0000034 error.
I have done the modify at the pending.xml, removing the 0000000000000000.cdf-ms string.
The PCs now works but the SP1 has failed at the 35%.
If i try to reinstall the SP1 it doesn't work because the last SP1 is frozen inside the OS.
It wants to reboot to complete the first SP1 installation, but this doesn't happens.
So : the first SP1 isn't complete and it wants to reboot the OS (but nothing changes), the second SP1 can't be installed because the first SP1 can't be uninstalled.
I think this is a big big big problem...
-
Thursday, March 10, 2011 10:39 AM
Hi,
We have sucessfully used this fix,
We have Experience the only pcs here, thats affected is 64bit - where the sp1 is automaticly installed.
-
Thursday, March 10, 2011 10:41 AM
Try this it
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Startup Repair"
--> PIC: http://notebooks.com/wp-content/uploads/2011/01/Recov-1.jpg
03. When the Startup repair starts, click cancel.
04. After you click cancel it will show a box. Click "Don't Send"
--> PIC: http://i52.tinypic.com/xgjriw.png
05. Click the link "View advanced options for recovery and support"
06. In the new window click Command Prompt at the bottom.
--> PIC: http://i51.tinypic.com/50imu8.png
07. In Command Prompt type this and press enter: %windir%\system32\notepad.exe
08. Notepad will open. In notepad go to File-->Open.
09. Change the type of files notepad views from .txt to All Files (see pic)
--> PIC: http://i51.tinypic.com/35nd74z.png
10. Now in Notepad, go to C:\Windows\winsxs\ (or whichever drive Windows is installed on)
11. In that folder, find pending.xml and make a copy of it
12. Now open the original pending.xml (it will load really slow because the file is huge)
13. Press CNTRL+F and search for the following exactly: 0000000000000000.cdf-ms
14. Delete the following text (yours will be a little different):
<Checkpoint/>
<DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
<MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
--> PIC: http://i54.tinypic.com/adzpzp.png
Your PC might not have all 3 sections of code (<Checkpoint>, <DeleteFile>, <MoveFile>). Just make sure you delete section "Checkpoint" and whatever other sections have "000000000000000.cdf-ms". They will be right next to eachother.
15. Save the file, close notepad, close command prompt, restart your computer.
Once your computer starts up, do a normal startup (it may stall for 5-10 minutes at the "starting windows" screen, but leave it going) and the Service Pack will install some more stuff and restart a few times and then everything should be working! For some people, it reverts everything and cancels the service pack installation. For other people, the service pack installation completes. Either result is fine.
-
Thursday, March 10, 2011 10:42 AM
Thanx for this!!!!!!!
i had 4 computers chrash out on this update (incl. the bosses)
you saved me a shitload of abuse and time and i REALLY want to thank you, so....THANX!
-
Thursday, March 10, 2011 10:57 AM
The fix works, or better it permit to complete the OS boot.The problem is that the SP1 installation is like frozen, because it hangs at 35%. And this are the results :
- the OS thinks to be a W7 SP1
- the Windows Update says that the PC needs to reboot to complete the SP1 installation (but it will be never completed)
- in Installed Applications the SP1 doesn't appears
If you try to reinstall the SP1 this isn't possible because the first installation wasn't complete.
Now i'm looking to a solution for this : uninstall the broken SP1 and reinstall it launched by the file.
And i've seen another thing : if you install the SP1 inside the OS (with Windows Update) and ONLY THEN you reboot the PC, is all OK.
But if you shutdown the PC and (before the PC has stopped) there is the installation of SP1... At the start probably you will have the problem.
-
Thursday, March 10, 2011 11:11 AM
This worked for me on 3 machines, all machins rolled back and did not go on to finish the sp1 install.
2 w7 ultimates 64bit and 1 w7 ultimate 32bit
nice work you clearly worked late on this.
I wonder if MS will "recall" the update from their global update service CDN, until this is resolved. I for one have denied the sp1 update on my update services server until im happy this has been resolved.
Thanks again, much appreciated, im sure you will end up helping millions with this post.
-
Thursday, March 10, 2011 11:15 AM
Hi,
Just to thank you for the solution!!!
We got 3 workstations that crashed on the sp1, got them working in 3 hours after the crash.
Thank,
Maarten
-
Thursday, March 10, 2011 11:21 AMA lot of people today !
-
Thursday, March 10, 2011 11:29 AM
Hi thiswoot - you are indeed a genius hero who has saved 4 machines in my office alone. Please can you advise how I should now proceed to install the update with SP1 for Win7 which failed in each case on our machines?
Microsoft Windoze 7 - the new Vista?
-
Thursday, March 10, 2011 11:30 AM
Hi thiswoot,
Just tried your above instructions to no avail.
The machine I'm working on has two pending files.
One is dated a few months ago and the other is current.
The current one only had mention of the 00000000... file in a string of text like you suggested. Tried deleting all as per your instructions still getting fatal error.
Also tried doing this with the older pending file but this one had a lot of references to the 00000000... string of text !? I tried deleting the string that looked relevant from the older file and still no luck.
My error is:
fatal error c0000034 applying update operations 282 of 118534 (_00000...)
Any help greatly appreciated.
Thanks,
-
Thursday, March 10, 2011 11:43 AM
a noi è successo su 7 workstation Hp, e su tutte ha funzionato.
mentre non ci sono stati problemi sui pc ( hp) e nemmeno sui notebook ( tutti con windows 7 pro 64 bit
Grazie ancora
Galliano
-
Thursday, March 10, 2011 11:48 AM
I got the same error on Windows 7 Enterprise x64 when applying update 291. I used the steps outlined by thiswoot and it worked. Cheers.
The only problem I had was getting the command prompt as it was asking me for the ASPNET account password just after step 5 in thiswoot's guide. A way around this is to boot off your Windows 7 installation disc and at the screen where it asks you to pick a language/time/keyboard, press Shift+F10 for a command prompt. What is usually my C: drive was mapped to D: but other than that, I could complete the rest of the steps.
-
Thursday, March 10, 2011 12:02 PM
Ok I did all this ( I hope I did it correct ) and it did a system restore as well ( one I have tried previously and didnt seem to work ). I did change the boot up back to regular w7 and not from the disk.
Via blue welcome screen it did some windows updates and once done and desktop showed up, i got this error
http://i52.tinypic.com/2v9651z.jpgThank you in advance
This is the mine !0x80070057
-
Thursday, March 10, 2011 12:15 PM
a noi è successo su 7 workstation Hp, e su tutte ha funzionato.
mentre non ci sono stati problemi sui pc ( hp) e nemmeno sui notebook ( tutti con windows 7 pro 64 bit
Grazie ancora
Galliano
Però adesso come sei messo con l' SP1 sulle 7 workstation ? -
Thursday, March 10, 2011 12:16 PM
stasera, prima di spegnerle le clono .... non mi va di avere sorprese domattina perchè l'ufficio tecnico non si deve fermare. ( e qui stamattina erano tutti fermi)
poi valuterò il da farsi da come reagiscono al riavvio.
-
Thursday, March 10, 2011 1:01 PM
You made my day thiswoot! Many thanks to you!
We received in our small company via WSUS the SP1 yesterday for our Win7 x64 Systems and this morning 4 from 5 PC's crashed with the fatal error C0000034!
After google and finding this posting from thiswoot we can now work again.But, how is it with reinstalling the SP1? I tried it, but Windows said there are missing some system components...
And i check google once again but didn't find anything.. The problem is, Windows said SP1 is installed, but it isn't!!
Any idea or help for this?Thanks
-
Thursday, March 10, 2011 1:15 PM
Thank you very much!
Work perfectly for me and saved me a lot of time and troubles!Systems were Win 7 Ult 64bit, Error was "Schwerer Fehler "C0000034" beim Updatevorgang 291 von 142731 (_00000...)" (german version)
SP1 was installed to the clients via WSUS on a SBS 2008 -
Thursday, March 10, 2011 1:33 PM
You made my day thiswoot! Many thanks to you!
We received in our small company via WSUS the SP1 yesterday for our Win7 x64 Systems and this morning 4 from 5 PC's crashed with the fatal error C0000034!
After google and finding this posting from thiswoot we can now work again.But, how is it with reinstalling the SP1? I tried it, but Windows said there are missing some system components...
And i check google once again but didn't find anything.. The problem is, Windows said SP1 is installed, but it isn't!!
Any idea or help for this?Thanks
If you try to reinstall the first problem is about a driver folder ATI (even if you have Nvidia card) that is missing in Windows\System32\Driverstore\Filerepository.I have put inside the missing driver folder, but the next error step is that it can't uninstall the frozen SP1.
It's my same situation, i have 15 PC with this "problem" now.
As you can see on my upper posts.
Bye
-
Thursday, March 10, 2011 1:58 PMYEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!
This method works without Safe Mode, without backups, without System Restore, without DISM, and without a Windows 7 DVD repair disc.
INSTRUCTIONS:
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Startup Repair"
03. When the Startup repair starts, click cancel.
04. After you click cancel it will show a box. Click "Don't Send"--> PIC: http://i52.tinypic.com/xgjriw.png
05. Click the link "View advanced options for recovery and support"
06. In the new window click Command Prompt at the bottom.--> PIC: http://i51.tinypic.com/50imu8.png
07. In Command Prompt type this and press enter: %windir%\system32\notepad.exe
08. Notepad will open. In notepad go to File-->Open.
09. Change the type of files notepad views from .txt to All Files (see pic)--> PIC: http://i51.tinypic.com/35nd74z.png
10. Now in Notepad, go to C:\Windows\winsxs\ (or whichever drive Windows is installed on)
11. In that folder, find pending.xml and make a copy of it
12. Now open the original pending.xml (it will load really slow because the file is huge)
13. Press CNTRL+F and search for the following exactly: 0000000000000000.cdf-ms
14. Delete the following text (yours will be a little different):<Checkpoint/><DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/><MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
--> PIC: http://i54.tinypic.com/adzpzp.png
Your PC might not have all 3 sections of code (<Checkpoint>, <DeleteFile>, <MoveFile>). Just make sure you delete section "Checkpoint" and whatever other sections have "000000000000000.cdf-ms". They will be right next to eachother.
15. Save the file, close notepad, close command prompt, restart your computer.
Once your computer starts up, do a normal startup (it may stall for 5-10 minutes at the "starting windows" screen, but leave it going) and the Service Pack will install some more stuff and restart a few times and then everything should be working! For some people, it reverts everything and cancels the service pack installation. For other people, the service pack installation completes. Either result is fine.
If you have any problems with the steps let me know.
ITS SOLVED MY PROBLEMThanks
-
Thursday, March 10, 2011 2:09 PM
This is amazing, thank you so much!! 2 out of 3 of our computers at work failed after installing SP1. After a morning of getting nowhere I found and tried your solution and it worked perfectly! This has saved me so much time and effort!YEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!
Got a few more computers to update still but not half as worried now I have this on hand! -
Thursday, March 10, 2011 2:25 PM
Thank you for your hard work in this matter. I am getting the same error message at boot up, but when I follow ThisWoot's instructions, I cannot find the 0000000000 file in my pending.xml. I've got three PCs down right now. Any help would be appreciated.
Eric
-
Thursday, March 10, 2011 2:45 PM
Not sure what happened to my previous post, but I am still having issues with this on three different PCs. But when I follow ThisWoot's well documented fix, I do not find the cdf-ms line to remove. I'm at a stopping point right now. Everywhere on Google points to this page. Any help would be greatly appreciated.
Eric
-
Thursday, March 10, 2011 2:59 PM
It worked for me, Windows 7 Professional 64bit!
Thanks!
F.
-
Thursday, March 10, 2011 3:00 PMI tried the method detailed by thiswoot (thank you for the investigative work) but when I bring up the Command Prompt and Notepad, I don't have an accessible c:\ drive. It looks like the computer refers to the c:\ drive as the x:\ drive (a.k.a. "Boot") and the pending.xml file in the x:\Windows\winsxs\ folder does not contain any of the script that is listed to look for (no "<DeleteFile>" or "<Checkpoint>" references at all). When I use Notepad to open the c:\ drive, the only thing that shows up is the SYSTEM file (no folders or other files of any type). Does anyone have any ideas on how to get around this? Thanx.
-
Thursday, March 10, 2011 3:06 PM
If you have an EFI based PC, probably you will find the pending.xml in D:\windows\winsxs
-
Thursday, March 10, 2011 3:19 PM
@thiswoot -
that worked a charm - thanks!
-
Thursday, March 10, 2011 3:37 PM
HUGE Thank You goes to ThisWoot for his time in finding the resolution to this problem and to dickfrey for pointing me to the correct winsxs folder. I was trying to edit the pending.xml file in X:\Windows\winsxs not D:\Windows\winsxs. Did not know there were too. This solutions has saved my butt.
Eric
-
Thursday, March 10, 2011 3:45 PM
We are in the same boat. After doing what thiswoot suggested we were able to at least get Windows 7 back up and running, but even though the Service Pack failed, Windows thinks it is installed. I manually loaded the update on some test machines in the office a few weeks ago and had no problems. I thought it was safe to roll it out with WSUS so I did and about half of my machines had fatal errored this morning....
I would highly advise people to not push this out with their WSUS server yet until there is more information out there on why this is happening.
-
Thursday, March 10, 2011 3:54 PM
Hello Thiswoot
It worked for me too. What does interesst me is how do you find the solution? Because I spent a lot of time to check many, many log files but did not find any hints on this solution. Thanks again.
Martin
-
Thursday, March 10, 2011 3:57 PMThanks you for posting this with great detail. This helped me get all our computers up and going this morning!!!
-
Thursday, March 10, 2011 3:58 PM
First... THANKS!
My only goal was to get the machines back up, 75% of my windows 7 laptops failed to install sp1 and 50% were rendered useless with the fatal error. I ended up just copying the pending.xml from x:\windows\winsxs to %systemdrive%\windows\winsxs. After a couple of automatic reboots, the service pack fails and rolls back. So users were able to get back to work.
Does anyone know the link to tell Microsoft the disaster this SP is doing? It's all I have been doing this morning. I think, it only affects 64bit-Laptops. Other than that, I cannot find other commonalities among the affected stations. Any clues?
- Edited by MaPaMa Thursday, March 10, 2011 4:13 PM
-
Thursday, March 10, 2011 4:09 PM
I also have seen that the computers that I have done this fix to they show as SP1 being installed but it actually reverted the changes when it booted up after changing the pending file. Does anyone know how to get sp1 installed properly after this happens. I would say about 50% of my machines had this failure.
Also to note. All of the machines had system restore enabled however, when I tried to do a restore there were no restore points. When I got them booted back up it also showed no restore points. Why would it delete them? Makes no sense to me!
-
Thursday, March 10, 2011 4:14 PM
We are having this same problem on the computers in our organization that are encrypted using Truecrypt. The fix works fine for computers that are not using truecrypt. The D: drive shows up, but "Needs to be formated." Anyone have any ideas?
Thanks
Sam
-
Thursday, March 10, 2011 4:29 PM
this worked for me, THANK YOU SO MUCH
any chance you might be willing to share with us the method you used to find the culprit? at least in brief.
-
Thursday, March 10, 2011 4:31 PM
Hi I followed your instructions but after restarting the pc it would go into the recovery mode. Then there are two options:
1. launch startup repair
2. start windows normally
However every time I choose the second option, it would revert back to this screen again (very quickly, only takes a few seconds). I have tried this many times but it always ends up like this, so is there any other advice that you could give me?
Many thanks!
-
Thursday, March 10, 2011 4:39 PM
IMHO the problem is born when the SP1 is installed with a shutdown. All the PCs that yesterday was turned off with the installation of the SP1, today alla give the problem. The PCs where the SP1 was installed inside W7 (without shutdown) are all OK. Probably the SP1 wants A REBOOT NOT A SHUTDOWN. So this is my experience.We are in the same boat. After doing what thiswoot suggested we were able to at least get Windows 7 back up and running, but even though the Service Pack failed, Windows thinks it is installed. I manually loaded the update on some test machines in the office a few weeks ago and had no problems. I thought it was safe to roll it out with WSUS so I did and about half of my machines had fatal errored this morning....
I would highly advise people to not push this out with their WSUS server yet until there is more information out there on why this is happening.
- Proposed As Answer by Frankvl777 Friday, March 11, 2011 10:46 AM
- Unproposed As Answer by Frankvl777 Friday, March 11, 2011 10:46 AM
-
Thursday, March 10, 2011 4:42 PM
@Sam from Canada
I think that you can only use a live cd with truecrypt inside.
The problem is that your hard drive is now encrypted...
-
Thursday, March 10, 2011 4:44 PM
@seaaa
You need a boot disk for W7 x64.
If you have another PC W7 x64 that is running, go to the message center and then create a boot disk.
Is something similar, now i don't remember because i'm using an XP.
-
Thursday, March 10, 2011 4:50 PM
IMHO the problem is born when the SP1 is installed with a shutdown. All the PCs that yesterday was turned off with the installation of the SP1, today alla give the problem. The PCs where the SP1 was installed inside W7 (without shutdown) are all OK. Probably the SP1 wants A REBOOT NOT A SHUTDOWN. So this is my experience.We are in the same boat. After doing what thiswoot suggested we were able to at least get Windows 7 back up and running, but even though the Service Pack failed, Windows thinks it is installed. I manually loaded the update on some test machines in the office a few weeks ago and had no problems. I thought it was safe to roll it out with WSUS so I did and about half of my machines had fatal errored this morning....
I would highly advise people to not push this out with their WSUS server yet until there is more information out there on why this is happening.
In our situation, that isn't the case. Our users had their computer on and logged out so the update would be pushed through. They came in this morning to the fatal error screen. What sucks is that I can't find a solution that actually lets me load the Service Pack on the failed machines after I use thiswhoot's method. -
Thursday, March 10, 2011 5:00 PM
Thanks so much to THISWOOT!!! Your solution worked on multiple Windows 7 computers with this MS Update of SP1 problem.
We are able to boot back up but SP1 failed to load. Has anyone tried downloading the file directly from MS instead of through MS Updates?
MICROSOFT: Take a look at this forum and look at all the wasted time and money that was caused not to mention those people that have not responded.
-
Thursday, March 10, 2011 5:16 PMTruecrypt - We were able to boot into a Ubuntu Live CD, install Truecrypt, open the Volume, and then edit the pending.xml file.
-
Thursday, March 10, 2011 5:22 PM
Thanks so much to THISWOOT!!! Your solution worked on multiple Windows 7 computers with this MS Update of SP1 problem.
We are able to boot back up but SP1 failed to load. Has anyone tried downloading the file directly from MS instead of through MS Updates?
MICROSOFT: Take a look at this forum and look at all the wasted time and money that was caused not to mention those people that have not responded.
Yes, it will fail to install. -
Thursday, March 10, 2011 5:47 PM
THANKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -
Thursday, March 10, 2011 5:48 PM
/agree
Beer for you!
however, you don't mention whether you should try to reinstall this update or not.
-
Thursday, March 10, 2011 6:24 PM
This worked for me. Had 5 machines that this happened to. Four were the exact same model and configuration...one was a little older. The commonality was that all five users used "SHUTDOWN" to install the update.
I had already messed up one PC before I found your post. I installed another instance of Win 7 64-bit...now I need to figure out how to undo that and revert to the old installation.
Thanks Thiswoot
-
Thursday, March 10, 2011 7:09 PMThis solution worked for me. A big THANK YOU to thiswoot for posting and updating this!!
-
Thursday, March 10, 2011 7:11 PM
Thank You!
I had this hit my school lab of 35 computers. Took an hour to fix them all, but the alternative was not that great.
-
Thursday, March 10, 2011 7:27 PMAfter trying various other solutions that didn't work, this one did. I appreciated the screenshots also. Many thanks.
-
Thursday, March 10, 2011 7:28 PM
Have we heard what is causing this problem? Microsoft, what's going on; what is the solution?
Sam
-
Thursday, March 10, 2011 7:46 PMThis only seems to affect some computers an not others. I had 7 in domain network that had this error occur on 3/9 the other 3 had no issue installing the SP1 the following day. Not sure what is triggering this? I ave 4 more workstations at other locations I instructed not to install unitl I could get to them. Called Microsoft Support the tech I got did not seem to be aware of this issue last night (3/9/11)!!! He also told me there is no way to intercept the downloaded update files from installing that I had to let them install. Fortunately the last 3 machines I had installed ok the rest with exception to one did not with the above fix.
-
Thursday, March 10, 2011 7:49 PM
Thank you for the solution, it worked on all computers with the problem.
I'm wondering in what state the installation is afterwards. It displays Windows 7 SP1 but I'm not sure if it's installed correctly. Reinstalling the service pack doesn't work, it says that components are missing.
What I'm also not sure about if this issue is somehow related to the WSUS server. All other computers on that I installed SP1 manually or through Windows Update didn't have any problems. Only the clients that get their updates through a WSUS server had these issues. We had these problems at a number of customers site all with their own WSUS server so I think it's not the installation of the server itself, but maybe the way it distributes the update to the client.
Alex
-
Thursday, March 10, 2011 7:52 PM
The commonality was that all five users used "SHUTDOWN" to install the update.
That was my experience also. Users who clicked the icon in the notification area and installed from the Windows Update control panel applet had no problem, while users who clicked "install updates and shut down" at close of business yesterday got the fatal error this morning. The fix from "Thiswoot" got us back in business, but I now have a bunch of workstations with questionable installs of SP1. -
Thursday, March 10, 2011 8:01 PM
Same issue at one of my customer sites. They have 3 identicle HP Windows 7 64 Bit systems. They did the shutdown update, 2 worked fine 1 got this error. The fix above worked. Thank You!
1) Is Microsoft aware of this issue, by this thread it seems it's a serious issue that's affecting quite a few systems.
2) By changing the pending.xml what are the ramifications? What happenes if we reinstall SP1? has anyone tried yet to reinstall?
Scott Anthony -
Thursday, March 10, 2011 8:06 PM
Firstly, a big THANK YOU!
A quick note that I couldn't get to the "advanced options for recovery and support" because it wouldn't accept my password (??)
I used this:; http://windows.microsoft.com/en-US/windows7/Start-your-computer-from-a-Windows-7-installation-disc-or-USB-flash-drive and followed your instructions from #6 onwards.
All is now well.
-
Thursday, March 10, 2011 8:30 PMAnswerer
For those impacted on this thread can you find these logfiles on your system and send them via skydrive to e_bitzie-at-hotmail.com?
1. Registry hives. COMPONENTS, and SYSTEM
a. C:\Windows\System32\Config\
2. CBS log directory
a. C:\Windows\Logs\CBS
3. Sessions.xml
a. C:\Windows\Servicing
4. Poqexec.log
a. C:\Windows\WinSXS
5. Pending.xml
a. C:\windows\winsxs\pending.xml
6. “Dir /s /b” Directory listing of c:\windows\winsxs
Please this is a high priority at Microsoft and they need to see these log files.
And ping me at susan-at-msmvps.com
- Edited by Susan BradleyMVP, Editor Thursday, March 10, 2011 9:08 PM
-
Thursday, March 10, 2011 8:55 PM
We are in the same boat. After doing what thiswoot suggested we were able to at least get Windows 7 back up and running, but even though the Service Pack failed, Windows thinks it is installed. I manually loaded the update on some test machines in the office a few weeks ago and had no problems. I thought it was safe to roll it out with WSUS so I did and about half of my machines had fatal errored this morning....
I would highly advise people to not push this out with their WSUS server yet until there is more information out there on why this is happening.
I ran into the Same Situation.
Does anyone know of a Fix to PREVENT this error from occurring before installing Win7 SP1. I am going to try installing the update manually on some workstations.
Additionally, I am concerned that this update is also for Windows Server 2008 R2. Does anyone know if it will break Windows Server 2008 R2?
I am in agreement with many on this posting, in hopes that Microsoft has taken witness of the problems this error has created, and hope that Testing Analyst are used to improve and augment hotfixes and service packs BEFORE being released to the public.
-
Thursday, March 10, 2011 9:03 PM
Susan,
I have posted a similar situation here:
As I mentioned in that thread, I have the machine running but SP1 will not install. Are you interested in this info from me?
Thanks!
Kevin
-
Thursday, March 10, 2011 9:05 PM
We are having the same problem with a handful of computers in the office... the fix above worked for all but one... Thanks thiswoot!
On the last computer it seems we cannot get the command prompt to open in order to continue with the fix, it just freezes and then reboots again... Anyone have any idea what to do about this? We do not have an original windows 7 disk.
-
Thursday, March 10, 2011 9:11 PM
We had today the same issue this morning that some customers gave us a call reporting machines not working anymore and hanging at "... step 282 of ..."
the solution from thiswoot worked for 3 of the affected machines - thank you for that, because of people like you other people can at least work again with their machines!
what I can confirm is that only 64Bit machines where affected and that it seems to be true that the problems only occured at machines that were shut down yesterday with the install updates and shutdown-option (one of our customers has a workstation that should run 24/7 - this one installed the sp1 correctly, although theres nearly exactly the same software on it like on the many others that crashed today).
Altough I´ve a problem with that solution and that is simply that the installation goes on until stating installation error - reverting changes - then users can login normally - the first one sees the sp1-install indicating that there was an installation error and that sp1 was not installed correctly although under computer properties it says windows 7 pro SP 1
So it would be great to find an answer to the question if theres now allright with the machines or not (although most functions needed in daily business life seem to work correctly as I could see on the first of the 3 "repaired" machines)
btw: I also tried the solution with the dism-command - it worked on none of the affected machines
I haven´t tried the method with applying an old registry-backup to the system (which in particular seems to be the same as the method removing the poqexec-key from registry) - but as it seems it leads to an 3/4 installed sp1 not able to reapply the update manually
Today I´m really embarrassed on microsoft since I called them in the afternoon looking at the dead computers of our customers letting me tell from ms that they want plenty of € before they help me to get things back running (although the ms worker told me that they´ve plenty of problems with sp1)!
-
Thursday, March 10, 2011 9:11 PM
A big thanks to thiswoot. We have 40 Win 7 64-bit computers. The calls starting coming at 7am this morning. Six of them had this C0000034 error from the SP1 update overnight. It apparently only happened to users who tried to run the update on their own and not wait for automatic updates in the middle of the night. There's no way I could have figured this out on my own. You saved my butt! Thank you!
-
Thursday, March 10, 2011 9:23 PMThe same commonality here - the only failed installations were those who used Shutdown to install the updates
-
Thursday, March 10, 2011 9:48 PMSimilar to Tim (above), we had about 30 computers across three locations with W7 64-bit and about 7 of them had this issue. The fix worked as far as getting them functional again--big thanks there--but now no Windows Updates will run on those machines. Has anyone else run into this? Each machine is spitting out error 666 after failing to install the updates. Not sure how to fix and have been unsuccessful in finding more information on that. Not sure of all the ins/outs that editing that section of code in the pending.xml file has in W7. Also, our system restore points are not to be found prior to this morning--I'm sure that's a symptom of this. Any help in re-fixing these machines with the new symptoms would again be greatly appreciated.
-
Thursday, March 10, 2011 10:08 PM
I have uploaded all the files but SYSTEM hive. They are in my public skydrive: http://cid-495f78ba5c771cf6.office.live.com/browse.aspx/.Public
-
Thursday, March 10, 2011 10:08 PM
Yes this works. Thanks - salvaged a 64 bit AMD processor laptop
-
Thursday, March 10, 2011 11:24 PM
Your are the man!!
We are an IT support company and we has a shock this morning.
But this fix it awesome.
-
Thursday, March 10, 2011 11:35 PMI'd like to thank Miguel for this fix. It works. I'd also like to thank Microsoft for their typical sub-par quality control. As a computer consultant they are making me rich. My clients don't particularly like it but it's paying off for me. Yay Windows!
-
Friday, March 11, 2011 2:49 AM
The same commonality here - the only failed installations were those who used Shutdown to install the updates
That's not the trigger. I manually set up 4 machines and installed the service pack using different methods... including 2 using "Install and shut down" and I haven't gotten any of them to fail yet. It's frustrating. I've got 8 machines to rebuild because of this and I can't figure out what is making some fail. -
Friday, March 11, 2011 3:49 AMYEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!
This method works without Safe Mode, without backups, without System Restore, without DISM, and without a Windows 7 DVD repair disc.
INSTRUCTIONS:
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Startup Repair"
03. When the Startup repair starts, click cancel.
04. After you click cancel it will show a box. Click "Don't Send"--> PIC: http://i52.tinypic.com/xgjriw.png
05. Click the link "View advanced options for recovery and support"
06. In the new window click Command Prompt at the bottom.--> PIC: http://i51.tinypic.com/50imu8.png
07. In Command Prompt type this and press enter: %windir%\system32\notepad.exe
08. Notepad will open. In notepad go to File-->Open.
09. Change the type of files notepad views from .txt to All Files (see pic)--> PIC: http://i51.tinypic.com/35nd74z.png
10. Now in Notepad, go to C:\Windows\winsxs\ (or whichever drive Windows is installed on)
11. In that folder, find pending.xml and make a copy of it
12. Now open the original pending.xml (it will load really slow because the file is huge)
13. Press CNTRL+F and search for the following exactly: 0000000000000000.cdf-ms
14. Delete the following text (yours will be a little different):<Checkpoint/><DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/><MoveFile source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"/>
--> PIC: http://i54.tinypic.com/adzpzp.png
Your PC might not have all 3 sections of code (<Checkpoint>, <DeleteFile>, <MoveFile>). Just make sure you delete section "Checkpoint" and whatever other sections have "000000000000000.cdf-ms". They will be right next to eachother.
15. Save the file, close notepad, close command prompt, restart your computer.
Once your computer starts up, do a normal startup (it may stall for 5-10 minutes at the "starting windows" screen, but leave it going) and the Service Pack will install some more stuff and restart a few times and then everything should be working! For some people, it reverts everything and cancels the service pack installation. For other people, the service pack installation completes. Either result is fine.
If you have any problems with the steps let me know or message me on Windows Messenger - thiswoot@hotmail.com
Feel free to send me a donation through paypal if this was helpful. :)
I LOVE YOU, It's really works!. Mi PC it's new i buy it yesterday and today when i was installing SP1 come this error and freak me out. Thanks, really for save mi ultra new PC. And the SP1 se desinstaló solo. -
Friday, March 11, 2011 3:57 AM
It is time to stop publishing SP1.
This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.
The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.
On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.
Company machines are less affected, but they failed too.
And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.
Please: Stop SP1, tame that bitch, release SP1a.
-
Friday, March 11, 2011 4:03 AMAnswerer
And until you call in, it won't happen. They are getting cases on this. And furthermore some machines go through just fine.
Posting here is not enough. Call 1-800-Micrsoft and open a case. State that you are having problems with a service pack.
They will issue a fix once they understand what the problem is but without data points of "why" they can't fix.
-
Friday, March 11, 2011 4:07 AM
It is time to stop publishing SP1.
This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.
The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.
On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.
Company machines are less affected, but they failed too.
And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.
Please: Stop SP1, tame that bitch, release SP1a.
hi ,what people need to do is understand what they are talking about , .... and follow instructions ! half of the comps are infected with who knows what and then they wonder they cant install anything ?
there are people who install it on vista , .....
now if people first take a look at whats inside sp 1 , maybe they would see that its not that whats causing problems , ...
on the other hand are all the computers that have no problem what so ever , ...
1000 plus and only two errors , one due memory burned and one due to power loss , .... both fixed within the hour , ...
but there is no forum for people who have managed to succeed , ... !!
oh and both under all four seven versions !
have a nice day
Scan with OneCare + Support ENDING for windows Vista & XP ! + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR + Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Get OFFICE 2010 FREE ! -
Friday, March 11, 2011 4:10 AM
I wanted to add my name to the list of users affected: I've got a Win 7 x64 laptop who tried to install SP1 using the shutdown method. I pretty much get the same error described here except it's on operation 291. Today I did successfully update 2 Win 7 32 bit laptops, but I did that through Windows Updates and not the shutdown & install method. Of note is that even on these two that were successful, the first time the PCs tried to install the SP, they both failed. The two 32 bit PCs are brand new Dell's not touched by a user yet, the 64 bit is 'new' Dell but has been used by a user for about 2 weeks now. Before I left work I left my PC shutting down and installing updates, I dread returning in the morning. :-/
To the point, I can't find any of the items in the pending.xml that have been cited. I've looked for 0000000000000000.cdf-ms, delete, deletefile, "checkpoint", "point", "0000" "pt-pt" as cited by jadedhero.
I've tried the method's listed here: http://support.microsoft.com/kb/975484/en-us and all have failed.
I have no system-restore points listed, and the Reg Key they recommend to delete wasn't there to begin with.
I can't find the "reboot.xml" file referenced by a previous poster.
I'm really not looking forward to going back to the office in the morning. Any help that you could provide would be much appreciated.
@thiswoot, the solution hasn't worked yet, but your sticking around here and helping is greatly appreciated. Are you still watching the forums?
Thanks in advance
::Edit::
I found that I was looking at the wrong drive. On the 64 bit computer I'm working with there were the C:\, D:\, X:\ and one other drive. C: was the factory dell partition, D:\ was the OS install partition and X: was the Recovery environment. I had been trying all of these steps on the X:\, When I changed to the D:\ I was able to find the section of the pending.xml that thiswoot referenced (and I found the reboot file). I removed the lines, and rebooted. It gave messages about failing and rolling back the SP, but when I go to windows update it shows SP1 as successfully applied. Is anyone else seeing this?
- Edited by an88truck Friday, March 11, 2011 5:16 AM
-
Friday, March 11, 2011 4:25 AMBig thanks to thiswoot who give me the answer with is post at Friday, February 25, 2011 3:22 PM 2/2 win 7 pro french x64 had this error c0000034. After the solution of thiswoot, on both computer, i had to go in system restore and move the slider to something different than 0%. They where at 1% before SP1. So check your restore point setting after SP1. For those who have company (not home user) with a lot of computer, use WSUS to deploy your update. It’s free and it a Microsoft product. Create a group of cobaye. Not more than 20% of all your computer int he cobaye group. So if an update fail like sp1, you will not loose all your win 7. WSUS http://www.microsoft.com/downloads/en/details.aspx?FamilyId=a206ae20-2695-436c-9578-3403a7d46e40&displaylang=en
-
Friday, March 11, 2011 4:25 AM
Message me on Windows Messenger and I will help - thiswoot@hotmail.comI wanted to add my name to the list of users affected: I've got a Win 7 x64 laptop who tried to install SP1 using the shutdown method. I pretty much get the same error described here except it's on operation 291. Today I did successfully update 2 Win 7 32 bit laptops, but I did that through Windows Updates and not the shutdown & install method. Of note is that even on these two that were successful, the first time the PCs tried to install the SP, they both failed. The two 32 bit PCs are brand new Dell's not touched by a user yet, the 64 bit is 'new' Dell but has been used by a user for about 2 weeks now. Before I left work I left my PC shutting down and installing updates, I dread returning in the morning. :-/
To the point, I can't find any of the items in the pending.xml that have been cited. I've looked for 0000000000000000.cdf-ms, delete, deletefile, "checkpoint", "point", "0000" "pt-pt" as cited by jadedhero.
I've tried the method's listed here: http://support.microsoft.com/kb/975484/en-us and all have failed.
I have no system-restore points listed, and the Reg Key they recommend to delete wasn't there to begin with.
I can't find the "reboot.xml" file referenced by a previous poster.
I'm really not looking forward to going back to the office in the morning. Any help that you could provide would be much appreciated.
@thiswoot, the solution hasn't worked yet, but your sticking around here and helping is greatly appreciated. Are you still watching the forums?
Thanks in advance
-
Friday, March 11, 2011 4:28 AM
It is time to stop publishing SP1.
This is yet the worst problem, but installing SP1 fails on such a huge amount of machines for completely different reasons.
The right way would be: Stop publishing SP1, fix those huge amounts of various problems why either SP1 renders the machines unusable, or why SP1 failes to install and reverts back, and publish SP1a once the issues are fixed.
On the non-company machines within my reach I have about 15% to 20% which cannot install SP1, only when doing the hard "in-place-upgrade" way. Another 15% to 20% require a lot of hard work to make SP1 install without the in-place upgrade way. Only a small amount of the users are "heavy windows modifiers", most of them do nothing special.
Company machines are less affected, but they failed too.
And now this which failes on a lot of company machines, this is the "hey, now it is getting _really_ critical" level where microsoft cannot state that only a few users who play around with their machines privately are affected. This is the "worse than virus infection" level since viruses of today do not render the machine dead.
Please: Stop SP1, tame that bitch, release SP1a.
hi ,what people need to do is understand what they are talking about , .... and follow instructions ! half of the comps are infected with who knows what and then they wonder they cant install anything ?
there are people who install it on vista , .....
now if people first take a look at whats inside sp 1 , maybe they would see that its not that whats causing problems , ...
on the other hand are all the computers that have no problem what so ever , ...
1000 plus and only two errors , one due memory burned and one due to power loss , .... both fixed within the hour , ...
but there is no forum for people who have managed to succeed , ... !!
oh and both under all four seven versions !
have a nice day
Your users seem to differ from mine: Only those running Windows 7 tried to install SP1, none of the XP and Vista users tried to run Sp1. None of the affected machine got viruses. None of the affected machines got hardware problems. The worst the affected machines have are two or three toolbars, Google toolbar (thanks google, I think bundled with java), Yahoo toolbar (thanks adobe flash), Ask-toolbar (thanks PDF creator).
Only a hand full (less than ten) of the SP1-completely-fail users are among those who dig deeper into the system, and their wording is: "Well, it was acting strange before, I needed to reinstall anyway." - and they do so and solve their problem that way and don't ask me to help.
-
Friday, March 11, 2011 4:42 AM
Okay, Ive got something that might help. (first time posting on TN btw, I read the fourms ALOT!)
I have a client that installed SP1 across their domain thanks to the WSUS implementation on SBS..
Anyway. out of all the users we originally thought only users with Asus laptops were affected, then we had a Dell fail.
Turns out, the only thing these machines have in common is they all ran Windows Anytime Upgrade, out of all the machines (3) that we upgraded using WAU , ALL of them failed to install SP1.
the fix for removing 000.cdf.ms rolled back the sp1 install fine and the user could login
Just trying to install SP1 from my usb key now to see if it is related to WSUS
ill let you know shortly.
Okay, Back.
The USB install throws errors about missing windows components, the solution to that is of course an in place upgrade, Ive not done this as the media the customer has is
1) a restore disk
2) Win 7 home (needs pro, hence WAU)
and my copy of win7 on usb is Enterprise.
So for now Ive barred this machine from installing SP1 and will see if a better solution is posted.
2 users here have gotten up and running with SP1 by formatting, installing 7, then SP1 then running WAU.. so looks like the issue MIGHT be there.
(edit) Corrected bad wording
- Edited by Atreidae Friday, March 11, 2011 5:15 AM
-
Friday, March 11, 2011 5:06 AMAtreidae, that must be a coincidence, since I know of 3 machines that were WAU'd, and all took SP1 fine.
-
Friday, March 11, 2011 6:00 AM
Hi all,
I, too, have been struggling with one of these this morning. One a site with identical machines (put in as a greenfield network), 5 of the machines took the update like a champ, whereas one has failed. Upon failure it reverts back to the PreSP1 state by means of a rollback, however this takes time.
The symptoms the customer sees is that the update appears to freeze at 70% for some time, then begins to rollback after about an hour. I've verified this with my own testing.
In order to get this far, I've also completed on this machine:
- Installation of the SUR tool, which reported zero errors.
- Perform a cleanup of the .NET Frameworks using the cleanup tool and reinstalled .NET Framework 4 Client
- Ran a full, non SP1 Windows Update, which located a number of minor patches. An interesting one that I noted was an updated Graphics Chipset driver for the Intel G35(I think) chipset.
- Clean reboot, of course
Luckily, while the install is running, you can browse to the C$ share of the machine and check the CBS logfile.
Here is an annotated version of what I found around the time of the failure:
----
2011-03-11 15:19:27, Info CSI 00000415 Calling generic command executable (sequence 29 (0x0000001d)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [52]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_TCPIP"-> LAST TIME THAT THE GUI WAS UPDATED TO SHOW A NEW PROGRESS PERCENTAGE.
2011-03-11 15:19:27, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 70.
2011-03-11 15:24:26, Info CSI 00000416 Done with generic command 29 (0x0000001d); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:48 [48]"Trying to install MS_TCPIP ...
...done.
"]
2011-03-11 15:24:26, Info CSI 00000417@2011/3/11:04:54:26.432 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-TCPIP, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;427187855
2011-03-11 15:24:26, Info CSI 00000418 End executing advanced installer (sequence 614)
Completion status: S_OK2011-03-11 15:24:26, Info CSI 00000419 Begin executing advanced installer phase 38 (0x00000026) index 576 (0x00000240) (sequence 615)
Old component: [ml:300{150},l:298{149}]"Microsoft-Windows-RasServer, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
New component: [ml:300{150},l:298{149}]"Microsoft-Windows-RasServer, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
Install mode: install
Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
Installer name: [15]"Generic Command"
2011-03-11 15:24:26, Info CSI 0000041a Calling generic command executable (sequence 30 (0x0000001e)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [53]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_RasSrv"
2011-03-11 15:29:16, Info CSI 0000041b Done with generic command 30 (0x0000001e); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:49 [49]"Trying to install MS_RasSrv ...
...done.
"]
2011-03-11 15:29:16, Info CSI 0000041c Calling generic command executable (sequence 31 (0x0000001f)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [56]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_Steelhead"
2011-03-11 15:29:19, Info CBS Startup: Changing logon timeout to a sliding window timeout: 900000
2011-03-11 15:34:06, Info CSI 0000041d Done with generic command 31 (0x0000001f); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:52 [52]"Trying to install MS_Steelhead ...
...done.
"]
2011-03-11 15:34:06, Info CSI 0000041e@2011/3/11:05:04:06.373 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-RasServer, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;828485001
2011-03-11 15:34:06, Info CSI 0000041f End executing advanced installer (sequence 615)
Completion status: S_OK2011-03-11 15:34:06, Info CSI 00000420 Begin executing advanced installer phase 38 (0x00000026) index 577 (0x00000241) (sequence 616)
Old component: [ml:296{148},l:294{147}]"Microsoft-Windows-RasBase, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
New component: [ml:296{148},l:294{147}]"Microsoft-Windows-RasBase, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
Install mode: install
Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
Installer name: [15]"Generic Command"
2011-03-11 15:34:06, Info CSI 00000421 Calling generic command executable (sequence 32 (0x00000020)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [54]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_NDISWAN"
2011-03-11 15:39:32, Info CSI 00000422 Done with generic command 32 (0x00000020); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:50 [50]"Trying to install MS_NDISWAN ...
...done.
"]
2011-03-11 15:39:32, Info CSI 00000423 Calling generic command executable (sequence 33 (0x00000021)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [53]""C:\Windows\System32\netcfg.exe" -e -c s -i MS_RASMAN"
2011-03-11 15:44:35, Info CSI 00000424 Done with generic command 33 (0x00000021); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:49 [49]"Trying to install MS_RASMAN ...
...done.-> THINGS START TO GO WRONG HERE IT SEEMS ..... STARTS TO TIMEOUT AND DETECT TIMEOUTS
"]
2011-03-11 15:44:35, Info CSI 00000425 Calling generic command executable (sequence 34 (0x00000022)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [51]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_PPTP"
2011-03-11 15:49:07, Info CBS Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Previous global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStateStageDrivers
2011-03-11 15:49:07, Info CBS Clearing HangDetect value
2011-03-11 15:49:07, Info CBS Saved last global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Setting HangDetect value to 1
2011-03-11 15:49:07, Info CBS Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:07, Info CBS Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Setting HangDetect value to 2
2011-03-11 15:49:07, Info CBS Startup: restarting the computer to attempt to continue or recover.->THIS RESTART NEVER HAPPENS...2011-03-11 15:49:07, Info CBS Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:07, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:07, Info CBS Setting HangDetect value to 3
2011-03-11 15:49:07, Info CBS Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:07, Info CBS Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:07, Info CBS Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:07, Info CBS Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:07, Info CBS Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:08, Info CBS Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:08, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info CBS Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info CBS Setting HangDetect value to 4
2011-03-11 15:49:08, Info CBS Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:08, Info CBS Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:08, Info CBS Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:08, Info CBS Startup: Timed out waiting for startup processing to complete
2011-03-11 15:49:08, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info CBS Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:49:08, Info CBS Setting HangDetect value to 5
2011-03-11 15:49:08, Info CBS Startup: restarting the computer to attempt to continue or recover.
2011-03-11 15:49:08, Info CBS Failed restart attempt. [HRESULT = 0x8007045b - ERROR_SHUTDOWN_IN_PROGRESS]
2011-03-11 15:49:08, Info CBS Startup: restart attempt failed, allowing the user to logon.
2011-03-11 15:49:43, Info CSI 00000426 Done with generic command 34 (0x00000022); CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Process output: [l:47 [47]"Trying to install MS_PPTP ...->....YET THIS COMPONENT COMPLETES SUCCESSFULLY.
...done.
"]
2011-03-11 15:49:43, Info CSI 00000427 Calling generic command executable (sequence 35 (0x00000023)): [30]"C:\Windows\System32\netcfg.exe"
CmdLine: [52]""C:\Windows\System32\netcfg.exe" -e -c p -i MS_PPPOE"-> WHY IS IT INITIATING A SYSTEM SHUTDOWN HERE....?
2011-03-11 15:49:46, Info CBS Startup: A system shutdown was initiated while waiting for startup to complete
2011-03-11 15:49:46, Info CBS Startup: Attempting to terminate the startup thread.
2011-03-11 15:49:46, Info CBS Failed a critical portion of startup processing. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
2011-03-11 15:49:46, Info CBS Ending the TrustedInstaller main loop.
2011-03-11 15:49:46, Info CBS Starting TrustedInstaller finalization.-> THESE DON'T LOOK GOOD!!
2011-03-11 15:49:46, Info CBS Failed to unload the COMPONENTS hive. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2011-03-11 15:50:52, Info CBS Starting TrustedInstaller initialization.
2011-03-11 15:50:53, Info CBS Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f\cbscore.dll
2011-03-11 15:50:56, Info CSI 00000001@2011/3/11:05:20:56.382 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x73d25d7d @0x73d0205a @0x701c99 @0x701236 @0x77c475a8)
2011-03-11 15:50:56, Info CSI 00000002@2011/3/11:05:20:56.392 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x73d67183 @0x73d64013 @0x701c99 @0x701236 @0x77c475a8)
2011-03-11 15:50:56, Info CSI 00000003@2011/3/11:05:20:56.392 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x73add84e @0x731f4bb0 @0x731f548e @0x701327 @0x701245 @0x77c475a8)
2011-03-11 15:50:56, Info CBS Ending TrustedInstaller initialization.
2011-03-11 15:50:56, Info CBS Starting the TrustedInstaller main loop.
2011-03-11 15:50:56, Info CBS TrustedInstaller service starts successfully.
2011-03-11 15:50:56, Info CBS SQM: Initializing online with Windows opt-in: False
2011-03-11 15:50:56, Info CBS SQM: Cleaning up report files older than 10 days.
2011-03-11 15:50:56, Info CBS SQM: Requesting upload of all unsent reports.
2011-03-11 15:50:56, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2011-03-11 15:50:56, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:56, Info CBS Blocked system sleep; prior state: 0x80000000
2011-03-11 15:50:56, Info CSI 00000004 CSI Store 723760 (0x000b0b30) initialized
2011-03-11 15:50:56, Info CBS Session: 30138275_3387440894 initialized by client SP Coordinater Engine.
2011-03-11 15:50:56, Info CBS Startup: current ExecuteState is CbsExecuteStateResolvePending
2011-03-11 15:50:56, Info CBS Disabling LKG boot option
2011-03-11 15:50:56, Info CBS Startup: Initializing driver operations queue.
2011-03-11 15:50:56, Info CBS Startup: Initializing advanced operation queue.
2011-03-11 15:50:56, Info CBS Startup: Waiting for SC autostart event
2011-03-11 15:50:56, Info CBS Startup: BlockTime: 10800000ms, BlockTimeIncrement: 900000ms
2011-03-11 15:50:56, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
2011-03-11 15:50:59, Info CBS Startup: SC autostart event signaled
2011-03-11 15:50:59, Info CBS Clearing HangDetect value
2011-03-11 15:50:59, Error CBS Startup: A possible hang was detected on the last boot. [HRESULT = 0x800705b4 - ERROR_TIMEOUT]
2011-03-11 15:50:59, Info CBS Current global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending
2011-03-11 15:50:59, Info CBS Previous global progress. Current: 119, Limit: 215, ExecuteState: CbsExecuteStateResolvePending->ROLLBACK STARTS HERE
2011-03-11 15:50:59, Error CBS Startup: No progress detected while needing to process the advanced operation queue, rolling back and cancelling the transaction. [HRESULT = 0x80004005 - E_FAIL]
2011-03-11 15:50:59, Info CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2011-03-11 15:50:59, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Rollback.
2011-03-11 15:51:01, Info CSI 00000005 Rolling back transactions...2011-03-11 15:51:01, Info CSI 00000006 Creating NT transaction (seq 1), objectname [6]"(null)"
2011-03-11 15:51:01, Info CSI 00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x1f8
2011-03-11 15:51:02, Info CSI 00000008 Performing 2387 operations; 2387 are not lock/unlock and follow:----
After this point, it's the rollback operation continuing.
Due to the two or three attempts to install, this customer's CBS log file is around the 35MB mark, but I think this is the relevant information here.
While the solution in this threat seems to get around it being stuck, it also appears to prevent an installation at a later date, so I'm hesitant to try this right now. I'm hoping this sheds a little light on the situation, or at least my situation.
Look forward to any info on this subject!
Cheers,
Dave
-
Friday, March 11, 2011 7:30 AM
If you see my past (and others users) posts, you can read that we are ALL in the same situationI found that I was looking at the wrong drive. On the 64 bit computer I'm working with there were the C:\, D:\, X:\ and one other drive. C: was the factory dell partition, D:\ was the OS install partition and X: was the Recovery environment. I had been trying all of these steps on the X:\, When I changed to the D:\ I was able to find the section of the pending.xml that thiswoot referenced (and I found the reboot file). I removed the lines, and rebooted. It gave messages about failing and rolling back the SP, but when I go to windows update it shows SP1 as successfully applied. Is anyone else seeing this?
-
Friday, March 11, 2011 7:35 AM
I've only been having the update issue with pre-installed systems. Cleanly installed systems are not having any problems at all.
Can any of you confirm this?
-
Friday, March 11, 2011 7:35 AMThanks a lot, this kicked life back into 2 portables :-)
-
Friday, March 11, 2011 7:56 AM
Ok, today the first surprise : ACDSEE 8 doesn't works and it's impossible to uninstall.
Great Microsoft !
-
Friday, March 11, 2011 7:57 AM
I've only been having the update issue with pre-installed systems. Cleanly installed systems are not having any problems at all.
Can any of you confirm this?
I hope ! There's only the OS... -
Friday, March 11, 2011 8:57 AM
Microsoft have released the official fix now for this problem.
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack
http://support.microsoft.com/KB/975484
Method 2: Delete the poqexec entry from the SetupExecute value (advanced users only)
Note We recommend that you try Method 2 only if you are an advanced user.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in WindowsTo delete the poqexec entry from the SetupExecute (REG_MULTI_SZ) value, you must clear the value. To do this, follow these steps:- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the Windows logon prompt appears and then
shutting down and restarting your computer.
Note On a computer that is configured to boot to multiple operating systems, you can press the F8 key when the Boot Menu appears. - Use the arrow keys to select Repair your Computer in the
Advanced Boot Options area, and then press Enter .
If you are prompted, select the Windows 7 installation to be repaired, and then click Next. - Select the language and a keyboard input method, and then click Next.
- Select a user name, type your password, and then click OK.
- Under System Recovery Options , click Command Prompt , and then press Enter .
- At the command prompt, type the following commands. Press Enter
after each command.
Reg load HKLM\BaseSystem C:\Windows\System32\config\SYSTEM
Reg Delete "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute
Reg add "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute /t REG_MULTI_SZ
Reg unload HKLM\BaseSystem - At the command prompt, type exit , and then press Enter .
- Restart your computer.
- Proposed As Answer by Nosey P Friday, March 11, 2011 8:59 AM
- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the Windows logon prompt appears and then
shutting down and restarting your computer.
-
Friday, March 11, 2011 9:05 AM
I found this:
http://tinyurl.com/4dbdqtc
and it solved my case.
Just my 2 cents, and if it works for you, please credit back the original author.
F.
-
Friday, March 11, 2011 9:13 AM
Microsoft have released the official fix now for this problem.
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack
http://support.microsoft.com/KB/975484
Now the question is : IT WILL WORKS for us that we have modified the "pending.xml" file ? Or it was better wait and take an holiday day (i'm joking) ?
-
Friday, March 11, 2011 9:30 AM
Thanks thiswoot, helped for me. i followed your instructions, rebooted, SP1 installation continued, then reverted and I finally couldstart up the computer again.
I am expecting problems in the future though: looking in windows update and on the systemtab in configuration, SP1 is marked as installed.
I hope Microsoft can find a clean solution for solving the consequences of this major disaster.
Luckily, we are relatively small organisation. I can imagine wat havoc this causing in big IT organisations.
Good luck all.
Frank
-
Friday, March 11, 2011 9:57 AM
Microsoft have released the official fix now for this problem.
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack
http://support.microsoft.com/KB/975484
Now the question is : IT WILL WORKS for us that we have modified the "pending.xml" file ? Or it was better wait and take an holiday day (i'm joking) ?
This Fix was also present yesterday. MS just added Windows 7 to the description and it is no longer only for Vista.
And to answer your question dickfrey, the result is the same as using the Fix stated here. We tried both and the result is the same. A System that is running for the moment. But a vague SP1 installation. The system thinks SP1 is installed but under installed Updates there is no SP. Also after the Reboot the SP1 installer stated installation failed. To reinstall SP1 manually also doesn`t work. At first you have problems with some ATI drivers as you also stated above. After fixing this the manual installation hangs on uninstalling the former SP1 installation.
So no real solution for all of us who had to fix the problems yesterday. Hopefully our Case at MS will give us a solution I am not interested in doing a fresh deployment on all systems that have been affected.
We also recognized that we are only facing the problem if you do: shut down and install . If you install manually everything is fine. And it doesn`t make any difference if you have a system that is running with Windows 7 for month or if the system is set up just a few days before. We`ve been able to reproduce the problem on a fresh deployed system.
-
Friday, March 11, 2011 10:39 AM
Eric,
Worked fine for me: search on ".cdf-ms". The first occurence in the file is in the correct block of text. It can take a while before finding it even on a fast computer.
To be sure: i think you mean that you don't find the line in the file. i want to make sure you are looking for the right things.
Frank.
-
Friday, March 11, 2011 11:07 AM
I can agree. The only computer that has the problem had SP1 installed via shutdown.
-
Friday, March 11, 2011 1:31 PM
Hopefully our Case at MS will give us a solution
Please keep us posted. -
Friday, March 11, 2011 1:50 PM
I"m about 50/50, all are pre-installed Dell Win 7 images. The two 64 bit computers have both failed, and the three 32 bit computer appear to have come through it okay. They all 5 of these were updated using the shutdown and install updates. Both 64 bits show that SP1 is installed.
::UPDATE::
At this point I have 14 Win 7 machines, 2 are 64 bit, 1 32 bit has yet to install SP1 and the other 11 Win 7 machines have updated successfully. The 64 bits have both failed and the both used Shutdown and install updates. All but one of these is a Dell pre-loaded OS. I've used a mixture of shutdown and install updates, and installing updates within windows on the 32 bit computers and they have all succeeded.
Anyone have advice on trying to remove SP1 to do force the re-install?
The tutorial listed here failed, because SP1 isn't listed in Add/Remove and the command line option reports that the KB isn't installed.
http://windows.microsoft.com/uninstallwindows7sp1
- Edited by an88truck Friday, March 11, 2011 3:52 PM forgot link to uninstall
-
Friday, March 11, 2011 2:07 PM
It saved my life!!!
Thanks!
-
Friday, March 11, 2011 2:28 PM
Hopefully our Case at MS will give us a solution I am not interested in doing a fresh deployment on all systems that have been affected.
I'm with you, man !!!
Please tell us something when Microsoft will give you a solution.
Me too, i don't want to format and reinstall 15 PC (with a lot of programs for mechanical engineers).
Thanks a lot
-
Friday, March 11, 2011 4:00 PM
Microsoft have released the official fix now for this problem.
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack
http://support.microsoft.com/KB/975484
Method 2: Delete the poqexec entry from the SetupExecute value (advanced users only)
You forgot to point out that there's a Method 1 that is both easier than Method 2 and recommended by MS over Method 2.
Method 1: Restore your computer to an earlier point in time by using System Restore
System Restore will restore your computer to an earlier point in time before you experienced this issue and then it will restart your computer. To restore your system, follow these steps:- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the
Windows logon prompt appears and then shutting down and restarting your computer.
Note On a computer that is configured for booting to multiple operating systems, you can press the F8 key when the Boot Menu appears - Use the arrow keys to select Repair your Computer in the Advanced Boot Options area, and then press Enter.
If you are prompted, select the Windows 7 installation to be repaired, and then click Next. - Select the language and a keyboard input method, and then click Next.
- Select a user name, type your password, and then click OK.
- Under System Recovery Options, click System Restore.
- n the System Restore window, click Next.
- Select the restore point for Windows 7 Service Pack 1 if one is available. If one is not available, select a restore point that you estimate was created before the problem started, and then click Next.
Note If you do not see any restore points, click to select the Show more restore points check box. - In the Confirm your restore point window, click Finish, and then click Yes when you are prompted.
- When you are prompted that System Restore completed successfully, click Restart.
Note If you see the black screen and the same error message or a similar error message, you may have to repeat these steps and restore your computer to an earlier date.
- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the
Windows logon prompt appears and then shutting down and restarting your computer.
-
Friday, March 11, 2011 4:03 PMThere is just a "little" thing that Microsoft doesn't know : the SP1 DELETE ALL the restore points...
-
Friday, March 11, 2011 4:04 PM
Microsoft have released the official fix now for this problem.
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack
http://support.microsoft.com/KB/975484
Method 2: Delete the poqexec entry from the SetupExecute value (advanced users only)
Note We recommend that you try Method 2 only if you are an advanced user.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in WindowsTo delete the poqexec entry from the SetupExecute (REG_MULTI_SZ) value, you must clear the value. To do this, follow these steps:- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the Windows logon prompt appears and then
shutting down and restarting your computer.
Note On a computer that is configured to boot to multiple operating systems, you can press the F8 key when the Boot Menu appears. - Use the arrow keys to select Repair your Computer in the
Advanced Boot Options area, and then press Enter .
If you are prompted, select the Windows 7 installation to be repaired, and then click Next. - Select the language and a keyboard input method, and then click Next.
- Select a user name, type your password, and then click OK.
- Under System Recovery Options , click Command Prompt , and then press Enter .
- At the command prompt, type the following commands. Press Enter
after each command.
Reg load HKLM\BaseSystem C:\Windows\System32\config\SYSTEM
Reg Delete "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute
Reg add "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute /t REG_MULTI_SZ
Reg unload HKLM\BaseSystem - At the command prompt, type exit , and then press Enter .
- Restart your computer.
We tried this official fix on a couple of PC's and both will not boot at all, we have to re-image them.Using the edit pending.xml fix by thiswoot works in getting the system up and running. The problem is SP1 appears to be half installed, some indications show it's at SP1 and others do not. You can't uninstall SP1 nor reinstall it. We are going to attempt to do a Win 7 w/SP1 DVD upgrade on those machines.
On a side note: this has been the worst update experience in my 17 years in IT.
- Restart your computer and start pressing the F8 key on your keyboard. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the Windows logon prompt appears and then
shutting down and restarting your computer.
-
Friday, March 11, 2011 4:15 PM
There is just a "little" thing that Microsoft doesn't know : the SP1 DELETE ALL the restore points...
You are dame right. Never liked restore points, but now I would be glad to have a restore point. -
Friday, March 11, 2011 4:25 PM
On a side note: this has been the worst update experience in my 17 years in IT.
Clearly you're forgetting the nightmare that was installing MS-DOS 6.21 over 6.20. It took seconds and cost many, many kilobytes. SP1 can't hold a candle to it.
On Method 1 not working because there are no restore points: Oh.
On Method 2 not working because it causes the system not to boot: My.
This isn't going to be a good day.
-
Friday, March 11, 2011 4:29 PM
I've uploaded my files to skydrive:
http://cid-85e24cb98d5dea2e.office.live.com/browse.aspx/Win7Pro%5E_SP1%5E_failure%5E_DellM4500x64?nl=1&uc=1
-
Friday, March 11, 2011 4:39 PM
Craig.B
I'm ready to retire over this. Read your "by the way..." Had to laugh. I'm sure I've had worse, but this is bogus.
Has anyone found the needle in the haystack yet?
Rock on...
-
Friday, March 11, 2011 4:53 PM
Just for information: here is an official MS statement to the procedure descripe by thiswoot:
And for all who want to know what MS says:
At moment MS only knows about this error in combination of having the SP1 from your WSUS und installing it through "shutdown and install updates". But MS is working on a solution for the problem we have now. I will keep you up to date when I know something new. Maybe on Monday there will be a fix.
For all of you a nice weekend.
Lars
-
Friday, March 11, 2011 5:01 PMWhat do you do when I have PC's on a server. Thiswoot won't work! Any solutions, I have 5 pc down now
-
Friday, March 11, 2011 5:07 PM
What do you do when I have PC's on a server. Thiswoot won't work! Any solutions, I have 5 pc down now
What do you mean by "PC`s on a server" ? Do you mean Virtual machines ? -
Friday, March 11, 2011 5:08 PM
But this thread predates by two weeks it appearing in WSUS.At moment MS only knows about this error in combination of having the SP1 from your WSUS und installing it through "shutdown and install updates". But MS is working on a solution for the problem we have now. I will keep you up to date when I know something new. Maybe on Monday there will be a fix.
-
Friday, March 11, 2011 5:11 PM
But this thread predates by two weeks it appearing in WSUS.At moment MS only knows about this error in combination of having the SP1 from your WSUS und installing it through "shutdown and install updates". But MS is working on a solution for the problem we have now. I will keep you up to date when I know something new. Maybe on Monday there will be a fix.
You are right. It is just what MS knows out of the offical support Calls. -
Friday, March 11, 2011 5:32 PM
- I am curious, has anyone figured out a way to automate this to some degree? I tried creating a batch file and running from USB stick that would copy a pending.xml file over, but it seemed that batch files might not be happy in windows recovery environment and the pending.xml has unique characteristics that is specific to the machine. Anyway to automate the removal of the checkpoint entry?
- Anyway to automate the registry solution suggested by Microsoft?
- Does anyone know if portable Notepad++ can be used in Windows Recovery Environment so the XML is easier to read and identify?
- I know there is a way via Linux to write scripts for cutting info out of a file, not sure how this can be accomplished in windows environment?
-
Friday, March 11, 2011 5:49 PM
If it helps confirm, my incident started from WSUS W7 SP1 auto install and user restart.
I was able to use "fix" by:
"rename and replace the DEFAULT, SYSTEM, SOFTWARE, SAM, and SECURITY files in "system32\config" folder throught the recovery console command prompt, I got the OS to boot up." quote from another user's post
System is now unstable and keeps trying to install SP1 and fails.
Side note: Turned off System Restore in domain via GP long ago, after too many problems with virus hiding in them. This is rare case where restore point would be nice, but apparently would not be available -- as posted above.
Hoping for fix from MS.
-
Friday, March 11, 2011 5:56 PM
Please read through these blog posts from the Windows setup/deployment platform support team:
If there are any issues that these blogs (and the KB referenced in them), please call Microsoft Support as soon as you can.
-Michael
-
Friday, March 11, 2011 6:46 PM
I posted a comment on the 2 blog. Jeff Hughes' second blog suggests to "wait for the failure to occur" so a rollback of the service pack is done. Anyone of the people that have posted in this thread know well that at the point of the fatal error, the machine is stuck. There is no waiting for the failure to occur so the service pack rolls back.
The 1st blog is more useful, however neither addresses a way to successfully install SP1. They just try to get you up an running, which renaming the pending.xml also does (enables the machine to get to a point were it can perform a roll back).
I hope the tech that have participated in this thread, head over to those blogs and make constructive comments so all the hard work done here is not lost in the ASK THE CORE TEAM blogs.
-
Friday, March 11, 2011 6:56 PM
Many thanks. This also worked for me to revert the SP1 install. For everyone's information we had failed updates on all of our Dell Latitude Laptops with I5 processors. Our desktop Vostros (Q8300) all updated flawlessly.
For our laptops the fix did not allow the install to complete but instead caused what appears to be a clean revert. Would welcome any insight into how and when I should attempt to compete the SP1 update.
-
Friday, March 11, 2011 6:58 PM
Before using this solution you should be aware of these
-
Friday, March 11, 2011 6:59 PM
I have another system that had the same problem. It is now 2 out of 5 identical systems that have failed. The only commonality is the fact that SP1 was installed during a shutdown event.
I will try the KB article and see if that works otherwise I will be forced to use "thiswoot"'s fix like I did on the first one.
Patiently awaiting a fix from Microsoft...
-
Friday, March 11, 2011 7:04 PM
These blogs were written by me. The intent was to help people get their systems recovered as quickly as possible. The first blog gives the data we have to help get the machines to a working state in most cases. I realize that this isnt in ALL cases. The second blog is meant to assist people in knowing exactly what is happening on their systems when they choose to do the pending.xml hack.
In both cases, getting SP1 back on the machine for many people has been as simple as reinstalling the service pack. If you have one of these issues and have sets of logs, post a link to your skydrive here and I will have them triaged so that we can come to the root of the problem. If you have had this problem and reinstalled SP1 and still experienced failure I want to know about it and I want your logs. The logs I would like captured are in my personal blog and my teams blog noted above.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 11, 2011 7:47 PM
Do you know the success rate of the SetupExecute solution? Ive had 2 people message me telling me it caused their computer to continually reboot at startup, which then made them unable to try the pending.xml solution. I know the pending.xml solution isnt perfect, but it gets 99% of the computers back up and running.These blogs were written by me. The intent was to help people get their systems recovered as quickly as possible. The first blog gives the data we have to help get the machines to a working state in most cases. I realize that this isnt in ALL cases. The second blog is meant to assist people in knowing exactly what is happening on their systems when they choose to do the pending.xml hack.
In both cases, getting SP1 back on the machine for many people has been as simple as reinstalling the service pack. If you have one of these issues and have sets of logs, post a link to your skydrive here and I will have them triaged so that we can come to the root of the problem. If you have had this problem and reinstalled SP1 and still experienced failure I want to know about it and I want your logs. The logs I would like captured are in my personal blog and my teams blog noted above.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 11, 2011 7:55 PM@woot: Right now the success rate I have seen internally is running in the 80% range. I havent seen a lot of the reboot loop behavior but the ones I have seen have been resolved using /revertpendingactions.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 11, 2011 9:06 PM
The solution from thiswoot worked most computers in the office, however we are still struggling with the last one.
The user was not logged in as an administrator when the problem happened, and because the user is locked out of all editing we cannot seem to get the solution to work (we cannot edit the file we need to delete any way we try).
It will not open to windows in any way, recovery or otherwise... how do we change the user to an administrator when we can only access BIOS?
-
Friday, March 11, 2011 9:16 PM
The solution from thiswoot worked most computers in the office, however we are still struggling with the last one.
The user was not logged in as an administrator when the problem happened, and because the user is locked out of all editing we cannot seem to get the solution to work (we cannot edit the file we need to delete any way we try).
It will not open to windows in any way, recovery or otherwise... how do we change the user to an administrator when we can only access BIOS?
If you take the hard drive out of the broken computer and plug it into a work computer, you can edit the file from there.
Or you can burn a Linux boot cd, put it in the broken computer, and edit pending.xml thru there.
200mb linux live iso: http://www.slax.org/get_slax.php
-
Friday, March 11, 2011 9:20 PMIf you can get into WinRE it shouldnt care about your user rights.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 11, 2011 10:10 PM
@woot: Right now the success rate I have seen internally is running in the 80% range. I havent seen a lot of the reboot loop behavior but the ones I have seen have been resolved using /revertpendingactions.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/Which I'm assuming is in reference to DISM:
http://technet.microsoft.com/en-us/library/dd744311(WS.10).aspx
Can you give us an example command line appropriate for this case? From the examples I've seen, it's more than the one switch.
-
Friday, March 11, 2011 10:17 PMthe command is
DISM /image:C:\ /cleanup-image /revertpendingactions
-
Friday, March 11, 2011 10:23 PMFYI, it could also be D: in the command above depending on if the system reserved partition has a drive letter. To ensure you have the right drive letter, do a DIR at the command prompt and choose the drive letter with a \Windows directory.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 11, 2011 10:44 PM
Thanks, modify pending.xml works.
-
Friday, March 11, 2011 11:22 PM
Summary thus far:
Multiple users were down. Tried official MS fix which led to continuous reboot. Used edit pending.xml fix and got users working in about 10 minutes. We tried to upgrade to Win 7 Ent x64 w/SP1 to a machine that we had used the pending fix but not everything is working properly. Back to build machines from WDS image and wait for SP1a for other machines.
-
Saturday, March 12, 2011 2:09 AMso NOW that i messed my registry and im in a constant loop how do i get back to thelovely error 00034?
-
Saturday, March 12, 2011 2:46 AMThat's what the DISM command is supposed to resolve. See the posts a few back. If you would, let us know how it goes.
-
Saturday, March 12, 2011 2:52 AM
Nope, dism doesnt work. I get an error 0x8000ffff
log says
PID=944 an error occured clearing the pending actions from the image.
-
Saturday, March 12, 2011 1:07 PM
@Craig: If you reinstall SP1, let me know how you did it (WSUS/standalone) and what the results were
@watever: Not sure what you mean by "messed up your registry" but if you delete and recreate the SetupExecute key it should break the loop. The error you mention is the exit code for catastrophic failure. You can try renaming the system hive and using the one in the \Windows\system32\config\regback folder to see if it will get the machine bootable.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Saturday, March 12, 2011 2:04 PMThis worked for me. It saved the day
-
Saturday, March 12, 2011 3:08 PMAfter replacing the old registry with the new one the update process appears again BUT this time it stops at 178 while updating "memtest.eli" and after that it just skips and attempts to go to the Operating System but all i see is a BLACK screen with the mouse on it. Same for safe mode and last known config.
-
Saturday, March 12, 2011 3:57 PM
This worked for me. It saved the day
Which method? -
Saturday, March 12, 2011 9:33 PMSounds like there's just something corrupt here watever. You could boot into WinRE and try Startup Repair to see if it finds any issues. Not being able to boot into safe mode though is never a good thing.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Saturday, March 12, 2011 10:01 PMno dice....:( I cant believe this is happening to me.. Am i the only person with this?
-
Saturday, March 12, 2011 10:53 PM
You're not the only person that's had this happen to them but you are in the minority of folks that havent had any solution work.
I guess at this point, you can to a parallel installation. At least that gets you back up and you can move your data.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Sunday, March 13, 2011 6:23 AMThing is , i already have windows xp on a different hard disk on my computer and i can simply opt for a windows 7 repair-reinstall but its just not right i don't want to have to let go of all personal settings and what have you.
-
Sunday, March 13, 2011 6:47 AM
This works perfectly!!!
YOUR A LEGEND!!!! Woot! Woot!!!
-
Sunday, March 13, 2011 11:01 AM
Thank you ThisWoot, MS shall give you a reward for that!
It worked for me.
-
Monday, March 14, 2011 12:35 AM
Hello,
For people encountering the c0000034, error we would like to capture some information to help us try to reproduce the issue.
What type of system is this? (x86 or x64?)
What SKU? (Home, Professional, Enterprise, R2 Standard, R2 Enterprise, etc.)
How was SP1 installed? (WSUS, WU, Standalone package, etc.?)
Any additional steps when installing would be good to know
Did you reboot immediately after installing SP1?
If not how long before you rebooted?
Did you click shutdown to complete the installation?
Did you install any other software or updates at the same time prior to rebooting the SP1 installation?
What types of software were on the system? (Anti-Virus, Music Software, Browsers, other software)
Can you post the answers or send them to me in email?
Send to darrellg@online.microsoft.com ( remove the online before sending)
Can you make some logs and other information available from your system?
1) CBS log directory (c:\windows\logs\cbs\*)
2) Pending.xml (c:\windows\winsxs\pending.xml)
3) Poqexec.log (c:\windows\winsxs\poqexec.log)
4) Sessions directory (c:\windows\servicing\sessions)
5) SYSTEM and COMPONENT hives (c:\windows\system32\config\SYSTEM *and* COMPONENTS)
6) System and application event logs
7) WindowsUpdate.log
8) Setupapi.dev.log
9) “Dir /s /b” listing of windows\winsxs
Can you post these to a location where they can be downloaded? Or send me email with the link if you do not want to post them.
Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en -
Monday, March 14, 2011 10:28 AMIn my case, WSUS was the one that sent update. Machines automatically went to reboot and error appeared. Problem appeared on W7 Enterprise, x64 version. On x32 systems, more then 200 machines went ok.
Standard software is McAfee Enterprise, Internet explorer, MS Office PRO 2010, Adobe Acrobat 9 STD, WinZip 11, MS Defender is ON, and some smaller programs/viewers. -
Monday, March 14, 2011 11:24 AMYEP I GOT IT WORKING!! I DONT KNOW IF MY METHOD IS THE BEST BUT IT WORKS!
Feel free to send me a donation thru paypal if this was helpful. I have no money. :)
Your solution worked for me too!!THANK YOU!!
Filippo
-
Monday, March 14, 2011 12:36 PM
Hello,
Resqued 32 PC's this mornign using Thiswoots remedy. Thanks!!!
We use all mainstrean software on a mainstream PC's so I would say to MS that they should do more thorough testing with updates. I tested Win7 SP1 on my x64 computer using manual installation. No problems although installation took a long time. Since everything seemed to be in order I allowed WSUS to update 50 PC's resulting 32 PC's failing to boot!!
Our System & applications image is the same on all PC's...
-
Monday, March 14, 2011 12:42 PM
If you are repairing more than few computers:
Repair one, capture repaired pending.xml, create WinPE and place repaired pending.xml there and a script that copies repaired xml from PE CD to C:\windows\winsxs. Boot to WinPE by CD and hit the command you wrote. This way it only takes a minute or two to repair a workstation.
-
Monday, March 14, 2011 12:45 PM
Everyone;
I know that you're all in situations where you might need to do the pending.xml suggestion by woot. I really want to caution all of you to do this only as a last resort. I wrote about what issues this could cause later in the OS lifecycle here: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
Please make sure you understand that information and assist Darrell and I in getting information from your systems so we can give you actual repair steps for the problem you're encountering and not a workaround that might put you in worse shape later.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Monday, March 14, 2011 2:47 PM
I've encountered the problem on Windows 7 Enterprise x64 machines and on one Windows Server 2008 R2 that is run on a users laptop. It appears that WSUS downloaded the update and even though it was not schedule to be installed until several days later it got installed, most likely when users did a ShutDown. In Win7/2008 R2 when updates are pending, your only option appears to be ShutDown (and install updates) as opposed to the options of ShutDown OR ShutDown and Install Updates. I've tested installs of SP1 via the downloaded files, going to Microsoft Updates and WSUS updates OK; as long as you click install the update. It appears that the Shutdown and Install Updates is what triggers the problem.
Base System Software: Office Professional Plus 2010, Visio 2010, Project 2010, Adobe Reader 9/X, TFS Explorer, Symantec Endpoint Protection
-
Monday, March 14, 2011 3:43 PM
Same here. Win7 Enterprise, x64. Some time ago I managed to install SP1 successfully on one of our PCs using online Windows Update. Today I tried to do the same on another PC over WSUS from our university WSUS server and got c0000034 error. Both PCs are identical hardware (Fujitsu ESPRIMO E9900) and have the same software installation.
For recover, I tried the registry trick first and got the blue screen. 'reg delete' didn't find the key (SetupExecute) to remove. After reboot into RE I launched regedit and loaded c:\windows\system32\config\SYSTEM. There were three ControlSets now:
ControlSet001 with SetupExecute set to 'c:\windows\system32\poqexec.exe /skip_critical_poq /display_progress \SystemRoot\WinSxS\pending.xml'
ControlSet002 with blank SetupExecute
*and* CurrentControlSet with blank SetupExecute, which was *created* by 'reg add' on my previous attempt and contained nothing besides SetupExecute key.
'Select' contained following values: Current=1, Default=1, LastKnownGood=2
I deleted CurrentControlSet, and applied thiswoot's fix (editing pending.xml), which worked, albeit after some trial and error.
First I attepmted to specify the path as %windir%\winsxs\pending.xml which was wrong, because %windir% pointed to RE (X:\Windows) and not to my Windows installation (C:\Windows). RE also has its own pending.xml, so I ended up editing the wrong file, which didn't contain anything similar to <CheckPoint/>
Then I found the right one (c:\windows\winsxs\pending.xml), but couldn't find the string. I ended up doing something like:
find /i "c0000034" c:\windows\winsxs\poqexec.log
then searching in pending.xml for a part of string returned by find and commenting out the directive that contained it and <CheckPoint/> before it.
That worked.
-
Monday, March 14, 2011 4:17 PM
Clarification
> Today I tried to do the same on another PC over WSUS from our university WSUS server and got c0000034 error.
Well, not *I myself tried*, it got installed automatically during reboot.
-
Monday, March 14, 2011 6:08 PM
FYI,
I tried the Microsoft KB article and had issues with both methods. Method1: there is no restore point to go back to. Method 2: caused a stop 0x0000067 error "CONFIG_INITIALIZATION_FAILED". Tried thiswoot's method and this time it did not resolve the problem presumably because Method 2 messed something up. The only option I had was to re-install Windows from scratch.
Bottom line, I have 5 new Windows 7 x64 computer, 2 encountered the problem as the enduser isntalled Sp1 during a shutdown. The other 3 installed fine as it was done using Windows Update and not through the shutdown method.
Hope this helps,
J
-
Monday, March 14, 2011 6:40 PM
Please, refer to this
Error 0xC0000034 during Service Pack 1 installations for Windows 7 and Windows 2008 R2
http://blogs.technet.com/b/askcore/archive/2011/03/10/error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspx
Even after doing this fix the system is still in unstable stage.
Impossible to install Win7 SP1 thereafter. It will say that some Windows Update components are missing. Trying to fix this with System Update Readiness Tool doesn't success. The only way to really fix all the mess done by the update is to do what Microsoft call a "in-place system update" which - to say the least - really pissed off us.
This is unacceptable that deploying SP1 via Automatic update or WSUS broke our systems.
Microsoft: Don't you test in your labs before saying to your customers that the update is ready for widespread deployment and fail proof?
-
Monday, March 14, 2011 7:56 PM
Also see...
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Win7 SP1... (Revised 11 March 2011)
http://support.microsoft.com/KB/975484Why you don’t want to edit your pending.xml to resolve 0xC0000034 issue
http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspxError 0xC0000034 during Service Pack 1 installations for Windows 7 and Windows 2008 R2
http://blogs.technet.com/b/joscon/archive/2011/03/09/error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspxGetting out of a no boot situation after installing updates [in Win7]
http://blogs.technet.com/b/joscon/archive/2009/10/15/getting-out-of-a-no-boot-situation-after-installing-updates-on-windows-7-2008r2.aspx
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft -
Tuesday, March 15, 2011 5:24 PM
My God, you are a genius with too much time on your hands. What an elegant solution!!! Something that the automatic repair should be able to handle you'd think. Thank you Mr. Swoot :-)
This worked for me on 3/15/2011 in a Domain environment that uses WSUS to auto update Win7 Pro x64 boxes(and other clients). Out of about a dozen SP1 installs (more than half automatic) only 1 PC failed.
-
Tuesday, March 15, 2011 7:52 PM
Well what a pile of poo SP1 seems to be, this can't be an isolated inncident.. SP1 needs withdrawing until MS finds out what's up with this sack of $hite....
Just paying a courier to ship a laptop back from an end user in Scotland.
1/10.
-
Tuesday, March 15, 2011 10:07 PM$15 to your paypal sir. That saved me HOURS and HOURS of work so the $15 is a drop in the bucket for me.
-
Wednesday, March 16, 2011 3:53 AMTo complicate things, it's not possible to do in-place upgrade with regular Windows 7 DVD which most people have. It won't even start, saying that your OS is newer than the one you're trying to install. I had to use Windows 7 with SP1 DVD from MSDN subscription to do in-place upgrade and finally fix everything.
-
Wednesday, March 16, 2011 7:00 AM
To complicate things, it's not possible to do in-place upgrade with regular Windows 7 DVD which most people have. It won't even start, saying that your OS is newer than the one you're trying to install. I had to use Windows 7 with SP1 DVD from MSDN subscription to do in-place upgrade and finally fix everything.
Thanks for hinting how to get the machine back into an "official supported" state instead of "maybe SP1 half installed". The interesting question: Will MSDN SP1 included DVD work on OEM Win7 machines with their key or OEM branding ? Did anyone try ? I won't have the time really soon.
What I did when I had to do in-place upgrade (a different thread with a different reason why SP1 refused to install, but not break my machine):
Copy contents of DVD to second HD root, and start setup from there. It's faster that way. Since there are no conflicting files or directories with an existing Win7 installation copy to C: should work too. Does it work when copied to a subdir of C:? Does anyone know or did anyone already try?
-
Wednesday, March 16, 2011 11:06 AM
To complicate things, it's not possible to do in-place upgrade with regular Windows 7 DVD which most people have. It won't even start, saying that your OS is newer than the one you're trying to install. I had to use Windows 7 with SP1 DVD from MSDN subscription to do in-place upgrade and finally fix everything.
Thanks for hinting how to get the machine back into an "official supported" state instead of "maybe SP1 half installed". The interesting question: Will MSDN SP1 included DVD work on OEM Win7 machines with their key or OEM branding ? Did anyone try ? I won't have the time really soon.
What I did when I had to do in-place upgrade (a different thread with a different reason why SP1 refused to install, but not break my machine):
Copy contents of DVD to second HD root, and start setup from there. It's faster that way. Since there are no conflicting files or directories with an existing Win7 installation copy to C: should work too. Does it work when copied to a subdir of C:? Does anyone know or did anyone already try?
And just to help us poor beleaguered support bods, MS has disabled official slipstreaming so you can't build your own supported version!
So, Service pack 1 kills Windows, the resolution is to break the service pack out leaving it neither installed nor uninstalled. WUSA.exe says it's not installed so you can't uninstall it and if you try to install SP1 you can't as it no longer meets the prerequisites.
Nice conundrum to leave us with....
-
Wednesday, March 16, 2011 11:14 AM
I strongly recommend that all of you read my post on why editing your pending.xml file is a really bad idea: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
I know some of you are in bad situations and you dont have any other options available but this will leave your machine in an unservicable state which is going to lead to more problems down the road in regards to being able to actually install updates and fixes on the machine later in its lifecycle.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 16, 2011 1:55 PM
I strongly recommend that all of you read my post on why editing your pending.xml file is a really bad idea: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
I know some of you are in bad situations and you dont have any other options available but this will leave your machine in an unservicable state which is going to lead to more problems down the road in regards to being able to actually install updates and fixes on the machine later in its lifecycle.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/Joscon, I don't see that it makes any difference in doing the pending.xml fix or the "official" method from Microsoft. I have done both on different machines, both say they are rolling the SP off the machine, and then both say they have SP1 loaded unde rcomputer properties although SP1 isn't really loaded and is in an unstable state. It doesn't show up in add/remove, and you can't manually install it because that will error out too.
What we need is an official fix from Microsoft to at least remedy the solution that doesn't really work found here http://support.microsoft.com/kb/975484/en-us, and if you want to be nice to your customers, then you will fix the pending.xml hack that a lot of us did too.
-
Wednesday, March 16, 2011 2:01 PM
@Philip D._
YOU ARE RIGHT !!
-
Wednesday, March 16, 2011 2:09 PMYou rock man. Saved us from re-imaging 10-15 machines. Thanks a million!
-
Wednesday, March 16, 2011 2:15 PM
@Phillip;
There is a large difference between the registry key and the pending.xml workaround. The registry key will allow for the service pack to gracefully uninstall. I know it doesnt work for everyone in every case but it does work the majority of the time in the cases we have worked on for this. The main difference is the pending.xml workaround will put you in a bad state every time based on what it is doing.
Everyone who has said that it has saved reimaging systems is actually incorrect here. It's saved you time getting the machine to a bootable state perhaps but there is no doubt you will have issues with installing future updates on the machine in almost all cases. The only way you're going to get those installations back to a supported OS is to rebuild them once you have done the pending.xml workaround and thats exactly the point I am trying to get across here.
I've said here and in many other places that we're actively working on this and I will have more information when its ready.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 16, 2011 2:55 PM
Joseph,
Been following this thread for a few days. Thanks for your hard work on this issue. Looking forward to what your team comes up with. (Hopefully a fix for those of us who used the pending.xml workaround before discovering this blog post as well.)
Mark
-
Wednesday, March 16, 2011 3:04 PM
Guys,
after following this KB (http://support.microsoft.com/kb/975484 ) to put back PC in bootable state, can you install or uninstall SP1? We have PC's that had this error, so SP1 did not passed. Nevertheless, W7 system is reporting SP1. In installed updates there is no SP1 and you cannot start new SP1 installation procedure.
So what are our options once PC's are back online. How to install SP1 after this failure?
-
Wednesday, March 16, 2011 3:48 PM
@Mark; Thanks for that. I know it doesnt do anyone any good but I do feel your pain here and we're working hard to resolve this.
@pidgen; it depends on how torn the state of the system is. I would guess that right now its a 60/40 chance or so of being able to uninstall and reinstall based on the feedback I have seen and been given.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 16, 2011 3:55 PM
@Mark; Thanks for that. I know it doesnt do anyone any good but I do feel your pain here and we're working hard to resolve this.
@pidgen; it depends on how torn the state of the system is. I would guess that right now its a 60/40 chance or so of being able to uninstall and reinstall based on the feedback I have seen and been given.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/Joscon, thank you for representing MS and I do really appreciate you trying to help us so don't take my frustration personal. :P
Is there a way to try and uninstall SP1 from the command line for those of us are having this problem after doing the official MS registry fix?
-
Wednesday, March 16, 2011 4:07 PM
@joscon,
I know you have posted here about the dangers of the pending.xml fix over the registry key fix but I didn't find it until after I had followed the registry.xml fix which was a god send in that it allowed us to regain use of the machines which were otherwise seemingly dead.Is there any chance of a fix for those of us who applied the SP in good faith, had our machines fall over and had to try to solve the problem and used the pending.xml fix?
I can't believe that Microsoft pushed out a service pack that put so many people into this state! Nothing personal to you and I appreciate your being here but I do have a grievance with MS.
-
Wednesday, March 16, 2011 5:41 PM
To complicate things, it's not possible to do in-place upgrade with regular Windows 7 DVD which most people have. It won't even start, saying that your OS is newer than the one you're trying to install. I had to use Windows 7 with SP1 DVD from MSDN subscription to do in-place upgrade and finally fix everything.
Thanks for hinting how to get the machine back into an "official supported" state instead of "maybe SP1 half installed". The interesting question: Will MSDN SP1 included DVD work on OEM Win7 machines with their key or OEM branding ? Did anyone try ? I won't have the time really soon.
What I did when I had to do in-place upgrade (a different thread with a different reason why SP1 refused to install, but not break my machine):
Copy contents of DVD to second HD root, and start setup from there. It's faster that way. Since there are no conflicting files or directories with an existing Win7 installation copy to C: should work too. Does it work when copied to a subdir of C:? Does anyone know or did anyone already try?
And just to help us poor beleaguered support bods, MS has disabled official slipstreaming so you can't build your own supported version!
So, Service pack 1 kills Windows, the resolution is to break the service pack out leaving it neither installed nor uninstalled. WUSA.exe says it's not installed so you can't uninstall it and if you try to install SP1 you can't as it no longer meets the prerequisites.
Nice conundrum to leave us with....
Do you remember the "good old" NT4.0/Windows2000/WindowsXP/Windows2003 days? Where you could install Sp6a/Sp4/Sp3/Sp2 as often as you want without breaking the machine? And it actually fixed strange behaviour?The "prerequisites" problem is the biggest of Sp1, it is bitchy as hell and hates ton's of things. This specific annoyance is just the top of failed QA. Who did this? Probably not the same who was responsible for Vista SP2 or Win7 RTM.
-
Wednesday, March 16, 2011 6:47 PM
Do somebody try to reboot after the pending.xml fix.
I have 5 laptop here and I want to know if we cant do the shutdown for the night.
Tomorrow morning I dont want to do this again...
Thanks.
ITBM -
Wednesday, March 16, 2011 8:35 PMyes I have rebooted all my machines which had the pending.xml fix with no issue.
-
Wednesday, March 16, 2011 9:18 PM
I would advise anyone hitting this problem to temporarily unapprove SP1 from your WSUS installation and install SP1 on every machine by hand!!!!
We had to get a machine bootable, grab the data off it then flatten it and make sure the very first action was installing SP1.
The machine that was borked by SP1 yesterday is now happy with it. The difference was not allowing WSUS to manage the installation.
-
Wednesday, March 16, 2011 10:49 PM
Thanks for your efforts, this fix got my Windows 7 64bit back up and running. Fingers crossed it will be stable.
Recommend this fix.
-
Wednesday, March 16, 2011 11:03 PMJoscon provided some new details:
New information on error code 0xc0000034
"A programmer is just a tool which converts caffeine into code"
Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221 -
Thursday, March 17, 2011 12:51 AM
I've brought this up in some of the meetings I have been on around this issue. No word yet, but I'll let you know if something changes in regards to this. You'll her me refer to machines like this as being in a "torn state" moving forward because thats the technically proper term. Torn state means that the servicing mechanics on the machine are in an in between state with regards to what it wants to service. In this case, some SP1 files, some RTM files. It's a difficult situation to work around.@joscon,
I know you have posted here about the dangers of the pending.xml fix over the registry key fix but I didn't find it until after I had followed the registry.xml fix which was a god send in that it allowed us to regain use of the machines which were otherwise seemingly dead.Is there any chance of a fix for those of us who applied the SP in good faith, had our machines fall over and had to try to solve the problem and used the pending.xml fix?
I can't believe that Microsoft pushed out a service pack that put so many people into this state! Nothing personal to you and I appreciate your being here but I do have a grievance with MS.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Thursday, March 17, 2011 12:53 AM
@Mark; Thanks for that. I know it doesnt do anyone any good but I do feel your pain here and we're working hard to resolve this.
@pidgen; it depends on how torn the state of the system is. I would guess that right now its a 60/40 chance or so of being able to uninstall and reinstall based on the feedback I have seen and been given.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/Joscon, thank you for representing MS and I do really appreciate you trying to help us so don't take my frustration personal. :P
Is there a way to try and uninstall SP1 from the command line for those of us are having this problem after doing the official MS registry fix?
No problem Philip, glad to help out as I can.
Nothng yet though, I'll update as I have new information though.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Thursday, March 17, 2011 10:36 AM
Joseph,
We have spoken, but I want to post my thoughts here.
This is a disgraceful situation that Microsoft have allowed. It needs a fix within a week.... not a month, not a few weeks. You are the only person I have seen in any forums really trying to address this issue, and I commend that, but the reality is that you are working for a massive organisation that should be able to resolve this quicker.
I have HAD to break licensing rules to get around this. I have no choice, and unless you (Microsoft) are going to pay my clients for the downtime, then I have no choice. System restore NEVER works and that REALLY should be taken out of the suggested solutions. It gives people false hope!
To fix this I have had to get a MSDN version of Windows 7 SP0 and edit the cversion.ini file to allow it to think its upgrading a different Windows build. Install over the top with an inplace upgrade, use my MSDN key!!!! HOLY COW! I cannot believe I am forced into this situation, and I am mad about it....
Unless Microsoft can come up with something PRONTO to fix people sitting in this torn state, then Microsoft need to release a version of the Windows 7 installer that effectivly does an inplace upgrade. Otherwise, you are forcing the likes of me - someone who cannot abide breaking licensing rules - to do so!
Whatever it takes!
Nick "The Naked MVP" Whittome -
Thursday, March 17, 2011 10:41 AMNot true. You can edit the cversion.ini file if you really must (like I really had to do.... no other choice)
Nick "The Naked MVP" Whittome -
Thursday, March 17, 2011 10:46 AM
@Nick; Thanks for the feedback, I understand your point and will make sure others here understand it as well. Obviously I dont want you breaking licensing rules to workaround an issue. I'm doing what I can here.
That being said....Happy St. Paddy's Day to you
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Thursday, March 17, 2011 10:50 AM
Hey Joseph, thanks! Same to you... I really should be in a pub instead of this forum;)
I know you are doing what you can. I am driving home the point deliberately to try to get across just how badly this is affecting our business.
Cheers
Nick
Nick "The Naked MVP" Whittome -
Thursday, March 17, 2011 11:04 AM
Trust me, we both need to head to the pub after this week :)
I'm working on mail to ensure all of this feedback is heard in an unfiltered way. Thanks again for giving it.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Thursday, March 17, 2011 12:58 PM
Thanks a lot !!! This solution was really helpfull for me this morning at work. I was able to boot the computer within less than hour. :)
-
Thursday, March 17, 2011 3:21 PM
I have two that was affected. One I rebuilt before I knew it was an issue. The other, I did this fix, but know I can't connect to anything, network, internet, etc. Several services are not started like dhcp, diaognostic policy. when I try to start them, I get error: access denied 5.
Gary -
Thursday, March 17, 2011 3:50 PM
I have two that was affected. One I rebuilt before I knew it was an issue. The other, I did this fix, but know I can't connect to anything, network, internet, etc. Several services are not started like dhcp, diaognostic policy. when I try to start them, I get error: access denied 5.
Gary
I found this article to set permissions, looks like it worked.http://support.microsoft.com/kb/943996
Gary -
Friday, March 18, 2011 7:43 AM
Some news from outher post (of joscon).
You can try to install from a W7 SP1 on our W7 "SP0.35" (because it stopped at 35% of SP1), but :
- you need a MSDN account to download the DVD with SP1 integrated (and this isn' t right, because it's only a W7+SP1)
- you need ANOTHER PRODUCT CODE !!! And this is madness...
joscon is the only one that i have seen in a forum that speaking about this informatic disaster. Respect to him.
Microsoft has done the big mistake, not joscon.
So we are all at disposition to joscon, because we want to resolve this situation of pending.xml
Regards
-
Friday, March 18, 2011 4:07 PMyou should look for the 000000000000.cdf-ms and you'll see it's actually _00000000000000000000.cdf-ms. That's the right one though. If I'm not mistaken this same sort happened in SP2 for Vista.
-
Friday, March 18, 2011 5:09 PM
I'll post my experience with this.
I just did SP1 on two Dell Servers and an HP DL165 G7.
All with WIn 2008 x64 R2.
Dell's, went about as quick as this update is going to go, which isn't very fast.
The HP got stuck at 15% for about 20 minutes before I went back to my desk to research what might have happened.
While reading this thread and the one at Microsoft reference the Update Readiness tool, I came to understand that the update readiness tool will be automatically be downloaded and run if "it's is determined to be needed. The article I read said that the progress bar will appear to freeze at 60% until it finishes. (Mine froze at 15%)
I had tried to connect via rdp and remote management, and nothing responded.
I burned the Update Readiness tool, printed out pages of documentation on recovering from this, went back down to the datacenter, and the console showed that the server was ready for me to login. (!?)
I logged in and was greeted with a 'SP1 is not installed' popup.
I began the install of the readiness tool, just to see what it would say, and after churning for about 3 minutes it informed me that it wasn't needed and unloaded.
My wild guessing is that:
a.) something had the CPU pegged out to the point where nothing else was responding during the SP install.
b.) Perhaps that 'something' was the downloaded version of the readiness tool checking 'stuff.'
c.) The best bet when installing the SP may be to first reboot, and just be patient. Wait an hour before panicking.
d.) Pre-Run the readniess tool before installing the SP.
Microsofts article on this tool, and the download for all versions of all Vista based (win 7, Win 2008 (r2) etc is here:
http://support.microsoft.com/kb/947821
-
Sunday, March 20, 2011 11:57 PM
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Win7 SP1... (v2.3 - 16 Mar-11)
http://support.microsoft.com/KB/975484New information on error code 0xc0000034 (16 Mar-11; references KB975484)
http://blogs.technet.com/b/joscon/archive/2011/03/16/new-information-on-error-code-0xc0000034.aspx
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft -
Monday, March 21, 2011 9:46 PMSo I guess all of us that did the pending.xml fix or the first "Original" official MS fix of editing the registry are just screwed? Has anyone figured out how to get their machines out of a torn state? You would think that MS would just allow you to reapply the Service Pack...
-
Monday, March 21, 2011 9:55 PMIt worked! Thank you! ^^
-
Wednesday, March 23, 2011 7:51 AM
you should look for the 000000000000.cdf-ms and you'll see it's actually _00000000000000000000.cdf-ms. That's the right one though. If I'm not mistaken this same sort happened in SP2 for Vista.
You really should leave the pending.xml checkpoint alone at this point. If you're in an active C34 state, use the script in the KB to get out of it and install SP1. If you're in a torn state, I am still looking into options on what to do. No word on timeframe.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 23, 2011 10:08 PM
10 W7 Pro machines, some 32, some 64.
Domain WSUS.
One non-domain W7 Pro computer.
Seven days ago, problem on one box with “Install updates and shut down.”
Fix was boot to Repair, rename reg files, replace with previous reg files, reboot, do in place upgrade, and reinstall updates and service pack.
Held off on the non- domain box (belongs to company owner).
Now, install SP1 on that box.
After, most Windows components (Control Panel, Properties, Windows Explorer, etc.) take ~ 55 seconds to respond.
Works okay in safe mode.
Any advice appriciated!
-
Thursday, March 24, 2011 10:23 AM
Stephen;
For your particular case we do have a fix, and its the script in the KB article. You didnt need to do anything with your registry or an inplace upgrade on any of the installations. I dont know how you did the repair install but it sounds like something different is broken there.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Friday, March 25, 2011 12:38 AMAnswererRecently 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 blogs below 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.
To get a feel of the true impact I'd like to find out the following. Can you please email me at susan-at-msmvps.com with the following information?
How many PCs under your control were impacted?
How many MS support cases did you open?
Thank you in advance for this info.
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
http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
http://blogs.technet.com/b/joscon/archive/2011/03/16/new-information-on-error-code-0xc0000034.aspx -
Friday, March 25, 2011 11:17 AM
In my entreprise we have like 60 computers (desktop and laptop). The c34 problem touch 5 of it.
I did the pending.xml fix but waithing like everyone else for the fix.
I did not open any MS support case.
ITBM -
Friday, March 25, 2011 12:20 PMI just pushed out via WSUS and already have 7 C34 errors this morning out of 50 so far!!!
-
Friday, March 25, 2011 2:55 PMWell make that 21 out of 50 now!
-
Friday, March 25, 2011 2:55 PM
This is what I am using to resolve the issue and is working so far.
-
Friday, March 25, 2011 10:33 PM
See my colleague Susan Bradley's recent post above.
<QP>
To get a feel of the true impact I'd like to find out the following. Can you please email me at susan-at-msmvps.com with the following information?How many PCs under your control were impacted?
How many MS support cases did you open?
</QP>
~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft -
Monday, March 28, 2011 11:54 PMThanks, thiswoot - worked for me too!
-
Tuesday, March 29, 2011 12:02 AMAnswererPhilip did you note that there's a kb with a script that should have been used instead?
-
Tuesday, March 29, 2011 12:32 AMHi Susan, I hadn't read that far down, but have now taken a look at it - I'm curious how that differs in terms of the end result... it seems to me that thiswoot's instructions were more succinct for me to enact, and certainly the system is working beautifully now.
-
Tuesday, March 29, 2011 12:40 AM
Your machine is most likely now in whats known as a torn state (meaning no future updates will install properly). Had you done the script in the KB article, the service pack would have installed properly and you wouldnt be in that state. I speak more about it here: http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx
--Joseph [MSFT] http://blogs.technet.com/b/joscon/- Marked As Answer by Susan BradleyMVP, Editor Tuesday, March 29, 2011 1:00 AM
-
Tuesday, March 29, 2011 12:59 AMAnswerer
Actually it's in a 1/2 rtm 1/2 sp1 condition now and not working as beautifully as you think.
-
Tuesday, March 29, 2011 1:02 AMAnswererNo disrespect at all to Thiswoot, but in the future should anyone read this solution and try to edit the pending xml file, follow instead the instructions in http://blogs.technet.com/b/joscon/archive/2011/03/16/new-information-on-error-code-0xc0000034.aspx
-
Tuesday, March 29, 2011 10:09 AMYou are a life saver! This worked perfectly. Avoided me to re-install the OS and all. Thanks!
-
Tuesday, March 29, 2011 6:06 PM
Instead of telling the masses why you shouldn't do this desperate solution that 100's of us already tried, please tell us how to fix it if we already did it.
If there is something worse than having a "torn state", it's not being able to boot into your system at all. At least this method I was able to save my personal data in case I end up having to re-format and re-install.
Is there a solution to reverse the torn state back to pre-sp1? I tried to system restore, but SP1 install apparently erases all previous restores.
I think the worst part of all this is that I just found out that this exact same error apparently was a huge problem when Vista SP1 came out 2 years ago and Microsoft still hasn't fixed the problem a whole operating system and two years later!:
http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/4491fe25-be44-430e-a384-fb58c5da5ad0/
-
Tuesday, March 29, 2011 6:38 PMCurrently there isnt a way to revert the torn state, we're looking over options for it. The reason I tell the masses they shouldnt be doing it is because the masses are still doing this when there is a way to recover properly without causing futher system problem.s
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Tuesday, March 29, 2011 8:43 PM
Thanks for the update Joseph(joscon).
Just a side note; On this forum, your posts don't reflect that you're like THE Guy when it comes to this! I don't mean the content of your posts, but the appearance of your posts. There's not much difference in the appearance to show that you're not someone like...well me, offering advice without knowing. And the MSFT in your signature didn't mean much to me until I started reading your blog.
I wasn't really familiar with the MSFT abbreviation before I got involved in this whole fiasco, and didn't know that you are a Senior Engineer at Microsoft.
Maybe they(you?) could give you guys a star or something next to your name, so us little people know we should listen to you. :^)
-
Tuesday, March 29, 2011 9:48 PMAfter reimaging, I ordered the SP1 disc (update only). It installed off the disc without any problems. The disc will do everything, including any reboots. If you haven't crashed your computer yet , you might try this. The disc is free ($6.00 postage).Service Pack Center - Microsoft Windows
-
Wednesday, March 30, 2011 11:00 AM@NYCDrew: Good point, I'll see if I can change my name or something to reflect it a little better.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 30, 2011 11:03 AMThere ya go...new alias, hopefuly that helps a little.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, March 30, 2011 4:21 PMBetter. :^)
-
Thursday, March 31, 2011 2:04 AMOwner
thiswoot,
Thank you for posting and wanting to help other users, but unfortunately, I had to delete your post. We have found that the steps in this post while allowing you to recover from the non-bootable state, leaves the machine in an unserviceable state, with SP1 partially installed. There is not a known way to recover a machine from this state at this time, so we recommend that people follow the steps in the KB article which allow you recover the system with Windows SP1 installed successfully. So as not to leave customers in state which is not serviceable, your post was removed.
KB article with steps to resolve the issue:
975484 Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;EN-US;975484We also have a blog post on the issue with more details of why the deleted steps should not be attempted:
Thanks-Tony Mann
IT Pro Audience Manager for Web Forums- Marked As Answer by Susan BradleyMVP, Editor Thursday, March 31, 2011 3:16 AM
-
Tuesday, April 12, 2011 4:48 PM
Hello,
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.
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en -
Wednesday, April 13, 2011 5:59 PM
Hi, any suggestions for people who are in an unserviceable state due to following the originally removed post? Is it possible to re-install the OS from Windows DVD and leave third party apps, data, and settings intact?
Thanks!
-sul
- Edited by Sul Wednesday, April 13, 2011 6:00 PM typo
-
Wednesday, April 13, 2011 6:32 PMAnswererI would strongly recommend that you call Microsoft to give them direct feedback. If you don't have support cases you can use ping me at susan-at-msmvps.com and I can set one up for you.
-
Thursday, April 14, 2011 2:03 PM
Hi, any suggestions for people who are in an unserviceable state due to following the originally removed post? Is it possible to re-install the OS from Windows DVD and leave third party apps, data, and settings intact?
Thanks!
-sul
Right now those of us with this problem have 4 Options that I can see, with only one being a perfect solution.
Option 1: Reload the machine (This sucks but as of right now it is the only way to be sure that the machine functions properly)
Option 2: Use a copy of Windows 7 w/ SP1 from MSDN to do an in place upgrade as other have mentioned. (This sucks because most of us have no way to get this DVD and it still isn't an official Microsoft solution)
Option 3: We wait for Microsoft to come out with a fix. (We have already waited 1 month so don't hold your breath on this one)
Option 4: A new work around has been posted here by a user named Kelvin Aston http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx?CommentPosted=true look towards the bottom or go directly to his blog at http://kelvinaston.blogspot.com/2011/04/possible-fix-for-torn-sp1-machines.html. (This isn't a Microsoft supported solution, but several people are saying that they were able to load SP1 cleanly and other new updates after applying his work around.)
-
Thursday, April 14, 2011 2:09 PMAnswerer
Bump 4 above 3.
I'll be honest that I don't see them coming out with a fix. We're not calling in enough to make the case that we need a fix coded up.
-
Thursday, April 14, 2011 2:42 PMI have done the Kelvin Aston method, and yesterday and today i have installed automatically from WSUS a lot of upgrades.
-
Thursday, April 14, 2011 3:42 PM
Thanks Philip.
With help of Susan, a microsoft case was opened and with their help, I was able to resolve my issue.
Before I list my steps, I should explain the issue, as it may not be the same as everyone. First of all, my machine is a windows 2008 Server R2 (x64) and not Window 7, however, I think the core issue is the same. Basically, after installing SP1 from windows update, the server resulted in a black screen with error code c0000034. I followed the original post (now deleted) to edit the pending.xml file, which resulted in the machine being in an "unserviceable state", i.e.: winver.exe reported that the version of windows included Service Pack 1, but Service Pack 1 was missing from the Installed Updates under Programs and Features, and any attempts to re-install service pack 1 would result in a message that the computer needs to be restarted.
If your issue is similar, then the following might help.
Here are the steps that worked in my case:
First, I went through methods 1, 2, 3, 4, 6, and 8 in the following article, however, this may or may not be necessary.
http://support.microsoft.com/kb/2509997
Next, I downloaded the service pack and extracted it to a folder. e.g.
windows6.1-KB976932-X64.exe /x c:\sp1
Then I launched a command prompt and changed to the directory of the the extracted folder (c:\sp1) and ran the following:
dism /online /remove-package /packagename:windows6.1-KB976932-X64.cab
After about 10 minutes I was prompted to reboot. When the machine was rebooting it kept saying that it was applying the service pack and at one point it said that it failed. After logging back into the machine I checked winver.exe, which still stated that the version was SP1, and as before, Service Pack was not listed under Installed Updates.
I then re-installed the service pack and this time it literally took 30 minutes to complete, but it actually installed correctly! After the reboot, I checked both winver.exe and Installed Updates and Service Pack for Microsoft Windows (KB976932) was listed.
I hope the above helps.
thanks!
-sul.
-
Tuesday, April 19, 2011 6:35 PM
Thanks for the tips to resolve the torn state problem.
Our fix thus far has been to rebuild the effected machines. I use Windows Easy Transfer to copy the user data to a network share, pull down a new WDS image (our standard build of Win 7 SP1 plus apps) to the computer, then transfer the user data back. It takes a little while but everything is solid.
-
Wednesday, April 20, 2011 12:06 AM
Hello I too am experiencing the c0000034 problem (this is after experiencing the c000009a problem - that makes two problems to solve! woohoo).
I have tried the kb article's script removing POQ method, but I at the moment am having trouble with this method:
At the command prompt where I type in the command:
F:\>CScript Script.vbs C:\Windows\winsxs\pending.xml
(F is where my script.vbs file is located, C is my windows installation)
I get this error:
Failure loading XML file C:\Windows\winsxs\pending.xml.
Please help me. I really don't feel like reformatting for this one stupid mistake of Microsoft (service pack issues because of language packs installed? really? do they even bothering testing software nowadays?)
Edit: I have a trusty Knoppix boot disk in which I can directly access my Windows files - even the pending.xml file. Can I manually execute what the script.vbs file does, since I can't get the script to work? -
Thursday, April 21, 2011 5:27 PMAnswererI would call Microsoft support (1-800-microsoft) state that you are having an issue with Win7 sp1. If you can't get a free support (it should be free) ping me at susan-at-msmvps.com and I can help you through the process.
-
Monday, April 25, 2011 10:14 PMAnswerer
Update on torn state systems - The Windows Servicing Guy - Site Home - TechNet Blogs:
http://blogs.technet.com/b/joscon/archive/2011/04/25/update-on-torn-state-systems.aspx"If you currently have a machine that is in a torn state from using the pending.xml workaround posted on the forums a couple of weeks ago, I am afraid I am not the bearer of good news.
As of right now, the recommendation from Microsoft support for these systems is going to be to rebuild the installations that are in the torn state even if other workaround have proved to allow proper servicing of the system. This isnt to say that there wont ever be a fix for systems in a torn state but there are other higher priority fixes that are being worked on internally right now to assist with SP1 issues (dont ask what they are because I am not saying <G>). The reason for this is that even in the cases where other workarounds have appeared to have worked for you, we cant ensure that you arent still in a torn state. The only way to ensure you arent in a torn state is to rebuild the installation.
The product group understands the impact this issue has caused for many of you by reading the blog comments and my own posts to them. But at this time rebuilding the OS is the only Microsoft supported solution for systems that have used the pending.xml workaround.
Post <on the blog> with any questions.
--Joseph"
-
Monday, April 25, 2011 10:44 PM
Just as an additional update, I have recently changed the blog wording and removed the following line: This isnt to say that there wont ever be a fix for systems in a torn state but there are other higher priority fixes that are being worked on internally right now to assist with SP1 issues (dont ask what they are because I am not saying <G>).
I did this because it was brought to my attention that this implied a potential fix and that wasnt my intent. Sorry for the confusion. So to reiterate, if you have a system that has been in a torn state, the only supported method of repair is a reinstallation of the OS.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/ -
Wednesday, April 27, 2011 10:32 AMI tried what the article said to do. I created the Script.vbs in another computer and saved it in an usb drive, but every time I try to run the command Cscript Script.vbs <Windows _7_drive_letter>:\Windows\winsxs\pending.xml. it tells me that the system cannot find the file specified
-
Thursday, April 28, 2011 6:58 AMYesterday other patches was installed in my "torn" PC... I used http://kelvinaston.blogspot.com/2011/04/possible-fix-for-torn-sp1-machines.html and for now all works.
-
Tuesday, May 10, 2011 1:06 PM
Hello,
I have the same problem and I am trying to find a solution.. but I am not able to see your fix. I see people talking about your fix works so please if you can provide me the steps, that will be great...
Thank you
-
Tuesday, May 10, 2011 1:23 PMHave you tryed the official fixs from Microsot ?
-
Wednesday, May 11, 2011 6:49 AMAnswerer
If you are hitting the c34:
New information on error code 0xc0000034 - The Windows Servicing Guy - Site Home - TechNet Blogs:
http://blogs.technet.com/b/joscon/archive/2011/03/16/new-information-on-error-code-0xc0000034.aspxIf you hit the c34:
Supported workaround for torn state installations on Windows 7 SP1 - The Windows Servicing Guy - Site Home - TechNet Blogs:
http://blogs.technet.com/b/joscon/archive/2011/05/10/supported-workaround-for-torn-state-installations-on-windows-7-sp1.aspxTo ensure you don't hit c34 in the future
Supported workaround for torn state installations on Windows 7 SP1 - The Windows Servicing Guy - Site Home - TechNet Blogs:
http://blogs.technet.com/b/joscon/archive/2011/05/10/supported-workaround-for-torn-state-installations-on-windows-7-sp1.aspx
-
Thursday, May 12, 2011 4:37 PMIt worked on my clients computer. The Microsoft fix. I had to attempt it a couple of times till I figured out the drives were labled differently. Changed the drive letters to their correct state and voila'
-
Thursday, June 23, 2011 3:55 PM
Hi,
I dont see the 12 steps here. I have made a copy of my pending.xml file, then from another solution i found online, which may have been a bad idea, but i copied the text from my reboot.xml file into the pending.xml file.
I saved and exited, the system rebooted, and tried to finish the install of service pack 1 three times, literally, then it reverted back automatically to a point previous to SP1.
The system rebooted, and now i'm able to log into windows no problem, but none of my programs work. My MSOFFICE suite icons are there, but when you click on them nothing happens. Even if you tried running the application from the start menu nothing happens.
Some of my other applications arent running either. Any help?
-
Wednesday, July 06, 2011 7:51 AM
This is the way I've solved my problem:
1. Press F8 on boot until the boot menu comes up. Choose the first option - Repair
2. Choose Command prompt in the repair menu. When the cmd window appears type the folowing:
d:
cd d:\windows\system32\config
rename default default_old
rename sam sam_old
rename security security_old
rename software software_old
rename system system_old
cd regback
copy default d:\windows\system32\config
copy sam d:\windows\system32\config
copy security d:\windows\system32\config
copy software d:\windows\system32\config
copy system d:\windows\system32\config
exit
Click RESTART
3. Press F8 on boot until the boot menu comes up. Choose SAFE MODE
4. in safe mode click Run and type services.msc and then ENTER. Find windows update in the list, dubleclick it and modify the Startup type to DISABLED
5. Open My Computer, go to c:\windows and delete the SOFTWARE DISTRIBUTION folder
6. Restart computer
-
Tuesday, September 06, 2011 3:18 PM
I'd recomend you read this KB article.
http://support.microsoft.com/kb/975484/en-us
Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Service Pack 1 on Windows 7 or Windows 2008 R2.
This fixed all my issues.
-
Wednesday, September 07, 2011 9:03 PM
thiswoot,
Thank you for posting and wanting to help other users, but unfortunately, I had to delete your post. We have found that the steps in this post while allowing you to recover from the non-bootable state, leaves the machine in an unserviceable state, with SP1 partially installed. There is not a known way to recover a machine from this state at this time, so we recommend that people follow the steps in the KB article which allow you recover the system with Windows SP1 installed successfully. So as not to leave customers in state which is not serviceable, your post was removed.
KB article with steps to resolve the issue:
975484 Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;EN-US;975484We also have a blog post on the issue with more details of why the deleted steps should not be attempted:
Thanks-Tony Mann
IT Pro Audience Manager for Web ForumsThanks for pulling great information. You could have just as easily put a disclaimer. But this whole torn business I don't buy for a second. The Domain PC that I used thiswoot's solution for has not had any issues installing updates at all. In fact, no issues of any kind. I bet the torn PC issue is more of an exception than the rule, probably even less than 10% of PCs using thiswoot's solution experienced any torn issue. And if they did, chances are they already had bigger issues.
To start pulling posts because you think it will create a larger issue is just wrong. This is the USA, we don't do that here. You are Microsoft, not Apple, stop squashing creativity and ingenuity. Put the post back up, and put the 'accepted' alternative as the primary answer and slap disclaimers on it. Considering thiswoot's solution was probably replicated to a dozen other sites, it would be in your best interest to repost it here so users actually visit your site instead of one of the other dozen.
-
Wednesday, September 07, 2011 9:10 PMAnswerer
The "c34" should be a non issue now. The main reason for this occuring was that Win7 sp1 was being put on WSUS without an exclusive flag. The editing of the pending xml was hurting people. We have a KB, we have clear guidance now to ensure we don't have C34.
The post isn't needed. If you are still seeing a c34 please ping me at susan-at-sbslinks.com
-
Monday, October 10, 2011 9:09 AM
-
Friday, November 25, 2011 1:51 AM
Can you please post the deleted solution? This indeed is still an issue. I have a Dell PC with a new install of Windows 7 64-bit. I install EVERYTHING through windows update, no 3rd party software, drivers, etc. However after the SP1 was presented and applied the system no longer boots. There is something wrong with SP1 if it can't install on a stock unmolested system.The "c34" should be a non issue now. The main reason for this occuring was that Win7 sp1 was being put on WSUS without an exclusive flag. The editing of the pending xml was hurting people. We have a KB, we have clear guidance now to ensure we don't have C34.
The post isn't needed. If you are still seeing a c34 please ping me at susan-at-sbslinks.com
-
Friday, November 25, 2011 3:51 AMAnswererYou need to follow this KB - http://support.microsoft.com/kb/975484 if you are truly getting a c34 it will help your issue. If it still won't fix it, then you may be hitting another issue - perhaps one of drivers. Like I said in the earlier post, email me and I'll set up a support case. susan-at-sbslinks.com or susan-at-msmvps.com
-
Tuesday, December 27, 2011 2:07 AMYou're the man!!!! That exaclty fix the problems in my company. Thank you so much!
.png){kind=spacer}
