©ASUSTEK COMPUTER INC. ALL RIGHTS RESERVED.

sfsccn · ‎08-09-2019

After upgrading my BIOS from 1301 to 1902 Hyper-V no longer works. If I try to start a VM I get the message "[VM] could not be started because the hypervisor is not running". I also see this message in the event viewer: "Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus 0x19, sub-status 0x2)."

Virtualization (VMX) is enabled in the BIOS, and the CPU section of the Windows Task Manager confirms this. I tried the suggestions here but the problem persists. I wanted to try reverting to 1301 but I had trouble doing this, see this post.

Any suggestions? In particular, any suggestions on trying a different BIOS version, like 1401, 1503 or 1704?

Thanks!

OS: Windows 10 Pro 1809 Build 17763.615

sfsccn · ‎08-09-2019

Update: I restored my disk to a time when I know Hyper-V worked. However, it still failed to work with BIOS 1902. So it was definitely the BIOS. I was, however, finally able to revert to 1301 (see this post). And now it works. So I'm good.

Too bad 1902 breaks Hyper-V, I wonder why?

JerhardoMX · ‎08-12-2019

sfsccn wrote:
After upgrading my BIOS from 1301 to 1902 Hyper-V no longer works. If I try to start a VM I get the message "[VM] could not be started because the hypervisor is not running". I also see this message in the event viewer: "Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus 0x19, sub-status 0x2)."

Virtualization (VMX) is enabled in the BIOS, and the CPU section of the Windows Task Manager confirms this. I tried the suggestions here but the problem persists. I wanted to try reverting to 1301 but I had trouble doing this, see this post.

Any suggestions? In particular, any suggestions on trying a different BIOS version, like 1401, 1503 or 1704?

Thanks!

OS: Windows 10 Pro 1809 Build 17763.615

Hi friend, i have the same problem, with my ASUS-TUF-X299-MARK1 updating to 1902 Hyper-V stop working. i'm really worried because i think that i couldn't downgrading my BIOS to 1301 because my processor is 9980XE. I read on blog the error is because "firmware or hardware issues, contact vendor system".

Asus Help Us!

sfsccn · ‎08-12-2019

JerhardoMX wrote:
Hi friend, i have the same problem, with my ASUS-TUF-X299-MARK1 updating to 1902 Hyper-V stop working. i'm really worried because i think that i couldn't downgrading my BIOS to 1301 because my processor is 9980XE. I read on blog the error is because "firmware or hardware issues, contact vendor system".

Asus Help Us!

Hi JerhardoMX, just wanted to make sure you saw above (8/10 post) that I was able to to downgrade to 1301 using Flashback. But, as you suggest, it may not work with your processor. Mine is a Core i7 7820X.

JerhardoMX · ‎08-12-2019

sfsccn wrote:
Hi JerhardoMX, just wanted to make sure you saw above (8/10 post) that I was able to to downgrade to 1301 using Flashback. But, as you suggest, it may not work with your processor. Mine is a Core i7 7820X.

Hi again, i just to downgrade to 1301 and Hyper-V works!, the processor did not have any compatibility errors.

So, i hope ASUS could resolve the bug with its 1902 BIOS and Hyper-V Broken.

jafin · ‎09-04-2019

sfsccn wrote:
After upgrading my BIOS from 1301 to 1902 Hyper-V no longer works.

Hyper-V broke here as well on a PRIME X299-A, reverting back to BIOS 1503 corrected the flaw. Hopefully someone at ASUS can fix a new release.

Aquamo · ‎09-15-2019

I had the same problem on my Prime X299-A *and BIOS 1902; downgrading the BIOS to 1704 fixed the problem for me.

Oddly, Virtualization was showing available in both windows and the BIOS but WSL2 and Sandbox on Windows 10 stopped working after I had upgraded to 1902. *

Thanks for posting this issue as I was going to blame it on my Windows install and go through a wipe/re-install.

*

daystrom_hrmgam · ‎09-19-2019

I've got a Rampage VI Extreme, and like the other x299 boards when updated to 1902 it looses the ability to run Hyper-V and VMware Workstation (tried on separate installs). Annoyingly I can't downgrade my BIOS as this is the first revision I've had that is stable with my RAM kits (at anything other than 2133Mhz)! Seriously, it's taken me two years to get a stable system and now I can't run my dev VMs :mad:

Is there somewhere I should be submitting a bug report to? I spent the better part of a day combing logs and playing trial and error games.

Thanks
HRMGamer

EDIT (adding system info):
Note: This is a stable and cool configuration based on testing. This problem also exists with components at stock clocks.

- UEFI Version: 1902
- CPU: 7980xe (4200Mhz average across cores, stable on 24hr runs of P95 non-AVX/AVX, y-cruncher, realbench, ADIA64 Cache Test)
- Memory kit part number (s) and amount in GB: 128GB 3600Mhz C17 Corsair Dominator Platinum RGB (2x CMT64GX4M4K3600C18). Passes both GSAT and HCI Memtest (30hr runs)
- GPU: 2x EVGA 1080Ti Founders with EK Waterblocks (2050Mhz/5900Mhz, stable on 12hr runs of 3DMark 2017 TimeSpy Extreme)
- SSD/HDDs/Optical drives: Samsung 960 Pro 2TB, Seagate Seagate Barracuda Pro 8TB
- PSU: Corsair AX1500i
- USB Devices (model/version number):
--- Cambridge Audio Azur 851D
--- Corsair 1000D, Commander Pro, 2x Node Pro
--- Flirc USB IR controller
--- Logitech G710+ keyboard
--- Logitech G903 mouse via powerplay mousemat
--- NaturalPoint Track IR 5
--- NZXT Internal USB Hub
Monitor:
--- Acer X34P
--- Dell 2713h
CPU Cooler: Custom EK waterloop
PC CASE: Corsair 1000D
Operating system: Windows 10 Enterprise LTSC (1809, build 17763.737). Activated.
Drivers Installed (include version):
--- Asus - R6E Driver - Aquantia 10GbE - Win7-10 - v1.40.42.0_20170807
--- Asus - R6E Driver - Bluetooth - Win10 - v21.30.0.5_20190801R
--- Asus - R6E Driver - Intel Chipset - Win10 - v10.1.1.45_20190402R
--- Asus - R6E Driver - Intel Management Engine Interface (IMEI) - Win10 - v1909.12.0.1236_via Intel
--- Asus - R6E Driver - Intel Turbo Boost Max Technology 3.0 Driver (ITBM) - Win7-10_64 - v1.1.0.1005_20190401R
--- Asus - R6E Driver - Realtek Audio Driver - Win7-10 - v6.0.1.8339_20180214R
--- Asus - R6E Driver - Wi-Fi 1 (Intel) - Win10 - v21.30.3.2_20190801R
--- Asus - R6E Driver - Wi-Fi 2 (Qualcomm) - Win7-10 - v1.1.5.89_20170807
--- Cambridge Audio - USB2.0 driver - Win32 - v4.47.0
--- Corsair iCUE - Win32 - Setup - v3.18.77
--- Flirc - Win32 - v3.22.4
--- Logitech Gaming Software - Win64 - v9.02.65
--- nVidia - Desktop - Win10-64 - v436.02-whql
--- TrackIR - Driver - Win32 - v5.4.2
Any third Party temp/voltage software installed:
--- MSI Afterburner v4.6.1
--- Complete SOE, e.g. Office, 7Zip, etc...
System Overclocked (provide details)? See above. But occurs on stock clocks. Contact me for more details

Aquamo · ‎10-12-2019

I noticed that a new version of the BIOS is available for Prime X299-A , version 2002 (2019/10/04).

The short ChangeLog just says:

*PRIME X299-A BIOS 2002
* 1.Add support for Intel® Core™ X-Series 10000 Processor Family
* 2.Improve system performance and stability.*

No mention of fixing virtualization support in the CPUs. * Does anyone know if ASUS monitors these forums and how to open a ticket to see if we can get virtualization fixed on the X299 boards?

Has anyone tried the version 2002 BIOS, does it fix the issue?

I will give it a try later but if you already tried and failed let me know before I go through the process 🙂

*

RoundRobin · ‎10-25-2019

Hyper-V was broken on my WS X299 SAGE with firmware 1902. With 2002 it works again.

Hyper-V Broken in BIOS 1902 for PRIME X299-DELUXE