How to Fix Error 0x80070570 in Windows 11

Error 0x80070570 signals that Windows is unable to read or process a specific file, typically due to corruption, a damaged file system, failing storage media, or an unstable connection. Resolving this error requires a methodical approach to isolate the root cause without risking data loss.

This guide walks you through a step-by-step workflow to fix Error 0x80070570 in Windows 11, starting with critical data protection, followed by file system repairs, media validation, and hardware health checks.

Prerequisites

• Administrative rights for command-line repairs
• External backup destination for at-risk data
• Known-good installation media if the error occurs during setup

Identify when and where the error appears

The first step in resolving error 0x80070570 is to confirm the exact scenario that triggers it, since the root cause and appropriate fix vary significantly depending on context.

Common scenarios include:

• During file copy or extraction inside Windows
• During Windows setup from USB or ISO
• When accessing a specific folder or drive

Log the exact step and file name if shown to guide next actions. For example, if the error appears only when copying files from a specific USB drive, the problem likely lies with the drive or its connection rather than the Windows installation itself. If it occurs during Windows 11 installation, the installation media itself may be corrupted or the target drive may have underlying issues.

Safeguard data and check drive health

Before attempting any repairs that could stress the storage subsystem, protect your data and assess drive health.

Back up important files from the affected volume first. Even if the drive appears functional, the error 0x80070570 can indicate impending failure, and repair operations like chkdsk can sometimes push a marginal drive over the edge.

Review SMART quickly with your preferred tool; if critical attributes such as reallocated sector count, pending sectors, or uncorrectable errors are failing, image the disk and replace it before repairs. For SSDs, check wear-leveling count and available spare blocks. If SMART is unknown or unavailable, avoid heavy writes until you have a complete backup.

This precaution is especially critical for system administrators managing endpoints with sensitive data, as an unexpected drive failure during repair could result in data loss and compliance issues.

Repair the file system and OS components

For errors occurring within a working Windows 11 installation, logical corruption is a common cause. Run these commands in sequence from an elevated terminal:

chkdsk C: /scan

If issues are found, schedule a repair on next reboot:

chkdsk C: /f

After chkdsk completes, repair the Windows component store:

DISM /Online /Cleanup-Image /RestoreHealth

Then scan and repair protected system files:

sfc /scannow

If DISM reports that it cannot find source files, mount a Windows 11 ISO that matches your build and specify the source explicitly:

DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\Sources\install.wim /LimitAccess

This sequence addresses most file system and component corruption that triggers error 0x80070570 during file operations or Windows updates.

Re-test with known-good media and ports

When error 0x80070570 appears during Windows installation or when copying from external media, the source itself is often the problem.

Recreate installation media using the official Windows 11 Media Creation Tool or download a fresh ISO from Microsoft. Verify the ISO checksum matches the published values before creating bootable media.

Try a different USB port and cable, preferably a direct port on the motherboard rather than a hub. USB hubs and extension cables can introduce signal integrity issues that corrupt data transfers, especially with older or marginal hardware.

For network-based installations or file copies, verify network stability and consider using a wired connection instead of Wi-Fi to rule out packet loss.

Isolate problem files and paths

If the error occurs when copying a large set of files, isolate the specific file causing the failure.

Copy in smaller batches to locate the failing file. Once identified, re-download it from the original source or restore it from a known-good backup.

For compressed archives, test integrity with the archive tool’s built-in verification feature. If corruption is detected, re-download the archive or extract it on a different system to confirm whether the issue is with the archive itself or the destination drive.

This methodical approach prevents wasting time on system-wide repairs when only a single file is corrupted.

Hardware triage

When software fixes don’t resolve error 0x80070570, hardware failure is likely.

For spinning disks, listen for clicking sounds and check reallocated sector counts in SMART data. Even a small number of reallocated sectors indicates the drive is failing.

For SSDs, review media wear indicators and available spare blocks. SSDs can fail suddenly when spare blocks are exhausted.

Run vendor diagnostics for HDD or SSD. Most manufacturers provide bootable diagnostic tools that perform thorough tests beyond what SMART reports.

Reseat data and power cables on desktops, as loose connections can cause intermittent I/O errors. If errors persist after software fixes, replace the drive and restore from backup or image.

For enterprise environments, this step is critical to prevent cascading failures across multiple endpoints.

Setup-specific remediation

Error 0x80070570 during Windows 11 installation requires specific approaches.

Delete and recreate the target partition during Windows setup if partition metadata looks inconsistent. This resolves corruption in the partition table or file system metadata that chkdsk cannot fix from within the setup environment.

If the target disk holds data, cancel installation and back it up first using a live USB or by connecting the drive to another system. Only clean the partition table after confirming you have a complete backup.

When installing to NVMe drives, ensure storage drivers and firmware are current. Some early NVMe firmware versions have bugs that cause data corruption under specific conditions.

Best practices

Troubleshooting

Error repeats on the same file only: Assume file corruption, re-download or restore from backup.

Error moves when changing ports or cables: Suspect flaky I/O path or hub. Test with direct motherboard ports and replace cables.

DISM cannot find source: Mount a matching ISO and specify /Source with the correct WIM index.

chkdsk reports bad sectors: Back up immediately and plan a drive replacement. Bad sectors indicate physical damage that will only worsen.

Setup still fails after recreating media: Clean install to a new drive or different slot, then migrate data. This isolates whether the issue is with the original drive or the system itself.

In summary

Most 0x80070570 cases trace to a corrupted file, damaged file system, or unreliable media. Protect data first, repair the file system and components, validate your media and ports, and confirm hardware health. Escalate to replacement only after you have a safe backup and clear diagnostics.