Trying to install W10 in Hyper-V with W8.1 pro as host.
Keep getting this error, but a search reveals fixes for the error only on installed OSes.
This wasn't happening previously.
Any ideas???
Wenda.
You mean when you are starting the VM? This error means the boot files are corrupt / missing. Are you running generation 1 or 2 VMs? It will show you the generation on the summary tab of the main Hyper-V manager (and it determines if you are doing BIOS or UEFI boot..
Gen 1 0r Gen 2 - it makes no difference. I tried both. 2 gives me an EFI boot error, 1 just gives the error in the thread title.
I tried it in Virtual-Box, and got this (see below).
I don't get it, this all worked before I went to W10 (this is a restored sys-image, NOT a roll-back).
I ran several of the betas no problem at all, on this setup, before imaging it and upgrading.
Could W10 have possibly screwed with my BIOS???
I am going to try an earlier image, which has known working VMs installed, and see if that solves the problem.
Meanwhile, I'll be on the W7 machine ...
Wenda.
You can't start a x64 VirtualBox VM if Hyper-V is enabled. Try disabling Hyper-V by entering this from administrator command prompt and rebootingNext try to start virtualbox VM. If it will still not start then check VT-x is enabled in BIOS (I can't imagine it would change it but you never know). If your VirtualBox VM will start then you know BIOS is OK.Code:bcdedit /set {default} hypervisorlaunchtype off
To re-enable hyper-v enter this and rebootFixing boot issues should be the same for VM as normal machine but it is worth checking BIOS first.Code:bcdedit /set {default} hypervisorlaunchtype auto
You beat me to it, but thanks for your help. Would have posted earlier, but was sleeping (it's now just after 6am here). I let the (150+GB) image restore overnight.You can't start a x64 VirtualBox VM if Hyper-V is enabled. Try disabling Hyper-V by entering this from administrator command prompt and rebootingNext try to start virtualbox VM. If it will still not start then check VT-x is enabled in BIOS (I can't imagine it would change it but you never know). If your VirtualBox VM will start then you know BIOS is OK.Code:bcdedit /set {default} hypervisorlaunchtype off
To re-enable hyper-v enter this and rebootCode:bcdedit /set {default} hypervisorlaunchtype auto
Fixing boot issues should be the same for VM as normal machine but it is worth checking BIOS first.
Yes, I know you can't run VB with Hyper-V enabled or vice-versa, but disabling it made no difference.
The older image restored OK, but Hyper-V still wasn't working. However, this time I got an error message which led me to the self-same fix you have posted. Now I just have to restore the current image (doing that now), apply the fix, and I shouldbe good to go (touch wood).
Thanks again for your help.
BTW, this is a laptop with the usual severely cut-down (non-UEFI) BIOS, VT-x cannot be accessed or changed. This is why I was worried W10 may have made irreversible changes to it.
Wenda.
Update: The fix has been applied, and tested with a Win 8 Pro 64 disc in Virtual-Box.
All now appears to be working as it should.
Wenda.
Good news
