Hardware virtualization BLOCKED - BIOS mistake by Dell ???

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?

There are many types of Virtualization and not all cpus or chipsets support them.  Trusted Execution is not the same as NX or Execute Disable bit.  Sounds like you improperly downgraded bios.

A11 is the current Bios.

http://downloads.dell.com/FOLDER01086746M/1/O7010A11.exe

Due to compatibility of features, and ensuring platform stability, the only way to properly downgrade is to reset all the settings in the machine to a default factory state as if it had been shipped with a Pre-Win8 Released BIOS; specifically including defaulting the boot mode to Legacy (not UEFI), removing all passwords, and defaulting all user selectable settings. The following is retained on the machine (all other settings are reset): Windows Keys (if present), Service Tag, Asset Tag, Ownership Tag, Manufacturing Date, Ownership Date, and Express Service Code.
Downgrading is blocked if either Secure Boot is on or if Computrace has been activated.

VT-x is not the same as VT-d and is based on chipset and processor and not related to being dell's issue in any way.  Intel also stopped allowing developers the ability to change these features via registry because hackers were using this to write malware.  I suggest checking if you are HAV or HAV NOT.

http://www.microsoft.com/en-us/download/details.aspx?id=592

 Windows Virtual PC requires processors capable of hardware-assisted virtualization with AMD-V™, Intel® VT or VIA® VT

The HAV detection tool helps you check if the computer processor supports hardware virtualization. The tool also checks if this feature is enabled on the processor.

Speed - whoa, boy - slow down a bit.

Per my post above, my Opti 7010 has BIOS A16  (It came that way.)  There are newer BIOSes A18 and A19 but I don't want to bother with them unless someone knows they are the answer..

Also, the Dell spec sheet on the 7010 says this about its BIOS (which is how I found it):

Virtualization Support
  Virtualization: Enable
  VT for Direct I/O: Enable
  Trusted Direct I/O Disable

Other Dell material on the 7010 says it has "desktop virtualization".

And the Intel material on my CPU (and its processor ID app) very clearly says it supports virtualization.

So yes I think Dell owes me an answer to this issue.

So far the problem isn't that I might have a VT-x and not a VT-d (or vice versa).  The problem is that all hardware virtualization is blocked somehow.

Come on speed, you're one of the most knowledgeable folks here - slow down to sub-Flash levels and let's have of your more focused wisdom.

Thanks.

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?

Why oh why does hardware virtualization not work?  Where did I go wrong?  Why me, why me?

You cannot run virtual machines in shell after shell after shell.  Virtuals need a bare metal host.

If you are wanting XP mode you must install XP into HyperV.  You cannot run WIN7 pro virtually under windows 8 and then run xp under that like a matruska doll.

ejn63 and Speed -

Apologies - I have confused the issue. My Optiplex 7010 happens to be a dual-boot machine.

I only intend to run XP Mode when I'm in Win 7 Pro 64-bit.  I have NO intention to do it when I'm in Win 8.  But XP Mode runs much better under hardware virtualization - Speed I think that's what you mean by bare metal - and my Optiplex 7010 is blocking hardware virtualization.

I mentioned my surprise discovery of the lines referring to Hyper-V only because it might be a clue as to why my machine rejects hardware virtualization.

Anyway, I just compared the listings in msinfo32 in each of Win 7 and Win 8.
The four lines for Hyper-V appear ONLY in Win 8.
► There is NO MENTION of Hyper-V in Win 7. 
Also, in either OS, there are no task manager process lines for Hyper-V - it isn't actually running.
So maybe it's a red herring - a distraction in the true plot of this murder mystery:  "Who killed Hardware Virtualization?"

Bottom line: I think my machine should have hardware virtualization regardless which OS I've booted into.  But my start focus is on using it when I'm in Win 7.   Any ideas?

Thanks, guys.  My wife says "When you're fussing with the computer, you aspire to be a geek, but you're only a nerd."

ejn63 and speed - Really weird news -

