Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | The file or directory is corrupted and unreadable. | Windows Event Viewer (System/Application logs) | -> |
| Affected build range | Windows 10/11 | C:\Windows\Panther\setupact.log | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ComponentStore | CBS.log (Component Based Servicing log) | -> |
| Relevant service/endpoint | Windows Update service (wuauserv) | C:\Windows\Panther\setupact.log | -> |
| Log line signature | Error 0x80070570 | C:\Windows\Logs\DISM\dism.log | -> |
Log Files to Check
C:\Windows\Logs\DISM\dism.logC:\Windows\Logs\CBS\CBS.log
What This Error Actually Means
The error code
0x80070570 translates to "The file or directory is corrupted and unreadable." This error is raised by the Windows operating system when it encounters a situation where a critical file or directory cannot be read due to corruption. The error is typically logged in the Windows Event Viewer under the System or Application logs, often accompanied by specific event IDs that provide additional context about the failure.
This error can occur during various operations such as Windows Update installations, OS upgrades, application installations, file copy operations, or even at system startup. It indicates that the operating system or an application has encountered a corrupted file, an unreadable disk sector, or a damaged file system structure. The error is particularly concerning because it can prevent critical updates from installing or cause system instability if not addressed promptly.
Affected Versions and Scope
The
0x80070570 error is observed across Windows 10 and Windows 11 operating systems. It does not discriminate based on specific builds but can occur in any build where the underlying conditions (such as file corruption, bad sectors, or component store damage) are present. The error is more prevalent in environments with aging hardware, insufficient maintenance, or improper handling of system updates.
This issue affects both physical and virtual machines running Windows 10/11. It can impact individual user devices, workstations, and even server-grade systems if they are running a compatible version of Windows. The scope of the error is broad, encompassing enterprise environments, small businesses, and personal computing setups.
Where To Look First: Logs and Event IDs
To diagnose the
0x80070570 error, you should examine several key log files and specific event IDs in the Windows Event Viewer. The primary logs to inspect are:
1. **Windows Update History**: Navigate to
Settings > Update & Security > Windows Update > Update history. Here, failed updates will be listed with their respective error codes.
2. **Event Viewer Logs**:
- **System Log**: Look for events related to disk errors or file system issues.
- **Application Log**: Check for specific events that may indicate corrupted files or directories.
Relevant Event IDs include:
- **Event ID 7 (Disk)**: This event often indicates a "Bad block" on the disk, which can lead to unreadable files and directories.
- **Event ID 1000 (Windows Update)**: This event is logged when Windows Update encounters an error during installation or rollback.
Additionally, inspect the following log files for detailed information:
-
C:\Windows\Logs\DISM\dism.log: Search for lines containing
Error 0x80070570 to identify specific issues with the component store.
-
C:\Windows\Logs\CBS\CBS.log: Look for entries marked with
[SR] and messages indicating corrupt files.
Root Causes
The
0x80070570 error can stem from several distinct issues. Identifying the root cause is crucial for applying the correct fix:
1. Bad Sectors on HDD or SSD
Physical damage to the storage media, such as bad sectors, can prevent the OS from reading critical files. This issue often manifests during disk-intensive operations like updates or installations.
2. Damaged Windows Component Store (WinSxS)
The component store (
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ComponentStore) is a repository of shared system components. Corruption here can prevent updates and applications from installing correctly.
3. Corrupted Temporary Files in SoftwareDistribution Cache
The Windows Update cache located at C:\Windows\SoftwareDistribution\Download\ may accumulate corrupted files that interfere with update processes.
4. RAM Errors Causing Corrupted Writes
Faulty memory modules can lead to data corruption on disk, which might not be immediately apparent but can cause the 0x80070570 error during read operations.
Fix Procedure
To resolve the 0x80070570 error, follow these steps:
- Run DISM to Check and Repair the Component Store:
Open an elevated command prompt and execute:
DISM /Online /Cleanup-Image /CheckHealth. If corruption is detected, proceed with:
DISM /Online /Cleanup-Image /RestoreHealth. This process can take up to 30 minutes. Review the log at C:\Windows\Logs\DISM\dism.log for errors.
- Run System File Checker:
In an elevated command prompt, run:
sfc /scannow. This scans and repairs corrupted system files. The results are logged in C:\Windows\Logs\CBS\CBS.log.
- Check Disk for Bad Sectors:
Use the following command to check and repair disk errors:
chkdsk C: /f /r /x. This requires a reboot. Results are logged in Event Viewer under Application > Source: Chkdsk.
- Test RAM for Errors:
Run Windows Memory Diagnostic (
mdsched.exe) or use MemTest86. After testing, check results in Event Viewer under System > Source: MemoryDiagnostics-Results.
- Check S.M.A.R.T. Drive Health:
Use
wmic diskdrive get Status or CrystalDiskInfo to assess drive health. A status of "Caution" or "Bad" with increasing Reallocated Sector Count (ID 5) indicates a failing drive.
- Clear Windows Update Cache:
Stop the Windows Update service (
net stop wuauserv), delete contents in C:\Windows\SoftwareDistribution\Download\, then restart the service (net start wuauserv).
- Replace Faulty Hardware:
If RAM or storage is faulty, replace the components. For mixed-brand RAM, test one module at a time to identify the culprit.
- Handle BitLocker-Related Issues:
Fully decrypt the drive via Control Panel > BitLocker Drive Encryption before performing updates. Re-enable BitLocker post-update.
- Clone Failing Drives:
Use tools like Clonezilla or Macrium Reflect to migrate data to a new drive. Post-cloning, run
chkdsk and sfc /scannow.
- Verify Fixes:
Re-run the operation that triggered the error (e.g., Windows Update). Check Event Viewer for remaining errors and ensure no corruption persists.
Error Code Variants
| Error Code |
Description |
Distinctive Features |
0x80070570 |
The file or directory is corrupted and unreadable. |
Indicates corruption in files or directories, often linked to disk errors or component store issues. |
0x8007010B |
The file could not be accessed because it is corrupted or a needed resource is missing. |
Similar to 0x80070570 but points more towards missing resources rather than corruption. |
0x800700E8 |
The file or directory is not found. |
Differentiates from corruption by indicating the absence of a file or directory altogether. |
Verification
After applying fixes, verify success by:
- Re-running the operation that triggered the error (e.g., Windows Update).
- Checking Event Viewer for any remaining disk errors.
- Running
sfc /scannow to ensure no corruption persists.
Prevention
To prevent recurrence of the
0x80070570 error, implement these measures:
1. **Regular Maintenance**: Schedule routine disk checks and component store repairs.
2. **Monitor S.M.A.R.T. Data**: Proactively replace failing drives before they cause issues.
3. **Disable Problematic Features**: If BitLocker is causing frequent issues, consider alternative encryption methods or ensure proper handling during updates.
4. **Use Reliable Storage**: Opt for high-quality SSDs with good error correction capabilities.
5. **Update Policies**: Ensure systems are regularly updated and patched to avoid outdated components.
By following this guide, sysadmins can effectively diagnose, fix, and prevent the
0x80070570 error, ensuring system stability and smooth operations.