• Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Window 10 will not boot after image

    Windows Problems
    2
    2
    208
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      IT Walrus last edited by

      I have spun up dozens of machines off of one image. Recently, I decided I wanted to update the image and capture a new one so I did.

      When I did that and imaged the reference machine after sysprep and image capture I got the error:

      Install Windows
      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.

      I will restart the machine several times and it does the same error. I decided its fine I guess I will just go back to the old image and work on it again.

      But now the image I had before throws the same error. Not sure what to do here.

      I tried the fix here: https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Reboot-loop-with-error-message/m-p/4048540?page=1#4049802

      It will get the machine to boot into windows but now I get an error that shows as this:

      The Recycle Bin on C:\ is corrupted. Do you want to empty the Recycle Bin for this drive?
      [yes] [no]

      After I click yes it seems fine but I don’t want to screw up another image. I am not sure how I broke the old image when I did nothing to it. Please Help.

      george1421 1 Reply Last reply Reply Quote 0
      • george1421
        george1421 Moderator @IT Walrus last edited by

        @it-walrus said in Window 10 will not boot after image:

        The computer restarted unexpectedly or encountered an unexpected error.

        I have seen this quite a while ago if the installation of a driver or something else causes widows to reboot out of order. I can tell you this can be a PAIN to try to debug. The problem typically had nothing to do with FOG, but something I did to the image, fog just faithfully duplicated the image.

        There are logs you can look at to see exactly where imaging has failed. When you are at the screen that says windows unexpectedly restarted you can hit a hot key combination to get a command window (maybe alt-f10 but check because its been about 6 years since I caused that issue). From the command window you can open notepad and then look at the imaging log files (google the location of these files too).

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        192
        Online

        10.4k
        Users

        16.4k
        Topics

        150.5k
        Posts

        Copyright © 2012-2023 FOG Project