Since Safe Mode, Windows Update repair, and resetting SoftwareDistribution/catroot2 were already tried, the next supported path is to repair Windows system files and the Windows image in this order from an elevated Command Prompt:
- Run:
Expected result: Command Prompt shows either “The restore operation completed successfully” or “The operation completed successfully.”DISM.exe /Online /Cleanup-image /Restorehealth - Then run:
Wait until verification reaches 100%.sfc /scannow - Restart the PC and try
wsl --installagain.
If sfc /scannow returns “Windows Resource Protection could not perform the requested operation”, run SFC in Safe Mode and make sure these folders exist:
-
%WinDir%\WinSxS\Temp\PendingDeletes -
%WinDir%\WinSxS\Temp\PendingRenames
If DISM /RestoreHealth fails because the repair source cannot be found or the source image is affected, provide a valid repair source and run RestoreHealth again. If an install.wim is available, use:
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess
sfc /scannow
If the issue is tied to Windows Update servicing corruption, restart after RestoreHealth, run sfc /scannow, and then retry the update or WSL installation.
If corruption persists after DISM and SFC, the supported next step for persistent servicing failures is an in-place upgrade. This repairs the servicing stack while preserving applications and data.
References:
- Troubleshooting Windows Subsystem for Linux
- Use the System File Checker tool to repair missing or corrupted system files
- Troubleshoot problems updating Windows
- System File Checker (SFC) incorrectly flags Windows Defender PowerShell module files as corrupted
- Troubleshoot Windows Update error 0x80004004