I downloaded and ran the MS Hardware-Assisted Virtualization Detection Tool in my Win 8 OS on the same PC and it reports "This computer is configured with hardware-assisted virtualization" !!!

So - why do I get a negative result when I'm in Win 7 on the same PC ???

Even weirder - when I first tried to run havdetectiontool.exe in Win 8, it would not run and gave me an error message that it could only run on Win 7.  So in Properties, I set its compatibility to Win 7 and set the program to run as an administrator and it gave me the good news above while I was still in Win 8.

What is going on??  Could it be I have different drivers for the chipset on Win 7 ??

Hyper=V is WIN8 only. XP Mode is virtualization on win7.

You CANNOT however run win7 and win8 on the same drive.

You would need 2 drives. Physically swapped out. Your system works with and supports virtualization.  DUAL BOOT Same partition Same Drive is not supported and causes driver contamination.

Speed - you are great but you need to slow down 15%, man.  I love you and I know you know the answer, but you are going too fast to pick up the details.

On my Optiplex 7010, there are THREE partitions in the hard drive.  THREE.

The smallest one is EFI System Partition
The next one is Windows 7 Pro 64-bit (C:)
The next one is Windows 8 Pro 64-bit (F:)

I am NOT running Win 7 and 8 in the same partition.  They are in DIFFERENT partitions.  Dual-boot DIFFERENT partitions on one drive is usually OK and usually how it's done, right?

I KNOW that Hyper-V is for Win 8 and that XP Mode is for Win 7.  Hey - believe me brother - I KNOW already.

We still have the question and I know you know the answer:

WHY DOES THE HAVDETECTION TOOL SHOW HARDWARE VIRTUALIZATION NOT ENABLED ON WIN 7 AND YES ENABLED ON WIN 8?  Same PC, same BIOS.

Speed - your chance to shine!!!  Show us how good you are.

While in Win 8, I just re-ran the verbose log version of havdetectiontool.exe.  The results are below.  Note the line
VmxProcessor IA32_FEATURE_CONTROL MSR value = 0x000005
That's different from the same line when I'm in Win 7, in the first post above.

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

Here's the full report - please compare it to the report at the top above when I'm in Win 7 and it doesn't work:
______________________

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

► What else is different from the first report above?  What has to be changed in Win 7 to make it work?

In a side discussion, Dell Rockstar RoHe (Ron) wonders whether my initial install of Win 7 Pro 64-bit might be a cause of this.

It's a good question, but I don't see how.

I have a Dell Win 7 Pro 64-bit SP1 Reinstallation disk and I ran it on a new, blank hard drive.  This left me with two partitions:  EFI System and C:\ Windows 7.

Then I ran the Dell Utilities disk do install drivers for many of the basic Device Manager entries.  And then came a gazillion Windows Updates, Avast anti-virus and other utility programs.

About a week afterwards, I reduced the size of the C:\ partition and installed Window 8 Pro 64-bit in the unallocated space.  The PC is definitely working as a dual-boot PC.

Well, RoHe may still be right.  if I can't figure this out, I might just start all over again.  I'll wipe the hard drive and reinstall Win 7.  This time, however, I'll again make it UEFI but with Enable Legacy ROMs off.  (We'll see if it installs that way.)

But do we really think that will make a difference?

You cannot have both on the same drive.

Separate partitions is not equal to allowed.

Request denied.

If you clean install on different physical drives not installed at the same time it works fine.

Speed - do you think if I started over and installed Win 7 Pro 64-bit only on a blank hard drive, I would have hardware virtualization?

I think - from what I've read - that I still want my BIOS to be in UEFI mode.  Secure Boot has to be off. 

But would it make a difference whether I re-installed with Enable Legacy ROMs ON or OFF?

Reminder this is all about hardware-assisted virtualization working with Win 7.  Right now, that's my only goal.

Thanks.

Use microsoft security essentials.  

Get Microsoft Security Essentials for the low, low price of free

http://www.microsoft.com/security