New
#1
Can I run Windows 10 ADK in VirtualBox and other questions?
Hi, I have few questions. Can I run Windows 10 ADK in VirtualBox and can I run it in a cloned Windows 10 VM and use the answer file from the clone in the original VM?
Can I run Windows 10 ADK in VirtualBox and other questions?
-
-
New #2
Yes, Yes and yes or it depends on your answer file, and if it makes any sense.
But I have a question for you. Why are you playing with VirtualBox, when your Windows version and CPU supports Hyper-V and virtualization? In order for you to get VirtualBox running properly and efficiently, you need to completely disable built in Hypervisor support in Windows, which is enabled by default. I'd rather uninstall VB and replace it with Hyper-V.
For Windows and Linux VMs Hyper-V is very good and you can use many Windows built in and downloadable tools for managing those VMs, while for VB VMs you can mostly only use VB.
-
New #3
It isn't enabled by default. You need to enable Hyper-V in Windows features. Virtualbox works fine on a clean install of Windows with no changes required. It is true if you enable Hyper-V you can't then run 64bit guests in VirtualBox.
It is less good if you want sound on Linux, want to also run your VMs on a non Windows host or run OSX guest.
I do use Hyper-V (and VirtualBox and VMWare for OSX guests) but it isn't always the best solution :)
-
New #4
Hypervisor is enabled by default in Windows, Hyper-V is not. There is a big difference.
If you want all features enabled in VirtualBox and VMWare, you MUST disable the hypervisor in Windows. This does not mean you have to uninstall Hyper-V, it just mean you need to boot Windows into a different configuration.
I too run Hyper-V, VMWare, VirtualBox, KVM and many more...
-
New #5
yes you can
-
New #6
enable hyper v as its Microsoft one
-
New #7
-
New #8
Here's how this works:
You can decide to install the Hyper-V services or not. All other Hypervisor brands will work or not work no matter if Hyper-V is there or not.
The thing you must do is to create a new boot profile where hypervisorlauchtype is set to OFF. This way all other Hypervisors will work. BUT if you want to run Hyper-V you must have a profile where hypervisorlauchtype is set to AUTO.
I have done this configuration ever since Hyper-V was introduced in Windows. Doing all the above I have been running Hyper-V, VirtualBox, VMWare and many other hypervisors on Windows successfully and without any limitations.
-
-
New #9
You are of course correct.
There is a tutorial for doing the same here which I found most useful moving from VBox to Hyper-V.
Switch easily between VirtualBox and Hyper-V with a BCDEdit boot Entry in Windows 8.1 - Scott Hanselman
-
New #10
YEP! That is the simplified version of it. Works great!
Because I was using both VirtualBox with GenyMotion and VMWare a lot at some point when Android emulation was horrible in Visual Studio I put the default boot profile to Windows hypervisor disabled. But copied the default profile so I could also occasionally use Hyper-V.
Now when VS has full support for Android emulation and Intel HAXM drivers, I have no need for VirtualBox and GenyMotion. I don't do these steps anymore. If for some reason I need any of the 3rd-party VMs I will add the appropriate boot entries again. :)
Quote
Related Discussions
