Windows 10: HYPER-V won't install properly on W10 HOST

Hi there

I can't install HYPER-V properly on a W10 HOST -- gets message about something in BIOS not enabled.

Installs fine on W8.1 . On W10 the boxes are greyed out.

Cheers

jimbo

:)

 

Not able to attach vhd for win2012 on windows 10

Win 10 has a different virtual host/client called Hyper-v. Should be no problem to install 2012r2 in it if your hardware supports Hyper-v (most does)

 

Windows 10 Creators Update... slow internet.

It's the virtualisation layer. You may not have installed it. It's an optional feature in W10. More here: Enable Hyper-V on Windows 10

But...I would like to have Hyper-V! It's not exactly a solution to remove it, is it?

 

Jimbo is the message about hypervisor not running?

 

I've added this to tutorial, end of Part Two:



Tip A tip from our admin z3r010 (original post):

If you get an error message about Hypervisor not running, open an elevated Command Prompt by pressing WIN + X and selecting Command Prompt (Admin) and give the following command:

bcdedit /set hypervisorlaunchtype auto

Hyper-V should now be able to run.

 

Hi there

Half the HYPER-V options are greyed out with BIOS firmware message on W10 Host.

Installing fine on W8.1 HOST - All the HYPER- V options were enabled -- never changed the BIOS. !!!

(I'll sort out anh Network changes later)

Cheers
jimbo

 

Jimbo, you've lost me now...

Please, a screenshot about those grayed out options you mean would be useful.

 

Hi there

I have to create a HOST W10 -- I'll backup my existing (working) W8.1 Host and install -- only takes around 20 mins or so.

What I did (I'll post screenshots later) was simply from a Base W10 (x-64 enterprise) install - no user applications at all added - go into the control panel and add programs and features -- when I selected HYPER-V the two sub options under the main HYPER-V were greyed out and when moving the mouse I had a tooltip come up = Virtualisation not enabled in BIOS firmware - which actually isn't true .

On W8.1 no problem - creating the W10 VM took around 5 mins even the Virtual switch worked.

Unlike VMWARE this VM is accessible from other computers (apart from XP which seems to have a trouble accessing shared HDD's on the VM). This machine itself (the HYPER-V VM) can access the other machines including the XP system.

I think I should have started using HYPER-V earlier -- and it's FREE. !!!

Cheers
jimbo

 

OK, now I got you. You have these two options grayed out and they cannot be selected:




It's very strange. Those not being available usually really means that the virtualization is not enabled but in your case Win 8 host on same hardware has it enabled. I have to Google this for more information, I have no idea at the moment.

 

Hi there

I'll create the W10 Host later and post -- those are the greyed out options though on W10 --- This was a CLEAN W10 X-64 Enterprise install - nothing added at all.

Any idea also why XP can't access the W10 VM - it can SEE the computer -- the W10 machine can access XP without any problem.

I've done the disable 128 bit encryption -- doesn't seem to make any difference. I would like to be able to share HDD's FROM the XP system as well as TO it. !!!

(Still it's a mega improvement over VMWARE). On an EXTERNAL USB HDD Old laptop SATA==>USB2 HDD) I'm getting a very decent response time on the VM. On an internal SSD I'm sure it would be indistinguishable from Native -- Thanks for getting me to have a go with this).

Cheers
jimbo

 

The XP <> Win10 networking is a bit complicated, I got it working with tips in this thread: https://www.tenforums.com/network-and...indows-xp.html.

Jimbo, you do RDP to Hyper-V virtual machines from host instead of default Virtual Machine Connection? If not you should try it, it's a whole new ball game!

 

Hi there

Just trying it now -- I like the LOCAL HDD's -I was wondering how to attach USB HDD's - no problem using them on the host and RDP with local HDD's.

What about though specialist hardware on the VM -- I think my XP VM might have to remain on VMware player for a while as I have several bits of specialist / legacy hardware -- Record Cutting (VINYL) studio, an old HP plotter and a Minidisc recorder for starters. No big deal -- as I'll probably keep an old computer for running it as a NATIVE machine. Still like the HDD's to share though. _ Will try out your suggestion for XP connectivity.

RDP is vastly improved since these days --on a LAN it actually works !!.

Cheers
jimbo

 

You have enough legacy stuff in XP, I agree it might be better to try that in Hyper-V.

 

Hi there

I'm going to leave the XP machine currently -- I'm Happy with the W10 VM running on HYPER-V under W8.1 -- I'll now see what happens with a REAL W10 and enable HYPER-V to see if I can re-create the previous error.

(I know also that VMWARE networking didn't work at all on a HOST W10 running a W10 VM (both x-64 enterprise before).

The RDP thing is good -- can leave the VM's running in the background with minimal resource consumption when not in use.

Cheers
jimbo