Share via

Windows 11 enters Automatic Repair after enabling WSL when AMD SVM is enabled

Y an 0 Reputation points
2026-05-12T12:47:14.9766667+00:00

Environment: Device: Lenovo Yoga Air 14s 【please fill in the exact model】 CPU: AMD Ryzen 7 7840S Windows edition: Windows 11 【Home / Pro】 Windows version/build: 10.0.26200.8246 BIOS version: M6CN37WW 【please confirm】 BIOS virtualization option: AMD SVM / AMD-V File system: NTFS 【remove this line if not confirmed】

Related components:

  • Windows Subsystem for Linux
  • VirtualMachinePlatform
  • Windows Hypervisor
  • Docker Desktop with WSL2 backend
  • Ubuntu on WSL

Problem description: After enabling WSL or VirtualMachinePlatform, Windows 11 fails to boot on the next restart if AMD SVM / AMD-V virtualization is enabled in BIOS.

The system may show a black screen, get stuck during Windows feature configuration, or enter Windows Automatic Repair. Automatic Repair cannot fix the issue. Uninstalling updates and System Restore also fail.

However, if I enter BIOS and disable AMD SVM virtualization, Windows can boot normally again.

Because Windows can boot normally when AMD SVM is disabled, this does not look like a normal EFI / BCD / bootloader corruption issue. It looks more like a low-level conflict during Windows Hypervisor initialization when AMD SVM is available.

Reproduction steps:

  1. Start with Windows 11 10.0.26200.8246 on a Lenovo Yoga Air 14s with AMD Ryzen 7 7840S.
  2. Enable WSL or VirtualMachinePlatform. This can be triggered by one of the following:
    • Installing Docker Desktop and allowing it to enable WSL2;
    • Enabling “Windows Subsystem for Linux” in Windows Features;
    • Enabling “Virtual Machine Platform” in Windows Features;
    • Running DISM or PowerShell commands to enable VirtualMachinePlatform;
    • Installing Ubuntu through WSL.
  3. Reboot the system.
  4. If AMD SVM / AMD-V is enabled in BIOS, Windows fails to boot and enters one of the following states:
    • black screen;
    • stuck during Windows feature configuration;
    • stuck around 30% and then black screen;
    • Windows Automatic Repair;
    • Automatic Repair fails;
    • uninstalling updates fails;
    • System Restore fails.
  5. Enter BIOS and disable AMD SVM / AMD-V.
  6. Windows can boot normally again.

Expected behavior: Windows should boot normally after enabling WSL / VirtualMachinePlatform when AMD SVM is enabled in BIOS. WSL2 and Docker Desktop should be able to use hardware virtualization normally.

Actual behavior: Windows crashes, shows a black screen, or enters Automatic Repair on the next reboot when AMD SVM is enabled. Disabling AMD SVM allows Windows to boot again.

Important observations:

  1. The issue is not simply a Docker Desktop installation problem. Docker only triggered the WSL2 / VirtualMachinePlatform dependency.
  2. The actual failure happens during the Windows boot process after WSL / VirtualMachinePlatform has been enabled.
  3. The bootloader does not appear to be permanently damaged, because disabling AMD SVM in BIOS allows Windows to boot normally.
  4. The failure seems to occur only when both conditions are true:
    • WSL / VirtualMachinePlatform / Hypervisor-related components are enabled or have been installed;
    • AMD SVM / AMD-V is enabled in BIOS.
  5. This suggests a possible low-level compatibility issue involving:
    • Windows 11 Build 26200;
    • Windows Hypervisor;
    • WSL2 / VirtualMachinePlatform;
    • AMD SVM / AMD-V;
    • Lenovo BIOS / ACPI / IOMMU / AMD AGESA firmware implementation.

Related references:

  1. WSL / Virtual Machine Platform cannot be enabled for 25H2: https://github.com/microsoft/WSL/issues/13509
  2. Unable to get WSL running in my development Windows: https://learn.microsoft.com/en-us/answers/questions/4165752/unable-to-get-wsl-running-in-my-development-window

