• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 10 Anniversary Update took my VT-x hostage

J

JimmiG

Platinum Member
I noticed after updating to Windows 10 1607 on my work laptop, Virtualbox would no longer let me use hardware virtualization. SecurAble would also report no hardware virtualization supported. The system has an i7 4710MQ which supports virtualization, and hardware virtualization is enabled in the BIOS.

Here's how I got it working again:
1. Enabled Hyper-V features in Windows 10 and rebooted
2. Disabled Hyper-V features in Windows 10 and rebooted
3. Rebooted and disabled hardware virtualization in BIOS
4. Rebooted and re-enabled them again in BIOS
5. Enabled Hyper-V features in Windows 10 and rebooted
6. Created and started a simple test VM in Hyper-V
7. Deleted the test VM
8. Rebooted
9. Disabled Hyper-V features in Windows 10 and rebooted
10. Suddenly, hardware virtualization is working in Virtualbox, and SecureAble reports hardware virtualization supported
 
Not sure if related, but myself and another poster in the Anniversary Update thread lost Bridged mode in VMware (I normally run 2-3 at a time). NAT mode works, but I could see the occasional problem with sharing the hosts IP address. So it would appear that this update may be doing something to virtual machines, just not sure what that would be at this point.

So one suggestion, if your virtual drives are VMDK files, would be to create virtual machines for them in VMWare. All virtual hardware is still working fine on my machines.
 
I know for virtualbox at least, it and hyper-v do not play well together. I had seen this is both Win8.1 and Win10 and Win10(1511). I have not tried it personally in Win10(1607) but i would expect the same.

If you need both, you can enable a boot menu entry to turn off the hyper-v. So at boot you would have two os selections 1 for normal and 1 for hyper-v off.

My guess for any other VM software I would say to remove and re-install it as it does hook into some lower level bits of the os and could cause some issues. like what Ketchup mention for the missing network items
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top