WSL2 / Hyper-V causes 0xc0000001 boot failure with SVM enabled
Author: Geant200Created Apr 28, 2026Updated Sep 17, 2026
Labelshypervisor-platform
Windows Version
Windows 11 Professionnel 25h2 26200.8246
WSL Version
2.6.3.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
No response
Distro Version
No response
Other Software
VS Code
Environment
| Component | Details |
|---|---|
| OS | Windows 11 Pro 25H2 – Build 26200.8246 |
| Motherboard | Gigabyte X570 AORUS MASTER (Rev. 1.1/1.2) |
| BIOS Version | F39 (AMD AGESA ComboV2 1.2.0.F – Oct 28, 2025) |
| CPU | AMD Ryzen (X570 platform) |
| Boot Drive | NVMe M.2 — GIGABYTE GP-ASM2NE6500GTTD |
| Additional Disks | 7x Samsung SATA SSDs/HDDs (8 disks total) |
| RAM | 128 GB |
| WSL Version Attempted | WSL2 |
| BIOS — SVM Mode | Enabled |
| BIOS — IOMMU | Disabled (also tested Enabled — same result) |
| BIOS — Secure Boot | Disabled |
| BIOS — TPM | Enabled |
Repro Steps
- Fresh install of Windows 11 25H2 (Build 26200.8246) from official Microsoft Media Creation Tool USB
- Connect all 8 storage disks
- Enable SVM Mode in BIOS (AMD Virtualization) and save
- Boot into Windows normally
- Open PowerShell as Administrator and run:
wsl --install - Reboot when prompted
- → System fails to boot
Note: Disabling SVM in BIOS restores normal boot immediately. Re-enabling SVM reproduces the crash every time.
Expected Behavior
Windows 11 should boot normally with both SVM Mode enabled and WSL2 installed, as it did on a previous installation of the same Windows 11 25H2 version (earlier build number) with identical hardware, BIOS version, and installation method.
WSL2 should be functional and Ubuntu should launch correctly for use with VS Code and GitHub Copilot.
Actual Behavior
After running wsl --install (which sets hypervisorlaunchtype Auto in BCD), the system crashes on every boot attempt when SVM is enabled in BIOS.
Boot error screen:
Recovery
Your PC couldn't start properly.
Error code: 0xc0000001
Or:
Your device encountered a problem and couldn't be repaired.
Log file: H:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt
Event Viewer — System Log errors at boot time:
Event ID 42 (Microsoft-Windows-Hyper-V-Hypervisor):
Failed to start the hypervisor;
The virtual machine is not present or not enabled in BIOS.
Event ID 124 (Microsoft-Windows-Kernel-Boot):
Failed to start Virtual Safe Mode (VSM) check for
Enable virtualization-based security policy at step 0.
Hyper-V or VSM not present or not enabled.
Event ID 153 (VBS):
Virtualization-based security (policies: VBS Enabled, VSM Required,
Boot Chain Signer Soft Enforced) is disabled due to the hypervisor
being unavailable.
Event ID 3502 (Microsoft-Windows-DeviceAssociationService):
Device dissociation (unpairing) failed.
Root cause hypothesis:
When hypervisorlaunchtype Auto is active and SVM is enabled, Windows re-enumerates disk controllers via the AMD hypervisor/IOMMU layer. With 8 disks connected on X570, the NVMe boot disk shifts from \Device\Harddisk5 (SVM off) to a different index (SVM on), causing Windows to fail finding its SYSTEM registry hive → 0xc0000001.
SrtTrail.txt shows all diagnostic tests return 0x0 (success) — Windows startup repair finds no errors, yet the system cannot boot.
Diagnostic Logs
1. SrtTrail.txt (Windows Startup Repair Log)
All tests returned 0x0 — startup repair finds no errors yet system fails to boot with SVM active.
Last successful boot: 27/04/2026 00:01:49 (GMT)
Number of repair attempts: 1
Test: OS information check → 0x0 ✓
Test: Build failure information → 0x0 ✓
Test: Disk system test → 0x0 ✓
Test: Disk metadata test → 0x0 ✓
Test: Target OS test → 0x0 ✓
Test: Volume content check → 0x0 ✓
Test: Boot manager diagnostic → 0x0 ✓
Test: System boot log diagnostic → 0x0 ✓
Test: Registry hive check → 0x0 ✓
Test: Windows boot log diagnostic → 0x0 ✓
Test: Error check analysis → 0x0 ✓
Test: Search for installed LCU → 0x0 ✓
Test: Search for installed driver updates → 0x0 ✓
Test: Detect fix via local plugins → 0x0 ✓
Test: Boot status test → 0x0 ✓
Test: Installation status check → 0x0 ✓
Test: Start network for cloud remediation → 0x0 ✓
Test: Detect fix via cloud plugins → 0x0 ✓
2. BCD Configuration (bcdedit /enum all)
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
timeout 1
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale fr-FR
default {current}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale fr-FR
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
3. Disk Configuration (Get-Partition)
DiskNumber PartitionNumber Type Size DriveLetter UniqueId
---------- --------------- ---- ---- ----------- --------
5 1 System 209715200 eui.6479A72452072020 ← EFI (boot)
5 2 Reserved 16777216 eui.6479A72452072020
5 3 Basic 499033047040 C: eui.6479A72452072020 ← Windows
5 4 Recovery 846200832 eui.6479A72452072020
4 1 Reserved 16759808 5000C500877CCB64
4 2 Basic 1000186314752 H: 5000C500877CCB64
0 1 Reserved 16759808 500253C840604EF8
0 2 Basic 1024191365120 D: 500253C840604EF8
1 1 Reserved 16759808 500253F843324E7A
1 2 Basic 2000381018112 E: 500253F843324E7A
2 1 Reserved 16759808 500253C840604F32
2 2 Basic 1024191365120 F: 500253C840604F32
3 1 Reserved 16759808 500253F892313A73
3 2 Basic 1000186314752 G: 500253F892313A73
7 1 Basic 33488896 600224803426183AAFEC9E61EC7A093A
Key finding: Windows boot disk is
Disk 5(NVMe,eui.6479A72452072020). When SVM activates, disk enumeration changes and Windows can no longer locate its SYSTEM hive →0xc0000001.
4. Disk Drivers (Get-WmiObject Win32_DiskDrive)
Model InterfaceType PNPDeviceID
----- ------------- -----------
GIGABYTE GP-ASM2NE6500GTTD SCSI SCSI\DISK&VEN_NVME&PROD_GIGABYTE_GP-ASM2\7&1663A440&0&000000
Samsung SSD 850 PRO 1TB IDE SCSI\DISK&VEN_SAMSUNG&PROD_SSD_850_PRO_1TB\7&12CB7DE7&0&020000
Samsung SSD 850 PRO 1TB IDE SCSI\DISK&VEN_SAMSUNG&PROD_SSD_850_PRO_1TB\7&12E1550D9&0&030000
Samsung SSD 870 EVO 2TB IDE SCSI\DISK&VEN_SAMSUNG&PROD_SSD_870_EVO_2TB\7&12CB7DE7&0&030000
Samsung SSD 870 QVO 1TB IDE SCSI\DISK&VEN_SAMSUNG&PROD_SSD_870_QVO_1TB\7&2E1550D9&0&010000
ST1000DX001-1NS162 IDE SCSI\DISK&VEN_&PROD_ST1000DX001-1NS1\7&2E1550D9&0&040000
Microsoft Virtual Disk SCSI SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\2&1F4ADFFE&0&000001
Brother DCP-J752DW USB Device USB USBSTOR\DISK&VEN_BROTHER&...
5. Event Viewer — Full System Log (boot crash at 27/04/2026 ~19:45)
TimeCreated Id Level Message
------------ -- ----- -------
2026-04-27 19:45:28 42 Error Failed to start the hypervisor;
The virtual machine is not present or not enabled in BIOS.
2026-04-27 19:45:28 124 Error Failed to start Virtual Safe Mode (VSM) check for
Enable virtualization-based security policy at step 0.
Hyper-V or VSM not present or not enabled.
2026-04-27 19:45:28 153 Information Virtualization-based security
(policies: VBS Enabled, VSM Required,
Boot Chain Signer Soft Enforced)
is disabled due to the hypervisor being unavailable.
2026-04-27 19:45:47 3502 Error Device dissociation (unpairing) failed.
Source: Microsoft-Windows-DeviceAssociationService
2026-04-27 19:45:33 219 Warning Driver \Driver\WUDFRd failed to load.
Device: ROOT\DISPLAY\0000
Status: 0xC0000365
Full VBS/VSM state at boot:
VBS policies: VBS Enabled, VSM Required, Boot Chain Signer Soft Enforced
VBS status: DISABLED — hypervisor unavailable
Credential Guard: NOT active (auto-activation requirements not met)
LSASS: Started as protected process level 4
6. Windows Features Status
# Enabled (confirmed via DISM):
Microsoft-Windows-Subsystem-Linux : Enabled
VirtualMachinePlatform : Enabled
HypervisorPlatform : Enabled
7. Registry — DeviceGuard / VBS (all attempts to disable)
HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard
EnableVirtualizationBasedSecurity = 0
RequirePlatformSecurityFeatures = 0
HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HyperGuard
Enabled = 0
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
LsaCfgFlags = 0
Note: Disabling all VBS/DeviceGuard registry keys had no effect on the boot failure.
8. WSL Install Error (with hypervisorlaunchtype Off)
PS C:\Windows\System32> wsl --install -d Ubuntu
Downloading: Ubuntu
Installing: Ubuntu
WSL2 is not supported with your current machine configuration.
Please enable the "Virtual Machine Platform" optional component
and ensure virtualization is enabled in the BIOS.
Enable "Virtual Machine Platform" by running:
wsl.exe --install --no-distribution
Error: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
What Was Tried (All Failed)
| Action | Result |
|---|---|
bcdedit /set hypervisorlaunchtype Auto |
Boot crash with SVM |
bcdedit /set hypervisorlaunchtype Off |
Windows boots but WSL2 fails: HCS_E_HYPERV_NOT_INSTALLED |
Disable VBS via registry (EnableVirtualizationBasedSecurity=0, RequirePlatformSecurityFeatures=0, LsaCfgFlags=0, HyperGuard Enabled=0) |
No change |
| Disable IOMMU in BIOS | No change |
| Enable IOMMU in BIOS | No change |
| Install latest AMD Chipset drivers (AGESA 1.2.0.F) | No change |
Rebuild BCD with bcdboot from WinRE |
No change |
sfc /scannow + DISM /Image /Cleanup-Image /RestoreHealth |
No corruption found |
| Disconnect all disks except NVMe → reinstall Windows with SVM active → reconnect disks | Worked until wsl --install was run again |
wsl --install --no-distribution + wsl --set-default-version 2 |
WSL2 still fails (HCS_E_HYPERV_NOT_INSTALLED) |
dism /enable-feature VirtualMachinePlatform + HypervisorPlatform + WSL |
No change |
WSL1 (wsl --set-default-version 1) |
Works but WSL2 is required |
Additional Context
- This exact configuration worked on a previous Windows 11 25H2 installation (earlier build number)
- Same hardware, same BIOS F39, same installation method (official Media Creation Tool)
- Memory Integrity (HVCI) is disabled
- No Storage Spaces configured (only Primordial pool)
- Intended use case: VS Code + WSL2 Ubuntu + GitHub Copilot
- WSL1 works as a temporary workaround but WSL2 is required
Questions
- Is this a known regression introduced between earlier 25H2 builds and Build 26200.8246?
- Is there a workaround to use WSL2 without
hypervisorlaunchtype Autocausing boot failure on AMD X570 with 8 disks? - Is a fix planned for this scenario: AMD X570 + multiple SATA disks + NVMe boot drive + Windows 11 25H2 Build 26200.8246 + WSL2?
Reported after extensive troubleshooting — April 27, 2026
Source: microsoft/WSL