By using this site you agree to the use of cookies for analytics, personalized content and ads.

Learn More

Community

Question
Applies to Windows
73298 views

fatal error c0000034 applying update operation

282 of 116925
LE

lemendo asked on February 25, 2011

Title is the error message I see when I start up windows.

I'm probably responsible for that though. This is how i got there: My computer froze after successfully
downloading and installing service pack 1, still running windows. SP1 was not applied however, to my
knowledge. After rebooting the update at startup worked a couple of stages but got stuck at 0% at the
windows installation/reparation? with flowers colored screen. I did a hardware reboot and know I get this
error message when windows tries to redo or finish the update at startup/boot.
I can access the windows harddrive from Ubuntu on another drive via BIOS. However I don't have a
cd/dvd drive.
System: Windows 7 Professional 64 bit, Athlon II x4 2.9, 4 GB ram, 60 GB ssd.
Any ideas welcome!
edit: I also tried the automatic startup repair but it couldn't resolve.
SOLUTION:
this made windows bootable:
http://answers.microsoft.com/enus/windows/forum/windows_7system/fatalerrorc0000034onboot
afterservicepack1/5f7127e898874f01aaa59729b69544b7
this made my windows installer functionable after multiple times of usage: sfc /scannow

90 people had this question

Me Too

Reply

Answer
TH

thiswoot replied on February 26, 2011

Try this. It should work but if it doesn't let me know because I made a couple changes.

INSTRUCTIONS:
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Setup Repair"
> PIC: http://notebooks.com/wpcontent/uploads/2011/01/Recov1.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" see pic from step 4
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\
11. Make a copy of pending.xml as a backup
12. Now open the original pending.xml it will take 13 mins to open because the file is huge
13. Turn off Word Wrap if it's on. Click Format>Word Wrap at the top and make sure it's not checked
14. Press CNTRL+F and search for the following exactly:
0000000000000000.cdfms
15. Delete the following textthe number after PendingRenames will be different:
<Checkpoint/>
<DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdfms"/>

 <MoveFile
source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._00000000
00000000.cdfms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdfms"/>
16. Save the file, close notepad and click the button to restart your compter

Once your computer starts up, the Service pack will install some more stuff and restart a few times and then
everything should be working!
If you have any problems let me know.

72 people found this helpful

Helpful

Reply

Answer
LE

lemendo replied on February 27, 2011

thiswoots method did not solve.

however this did: http://answers.microsoft.com/enus/windows/forum/windows_7system/fatalerror
c0000034onbootafterservicepack1/5f7127e898874f01aaa59729b69544b7
windows seems to be instable still though. windows installer is for example 'fried'.

4 people found this helpful

Helpful

Reply

All replies (55)

Answer
TH

thiswoot replied on February 26, 2011

Try this. It should work but if it doesn't let me know because I made a couple changes.

INSTRUCTIONS:
01. Reboot your computer while it's starting up.
02. When your computer starts up again, choose the option "Launch Setup Repair"
> PIC: http://notebooks.com/wpcontent/uploads/2011/01/Recov1.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" see pic from step 4
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\
11. Make a copy of pending.xml as a backup
12. Now open the original pending.xml it will take 13 mins to open because the file is huge
13. Turn off Word Wrap if it's on. Click Format>Word Wrap at the top and make sure it's not checked
14. Press CNTRL+F and search for the following exactly:
0000000000000000.cdfms
15. Delete the following textthe number after PendingRenames will be different:
<Checkpoint/>
<DeleteFile path="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdfms"/>
<MoveFile
source="\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._00000000
00000000.cdfms" destination="\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdfms"/>
16. Save the file, close notepad and click the button to restart your compter

Once your computer starts up, the Service pack will install some more stuff and restart a few times and then
everything should be working!
If you have any problems let me know.

72 people found this helpful

Helpful

Reply

Answer
LE

lemendo replied on February 27, 2011

thiswoots method did not solve.

however this did: http://answers.microsoft.com/enus/windows/forum/windows_7system/fatalerror
c0000034onbootafterservicepack1/5f7127e898874f01aaa59729b69544b7
windows seems to be instable still though. windows installer is for example 'fried'.

4 people found this helpful

Helpful

AN

Reply

Andre replied on March 10, 2011

In reply to thiswoot's post on February 26, 2011

This worked for me on 3 computers, 2 64bit windows 7 pro's and one 32 bit windows 7 pro
For me the windows update was reverted, it didnt continue with the install as described.

1 person found this helpful

Helpful

Reply

JO

JosephMay replied on March 10, 2011

In reply to Andre's post on March 10, 2011

I had the same results. Both machines windows update was reverted and didn't continue with the install.

2 people found this helpful

Helpful

TM

Reply

Tim Malone, MCSE replied on March 10, 2011

In reply to thiswoot's post on February 26, 2011

Dude, this saved my butt! Thanks so much for sharing. Out of 40 Win 7 computers, 6 had this error this
morning after automatic updates last night. Using this method, I recoved all of them in 20 minutes each
with no data loss. I would have never figured this out on my own. Thank you!

2 people found this helpful

Helpful

PA

Reply

pannivas replied on March 14, 2011

In reply to thiswoot's post on February 26, 2011

This fixed the problem for me.

Thanks very much

1 person found this helpful

Helpful

Reply

DI

DimaDimaDima111 replied on March 14, 2011

In reply to thiswoot's post on February 26, 2011

It works for me W7, 64

Be the first person to mark this helpful

Helpful

PA

Reply

PatrickKeeney replied on March 14, 2011

In reply to thiswoot's post on February 26, 2011

Thank you That work like a charm

Be the first person to mark this helpful

Helpful

MA

Reply

Marky_Powell replied on March 15, 2011

In reply to thiswoot's post on February 26, 2011

Worked for me on our 2 installations. Glad someone knows what they are doing.

Thank you.

Be the first person to mark this helpful

Helpful

Reply

DA

Dave052 replied on March 15, 2011

In reply to Marky_Powell's post on March 15, 2011

We approved SP1 for internal rollout via WSUS yesterday 3/14/11. Everyone who installed it was hosed.
Thiswoot's procedure worked for us in every case.

3 people found this helpful

Helpful

Reply

Next

Still have questions?

Ask the community

Related Content
Show more content like this

English
Microsoft Community Code of Conduct
Community Participation Center
Trademarks
Privacy & Cookies

Terms of Use
2016 Microsoft