Unable to start guest OS in Hyper-V on Server 2012 R2

Question

I get the following error trying to start any guest OS in Hyper-V Manager:
"An error occurred while attempting to start the selected virtual machine(s)::
'TestVM' failed to start.
Virtual Machine 'TestVM' could not be started because the hypervisor is not running.
'TestVM' failed to start. (Virtual machine ID xxxxxxxxxxxx)
Virtual machine 'TestVM' could not be started because the hypervisor is not running (Virtual machine ID xxxxxxxxxxxx).
The following actions may help you resolve the problem:
1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then
turn it back on. Resetting the physical computer is not sufficient.)
2) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically."
Host (Physical) Hardware: 
- Supermicro X9SRL-F, BIOS Rev 3.0a (current) with Intel Virtualization enabled and Execute Disable Bit enabled
supermicro.com/products/motherboard/Xeon/C600/X9SRL-F.cfm
- Intel Xeon E5-2620 CPU 
http://ark.intel.com/products/64594/Intel-Xeon-Processor-E5-2620-15M-Cache-2_00-GHz-7_20-GTs-Intel-QPI
- 96GB ECC DDR3 RAM
Host Software: 
- Server 2012 R2 DataCentre with update 1 (clean install)
- Hyper-V role installed
All hardware supports virtualization and was previously running VMWare VSphere 5.5 without problem.
The BIOS settings for Intel Virtualization and Execute Disable Bit are both enabled.
The server has been physically shutdown and powered off numerous times, but still doesn't work.
I've read Ben Armstrong's notes on setting the Hypervisor Launch type in BCDEdit
Here's the current Boot Configuration Data
Windows Boot Manager
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume8
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
bootshutdowndisabled    Yes
default                 {current}
resumeobject            {06bff081-9477-11e4-ab74-9faf6fe9d444}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30
Windows Boot Loader
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows Server 2012 R2
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {06bff083-9477-11e4-ab74-9faf6fe9d444}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {06bff081-9477-11e4-ab74-9faf6fe9d444}
nx                      OptOut
hypervisorlaunchtype    Auto
Here's my System Info:
OS Name Microsoft Windows Server 2012 R2 Datacenter
Version 6.3.9600 Build 9600
Other OS Description  Not Available
OS Manufacturer Microsoft Corporation
System Name HYPER1
System Manufacturer Supermicro
System Model X9SRL-F
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz, 2001 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3.0a, 5/12/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Supermicro
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Workstation
Secure Boot State Unsupported
PCR7 Configuration Not Available
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume8
Locale Australia
Hardware Abstraction Layer Version = "6.3.9600.17196"
User Name Not Available
Time Zone AUS Eastern Daylight Time
Installed Physical Memory (RAM) 96.0 GB
Total Physical Memory 96.0 GB
Available Physical Memory 93.0 GB
Total Virtual Memory 110 GB
Available Virtual Memory 107 GB
Page File Space 14.0 GB
Page File C:\pagefile.sys
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 Protection
Yes
I do have the following two errors in the Hyper-V server role event log that occur at system startup, but can't find any info on it:
Log Name:      System
Source:        Microsoft-Windows-Hyper-V-Hypervisor
Date:          12/01/2015 3:35:37 PM
Event ID:      63
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      HYPER1
Description:
Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase 0x5), and was not started.  This initialization failure may be the result of a platform configuration or firmware issue.  Contact your system vendor for more
information or updated firmware.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52FC89F8-995E-434C-A91E-199986449890}" />
    <EventID>63</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-01-12T04:35:37.814579300Z" />
    <EventRecordID>3955</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>HYPER1</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="Phase">0x5</Data>
  </EventData>
</Event>
Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          13/01/2015 11:21:23 AM
Event ID:      15350
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      HYPER1
Description:
The virtualization infrastructure driver (VID) is not running.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>15350</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-01-13T00:21:23.250980100Z" />
    <EventRecordID>181</EventRecordID>
    <Correlation />
    <Execution ProcessID="1512" ThreadID="1576" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>HYPER1</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
    </VmlEventLog>
  </UserData>
</Event>
I've also read a number of other threads that haven't assisted including:
 - https://social.technet.microsoft.com/Forums/en-US/396c882f-2cc8-4bc8-804d-eec75c0b8066/virtual-machine-could-not-be-started-because-the-hypervisor-is-not-running
 - https://social.technet.microsoft.com/Forums/windowsserver/en-US/85b323a8-9233-49b9-bc38-e28e7a4222c6/server-2008-hypervisor
There is no event ID 3112 in the event log, so this MS KB article (2490458) is not relevant
Following pics attached show BIOS settings for CPU and Virtualization / Execute Bit Disable settings:

Answer 1

I recently ran into this.  The person had made a modification to the System Properties of the Windows operating system.
System Properties > Advanced > Performance > Settings ...
On the Performance Options window, select the Data Execution Prevention tab. Ensure Turn on DEP for all programs and services except those I select is the option selected.  He had the other option selected.  The only way to get it to get it working
was to change the setting, uninstall Hyper-V, reboot, install Hyper-V, reboot.
. : | : . : | : . tim