locked
Windows 7 - Dont boot after install (Hyper-V) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi,

    Today I was install a VM with Windows 7 Ultimate. The setup ran very fine, I've allocated 200GB in virtual HD and set 2GB to RAM.

    After the install completes, a black screen appear and Windows dont boot (or start)...

    Any tip?
    Friday, February 5, 2010 5:14 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I would also like to encourage anyone who sees this issue to contact Microsoft product support.  This is something that should "just work" and if there is a problem here we would like to figure it out ASAP.
    Cheers,
    Benjamin Armstrong
    ============================
    Windows Virtualization
    Senior Lead Program Manager

    This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.
    Tuesday, July 20, 2010 7:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hyper-V v1 or Hyper-V R2?

    You installed Ultimate.  Have you tried Pro or business client SKUs?
    Brian Ehlert (hopefully you have found this useful)
    Friday, February 5, 2010 5:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Brian,

    I'm using Hyper-V R2.

    I've tried only Ultimate, because my license is for Ultimate. There's any trouble with Ultimate?
    Friday, February 5, 2010 6:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did this issue get resolved?  If so, please share with community how you resolved.  Otherwise, re-activate post if you still require assistance.

    Carmen M. Summers (MSFT) --Posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, March 30, 2010 1:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Carmen,

     

    I didn't solve the trouble. I uninstall Hyper-V and install VMWare. Now, all it's working perfectly.

     

    Regards.

     

     

    Tuesday, March 30, 2010 9:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same problem . I also tried using an ISO but same issue. Blank screen with cursor blinking.
    Sunday, June 27, 2010 7:39 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I am having the same exact problem.

    I can install other operating systems as virtual machines in Hyper-V R2, but not Windows 7. I have tried both 32-bit and 64-bit installs and after a full installation and reboot both turn up with a black screen prompting for CD/DVD....and the prompt is useless - I can neither boot to DVD again nor does it move on to booting from the hard drive.

    I have used the ISO to successfully install Windows 7 on a physical machine.

    Any ideas?

    • Proposed as answer by cloudsquall45 Wednesday, September 28, 2016 7:18 PM
    • Unproposed as answer by cloudsquall45 Wednesday, September 28, 2016 7:18 PM
    Wednesday, June 30, 2010 5:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am having the same exact problem, with Windows 7. Black screen, doesnt boot after putting in a user name and password.  Does it have to do somehting with the partitions?


    I am also trying to virtualize SBS 2008.  No success.  75% of the install it bluescreens, then boots to the SBS suggesting I reinstall.

     

    ANy suggesstions would be a great help.

    Tuesday, July 20, 2010 3:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ohhh.  The server I am running now is Windows Server 2008 Standard R2.

    Having issues using Hyper-V.  Someone is suggesting that VMware is better?

    Tuesday, July 20, 2010 3:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What do you mean "doesn't boot after putting in username and password"?

    At what point int he process are you entering a username a password?  In the installation wizard.  And it is after that that it hangs?

    Brian Ehlert (hopefully you have found this useful)
    Tuesday, July 20, 2010 3:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    More details would be great:

    1) the version of Hyper-V

    2) how the VMs are being installed

    3) where the media was downloaded from (and possibly when)

    4) the point during the instalaltion that the problem is seen.

    During your installation of SBS 2008 - what is happening at the time the VM blue screens (I am assuming it is the VM).

    We really need more information / details to make good guesses.

    Brian Ehlert (hopefully you have found this useful)
    Tuesday, July 20, 2010 7:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I would also like to encourage anyone who sees this issue to contact Microsoft product support.  This is something that should "just work" and if there is a problem here we would like to figure it out ASAP.
    Cheers,
    Benjamin Armstrong
    ============================
    Windows Virtualization
    Senior Lead Program Manager

    This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.
    Tuesday, July 20, 2010 7:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1) Hyper-v R2 installed on a Windows 2008 R2 Std. Server.

    2) The VMs are being installed as new machines through the Hyper V Manager.  The software is being installed (SBS 2008 from the DVD)  and Windows 7 Pro (From ISO burned from eOpen Account a few days ago).

    3) *see #2 above*

    4) For SBS 2008 the installation seems to proceed fine but during one the the final reboots the VM blue screens.  When restarted a dialog box appears stating that the installation was unsuccessful and that the product will need to be reinstalled. It also suggests that the existing partitions be removed before trying again.

    For Windows 7 the installation fails after asking for a user name and password. The system will reboot then hang at the "Press any key to boot from CD screen".

    Wednesday, July 21, 2010 11:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    VMware works perfectly.  However I would like to use Hyper-V since it is the only one supported by Microsoft.  Suggestions?
    Saturday, July 24, 2010 4:36 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I have the same Problem and I am using Windows Server 2008 R2 Enterprise with Hyper-V Role as Server , and windows Seven Ultimate X64 as Virtual Machine.

     

    After the install completes, a black screen appear and Windows dont boot

    I have used my Windows Seven DVD on different Physical Machines and they are working fine.

    Tuesday, January 18, 2011 9:51 AM
  • Question
    Sign in to vote
    47
    Sign in to vote

    Okay, I am ABSOLUTELY SHOCKED after a ton of web searching that an incredibly SIMPLE solution to this problem exists, but no one on any of these forums seems to be capable of understanding and revealing the answer... SO -- here it is:

    1. Create a new Virtual Machine on your Hyper-V (Server 2008 R2).
    2. Install Windows 7 from a DVD or an ISO file, whatever makes you happy.
    3. On the final reboot of the install, you will, of course, get the above mentioned black screen.
    4. Reboot the VM, but this time press a key to boot from the Windows 7 DVD (or boot from your ISO) so that you can get into the repair mode (recovery console/DOS prompt).
    5. Type C: to go to the C (boot) drive of your Windows 7 VM.

    Here's the magic:

    6. Simply type the following command at the recovery console DOS prompt:

    bootsect.exe /nt60 all /force

    7. type EXIT and then reboot the machine.

    ENJOY!

    • Proposed as answer by Eric D Madsen Friday, January 21, 2011 3:44 PM
    Friday, January 21, 2011 3:42 PM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Okay, I am ABSOLUTELY SHOCKED after a ton of web searching that an incredibly SIMPLE solution to this problem exists, but no one on any of these forums seems to be capable of understanding and revealing the answer... SO -- here it is:

    1. Create a new Virtual Machine on your Hyper-V (Server 2008 R2).
    2. Install Windows 7 from a DVD or an ISO file, whatever makes you happy.
    3. On the final reboot of the install, you will, of course, get the above mentioned black screen.
    4. Reboot the VM, but this time press a key to boot from the Windows 7 DVD (or boot from your ISO) so that you can get into the repair mode (recovery console/DOS prompt).
    5. Type C: to go to the C (boot) drive of your Windows 7 VM.

    Here's the magic:

    6. Simply type the following command at the recovery console DOS prompt:

    bootsect.exe /nt60 all /force

    7. type EXIT and then reboot the machine.

    ENJOY!

    ty 4 your best solution Eric

    • Proposed as answer by psaratscheff Wednesday, April 24, 2013 2:53 AM
    • Unproposed as answer by psaratscheff Wednesday, April 24, 2013 2:53 AM
    • Proposed as answer by Thomas M. Coyle Tuesday, February 4, 2014 12:08 PM
    Monday, July 18, 2011 5:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey

    I was seeing the same problem i.e whenever I created a VM (with win 7 os) and after install after the first boot it would go to the login prompt and then reboot and would just sit on a black screen with a cursor blinking.

    I boot the VM with iso and choose prompt and gave the command as mentioned earlier by ERIC

    bootsect.exe /nt60 all /force

    Restarted and it is working.

    Thanks

     

    Sunday, August 21, 2011 1:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Eric,

     

    After 2 weeks of trying all sorts of configuration changes .. i typed in your suggestion and IT  WORKED.  may you live long and prosper .. d*** what a royal pain that was.

     

     

    namaste

     

    Monday, September 5, 2011 6:01 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

     

    Eric, I shall scour the surface of the earth until I find you.  Wherever you are, I shall find you.  And when I find you, I shall .... I shall...... shake your hand, and buy you a beer and a philly steak sandwich (or pizza if you prefer).  THANKS!  That worked just right.

     

     

    Friday, November 18, 2011 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Freekin yeh  Eric you are King for the week in my book.

    Come to SA Give me a call and I will catch a Lion for you to ride.

     

    Thanx a Million!!!!!

    Wednesday, January 4, 2012 7:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a Lot. but please tell us why this is happen and what is the logic behind it. Is it the Microsoft fault or some other problem.

    And Thanks Again.

    Wednesday, April 4, 2012 7:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a Lot. but please tell us why this is happen and what is the logic behind it. Is it the Microsoft fault or some other problem.

    And Thanks Again.

    Beautifull : Awesome

    I was suffering with this issue since the first time I installed Win7; maybe a month after the release; almost 2 years; You are an Angel


    Tuesday, June 5, 2012 4:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I would say that the thing to do is what Ben Armstrong suggested - contact Microsoft if this happens.  I've installed Windows 7 countless times on Hyper-V and never seen this problem.  I know a lot of other people that have installed it countless times without this issue.  Without working with Microsoft to get to the root cause for your particular environment, it will be pretty hard for anyone to say why it happens for some people and never for others.

    timcerl

    Wednesday, June 6, 2012 6:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks

    w8r2 as hyperv guest needed the same treatment

    Friday, August 17, 2012 7:06 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    You don't even have to boot into Repair mode, 

    1. Mount the vhd using disk managment

    2. Open a cmd prompt

    3. Insert any Windows 7 or 8 install disk in dvd drive

    4. <dvd letter>:/boot/bootsec.exe /nt60 <vhd system drive letter>: /force

    5. Detach the vhd

    6. Reboot your VM

    Saw this elsewhere, so much easier than booting into Repair.

    Thursday, November 15, 2012 3:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    After pulling out what little is left of my hair, I just realized that Eric, you are a god.

    I can't believe why Microsoft still doesn't get this resolved -- in year 2013!!!!

    The bootsect trick works perfectly -- however, for those coming later, you must first use diskpart to map the "Reserved" volume to a drive letter, and then do the bootsect trick on that drive letter.  Doing it on C: doesn't work.


    Wednesday, July 24, 2013 5:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Stephen, may you just describe it step by step?

    I tried with the Erics trick, but i gets the message in cmd:

    'bootsec.exe' is not recognized as an internal or external command, operable program or batch file.

    Thanks in advance.

    Wednesday, September 4, 2013 5:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Bro... You're a genius :)
    Monday, November 11, 2013 11:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    After about 2 weeks of trying to look for a solution and here it is, with this great man.

    you have saved me tons of time.

    THANKS!!!!

    Friday, November 15, 2013 7:55 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Should read bootsect.exe
    Tuesday, November 19, 2013 1:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just ran into this same issue.

    My problem got resolved after using the x64 version DVD of Win7 (just x64 instead of the DVD that had both x86 and x64 versions).

    What I did:

    My host is Windows 8.1

    After installing Windows 7 x64 as VM on my 8.1 based laptop two days ago, I wanted to do the same on my desktop PC, but I had the same issue described here.

    I used a DVD just with the x64 version for my laptop and a DVD with both x86 and x64 version for my desktop.

    Tried repairing as advised by a post, but got the error: "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of windows."

    I exported and imported the VM from my laptop to my desktop to test it and it ran with no problems.

    So I tried the DVD that had just the x64 version of Win7 and that installed without issues.

    I'm curious if this happens only when a DVD with more than one Win7 versions is used.

    • Edited by Mircea Bugan Sunday, March 30, 2014 6:49 PM clarifications
    Sunday, March 30, 2014 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is the best and fastest option.

    Until now microsoft hasn't fixed this yet.

    Saturday, May 24, 2014 2:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i would like to request you to check the following points.

    1. on which drive your os has been installed. (if its not on c drive, then you have to use the fixboot command from Recovery console.



    Thursday, June 12, 2014 11:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    How can I do it? do you have a print screen? I'm trying to install w7 on hyper-V, but after installing black screen and a cursor blinking. But I don't know how to do what you suggested. Appreciate your help. Best regards
    Wednesday, August 6, 2014 6:13 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    For those of you who are still having the  "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of windows.".

    Notice that what your highlighting, unhighlight the windows 7 in the repair menu and then click next, THEN you can navigate to the cmd to do the bootrec

    Hope this helps

    Monday, August 11, 2014 3:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Okay, I am ABSOLUTELY SHOCKED after a ton of web searching that an incredibly SIMPLE solution to this problem exists, but no one on any of these forums seems to be capable of understanding and revealing the answer... SO -- here it is:

    1. Create a new Virtual Machine on your Hyper-V (Server 2008 R2).
    2. Install Windows 7 from a DVD or an ISO file, whatever makes you happy.
    3. On the final reboot of the install, you will, of course, get the above mentioned black screen.
    4. Reboot the VM, but this time press a key to boot from the Windows 7 DVD (or boot from your ISO) so that you can get into the repair mode (recovery console/DOS prompt).
    5. Type C: to go to the C (boot) drive of your Windows 7 VM.

    Here's the magic:

    6. Simply type the following command at the recovery console DOS prompt:

    bootsect.exe /nt60 all /force

    7. type EXIT and then reboot the machine.

    ENJOY!

    Thanks it worked
    Wednesday, February 25, 2015 8:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This works!
    Friday, June 26, 2015 4:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked for me as well installing windows 7 VM on a windows 10 host
    Sunday, December 20, 2015 11:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanx man, work fine now!
    Friday, April 29, 2016 8:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you. It just worked for me still on Win 10 and in the year 2016!
    Friday, May 6, 2016 7:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Superb it Work for me ! 

    Thank you Eric D Madsen 

    Tuesday, May 24, 2016 6:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The Eric solution is worked with me with a tiny modification,

    5. Type C: to go to the C (boot) drive of your Windows 7 VM.
Here's the magic:
    there is no C: drive in my case, only X: drive. So I typed it in the root of X: drive and worked well with me.

    Sunday, October 2, 2016 3:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the trick.
    Saturday, October 22, 2016 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I CREATED AN ACCOUNT JUST TO SAY THANKS!

    Worked Perfectly on Server 2008 r2 vm. All i did was type the code ERIC mentioned, inside command prompt, after booting with Server 2008 r2 ISO.

    THANKS A LOT. SAVED MY DAY.

    Friday, November 18, 2016 7:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks you very much it  mind blowing Trick
    Tuesday, November 22, 2016 11:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you Eric!
    Friday, December 9, 2016 6:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    After a lot of efforts a lot of working and too many new installations with multiple scenarios finally this solution rocks

    Thanks brooooo 

    Tuesday, May 9, 2017 11:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Simple changes to this command the bootsec.exe is missing the t. It should read bootsect.exe. Also the drive letter that you need to point this at is the "System Reserved" drive, not "C"...
    Saturday, May 20, 2017 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a lot Eric D Madsen.  It works!
    Friday, June 16, 2017 2:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks absolutely Eric. Perfect!
    Sunday, June 18, 2017 2:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You are a great guy. You solved the problem
    Wednesday, June 28, 2017 11:20 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have tried the solution and it worked

    Really thanks to you

    Monday, December 18, 2017 2:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    2018 and still works on server2016! Thumbs up!
    Thursday, July 26, 2018 11:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    THANKS WORKED FINE
    • Proposed as answer by mackahanaky Sunday, April 7, 2019 11:22 AM
    • Unproposed as answer by mackahanaky Sunday, April 7, 2019 11:23 AM
    Sunday, April 7, 2019 11:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    you are life saver

    tried and it works

    Wednesday, October 23, 2019 8:24 AM