Things already checked or considered:

  • The AMD Ryzen 7 7840S CPU supports hardware virtualization.
  • AMD SVM can be enabled and disabled in BIOS.
  • When AMD SVM is disabled, Windows can boot.
  • When AMD SVM is enabled and WSL / VirtualMachinePlatform has been enabled, Windows may fail to boot.
  • This does not look like a normal BCD or EFI boot failure, because disabling AMD SVM restores bootability.
  • Docker Desktop is not considered the root cause. It only triggered WSL2 / VirtualMachinePlatform installation.

Questions:

  1. Is there a known issue in Windows 11 25H2 / Build 26200 where enabling WSL2 / VirtualMachinePlatform causes boot failure or Automatic Repair on AMD systems?
  2. Could this be related to Windows Hypervisor initialization when AMD SVM / AMD-V is available?
  3. Are there known compatibility issues involving WSL2 / VirtualMachinePlatform / VBS / HVCI / Device Guard and AMD SVM on Windows 11 Build 26200?
  4. Is there a recommended way to safely disable or reset WSL / VirtualMachinePlatform / Hypervisor configuration from Windows Recovery Environment?
  5. Should I reinstall or downgrade to Windows 11 24H2 / Build 26100 as a workaround?
  6. Which logs should I collect to identify where the boot failure occurs? For example:
    • SrtTrail.txt
    • CBS.log
    • DISM.log
    • Event Viewer logs
    • WSL logs

Request: Please help determine whether this is a known Windows 11 Build 26200 / WSL2 / VirtualMachinePlatform / AMD SVM compatibility issue, and whether there is any official workaround or fix.

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-12T12:47:37.4366667+00:00

    The provided context does not document any known Windows 11 25H2 / build 26200-specific issue where enabling WSL2/VirtualMachinePlatform with AMD SVM causes boot failure or Automatic Repair, nor any AMD‑specific WSL2/Hypervisor compatibility bug.

    From the context, the only directly relevant guidance for the error pattern seen with WSL is the generic WSL troubleshooting note for error 0x80370102, which attributes failures to missing virtualization support and recommends:

    1. Ensuring the Virtual Machine Platform Windows feature is enabled.
    2. Ensuring virtualization is enabled in BIOS/UEFI.
    3. Verifying Hyper‑V system requirements.
    4. Enabling nested virtualization if running inside a VM.
    5. Following OEM guidance for enabling virtualization.

    There is no additional information in the context about:

    • Build 26200‑specific WSL/Hyper‑V/AMD SVM regressions.
    • Interactions between VBS/HVCI/Device Guard and AMD SVM on 25H2.
    • Any official workaround such as downgrading from 25H2 to 24H2.
    • A documented procedure from WinRE specifically for “resetting” WSL/VirtualMachinePlatform/Hypervisor configuration beyond standard recovery options.

    The context also includes general guidance for:

    • Enabling virtualization in BIOS/UEFI and turning on Virtual Machine Platform in Windows.
    • Basic troubleshooting for Windows 11 blue/black screen and stop‑code issues (remove new hardware, Safe Mode, Device Manager, free disk space, Windows Update, and Windows 11 recovery options).
    • Using Windows 11 recovery options (system restore, reset/reinstall) when basic troubleshooting does not resolve repeated boot failures.

    However, none of these documents describe the specific AMD SVM + WSL2 + build 26200 boot‑loop/Automatic Repair scenario, nor do they provide an official statement that this is a known compatibility issue or a prescribed downgrade path.

    Because of that, the questions about whether this is a known 25H2 bug, whether it is specifically tied to Windows Hypervisor initialization on AMD SVM, whether there are documented VBS/HVCI/Device Guard conflicts on this build, and which exact logs to collect for this scenario cannot be answered from the supplied context.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.