| Previous | Next |
| ERROR_NO_SAVEPOINT_WITH_OPEN_FILES | ERROR_SPARSE_NOT_ALLOWED_IN_TRANSACTION |
ERROR_DATA_LOST_REPAIR
Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
ERROR_DATA_LOST_REPAIR is Win32 error 6843 (0x00001ABB) in Windows file-system and storage integrity handling.
Where the result appears
- opening a file after self-healing file-system repair.
- receiving the result from storage repair or integrity handling.
- recovering an application database or document after corruption.
- validating data after an online repair operation.
What to verify
Verify whether the repaired file still contains all application-required records and remains semantically consistent. Check file identity and repaired ranges, file-system and storage events, and application checksums or database consistency results.
Likely causes
- damaged clusters or metadata required reconstruction.
- a torn write left an invalid file range.
- repair discarded unrecoverable bytes.
- storage or memory corruption altered file content.
- the file-system repair succeeded structurally but could not prove application integrity.
Troubleshooting steps
- Collect file identity and repaired ranges.
- Record file-system and storage events.
- Correlate application checksums or database consistency results with the Windows System log, NTFS/ReFS events, storage-controller diagnostics, application integrity checks, and backup or replica logs.
Handling, retry, and recovery
Quarantine the repaired copy, validate it with the owning application, restore missing data from backup or replica, and investigate the underlying storage before returning the file to production.
Related errors
ERROR_FILE_CORRUPT reports corruption that prevents use; it says Windows repaired the file but warns that repair may have discarded data.
Example
A document opens after NTFS repairs a damaged extent. The application-level checksum no longer matches, so the administrator restores the last backup and retires the failing disk rather than treating the repair as complete.
Developer and administrator guidance
Administrators should prioritize data preservation and hardware evidence before repair. Developers should separate structural file-system success from application-level integrity, because a readable or repaired file can still be semantically incomplete.
References
Looking for a different code? Search another status or error code.