Success with Win10 Build 14393.5

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).
Post Reply
FireNWater
Posts: 2
Joined: 27. Jul 2016, 18:52

Success with Win10 Build 14393.5

Post by FireNWater »

Success with Win10 Build 14393.5 and VB 5.1.3 Build 109110 on my Surface Pro 4.
.
Build 14393.5 is supposed to be the RTM build for Windows 10 Anniversary Edition, so I figured I would post my journey arriving at a working VB install.
.
The big roadblock was that I had Hyper-V installed and it was interfering with VB. The first symptom was that only 32-bit versions of any Guest OS would show up in the dropdown box of VB Manager. The next symptom was that the machine would immediately BSOD when starting the VM with a 64-bit install disk. Once I went into Windows Components and removed Hyper-V from my system it all seems to work well with both Ubuntu and Debian 64-bit guest OS's.
.
I now know that Hyper-V is listed as an incompatible "3rd Party" system here in the forums. However, since it is part of Windows, I didn't expect it to be listed as such and didn't open that sticky until after I got a working installation.
.
Perhaps it would be possible for the developers of VB to check or the presence of Hyper-V and other non-compatible software packages during the installation process. It would save newcomers a lot of searching and frustration.
.

Code: Select all

VirtualBox COM Server 5.1.3 r109110 win.amd64 (Jul 25 2016 15:32:55) release log
Log opened 2016-07-27T13:52:41.511920700Z
Build Type: release
OS Product: Windows 10
OS Release: 10.0.14393
OS Service Pack: 
DMI Product Name: Surface Pro 4
DMI Product Version: D:0B:08F:1C:03P:38
Host RAM: 16310MB total, 12189MB available
Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
Process ID: 7876
Package type: WINDOWS_64BITS_GENERIC
wdupree
Posts: 11
Joined: 12. Apr 2016, 03:14

Re: Success with Win10 Build 14393.5

Post by wdupree »

Perhaps it would be possible for the developers of VB to check or the presence of Hyper-V and other non-compatible software packages during the installation process. It would save newcomers a lot of searching and frustration.
This - I totally forgot about this and didn't think that after a reset it got enabled again. I went and disabled it and no more crashes. Having this would be a great help... hope it can be done!
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Success with Win10 Build 14393.5

Post by socratis »

It is done already. VirtualBox checks for the availability of VT-x and it tells you:

Code: Select all

VT-x is not available.
Now why it's not available, well, the possibilities are too much to handle.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply