Hardware virtualization is blocked in Win 7 Pro 64-bit Dell machine - what to do?

[DGlan]

Hello experts - hope you all had a great and tasty Thanksgiving - but this one is a doozy:

I have a new Dell Optiplex 7010 MT with with 8GB RAM, a 500GB hard drive and an Intel Core i5-3470 CPU @ 3.20GHz – this is a genuine quad core processor with hardware virtualization.

Also, I have BIOS A16 with the following settings:

Virtualization Support: Virtualization – Enable Intel Virtualization Technology is ON VT for Direct I/O is Enabled – ON Trusted Execution is OFF

HOWEVER, in Win 7 Pro 64-bit, I am getting ready to do XP Mode but when I first run the havdetectiontool.exe from Microsoft, it says "Hardware-assisted virtualization is not enabled on this computer".

Hardware virtualization should be working but something is blocking it.

The MS havdetectiontool can create a detailed report - and I am pasting it below. BUT I HAVE ALREADY POWERED DOWN AND UP THE MACHINE MANY TIMES WITH THE ABOVE BIOS SETTINGS. Something is wrong. What is it?

This is the full report:

Intel VT or VIA Centerhauls processor.

System CPU supports Hardware Assisted Virtualization.Setting up driver.The file "C:\Users\glnz Admin\Downloads\sources\amd64\\detecthav.sys" is signed and the signature was verified.Driver installed.

-------------MSR Details------------------

Number of Processors in the system = 4Information for processor 0 :VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001VMX Enabled Bit not setTXT Enabled Bit not setHardware Assisted Virtualization is not enabled in the BIOSHardware Assisted Virtualization is not enabled in the BIOS.Please enable "Intel Virtualization Technology" in the BIOS, power down the computer completely, and then rerun the tool on power upInformation for processor 1 :VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001VMX Enabled Bit not setTXT Enabled Bit not setHardware Assisted Virtualization is not enabled in the BIOSHardware Assisted Virtualization is not enabled in the BIOS.Please enable "Intel Virtualization Technology" in the BIOS, power down the computer completely, and then rerun the tool on power upInformation for processor 2 :VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001VMX Enabled Bit not setTXT Enabled Bit not setHardware Assisted Virtualization is not enabled in the BIOSHardware Assisted Virtualization is not enabled in the BIOS.Please enable "Intel Virtualization Technology" in the BIOS, power down the computer completely, and then rerun the tool on power upInformation for processor 3 :VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001VMX Enabled Bit not setTXT Enabled Bit not setHardware Assisted Virtualization is not enabled in the BIOSHardware Assisted Virtualization is not enabled in the BIOS.Please enable "Intel Virtualization Technology" in the BIOS, power down the computer completely, and then rerun the tool on power up

Proc VMXLock VMXEn TXTBit

0 1 0 0 1 1 0 0 2 1 0 0 3 1 0 0

-------BIOS INFORMATION-------------------

Number of values: 15(01) BiosMajorRelease : 4(02) BiosMinorRelease : 6(03) ECFirmwareMajorRelease : 255(04) ECFirmwareMinorRelease : 255(05) BaseBoardManufacturer : Dell Inc.(06) BaseBoardProduct : 0GY6Y8(07) BaseBoardVersion : A03(08) BIOSReleaseDate : 09/09/2013(09) BIOSVendor : Dell Inc.(10) BIOSVersion : A16(11) SystemFamily : (12) SystemManufacturer : Dell Inc.(13) SystemProductName : OptiPlex 7010(14) SystemSKU : OptiPlex 7010(15) SystemVersion : 01BIOS Vendor : Dell Inc.BIOS Version : A16System Manufacturer : Dell Inc.Final returnValue = 2Send SQM data to Microsoft.The SQM machine ID already existsThe SQM user ID already existsReceived SQM upload callback:result 0x0Current file C:\Users\glnz Admin\AppData\Roaming\Microsoft\HAV Detection Tool\HAVDetectionTool.sqmHTTP code: 200

► SO WHAT TO DO ?? Hey, Dell, did you make a dumb mistake in the BIOS?

And here's the info from the Intel Processor ID utility:

Intel(R) Processor Identification Utility

Version: 5.01.20140910

Time Stamp: 2014/11/28 01:02:59

Operating System: 6.1-7601-Service Pack 1

Number of processors in system: 1

Current processor: # 1

Active cores per processor: 4

Disabled cores per processor: 0

Processor Name: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz

Type: 0

Family: 6

Model: 3A

Stepping: 9

Revision: 19

Maximum CPUID Level: D

L1 Instruction Cache: 4 x 32 KB

L1 Data Cache: 4 x 32 KB

L2 Cache: 4 x 256 KB

L3 Cache: 6 MB

Packaging: LGA1155

Enhanced Intel SpeedStep(R) Technology: Yes

MMX(TM): Yes

Intel(R) SSE: Yes

Intel(R) SSE2: Yes

Intel(R) SSE3: Yes

Intel(R) SSE4: Yes

Intel(R) AES-NI: Yes

Intel(R) AVX: Yes

Enhanced Halt State: Yes

Execute Disable Bit: Yes

Intel(R) Hyper-Threading Technology: No

Intel(R) 64 Architecture: Yes

Intel(R) Virtualization Technology: Yes

Intel(R) VT-x with Extended Page Tables: Yes

System Graphics: Intel(R) HD Graphics 2500

Expected Processor Frequency: 3.20 GHz

Reported Processor Frequency: 3.39 GHz

Expected System Bus Frequency: 100 MHz

Reported System Bus Frequency: 105 MHz

*************************************************************

SO HOW CAN I USE THE HARDWARE VIRTUALIZATION? Many thanks and happy turkey sandwich to all.

[DGlan]

Update -

I ran an odd test from Intel called BITS, and it showed an error in the MP Table and two errors in MSR. Don't know what that means, except that "MSR" shows in the "havdetectiontool" results I posted above.

Also, I strictly followed AGAIN the instructions above in the havdetectiontool test -

1) changed the BIOS to DISABLE the two virtualization options, did a complete power down, waited, pulled out AC plug, waited, pushed power button to discharge the capacitor, waited, connected the AC cord, waited, powered up, ran the havdetectiontool test, got the same results.

2) changed the BIOS to ENABLE the two virtualization features AND the Trusted Execution feature, did all the same power down and back up recycling and got an immediate boot error: "Alert! Invalid Trusted Execution Technology Configuration. Please refer to the Trusted Execution Technology Setup option helptext for details." But I have no idea where that helptext is. In any case, it is EXPECTED that Trusted Execution not work. But surprised it prevented boot-up.

