Intel Motherboards - x299 Taichi and Intel Virtualization (VT-x)

Print Page | Close Window

x299 Taichi and Intel Virtualization (VT-x)

Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6330
Printed Date: 29 Jul 2025 at 11:17pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: x299 Taichi and Intel Virtualization (VT-x)

Posted By: iconoclast
Subject: x299 Taichi and Intel Virtualization (VT-x)
Date Posted: 14 Oct 2017 at 9:34am

I just bought an x299 Taichi board and fitted it with an i9 7940x, which according to the datasheet supports both VT-x and VT-d.

"Intel Virtualization Technology" and "VT-d" are both enabled in the UEFI, I use 64-bit Windows 10 Pro but systeminfo.exe reports the following under "Hyper-V Requirements":

- VM Monitor Mode Extensions: Yes

- Virtualization Enabled in Firmware: No

- Second Level Address Translation: Yes

- Data Execution Prevention Enabled: Yes

Fast Boot is disabled (I've read that enabling that can mess with virtualization).

I am using UEFI v1.40. I see there's a newer version (v1.60), but want to make sure there's absolutely nothing else I can do before that.

Replies:

Posted By: wardog
Date Posted: 14 Oct 2017 at 10:35am

" rel="nofollow - Is this with another Hypervisor installed that you see this?

If you have VMware or the like installed, disable MS's Hyper-V. Only one hypervisor is allowed.

How do I disable Hyper V?

Hit the Windows Key and type "windows features"
Hit the Windows Key + W combo to bring up the Windows Settings panel of the Start Screen.
Click on Turn Windows features on or off.
When the Turn Windows features on or off dialog appears, look for Hyper-V and deselect it.
Click OK.
Restart your computer when prompted.

hth

Posted By: iconoclast
Date Posted: 14 Oct 2017 at 11:19am

No, this is on a clean installation of Windows. I am not even allowed to install the Hyper-V feature (the only hypervisor I'm planning on running) because of this.

Posted By: iconoclast
Date Posted: 15 Oct 2017 at 2:51am

I am happy to report that upgrading the UEFI to v1.60 resolved the issue.