Windows

  • Windows 7
  • Windows
  • All forums
Question

'Fatal error C0000034' on boot after Service Pack 1 for 64-bit systems install

Hi there,

I installed Windows 7 Service Pack 1 for 64-bit system on my laptop after it appeared on Windows Update. The install seemed to go alright, however, when I restarted the computer at the prompt of Windows Update, it gets as far as the Starting Windows screen, before throwing 'Fatal Error C0000034 applying update operation 282 of 114599 (_00000...)'

At this point, the startup sequence hangs and gos no further. I restarted again by switching off at the mains, and this time was prompted to run Startup Repair. I tried this, however the Startup Repair program hung (I left it for several hours with apparently no effect). I then proceeded to try the following things:

-Boot in Safe Mode
This led to the startup to hang at the 'Loaded: CLASSPNP.SYS', 'Please wait...' stage. Again, left for several hours, no progress.

- Run the recovery CD to restore from a System Restore point.
The program hung at the restoring system stage - again, left for several hours, nothing happens.

- On advice from google, I tried using the recovery console to run DISM /image:D:\ /cleanup-image /revertpendingactions (I should mention that the recovery CD seems to think my windows install is now at D rather than C)
This led to an error attached at http://cid-78779374d6b6f1f3.office.live.com/self.aspx/.Public/dism.log

- Booting from last known good configuration
This just resulted in the same error as when I boot it normally

I haven't tried a complete system reinstall, as ideally I'd like to keep my files...

Any help would be greatly appreciated.

Sam

 

System Specs:

Windows Home Premium x64
Sony VAIO VPCEB2C5E Intel(R) Core(TM) i5 CPU M 520  @ 2.40GHz
4Gb RAM
Samsung HM321HI 500Gb HDD
ATI Radeon HD 5600 series graphics

Alsi uploaded CBS.log: http://cid-78779374d6b6f1f3.office.live.com/self.aspx/.Public/CBS.log
And poqexec.log: http://cid-78779374d6b6f1f3.office.live.com/self.aspx/.Public/poqexec.log
Don't know if they'll be useful or not.

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation
13 People had
this question

Was this helpful?

17

Votes

Answer

Okay, after much searching of Google, I found an answer that worked for me, my computer is now fixed without having to reinstall the OS. Solution courtesy of Aran, was found athttp://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/4491fe25-be44-430e-a384-fb58c5da5ad0/

It essentially involves doing a manual system restore.

- Open the recovery console

- Change working directory to whatever the root folder of the Windows install is (might be D: or some other letter for some people):

cd /d C:\windows\system32\config

Rename the following files by typing the following:

ren default default.old
ren sam sam.old
ren security security.old
ren software software.old
ren system system.old


- Change the working directory:

cd regback

- Copy the files from this directory to the previous directory as follows:

copy default c:\windows\system32\config
copy sam c:\windows\system32\config
copy security c:\windows\system32\config
copy software c:\windows\system32\config
copy system c:\windows\system32\config

- Having done this, I restarted my computer, and it booted all the way with no errors. However, it seemed somewhat unstable, so I booted into Safe Mode and ran CHKDSK (chkdsk /B) and conducted a normal system restore to before the service pack install using the normal method. To fix remaining problems, I ran sfc /scannow. My computer now seems to be running as well as ever.

Hope this helps,

Sam

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

uh, not nice, I was very worried and I am  even more worried now, I have exactly same problem as above, same error code etc, however, I even cant get into safe mode, all i get when pressing f8 is that I can use normal recovery or option with repair , however both failed constantly.

 

dont want to sound pathetic but my life is on that PC, I just transfered very important docs and files on it and was about to transfer some more before making usual back up, I use it only for couple of days and erased all from the old pc, I really hope something will be possible to do in this matter so that I get my stuff back asap

 

 

my system spec

 

Win7 Ultimate x64
Intel i7 975 extreme 3.33ghz
6gb memory
5 x 2TB WD and 160GB SSD C partition
ATI Radeon HD 5900 2GB

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

17

Votes

Answer

Okay, after much searching of Google, I found an answer that worked for me, my computer is now fixed without having to reinstall the OS. Solution courtesy of Aran, was found athttp://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/4491fe25-be44-430e-a384-fb58c5da5ad0/

It essentially involves doing a manual system restore.

- Open the recovery console

