New VM won't boot

Page 2 of 2 FirstFirst 12

  1. Posts : 913
    CP/M
       #11

    Iíll need to learn how to set the boot order in Hyper-V. Never done that before.

    You need to go into VM emulated BIOS.

    ----------------------------------------------------------

    In Recovery command prompt, type:

    bootrec /scanos
    bootrec /fixboot
    bootrec /rebuildbcd

    https://support.microsoft.com/en-us/...startup-issues
      My Computer

  2. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #12

    muchomurka said:
    You need to go into VM emulated BIOS.

    ----------------------------------------------------------

    In Recovery command prompt, type:

    bootrec /scanos
    bootrec /fixboot
    bootrec /rebuildbcd

    https://support.microsoft.com/en-us/...startup-issues
    Thanks. I’ll take a wack st this tomorrow morning and let you know how it works.
      My Computers

  3. cereberus's Avatar
    Posts : 12,008
    Windows10
       #13

    SoFine409 said:
    Thanks. I’ll take a wack st this tomorrow morning and let you know how it works.
    Much easier to mount a Macrium Reflect Free Rescue iso as a dvd drive, and set Hyper-V to boot from dvd first.

    Then when booted into Reflect use ''fix windows boot problems".
      My Computer

  4. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #14

    Thanks cereberus. I’ll give that a try also.
      My Computers

  5. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #15

    muchomurka,
    In Recovery command prompt, type:
    bootrec /scanos
    Total identified windows installations - 0
    bootrec /fixboot
    ran OK

    bootrec /rebuildbcd
    Total identified windows installations - 0

    cereberus:
    Did as you suggested but the VM still boots to the recovery console saying that the required device isn't connected or cannot be accessed error code 0x000000e.
      My Computers

  6. cereberus's Avatar
    Posts : 12,008
    Windows10
       #16

    SoFine409 said:
    muchomurka,
    In Recovery command prompt, type:
    bootrec /scanos
    Total identified windows installations - 0
    bootrec /fixboot
    ran OK

    bootrec /rebuildbcd
    Total identified windows installations - 0

    cereberus:
    Did as you suggested but the VM still boots to the recovery console saying that the required device isn't connected or cannot be accessed error code 0x000000e.
    It is a little tricky as you do not get enough time to press enter during reboot as the vmconnection session opens.

    Just use reset from the Hyper-V task menu and it reboots from "dvd", and you can press enter.
      My Computer


  7. Posts : 913
    CP/M
       #17

    SoFine409 said:
    muchomurka,
    In Recovery command prompt, type:
    bootrec /scanos
    Total identified windows installations - 0
    bootrec /fixboot
    ran OK

    bootrec /rebuildbcd
    Total identified windows installations - 0.



    I do not know why, but once if this happened to me, some diskpart commands entered before bootrec resolved this situation, please try this:

    diskpart
    list disk
    sele disk 0
    list part
    sele part 1
    list volu
    sele volu 1
    exit

    ...and continue using bootrec commands. (No warranty this will work, it is only trial.)

      My Computer

  8. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #18

    cereberus said:
    It is a little tricky as you do not get enough time to press enter during reboot as the vmconnection session opens.

    Just use reset from the Hyper-V task menu and it reboots from "dvd", and you can press enter.
    hi cereberus. There was ample time to boot from the Macrium iso but the fix boot problems didn’t work. I looks to me like the multiboot menu on the system partition isn’t running otherwise I’d see the metro boot loader menu and be able to select the Win7 OS. I’m assuming that the multiboot menu is what given me grief.
      My Computers

  9. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #19

    muchomurka said:
    I do not know why, but once if this happened to me, some diskpart commands entered before bootrec resolved this situation, please try this:

    diskpart
    list disk
    sele disk 0
    list part
    sele part 1
    list volu
    sele volu 1
    exit

    ...and continue using bootrec commands. (No warranty this will work, it is only trial.)

    [/LEFT]
    Making progress. I was able to navigate to the correct place in the multiboot menu. The Win7 OS was found on disk "D". Fixboot ran and completed and rebuildbcd installed a new boot entry.

    When I restarted the VM I was able to select the Win7 OS but unfortunately the OS is damaged and wouldn't run, likely from previous repair attempts. Right now the Win7 install disk is try to complete automatic repairs if its successful then great, were done. If not I'm making a fresh VHDX of the Win7 partition to use in place of the suspect one.

    I'll let you knew what happens.

    UPDATE:
    Unfortunatly, and after recreating the VM several times, I was unable to get the Win7 to run. It got to the splash screen and shut down. Repeated repair attempts failed. I finally decided to do a clean install with my Win7 setup DVD and that ran perfectly so now I have a clean VM to play with. Go figure, Disk2VHD does have issues and Iím not the first person who has had issues with it.
    I was also able to restore a Macrium image of the Win7 system from the parent PC to a spare SSD and that worked perfectly. Iíve certinly learned a lot including how to use a Macrium rescue.iso to fix boot issues.
    Thnks for your help.
    Last edited by SoFine409; 16 Nov 2018 at 20:16. Reason: Updated Information
      My Computers

  10. SoFine409's Avatar
    Posts : 1,282
    Win10 Pro
    Thread Starter
       #20

    cereberus said:
    Much easier to mount a Macrium Reflect Free Rescue iso as a dvd drive, and set Hyper-V to boot from dvd first.

    Then when booted into Reflect use ''fix windows boot problems".
    Thanks, that worked. Good to know. I did that with with an iso of a windows rescue disk and used some of the tools on that as well.
      My Computers


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:36.
Find Us




Windows 10 Forums