| Previous | Next |
| STATUS_MUTUAL_AUTHENTICATION_FAILED | STATUS_DATATYPE_MISALIGNMENT_ERROR |
STATUS_CORRUPT_SYSTEM_FILE
A system-file integrity repair has already taken place
STATUS_CORRUPT_SYSTEM_FILE is more specific than a generic file corruption result: the NTSTATUS text says the system file became corrupt and was replaced. The useful follow-up is to establish which file was repaired and whether the event is isolated or part of broader component-store or storage damage.
Windows Resource Protection and System File Checker are the relevant integrity mechanisms for protected Windows files. Current Microsoft guidance uses DISM to repair the Windows image when necessary and SFC to verify and repair protected system files; SFC details are recorded in CBS.log.
Do not assume that replacement closes the investigation. If the same protected file is repeatedly repaired, compare hashes and timestamps, review CBS and servicing logs, and check disk or controller events. Recurrent corruption can be downstream evidence of unstable storage or an incomplete servicing state.
What to inspect
- The exact protected file and the CBS log entries for the repair event.
- DISM component-store health and whether SFC reports additional unrepaired files.
- Storage and WHEA events if corruption repeats after a clean repair.
References
- Microsoft Support: Use System File Checker to repair system files
- Microsoft Support: Using System File Checker in Windows
- Microsoft: Description of System File Checker
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.