You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VirtualMachinePlatform fails to enable with 0xc1900401 on Windows 11 26H2 (26300.9974) – all FOD downloads fail #42314
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
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)
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:
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.
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'.
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!
Activity
github-actions commentedon Nov 20, 2026
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:
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 networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce 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'.
DaisukeUema commentedon Nov 20, 2026
/emailed-logs
github-actions commentedon Nov 20, 2026
Diagnostic information
DaisukeUema commentedon Nov 21, 2026
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-distributioncompleted successfully, and Ubuntu now runs on WSL 2.What I found before the fix (in case it helps)
10.0.26100.9818(the October 28 preview, KB5127936) were registered, but their.mummanifests were missing (Store corruption, manifest missing for package: ...~10.0.26100.9818). This includedHyperV-OptionalFeature-VirtualMachinePlatform-Client-Disabled-FOD-Package.WindowsUpdateDownloadFromUUPreturned0xC1900401(Download Size: 0). Other FoDs, such asPrint.Management.Console~~~~0.0.1.0, failed the same way on both my home network and a mobile hotspot.DISM /RestoreHealthfailed with0x800f0915. KB5132057 failed with0x800f0831because the manifest ofMicrosoft-Edge-WebView-FOD-Package~...~10.0.26100.9818was missing.Add-WindowsCapabilityfor the same FoD completed without errors (state changed from NotPresent to Staged), and WSL 2 works there. So the problem looked device-specific.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!