Windows 10: 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?

:)

 

Windows 10 ADK

Is there a Windows 10 ADK available now that Windows 10 has released? I have the ADK Tech Preview, looking for the final ADK.

EDIT: It appears that the preview ADK will not open the WIM files from the downloaded ISO's

 

Check your PC - indicates Windows 10 can't be installed because of VirtualBox Graphics Adapter for Windows 8

Those links do not address the reported issue - they apply only to actual hardware, not to VirtualBox. The problem is that the Windows 10 compatibility appraiser does not recognize the VirtualBox display adapter as being compatible with Windows 10. In
fact, it is compatible - numerous people are running Windows 10 Technical Preview in VirtualBox using that configuration. Microsoft needs to update the appraiser application to recognize that the VirtualBox display adapter actually is compatible with Windows
10. For reference, VirtualBox reports its display adapter to Windows as follows:

Manufacturer: InnoTek Systemberatung

Model: VirtualBox Graphics Adapter for Windows 8

Device ID: 80EE-BEEF

Subvendor: 0000

Driver Version: 4.3.28.0

Until Microsoft updates the Compatibility Appraiser to recognize this device as being compatible with Windows 10, there is nothing a user can do to reserve Windows 10 for a Windows system running in VirtualBox. Users will be able to install Windows 10 after
it is released, but they won't be able to reserve it in advance unless Microsoft adds the above adapter to its list of Windows 10 compatible devices.

 

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.

 

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 *Smile

 

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...

 

enable hyper v as its Microsoft one

 

No - bad advice.

If you enable Hyper-V you can't run VirtualBox (or VMWare) 64 bit guests.

 

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.

 

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

 

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. *Smile