- Change working directory to whatever the root folder of the Windows install is (might be D: or some other letter for some people):

cd /d C:\windows\system32\config

Rename the following files by typing the following:

ren default default.old
ren sam sam.old
ren security security.old
ren software software.old
ren system system.old


- Change the working directory:

cd regback

- Copy the files from this directory to the previous directory as follows:

copy default c:\windows\system32\config
copy sam c:\windows\system32\config
copy security c:\windows\system32\config
copy software c:\windows\system32\config
copy system c:\windows\system32\config

- Having done this, I restarted my computer, and it booted all the way with no errors. However, it seemed somewhat unstable, so I booted into Safe Mode and ran CHKDSK (chkdsk /B) and conducted a normal system restore to before the service pack install using the normal method. To fix remaining problems, I ran sfc /scannow. My computer now seems to be running as well as ever.

Hope this helps,

Sam

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

You are a lifesaver!  I was dreading the hours I would spend restoring my computer back to it's former self. Your advice had me back up in 20 minutes!  Now I wonder: should I retry the service pack update or consider it a lesson learned and leave everything alone? 
    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

I could kiss you my friend...saved me
    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

Hi Only registered here to say THANKS, Sam! Your guide just saved my ****, after an SP1 update gone wrong. Now I can get back to work. Good job! /JRBDK
    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

Try this solutions, it helps for me

http://www.techguy.at/2011/03/10/windows-7-sp1-fehler-c0000034-beim-updatevorgang-282-von-118412-behoben/

regards
    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Seidlm

Seidlm
mfg

Was this helpful?

I never reply to these.  But I have to take the time to say THANK YOU.  The solution worked perfectly.  Saved an incredible amount of time.

 

Thanks Again.

    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

Simply Fantastic, searched for ages in desperation. We had exactly the same problem on two HP Z600 machines. Safe mode would not work, but was able to get to the system recovery and run the command prompt, however, all the files that needed to be renamed and copied seemed to be locked or being used by another process. I suspect this is a HP thing, as the main drive letter appeared as an X:\

Our sub-solution was to remove the hard drives of the two problem machines and put into a working machine. Navigate manually to the
C:\windows\system32\config and copy out, just incase...
Manually rename the files as mentioned in the above solution, then copy new files from the regback.
Hope this helps those that are locked out of cmd,
Brett

Thanks Sam for the solution, saved us many hours of downtime.


    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation

Was this helpful?

Wow - Thank you.  Have been working on this all day.  Finally determined that my system was installed on my D drive, so was able to do all of the above steps on my D drive and I can now boot normally into my Windows 7 system.  Spent much time trying the above steps on my X drive(seems to be labeled my "Boot" drive?  Also tried unsuccessfuly to do the above steps on my C drive.  Someone said they found their solution in finding their operating system on a different drive.  Wasn't sure how many drives I had because you cant see the drives at the command prompt.  So i just tried changing the drive from a to whatever and found that I also had a drive D on this computer.  So I then tried the above steps on the Drive D and WHAM!   it all worked.  I had initially found my files on the X drive but the system would not let me rename the files as suggested above.  My files on the D drive did let me rename the files and so SUCCESS!!!! was also able to do the remaining steps and I am back up and running!  Thank you.
    • Child exploitation or abuse
    • Harassment or threats
    • Inappropriate/Adult content
    • Nudity
    • Profanity
    • Software piracy
    • SPAM/Advertising
    • Virus/Spyware/Malware danger
    • Other Term of Use or Code of Conduct violation
<< PreviousPage of 3 Next >>

Message marked as answers cannot be deleted

To delete this message, first unmark this message as an answer, then delete it.

Reason to remove escalation


Merge

Enter the thread ID of the thread you are merging into


Reply will be posted to a public thread

You are replying to a public portion of this thread. To reply privately, click Cancel, click the Private Messages tab, and Reply on that private message.

Don't show this message again

To report abuse, sign in or continue without signing in

Thank you.

Report abuse

Abuse type:

Details (optional):

Report abuse

Abuse type:

Details (required):
Enter the characters you see (required):
Type the numbers that you see in the picture.
Play audio and type the numbers that you hear.
Show a different picture.

Sign in

Hotmail, Xbox Live, Messenger, or msn accounts will also work.

Don't have one of the above accounts?

Signing in...
This page will automatically update after you are signed in.
If you are having problems, you can close this message and try to connect again.