Windows 7 64bit SP1 Update failing

Optegris

Free Member
  • Business Listing
    If like me you had a squeaky bum moment this morning after applying SP1 to your shiny Windows 7 64bit machine and you were faced with this error after starting up:

    Fatal error C0000034 applying update operation 282 of (insert random number here)

    then there is hope! This solution worked for me straight away and was found by one of the chaps over at MSN technet

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

    Now it may not work for everyone but it worked for me hence why I'm reposting this solution. I've switched off the automatic updates for now until I'm sure that SP1 actually fixes my machine rather than goosing it :rolleyes:
     
    Last edited:
    • Like
    Reactions: RemoteTechs
    I was only thinking earlier that.......... "so far I haven't seen or heard of many complaints about the SP1 upgrades!!"
    We upgraded some internal machines last week when it rolled out, just some for testing and not a single problem, and then I thought the phone might start ringing... come on this is a MS Service pack!!! Nothing!
    I think a lot of people just haven't taken the plunge yet, but early signs are a little better than normal! He says touching wood!!
     
    Upvote 0
    I've not seen many problems across the 'net about SP1, but thought I'd share my experience.
    I installed SP1 across my network a week or so ago, and on my Win7 Ultimate HP the update failed. The HP just kept rebooting after about 15 seconds.
    Using Windows recovery I rolled back to the restore point, rebooted, and everything was fine. I then went to Windows Update, and did the SP1 again. This time it worked perfectly, so I imagine it was down to a slightly corrupt download the first time.
    None of my other machines had any problems whatsoever.

    Steve.
     
    Upvote 0

    Latest Articles