Skip to content

VirtualMachinePlatform fails to enable with 0xc1900401 on Windows 11 26H2 (26300.9974) – all FOD downloads fail #42314

Closed

Description

@DaisukeUema

Windows Version

Microsoft Windows [Version 10.0.26300.9974]

WSL Version

3.0.5.0

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

  • WSL 2
  • WSL 1
  • WSLC

Kernel Version

6.18.58.1-1

Distro Version

N/A (no distribution installed – failure occurs while enabling VirtualMachinePlatform, before any distro is installed)

Other Software

No response

Repro Steps

  1. Use a Windows 11 Pro 26H2 (build 26300.9974) machine where VirtualMachinePlatform is disabled.
  2. Open PowerShell as Administrator.
  3. Run: wsl --install --no-distribution
  4. DISM runs to 100% and then fails with error 0xc1900401.

The same error occurs with:

  • dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
  • Add-WindowsCapability -Online -Name "Print.Management.Console~~~~0.0.1.0"

Expected Behavior

VirtualMachinePlatform should be enabled successfully (the required Feature on Demand payload should be downloaded from Windows Update), and after a restart WSL 2 should be usable, as described in the official installation guide:
https://learn.microsoft.com/windows/wsl/install

Other Features on Demand (e.g. Print.Management.Console) should also install normally via Add-WindowsCapability.

Actual Behavior

DISM runs to 100% and then fails:

Error: 0xc1900401
DISM failed. No operation was performed.
Failed to enable Windows component 'VirtualMachinePlatform' (exit code 3247440897)
Error code: Wsl/WSL_E_INSTALL_COMPONENT_FAILED

VirtualMachinePlatform remains "Disabled" (Get-WindowsOptionalFeature).

Findings from the logs:

  • CBS.log: "Failed to download FOD from WU", "Download Size: 0"
    (feature: Windows.HyperV.OptionalFeature.VirtualMachinePlatform.Client.Disabled~)
  • All Features on Demand fail with the same 0xc1900401
    (e.g. Print.Management.Console)
  • DISM /ScanHealth reports the component store is repairable;
    /RestoreHealth fails with 0x800f0915
  • CBS.log has many "Store corruption, manifest missing" entries for
    10.0.26100.9818 FOD packages
    (e.g. Undocked-Hypervisor-Drivers-Package, Microsoft-Edge-WebView-FOD-Package)
  • KB5132057 fails to install with 0x800f0831 (CBS_E_STORE_CORRUPTION)
  • Hyper-V (Microsoft-Hyper-V-All) can be enabled, but VirtualMachinePlatform cannot
  • Same result on home network and mobile tethering

Tried without success:

  • "Fix problems using Windows Update" (in-place reinstall)
  • Manually installing KB5127936 (.msu)
  • Resetting the Windows Update cache
  • No WSUS or servicing policies are configured

Diagnostic Logs

No response

Activity

  1. github-actions commented on Nov 20, 2026

    @github-actions
    Contributor

    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'.

  2. DaisukeUema commented on Nov 20, 2026

    @DaisukeUema
    Author

    /emailed-logs

  3. github-actions commented on Nov 20, 2026

    @github-actions
    Contributor
    Diagnostic information
    Found '/emailed-logs', adding tag 'emailed-logs'
    
  4. DaisukeUema commented on Nov 21, 2026

    @DaisukeUema
    Author

    Update: resolved by resetting Windows with "Cloud download"

    I resolved this by running Settings > System > Recovery > Reset this PC and choosing Cloud download. After the reinstall, wsl --install --no-distribution completed successfully, and Ubuntu now runs on WSL 2.

    What I found before the fix (in case it helps)

    • 87 packages at version 10.0.26100.9818 (the October 28 preview, KB5127936) were registered, but their .mum manifests were missing (Store corruption, manifest missing for package: ...~10.0.26100.9818). This included HyperV-OptionalFeature-VirtualMachinePlatform-Client-Disabled-FOD-Package.
    • The same 87 packages were already logged as "Failed opening package" in dism.log about 30 minutes after a local-reinstall reset (Remove everything, with drive cleaning) on 2026-11-19.
    • Enabling VMP failed because WindowsUpdateDownloadFromUUP returned 0xC1900401 (Download Size: 0). Other FoDs, such as Print.Management.Console~~~~0.0.1.0, failed the same way on both my home network and a mobile hotspot.
    • DISM /RestoreHealth failed with 0x800f0915. KB5132057 failed with 0x800f0831 because the manifest of Microsoft-Edge-WebView-FOD-Package~...~10.0.26100.9818 was missing.
    • On a brand-new second PC with the same build (26H2, 26300.9974), Add-WindowsCapability for the same FoD completed without errors (state changed from NotPresent to Staged), and WSL 2 works there. So the problem looked device-specific.
    • Neither the local-reinstall reset nor an in-place repair ("Fix problems using Windows Update") fixed it. Only the cloud reinstall did.

    This may be related to the known issue in KB5132061 (the November update failing on devices that had installed KB5127936), but I can't confirm that.

    The logs I emailed earlier were collected before the fix. Since my problem is resolved, I'm closing this issue. Feel free to reopen it if you need more information. Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    emailed-logsLogs have been emailedwsl2Issue/feature applies to WSL 2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions