Windows 8 and 8.1 Forums


Hardware virtualization BLOCKED - mistake by Dell ???

  1. #1


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit

    Hardware virtualization BLOCKED - caused by AVAST !!


    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. I am dual booting Win 7 Pro 64-bit and Win 8 Pro 64-bit.

    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, 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 – and it’s some type of weird BIOS - hardware problem.

    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 = 4
    Information for processor 0 :
    VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001
    VMX Enabled Bit not set
    TXT Enabled Bit not set
    Hardware Assisted Virtualization is not enabled in the BIOS
    Hardware 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
    Information for processor 1 :
    VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001
    VMX Enabled Bit not set
    TXT Enabled Bit not set
    Hardware Assisted Virtualization is not enabled in the BIOS
    Hardware 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
    Information for processor 2 :
    VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001
    VMX Enabled Bit not set
    TXT Enabled Bit not set
    Hardware Assisted Virtualization is not enabled in the BIOS
    Hardware 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
    Information for processor 3 :
    VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000001
    VMX Enabled Bit not set
    TXT Enabled Bit not set
    Hardware Assisted Virtualization is not enabled in the BIOS
    Hardware 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 : 01
    BIOS Vendor : Dell Inc.
    BIOS Version : A16
    System Manufacturer : Dell Inc.
    Final returnValue = 2
    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 TO DO ?? Hey, Dell, did you make a dumb mistake in the BIOS?

    ►MORE INFO:

    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?
    Last edited by glnz; 17 Jan 2015 at 12:46.

      My System SpecsSystem Spec

  2. #2


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    ► More info --

    The Optiplex 7010 is dual-boot. At the moment, I'm in my Win 8 Pro 64-bit OS. Its "System Information" shows the following four lines:

    Hyper-V - VM Monitor Mode Extensions ... Yes
    Hyper-V - Second Level Address Translation Extensions ... Yes
    Hyper-V - Virtualization Enabled in Firmware ... Yes
    Hyper-V - Data Execution Prevention ... Yes.

    I am not familiar with Hyper-V, and I certainly didn't install it on my own. I don't know why there are any references to it. But, anyway, do these four lines mean anything?

    Does the machine's DEP prevent the use of hardware virtualization?
      My System SpecsSystem Spec

  3. #3


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    ►► More more info ---

    My post directly above about Hyper-V might be irrelevant. Those four lines appear in msconfig only when I'm in Win 8. They do NOT appear when I'm in Win 7. And they probably have nothing to do with the problem, which is:

    What is blocking hardware virtualization on my PC?

    Thanks.
      My System SpecsSystem Spec

  4. #4


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    ►Not an answer but a really weird development.

    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 !!!!!
      My System SpecsSystem Spec

  5. #5


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    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.


      My System SpecsSystem Spec

  6. #6


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit



    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.

    I've been thinking about this and wondering. So 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?
      My System SpecsSystem Spec

  7. #7


    Posts : 1,875
    Windows 10 Pro Prieview x64


    Are you sure it is Avast? No reason for an AV to run a VM but you never know I suppose - I don't use Avast..

    My guess would be Hyper-V. You thought it was a red herring but I don't think so. If you have it enabled (the feature is turned on) then it takes control of the VT-x at boot time even if you are not using it and it is then not available for other hypervisors. TPM has got nothing to do with it.

    Disable Hyper-V (remove it windows add/remove features is easiest) and see if it works. You can change your boot options to enable/disable Hyper-V but if you aren't using it best just remove it.
      My System SpecsSystem Spec

  8. #8


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    adamf - yes, it's Avast, which I have now actually confirmed on two OSes.

    Note that I don't have any problem in Win 8.1 where I am NOT using Avast at all. And I found hypervisor only in Win 8, so I don't think there's any connection.

    I have the problem only in Win 7 where I am using Avast - but the problem goes away if I go into the Avast settings and UNcheck "enable hardware-assisted virtualization". I don't think there is hypervisor in Win 7 but let me know if I'm wrong.

    I don't know anything about virtualization yet - haven't had enough free time. But, preliminarily, I was stymied by the negative results in MS's HAV detection tool until I found the problem.

    Note that this is the new 2015 (or maybe "NG") version of Avast.
      My System SpecsSystem Spec

  9. #9


    Posts : 1,875
    Windows 10 Pro Prieview x64


    I just saw your thread here https://forum.avast.com/index.php?topic=162445.0 (I guess it is you). Sorry to have missed it.

    Anyway the theory is quite straightforward. Only one program can use the VT-x instructions. If Hyper-V is installed it will take control at boot (and then you can't run VMWare, VirtualBox or other hypervisors etc in 64bit mode - you get the same error).

    Apparently for some unknown (to me) reason Avast does also. So Avast has taken control and your hypervisor (XP mode) can''t run.

    The detection tool is telling you if you CPU is OK and it is turned on in BIOS - not that something has grabbed it.

    Good find though
      My System SpecsSystem Spec

  10. #10


    Posts : 36
    Dual boot - Win 7 Pro 64-bit and Win 8.1 Pro 64-bit


    adamf - you write "The detection tool is telling you if you CPU is OK and it is turned on in BIOS - not that something has grabbed it."

    But I think in Win 7 Avast DID grab it. As soon as I unchecked EHAV in Avast (in Win 7), the MS havdetectiontool gave good results. I already knew my CPU and BIOS were OK - the earlier negative results in the MS havdetectiontool had been driving me nuts.

    Can you advise further how this works? There is room only for one virtualization system running at a a time? If so, why has Avast done what it's done? How come I'm the first person to notice?
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Hardware virtualization BLOCKED - mistake by Dell ???
Related Threads
How to enable hardware virtualization in Aptio Setup Utility? I am not able to enable it in BIOS. I want this because while installing Androin 4.4 in Virtualbox it is giving some error. I have also uploaded Speccy CPU configuration which states that virtulization is supported and few pics of...
Hi everyone, this is my 1st post. I've been lurking for a few months for answer to general tech support issues and it seems if anyone can help with this issue they can definitely be found on this forum. So I decided to get a little too confident and tried to fix an issue with bluetooth on my Dell...
Problem with virtualization in Virtualization
I installed Windows 8.1 with hardware virtualization (intel vt-x) disabled. After I installed Windows Phone SDK, I came to know that the emulator needs vt-x enabled. But when I enabled it, the OS is not booting, just showing the initial Windows logo. Can anyone help?
Before they close the door the end of the month, I wasted $40 and got a Windows 8 .iso and key. I want to install it in a virtual system - just to keep up with you guys, In the past I have always used Virtual Box which served me well. But recently I had a lot of problems with the networking in...
Virtu™ GPU Virtualization in Virtualization
Lucidlogix's Green Virtu™ GPU Virtualization worked fine in windows 7 64 bit but is not working Windows 8 64 bit Consumer Preview. Any Idea to fix the issue? :cry::cry:
Solved My Windows 8 Mistake in Installation & Setup
I installed the consumer version of Windows 8, and after playing around with it, I decided to remove it. So I installed Easy BCD and com e to find out Windows 8 did not install on a separate partition. So in other words it is not dual booting. So I might have to clean install my Windows 7. But...
Windows 8 and Virtualization in Windows 8 News
More - Windows 8 and Virtualization | Windows 8 News
Eight Forums Android App Eight Forums IOS App Follow us on Facebook