3) Went back into BIOS, turned OFF Trusted Execution, left ON the other two virtualization options (so I'm back where I started), did the whole power off wait AC out power on again, booted OK, but same "Hardware-assisted virtualization is not enabled on this computer" message from the MS havdetectiontool test - back where I started.

Big pain in place where I sit on Michael Dell's nose.

Are you awake after reading this exciting saga? Any ideas?

[fbit]

hi,

http://blogs.msdn.com/b/volkerw/archive/2007/05/21/hardware-virtualization-check-utility.aspx http://blogs.msdn.com/b/volkerw/archive/2007/05/21/hardware-virtualization-check-utility.aspx

how about trying the http://www.grc.com/securable.htm http://www.grc.com/securable.htm by Gibson Research Corp sort of third party tool to check for VT-x support.

if you see Locked on, then the bios doesn't really switch on the VT-x (time to grab latest bios then)

if it is big "Yes", then according to virtualbox forum thread here,

https://www.virtualbox.org/ticket/10694 https://www.virtualbox.org/ticket/10694

https://forums.virtualbox.org/viewtopic.php?f=8&t=48660 https://forums.virtualbox.org/viewtopic.php?f=8&t=48660

there are possibility another application to switch off VT-x? maybe,

[DGlan]

►Not an answer but a really weird development.

My Optiplex 7010 is actually a dual-boot machine. I have both Win 7 Pro 64-bit and Win 8 Pro 64-bit, on separate partitions in the hard drive. Win 7 was first, and I installed Win 8 later. The problem described here is in Win 7.

All of the above bad news was from running havdetectiontool.exe from Microsoft while in Windows 7 Pro 64-bit. HOWEVER, when I booted into my Windows 8 Pro 64-bit, the havdetectiontool.exe says I DO have hardware virtualization!!!

So, not enabled in 7 and yes enabled in 8 - ON THE SAME PC WITH THE SAME BIOS SETTINGS !!!!! 

What is this? What is the problem?

I need it OK in 7 because I want to do XP Mode in 7. What is the crucial difference between 7 and 8 on the same PC ???

[One more detail: When I first tried to run the havdetectiontool.exe from Microsoft while in Windows 8, it gave me an error message that it could only run in 7, so (while staying in Win 8) I set its Properties to compatibility for 7 and Administrator privilege level. That's when it told me that hardware virtualization IS enabled. But when I ran exactly the same tool again in 7, I got the negative info posted above.]

Help !!!!!

[DGlan]

► More weirdness:

I just re-ran the verbose havtool.exe test while in Win 8 (where I have hardware virtualization), and I got the following results (pasted at bottom here).

Note the line

VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005

How do it get it to 0x000005 when I'm in Win 7?

Please also let me know if you see any other clues in the differences between the first test above (not enabled in Win 7) and the test below (yes enabled in Win 8 - on the same PC and same BIOS !!)

Here are the test results:

_________________________________

Intel VT or VIA Centerhauls processor.

System CPU supports Hardware Assisted Virtualization.

Setting up driver.

The file "C:\Users\glnz Admin\Downloads\HAVTool\sources\amd64\\detecthav.sys" is signed and the signature was verified.

Driver installed.

-------------MSR Details------------------

Number of Processors in the system = 4

Information for processor 0 :

VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005

TXT Enabled Bit not set

Hardware Assisted Virtualization is enabled in the BIOS

Information for processor 1 :

VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005

TXT Enabled Bit not set

Hardware Assisted Virtualization is enabled in the BIOS

Information for processor 2 :

VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005

TXT Enabled Bit not set

Hardware Assisted Virtualization is enabled in the BIOS

Information for processor 3 :

VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005

TXT Enabled Bit not set

Hardware Assisted Virtualization is enabled in the BIOS

Proc VMXLock VMXEn TXTBit

0 1 1 0

1 1 1 0

2 1 1 0

3 1 1 0

-------BIOS INFORMATION-------------------

Number of values: 15

(01) BiosMajorRelease : 4

(02) BiosMinorRelease : 6

(03) ECFirmwareMajorRelease : 255

(04) ECFirmwareMinorRelease : 255

(05) BaseBoardManufacturer : Dell Inc.

(06) BaseBoardProduct : 0GY6Y8

(07) BaseBoardVersion : A03

(08) BIOSReleaseDate : 09/09/2013

(09) BIOSVendor : Dell Inc.

(10) BIOSVersion : A16

(11) SystemFamily :

(12) SystemManufacturer : Dell Inc.

(13) SystemProductName : OptiPlex 7010

(14) SystemSKU : OptiPlex 7010

(15) SystemVersion : 01

BIOS Vendor : Dell Inc.

BIOS Version : A16

System Manufacturer : Dell Inc.

Final returnValue = 0

Send SQM data to Microsoft.

The SQM machine ID already exists

The SQM user ID already exists

Received SQM upload callback:result 0x0

Current file C:\Users\glnz Admin\AppData\Roaming\Microsoft\HAV Detection Tool\HAVDetectionTool.sqm

HTTP code: 200

► So, what is the difference between my two OSes that is causing the problem in Win 7??

Thanks.

[fbit]

no idea then,

run as administrator, turn off antivirus, update windows,

maybe a clean install of win7 pro will help?

[DGlan · Accepted solution]

To all watching this thread -

You are NOT going to believe this. I found the cause of the problem, and it's... AVAST !!! On my Win 8, where HAV says it works, I do NOT use Avast AV. I've been using Windows Defender. On my Win 7, where HAV says it's not enabled, I use AVAST AV Free, and it's been at the new 2015 Avast for a while. Over the past week, I've been thinking about this and wondering. So today, I ran some experiments, and it's an AVAST default setting that is the villain. Avast - Settings - Troubleshooting - "Enable hardware-assisted virtualization" has been on, so I turned it off, rebooted, and now the havdetectiontool shows "This computer is configured with hardware-assisted virtualization". Great!!! But bloody hell !!!! First my apologies to Dell. Mike, I just stopped eating beans and sitting on your nose. Second, my thanks to all who have tolerated my long posts here. Can anyone tell me why Avast's internal setting to enable HAV takes HAV away from everything else? Avast has certainly been getting sleazy the last two years, so apparently they're also not quality-testing their new versions very well. Any thoughts? Was this supposed to happen?