Windows Hypervisor / WSL2 causes black screen on ASUS FX505DT Ryzen 7 3750H, Safe Mode works

[HAOTIANGUO22]

Windows Hypervisor causes black screen on ASUS FX505DT when SVM is enabled, but Safe Mode works

Summary

I am trying to enable WSL2 / Windows Hypervisor on an ASUS TUF Gaming FX505DT laptop.
BIOS SVM can be enabled, but when Windows boots with hypervisorlaunchtype Auto, the system shows the Windows boot logo/spinner briefly and then goes to a black screen. Fan speed increases, and the system never reaches the login screen.

If I boot with hypervisorlaunchtype Off, Windows starts normally.
Interestingly, Hypervisor Auto + Safe Mode can boot successfully.

Hardware

• Model: ASUS TUF Gaming FX505DT / FX95DT
• CPU: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx
• iGPU: AMD Radeon RX Vega 10 Graphics
• dGPU: NVIDIA GeForce GTX 1650
• BIOS: American Megatrends Inc. FX505DT.316, 2021-01-28
• BIOS mode: UEFI
• SVM Mode: Enabled during failed tests

OS

• Windows 11 Education
• Version: 25H2
• Build: 26200.8737
• Architecture: x64

Note: Some registry fields still show Windows 10 Education, but Get-ComputerInfo reports Microsoft Windows 11 教育版, 25H2, build 26200.

Main Symptom

With SVM enabled and:

bcdedit /set hypervisorlaunchtype Auto
bcdedit /set vsmlaunchtype Off

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[HAOTIANGUO22]

Logs attached.

Important note: the main failure happens during boot when hypervisorlaunchtype is set to Auto. The machine reaches the Windows logo/spinner, then the screen goes black before login, so I cannot collect logs from the failed Hypervisor-enabled desktop session.

These logs were collected from the recoverable Hypervisor Off boot entry. On the same machine:

• hypervisorlaunchtype Off boots normally.
• hypervisorlaunchtype Auto black-screens before login.
• Hypervisor-enabled Safe Mode can boot.
• WSL and VirtualMachinePlatform are enabled.
• Full Hyper-V is disabled.
• VBS / Core Isolation / Memory Integrity were disabled during testing.

WslLogs-2026-06-28_11-37-32.tar.gz

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Appx package is not installed
Found no WSL traces in the logs

[HAOTIANGUO22]

I collected a new log package while WSL commands were running.

During the trace collection, I ran:

• wsl --version
• wsl --status
• wsl -l -v
• wsl --list --online
• wsl --shutdown

Please note that no Linux distribution is installed yet. The main issue is still that Hypervisor-enabled normal boot black-screens before login, so I cannot collect logs from the failed boot itself.

WslLogs-2026-06-28_12-05-04.tar.gz

[github-actions]

Diagnostic information

Appx package is not installed
Detected user visible error: Wsl/WSL_E_DEFAULT_DISTRO_NOT_FOUND

[chemwolf6922]

Hi @HAOTIANGUO22 , According to this discussion #4784 (comment). This seems to be an issue with ASUS BIOS settings.
Please follow the instructions provided in the link and set the UMA size to Auto.

[OneBlue]

/bsod

[microsoft-github-policy-service]

Hello! Could you please provide a kernel dump to help us better diagnose your issue? To collect a kernel dump, follow 10) Reporting a Windows crash (BSOD)
Thank you!