Windows 11 Error 573: “The Required System File %hs Is Bad or Missing”

Why This Error Happens

Error 573 occurs when Windows cannot locate or properly read a critical system file needed during boot or normal operation, typically due to corruption in the file itself or damage to the underlying disk sectors where it resides. This can result from improper shutdowns, failing storage hardware, malware interference, or incomplete Windows updates that leave system files in an inconsistent state. Since core OS components rely on a chain of interdependent files, even one corrupted file can trigger this error and prevent normal system functionality.

Step-by-Step Resolution Guide

Run System File Checker (SFC): Open Command Prompt as Administrator (right-click Start > Terminal (Admin)) and type sfc /scannow. Let it complete fully—this scans and repairs corrupted system files automatically using a cached copy.
Run DISM to Repair the Windows Image: If SFC reports it cannot fix some files, run DISM /Online /Cleanup-Image /RestoreHealth in the same elevated Command Prompt. This pulls clean file copies from Windows Update to repair the underlying system image that SFC relies on.
Check Disk for Errors: Run chkdsk C: /f /r and restart when prompted. This scans your drive for bad sectors and file system errors that may have caused the corruption in the first place.
Boot into Windows Recovery Environment (WinRE): If the error prevents normal startup, force a restart 2-3 times during boot to trigger WinRE, then navigate to Troubleshoot > Advanced Options > Command Prompt and run the same sfc /scannow and DISM commands targeting your offline Windows partition (e.g., sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows).
Update or Reinstall Windows: If files remain corrupted after the above steps, use Settings > Windows Update to install the latest cumulative update, or perform an in-place upgrade repair using Windows 11 installation media (Setup.exe > “Keep personal files and apps”).

Alternative or Verification Steps

Verify the fix: Re-run sfc /scannow—a clean result showing “Windows Resource Protection did not find any integrity violations” confirms the repair was successful. Also check Event Viewer (Windows Logs > System) for any recurring Error 573 entries.
Alternative solution: If corruption persists or recurs frequently, back up your data and perform a clean Windows 11 reinstall, as this may indicate failing storage hardware—run a manufacturer diagnostic tool (e.g., CrystalDiskInfo) to check drive health first.