Windows Version

Microsoft Windows [Version 10.0.26200.9457]

WSL Version

3.0.1.0

Are you using WSL 1, WSL 2, or WSLC?

• WSL 2
• WSL 1
• WSLC

Kernel Version

6.18.40.1-1

Distro Version

Not installed (Windows fails to boot with Hyper-V enabled before any WSL distribution can be launched).

Other Software

今回の問題は、Linuxディストリビューションを起動したときのエラーではありません。

Windows Hypervisorを有効にしただけで、Windowsそのものが起動できなくなる問題です。

そのため、WSLのカーネルバージョンはインストール済みコンポーネントの情報として記載しますが、Linuxカーネルが実際に起動したことを意味しません。

Repro Steps

1. On Windows 11 build 26200.9457, create a separate Windows Boot Manager entry pointing to the same Windows installation.
2. Keep the normal entry configured with hypervisorlaunchtype Off.
3. Configure the test entry with hypervisorlaunchtype Auto.
4. Restart the computer and select the test entry.
5. Observe that Windows fails during startup, the system restarts, and the boot selection screen reappears.
6. Select the normal Windows entry. Windows boots successfully.

Expected Behavior

Windows 11 should boot normally when hypervisorlaunchtype is set to Auto on an AMD Ryzen 9 9950X3D system with SVM enabled in firmware.

After Windows starts successfully, WSL2 and Docker Desktop should be able to use hardware virtualization without requiring hypervisorlaunchtype Off.

Actual Behavior

When hypervisorlaunchtype is set to Auto, Windows 11 fails during startup.

The Windows boot logo appears, then the display goes black and the computer restarts. The ASUS firmware logo appears again, followed by the Windows Boot Manager selection screen.

Selecting the normal Windows 11 entry with hypervisorlaunchtype Off allows Windows to boot successfully.

System configuration:

• CPU: AMD Ryzen 9 9950X3D
• Motherboard: ASUS TUF GAMING X870E-PLUS WIFI7
• BIOS: 2503
• Windows: 11, build 26200.9457
• RAM: 64 GB DDR5-5600
• WSL version: 3.0.1.0
• WSL kernel package version: 6.18.40.1-1

Troubleshooting already performed:

• AMD SVM virtualization is enabled.
• SLAT and virtualization extensions are supported.
• Virtual Machine Platform is enabled.
• No relevant WHEA hardware errors were found.
• No BugCheck event or new crash dump was recorded.
• Hyper-V Hypervisor Admin and Operational logs contain no relevant entries.
• Windows Startup Repair did not identify a root cause.
• Boot logging was enabled for the test boot entry, but C:\Windows\ntbtlog.txt was not generated.
• AMD Ryzen Master and its V30 driver were uninstalled, but the issue persisted.

Both boot entries reference the same Windows installation. Only the Hypervisor launch configuration differs in the tested setup.

No Linux distribution is installed yet because Windows itself cannot boot with the Hypervisor enabled.

The issue occurs before WSL2 or Docker Desktop can be launched.

Diagnostic Logs

No crash dump or WSL diagnostic trace is available because Windows fails during early boot, before WSL can be launched.

The System event log reports a previous unsuccessful boot, but no actionable BugCheck code was captured.

Hyper-V Hypervisor Admin and Operational logs were enabled but contained no events.

Boot logging was enabled using bcdedit /set <test-entry-guid> bootlog Yes, but C:\Windows\ntbtlog.txt was not created after reproducing the failure.

Boot logging has since been disabled. The normal Windows boot entry remains functional with hypervisorlaunchtype Off.

I can provide sanitized BCD output, System event log excerpts, and additional diagnostic information upon request.