Results 1 to 7 of 7
  1. #1
    ROG Member Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    7

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

    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

  2. #2
    ROG Member Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    7

    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?

  3. #3
    New ROGer Array
    Join Date
    Aug 2019
    Reputation
    10
    Posts
    2

    Quote Originally Posted by sfsccn View Post
    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!

  4. #4
    ROG Member Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    7

    Quote Originally Posted by JerhardoMX View Post
    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.

  5. #5
    New ROGer Array
    Join Date
    Aug 2019
    Reputation
    10
    Posts
    2

    Quote Originally Posted by sfsccn View Post
    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.

  6. #6
    New ROGer Array
    Join Date
    Sep 2019
    Reputation
    10
    Posts
    1

    Quote Originally Posted by sfsccn View Post
    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.

  7. #7
    New ROGer Array
    Join Date
    Sep 2019
    Reputation
    10
    Posts
    1

    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.

    *

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •