Error message "The Computer Restarted unexpectedly or encountered an unexpected error" after System Startup on Windows 7 Recovery

Anonymous
2011-03-03T22:12:20+00:00

Recently, I needed to restore my laptop to factory settings.  I have an HP Pavilion Model Number G-60.  I purchased a set of recovery disks from HP and when they arrived, I booted the system with Disc 1 in the CD/RW drive.  The installation asked for all 3 discs and after it ejected the 3rd disc, the system rebooted and then restarted.  I got the message, "Setup is preparing your computer for first use"....then the Error message "The Computer Restarted unexpectedly or encountered an unexpected error.  Windows installation cannot proceed.  To install Windows, click OK to restart the computer and then restart the installation".  Doing this only keeps repeating the error message.  I looked at some of the messages already on the forum and tried the solution by Syed Karim but that did not work.  Can you think of anything else that I can try to get this working?   Honestly, I am very frustrated with this.  I didn't buy this laptop so that I can have these problems with a Windows 7 installation that would make my laptop useless.  I would appreciate any help you can give me.  Thanks,  Dave

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2011-04-12T18:53:35+00:00

1)      On the same error screen press SHIFT+F10 and it will open up a black Window. (a command prompt window)

2)       In  the black windows type the word "regedit"(without the inverted commas and hit enter. That will open the registry editor.

        In the Registry Editor..

                Browse to....

        HKLocal machine/SYSTEM/SETUP/STATUS/ChildCompletion, and after highliting childcompletion,on the right hand side check for setup.exe. if the value is 1 change it to 3.(by double clicking on setup.exe and changing the value shown in the box).

Then close the registry editor and then also close the black window.

      Then click on OK for the error and the computer will restart and the installation may complete.  just try it and let me know if it worked.

Was this answer helpful?

2 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2011-03-03T23:03:31+00:00

Seeing as how you are trying to restore your system from OEM disks that were supplied by HP, you need to contact HP about the problem, it could be hardware related.

Also, OEM versions of Windows 7 are to have all support supplied be the computer manufacturer, not Microsoft.

Was this answer helpful?

0 comments

704 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-04-25T18:25:16+00:00

    1)      On the same error screen press SHIFT+F10 and it will open up a black Window. (a command prompt window)

    2)       In  the black windows type the word "regedit"(without the inverted commas and hit enter. That will open the registry editor.

            In the Registry Editor..

                    Browse to....

            HKLocal machine/SYSTEM/SETUP/STATUS/ChildCompletion, and after highliting childcompletion,on the right hand side check for setup.exe. if the value is 1 change it to 3.(by double clicking on setup.exe and changing the value shown in the box).

    Then close the registry editor and then also close the black window.

          Then click on OK for the error and the computer will restart and the installation may complete.  just try it and let me know if it worked.

    Worked for me. Thank you. Saved me a few hours of work!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-04-24T07:09:29+00:00

    In my experience I was getting this error when attempting to apply a customisation script to a VMware virtual machine that was deployed from template (Windows 2008 R2). This error was caused by the VM not having its NIC set to "connect at power on"

    After deleting and re-creating the VM about 6 times I finally noticed that the NIC was not set to "connect at power on", and after deploying fresh from a template I set the vmnic to "connect at power on" and the customisation then worked fine first go and gave no errors.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-04-13T04:19:51+00:00

    WOW... one year to the day..exact same problem.. thanks for the solution..I have no idea what I just did, but it works..if you don't mind posting why we did that and why windows had issues in the first place.

    Thanks

    Was this answer helpful?

    0 comments