Page 5 of 5

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 6. Oct 2016, 09:39
by amicidavinci
shadowless wrote:This fix worked for me...
I hope this helps someone out there.


This worked for me too - THANK YOU shadowless!

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 10. Nov 2016, 14:35
by Auresco
I had the same issue, my Virtual Box GUI was not showing up. Uninstalling and installing the latest version worked fine for me.

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 10. Nov 2016, 14:41
by hamlatzis
I am enabling and disabling (with reboot) each time I want to develop for different platform. I hate it but since I cannot do anything else .... In my opinion Oracle and virtualbox is to be blamed. If other software works without a problem then it can be done.

I am using VMWare for the BlackBerry emulator, Visual Studio's emulator for Android and Google's emulator for Android work perfectly. Only company that has a problem is Jolla with SailfishOS that ise virtualbox for their emulator have the problem

Disabling: bcdedit /set hypervisorlaunchtype off
Enabling: bcdedit /set hypervisorlaunchtype auto

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 28. Jan 2017, 01:52
by JM89
When I Start A VM In Virtual Box It Crashes My Whole Computer Windows 10 I Get BSOD :(

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 28. Jan 2017, 15:09
by socratis
@JM89
Since this is a broad topic with more than 60 replies, I believe you should start your own topic. Do not forget to include full details about Windows version, VirtualBox version, VM full details. See: Minimum information needed for assistance.

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 30. Apr 2017, 14:08
by Stepe
Anything new 'bout the BSOD in context with hyper-v enabled?

(There's a ticket #15984 bout 7 month ago... :( )

Re: Windows 10 Anniversary Update Broke VirtualBox?

PostPosted: 3. May 2017, 16:50
by socratis
Stepe wrote:Anything new 'bout the BSOD in context with hyper-v enabled?
Not unless Microsoft changed their tactics and decided to not lock VT-x exclusively.