-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Hardware and Upgrade Questions
- Elitebook 8570w - Cannot enable VT-x - Windows 8.1

Create an account on the HP Community to personalize your profile and ask a question
02-10-2014 12:05 PM
I have an strange behaviour on my laptop, when I enable VT-x in bios, CPUid (http://www.cpuid.com/softwares/cpu-z.html) shows it as disabled.
If I disable VT-x CPUid shows it as enabled..
But in either case, i cannot install IntelHaxm (Android emulator), and VMwhare Workstation cannot create 64bit vm's, which worked flawlessly before.
It seems that this might have happened around the time I upgraded Windows8 to 8.1, but I am not too sure, I guess Hyper-V doesn't disable other applications ability to see VT-x?
My cpu is an i7-3610QM which supports VT-x according to ark.intel.com
I'm using Bios F43, but have tried to restore F31 to see if it was bios related, but same behaviour.
I have also cleared bios defaults, and also used BCU to try to configure, but nothing happens, CPUid reports the oposite as Bios settings (BCU reports same as bios settings so that's fine)
What can be wrong?
Others in my office with the same computer have no problems, but they have installed windows 8.1 from scratch though
Solved! Go to Solution.
Accepted Solutions
02-11-2014 05:04 AM
Found the solution, it was Hyper-V that stole the VT-x status, so all other apps did not get info about the proper VT-x status, even if I did not use Hyper-V.
Not sure where Hyper-V came from, if it was Win 8.1 or VS 2013's mobile tools, but anyhow, using bcdedit diplayed that "hypervisorlaunchtype" was set to auto, setting this to off using:
bcdedit /set hypervisorlaunchtype off
solved the whole problem, now i can use vmware and intel haxm again..
what a load of crap..
02-11-2014 05:04 AM
Found the solution, it was Hyper-V that stole the VT-x status, so all other apps did not get info about the proper VT-x status, even if I did not use Hyper-V.
Not sure where Hyper-V came from, if it was Win 8.1 or VS 2013's mobile tools, but anyhow, using bcdedit diplayed that "hypervisorlaunchtype" was set to auto, setting this to off using:
bcdedit /set hypervisorlaunchtype off
solved the whole problem, now i can use vmware and intel haxm again..
what a load of crap..
08-28-2015 01:28 PM
It is resolved as follows:
1. Reboot
2. Press ESC, then select F10
3. Go to System Configuration tab
4. Go to Device Configuration (not Set Security Level)
5. Move to Virtualization Technology (VTx), and check the box
6. Save and boot
After these steps, I successfully enable VTx and installed Intel HAXM.