By dbminter - 19 April 2017 10:27 PM
I am guessing this question goes here.
I tried to Boot an image with the Boot Image option, but I got the following message:
Failed to boot image file
HyperV is not installed or is before version 6.03
Is HyperV something you have to install separately? I recently updated Windows 10 Anniversary Update to Windows 10 Creators Update. Is HyperV something that is installed as part of Windows 10 Creators Update? Is HyperV something you have pay for a license for?
HyperV is entirely new to me. Actually, I admit, virtual machines are entirely new to me. I've never tried working with them before. viBoot was installed as part of my Version 7 license so I thought I'd try it out. However, I didn't get anywhere for the stated reasons.
By dbminter - 19 April 2017 10:39 PM
Actually, I think I just found the answer to my question. I forgot to mention I'm using the Windows 10 Home version. I believe HyperV only works on Professional and Enterprise editions? Is that correct?
By Froggie - 20 April 2017 12:29 AM
DB, that's correct.
By MarkusL - 20 April 2017 8:12 AM
I'm not sure about Professional. But it is included in the Enterprise edition. It's no fun there either, because it conflicts with VMware and/or Virtualbox, so I don't use the feature at all.
By Mike A - 20 April 2017 8:52 AM
Windows Professional and Enterprise include the Hyper-V functionality. ViBoot is still installed on Windows Home, as it is possible to upgrade from Home to Professional without re-installation of Windows.
Windows only allows the use of one HyperVisor at a time, i.e. HyperV or VMWare. It is possible to have both installed at the same time but only one can be active to utilise hardware virtualisation. You can create different boot entries that allow you to switch between different HyperVisor's. Please read the following article on how to do this:
By dbminter - 20 April 2017 5:07 PM
Yeah, it's weird. I'm running Windows 10 Home, but I checked Services just to see, and there are 8 entries for Hyper-V services in it. I guess they're there because, as was said, some people might upgrade from Windows 10 Home to a higher version that might run Hyper-V.
By jphughan - 20 April 2017 6:34 PM
Wow dbminter, you're on a roll creating threads lately, and often then answering your own questions! :p
By dbminter - 20 April 2017 7:00 PM
I tend to be the one to answer my own questions because I can do a lot of research and testing. I juggle partition restores to do various tests and often find the culprit that way.
The funny thing is, I DON'T find the answers until usually after I've posted, even though I do Googles before I post. To avoid wasting people's time, I try to find my own answers. However, it generally tends to work out I don't find the answer until AFTER I've wasted everyone's time.
I've been beta testing ImgBurn for over 10 years, so I'm pretty familiar with troubleshooting issues. Just discovered a bug in the latest release of another software I use, as well.
By jphughan - 24 August 2017 10:11 PM
Some of those Hyper-V services are also there in case Windows 10 is running as a GUEST on some other host, which of course Windows 10 Home can.