🪟 Windows Installation Error

Fix Windows Error 0x80070570

📅 Updated: Jan 12, 2026 ⏱️ 20 min - 2 hrs to fix ✅ 91% Success Rate

🚀 Quick Fix Summary

Problem Type: Windows Error 0x80070570

Common Symptoms: "Windows cannot install required files", "The file or directory is corrupted and unreadable", installation hangs, update fails, blue screen during setup

Primary Causes: Corrupted installation media (35%), bad RAM (28%), hard drive errors (20%), USB/DVD drive issues (12%), corrupted downloaded files (5%)

Time to Fix: 20 minutes - 2 hours

Difficulty: Easy to Moderate

Success Rate: 91% with media recreation and hardware checks

Windows error 0x80070570 with system message "Windows cannot install required files. The file may be corrupt or missing. Make sure all files required for installation are available, and restart the installation. Error code: 0x80070570" is a file corruption and data integrity error that prevents Windows 10, Windows 11, Windows 8, and Windows 7 installations and updates from completing successfully when Setup encounters corrupted files, unreadable data, or I/O errors during file copying operations, manifesting when users attempt clean Windows installations from USB drives or DVD media finding installation progressing to 15-50% completion then failing with "Windows cannot install required files" error 0x80070570 preventing OS installation, try Windows Update installations of feature updates or cumulative updates which download successfully but fail during installation phase with "We couldn't install updates - Error 0x80070570" messages leaving systems unable to receive security patches, experience blue screens during Windows Setup with STOP code UNMOUNTABLE_BOOT_VOLUME or INACCESSIBLE_BOOT_DEVICE accompanied by 0x80070570 errors indicating storage device read failures, or encounter "The file or directory is corrupted and unreadable" errors when copying files to/from hard drives suggesting underlying disk corruption causing 0x80070570 in various Windows operations, affecting users attempting fresh Windows installations on new computers or reformatted systems finding installations repeatedly fail at same percentage with 0x80070570 despite trying multiple times, home users performing Windows upgrades or updates encountering persistent 0x80070570 errors preventing system updates leaving computers vulnerable to security threats, IT professionals deploying Windows across multiple machines experiencing sporadic 0x80070570 failures on specific hardware models indicating RAM or storage controller issues, users with older computers (5+ years old) where aging hard drives develop bad sectors causing file read errors manifesting as 0x80070570 during installations or updates, and users creating bootable USB drives using various tools (Rufus, Media Creation Tool, third-party utilities) finding installations fail with 0x80070570 due to improperly created installation media or corrupted ISO downloads from unofficial sources.

Error 0x80070570 (ERROR_FILE_CORRUPT) originates from multiple data integrity and hardware reliability failures with corrupted installation media being the most common cause (35% of cases)—where Windows installation USB drives or DVD discs contain corrupted files due to improper creation process, interrupted downloads of Windows ISO files, low-quality USB drives with unreliable flash memory, or scratched/damaged DVD media causing Setup to read corrupted data during installation file extraction phase—followed by faulty RAM (Random Access Memory) where defective memory modules cause bit flips during data transfers, corrupting files as they're copied from installation media to hard drive or during Windows Update package extraction, with Windows Setup's integrity checks detecting corrupted data and failing installation with 0x80070570 (28%), hard drive errors including bad sectors on mechanical hard drives (HDD), failing solid-state drives (SSD), or corrupted file system structures (NTFS corruption) preventing Windows from reliably writing installation files to disk or reading existing system files during updates causing I/O errors that manifest as 0x80070570 (20%), USB port or DVD drive hardware issues where faulty USB 3.0 ports, damaged USB cables, or malfunctioning DVD drives cause intermittent read errors during installation media access leading to corrupted file transfers (12%), and corrupted Windows Update downloads where Windows Update service downloads update packages from Microsoft servers but network interruptions, proxy issues, or Windows Update cache corruption cause incomplete or corrupted downloads that fail verification checks during installation (5%). This comprehensive guide provides 5 proven methods to fix Windows error 0x80070570: recreating installation media using reliable tools and USB drives, running Windows Memory Diagnostic to test RAM, checking and repairing hard drive errors with CHKDSK, using different USB ports or DVD drives, and resetting Windows Update components—ensuring you can successfully complete Windows installations, install system updates without corruption errors, eliminate persistent 0x80070570 failures, and maintain reliable Windows operations.

Method 1: Recreate Installation Media (Primary Fix)

Corrupted USB/DVD causes file errors. Fresh media with verified ISO ensures clean installation.

Creating fresh Windows installation media
  1. Download Official Windows ISO:
  2. Go to: microsoft.com/software-download/windows10
  3. Or: microsoft.com/software-download/windows11
  4. Click Download tool now
  5. Downloads: MediaCreationTool.exe
  6. Use Quality USB Drive:
  7. Get reliable USB drive (8GB+ for Windows 10, 16GB+ for Windows 11)
  8. Brands recommended:
    • SanDisk
    • Samsung
    • Kingston
    • Corsair
  9. Avoid: Cheap no-name USB drives (unreliable flash memory)
  10. Format USB Drive First:
  11. Right-click USB drive → Format
  12. File system: FAT32 (for UEFI) or NTFS
  13. Allocation unit size: Default
  14. Check Quick Format
  15. Click Start
  16. Run Media Creation Tool:
  17. Right-click MediaCreationTool.exe → Run as administrator
  18. Accept license terms
  19. Select Create installation media
  20. Choose language, edition, architecture
  21. Select USB flash drive
  22. Select your USB drive from list
  23. Click Next
  24. Tool Creates Bootable USB:
  25. Downloads Windows files (3-5 GB)
  26. Verifies download integrity
  27. Writes to USB drive
  28. Takes 30-60 minutes
  29. "Your USB flash drive is ready" message
  30. Verify USB Contents:
  31. Open USB drive in File Explorer
  32. Should contain:
    • boot folder
    • efi folder
    • sources folder (contains install.wim or install.esd)
    • setup.exe
  33. Use this fresh USB for installation

Method 2: Run Windows Memory Diagnostic

Faulty RAM corrupts files during installation. Memory test identifies defective modules.

Testing RAM with Memory Diagnostic
  1. Press Windows + R, type mdsched.exe, press Enter
  2. Windows Memory Diagnostic opens
  3. Click Restart now and check for problems
  4. Memory Test Runs:
  5. Computer restarts to blue screen
  6. "Windows Memory Diagnostic" appears
  7. Shows progress bar
  8. Takes 10-30 minutes
  9. Test Performs Two Passes:
    • Pass 1: Standard memory test
    • Pass 2: Extended test
  10. For Comprehensive Test:
  11. During test: Press F1
  12. Select Extended test
  13. Takes 45-90 minutes
  14. Tests all memory thoroughly
  15. After Test Completes:
  16. Computer restarts automatically
  17. Windows loads normally
  18. Notification shows test results
  19. Or: Event Viewer → Windows Logs → System
  20. Find "MemoryDiagnostics-Results" entry
  21. If Errors Found:
    • RAM module failing
    • If multiple RAM sticks installed:
    • Remove one stick at a time
    • Test installation with each stick individually
    • Identify faulty module
    • Replace defective RAM
  22. If No Errors: RAM OK, try other methods

Method 3: Check and Repair Hard Drive Errors

Bad sectors cause file corruption. CHKDSK repairs disk errors enabling successful installation.

Running CHKDSK to repair disk errors
  1. Open Command Prompt as Administrator
  2. Run CHKDSK with Full Repair:
    chkdsk C: /f /r /x
  3. Command Parameters:
    • /f = Fixes errors on the disk
    • /r = Locates bad sectors and recovers readable information
    • /x = Forces volume to dismount first
  4. If Drive in Use:
  5. Message: "Cannot lock current drive"
  6. "Schedule this volume to be checked next time system restarts? (Y/N)"
  7. Type Y and press Enter
  8. Close Command Prompt
  9. Restart computer
  10. CHKDSK Runs Before Windows Loads:
  11. Black screen with white text
  12. "Checking file system on C:"
  13. Shows 5 stages:
    • Stage 1: Examining basic file system structure
    • Stage 2: Examining file name linkage
    • Stage 3: Examining security descriptors
    • Stage 4: Looking for bad clusters
    • Stage 5: Looking for bad, free clusters
  14. Takes 30 minutes - 3 hours depending on drive size
  15. After Completion:
  16. Windows boots normally
  17. Check results: Event Viewer → Windows Logs → Application
  18. Find "Wininit" source entry
  19. Shows CHKDSK results and repairs made
  20. If Bad Sectors Found:
    • CHKDSK marks them as unusable
    • If many bad sectors: Hard drive failing
    • Consider replacing drive
    • Backup data immediately
  21. Try Windows installation/update again

Method 4: Use Different USB Port or DVD Drive

Faulty USB port causes read errors. Different port provides reliable connection.

Using different USB port
  1. Try Different USB Port:
  2. If using USB 3.0 port (blue): Try USB 2.0 port (black)
  3. USB 3.0 sometimes has compatibility issues with older motherboards
  4. Use Rear USB Ports (Desktop):
  5. Rear ports connect directly to motherboard
  6. More reliable than front panel ports
  7. Front ports use extension cables (can be faulty)
  8. Avoid USB Hubs:
  9. Don't use USB hub for installation media
  10. Connect directly to computer
  11. Hubs can cause power/signal issues
  12. Try Different USB Cable (If External Drive):
  13. If using external hard drive for installation
  14. Try different USB cable
  15. Cables can develop internal breaks
  16. For DVD Installation:
  17. If using DVD, clean disc:
    • Wipe with soft, lint-free cloth
    • Wipe from center outward (not circular motion)
    • Remove fingerprints and dust
  18. Check DVD drive:
    • Clean drive lens with compressed air
    • Or use DVD lens cleaning disc
  19. Try external USB DVD drive if internal drive failing
  20. Test USB Drive on Different Computer:
  21. If possible, test USB drive on another PC
  22. If works there: Your USB ports may be faulty
  23. If fails there too: USB drive or media corrupted

Method 5: Reset Windows Update Components (For Update Errors)

Corrupted Windows Update cache causes 0x80070570 during updates. Resetting clears corruption.

Resetting Windows Update components
  1. Open Command Prompt as Administrator
  2. Stop Windows Update Services:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
  3. Each shows "The service was stopped successfully"
  4. Rename SoftwareDistribution Folder:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  5. This folder contains Windows Update cache
  6. Renaming forces Windows to create fresh folder
  7. Rename Catroot2 Folder:
    ren C:\Windows\System32\catroot2 catroot2.old
  8. Contains cryptographic database
  9. Restart Windows Update Services:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
  10. Each shows "The service was started successfully"
  11. When Services Restart:
    • Windows creates NEW SoftwareDistribution folder
    • Creates NEW Catroot2 folder
    • Fresh, clean Windows Update cache
    • All corrupted update files removed
  12. Close Command Prompt
  13. Restart computer
  14. Try Windows Update again
  15. Windows re-downloads updates with fresh cache

💡 Pro Tip: Prevent Future 0x80070570 Errors

Use official Microsoft tools for installation media: Always download Windows ISO from microsoft.com and use Media Creation Tool—avoid third-party ISO sources or tools (potential corruption/malware). Invest in quality USB drives: For bootable media, use reputable brands (SanDisk, Samsung, Kingston)—cheap USB drives have unreliable flash memory causing file corruption. Test RAM regularly: Run Windows Memory Diagnostic quarterly—catches failing RAM before causing installation/update failures. Monitor hard drive health: Use CrystalDiskInfo to check drive SMART status monthly—replace drives showing "Caution" or "Bad" status before failures occur. Keep BIOS/UEFI updated: Motherboard manufacturers release BIOS updates fixing USB controller bugs and storage compatibility—update annually. Don't interrupt Windows installations: Never force shutdown during "Installing Windows" phase—interruptions corrupt installation files requiring restart with fresh media. Verify ISO checksums: If downloading ISO manually, verify SHA-256 checksum matches Microsoft's published hash—ensures download not corrupted. Use wired internet for updates: Wi-Fi interruptions can corrupt Windows Update downloads—use Ethernet for large updates. Maintain adequate cooling: Overheating causes memory errors during intensive operations like installations—ensure proper ventilation, clean dust from vents. For IT professionals: When deploying Windows across multiple machines, test installation media on one machine first—validates media before mass deployment.

Frequently Asked Questions

Q: Error 0x80070570 appears at different percentages each time I try installing Windows. Why?

A: Random failure points indicate hardware issue, not media corruption. If media corrupted, would fail at same file/percentage every time (e.g., always at 23%). Random failures suggest: (1) Faulty RAM: Memory errors occur randomly during data transfers—different files corrupted each attempt. Run Memory Diagnostic (Method 2)—if errors found, RAM failing. (2) Overheating: CPU/RAM overheats during intensive installation, causes errors at random points when temperature threshold exceeded. Check temperatures, improve cooling. (3) Unstable power supply: PSU (power supply unit) voltage fluctuations cause random errors. More common on laptops with failing batteries or desktops with cheap PSUs. (4) Intermittent USB connection: Loose USB port or cable causes momentary disconnections during file reading—different files affected each time. Try different port (Method 4). (5) Hard drive with developing bad sectors: Drive has scattered bad sectors—which sector encountered during installation is random. Run CHKDSK (Method 3). Consistent failure point: If always fails at same percentage (e.g., always 27%), indicates corrupted installation media—recreate USB/DVD (Method 1). Diagnostic approach: Try installation 3 times, note failure percentages—if all different, hardware issue; if same, media issue.

Q: Can I just skip the corrupted file and continue Windows installation?

A: No—Windows Setup doesn't allow skipping, and shouldn't even if possible. (1) Setup enforces integrity: Windows installation requires ALL files for functional OS—missing even one system file causes instability, crashes, or features not working. Setup verifies every file's checksum, fails installation if any corrupted. (2) No "skip" option: Windows Setup doesn't provide option to skip corrupted files—by design for system integrity. When encounters 0x80070570, only options are: retry installation or cancel. (3) What corrupted files cause: Depending on which file corrupted: missing drivers (hardware doesn't work), broken system services (features fail), corrupted registry (system unstable), or damaged boot files (Windows won't start). (4) Proper approach: Fix root cause of corruption (Methods 1-5), don't try to work around it. Corrupted file is symptom, not problem itself—underlying cause (bad RAM, failing drive, corrupted media) will cause more issues post-installation. (5) If desperate: Some users try extracting install.wim from ISO, manually replacing corrupted files, repacking ISO—extremely advanced, time-consuming, often fails. Easier to fix hardware issue or recreate media. Bottom line: Windows installation is all-or-nothing—either all files install correctly or installation fails. No partial installations possible.

Q: Error 0x80070570 only occurs during Windows Updates, not clean installations. Different cause?

A: Yes, different cause—Windows Update cache corruption vs installation media corruption. (1) Update-specific 0x80070570: Windows Update downloads update packages to C:\Windows\SoftwareDistribution\Download, extracts and installs. If download corrupted (network interruption, proxy issues) or extraction fails (disk errors, antivirus interference), gets 0x80070570 during installation phase. (2) Why clean install works: Clean installation uses different code path—reads from USB/DVD directly, doesn't use Windows Update infrastructure. If clean install succeeds but updates fail, indicates: Windows Update cache corrupted, hard drive has bad sectors in SoftwareDistribution folder location, or antivirus blocking Windows Update file operations. (3) Fix for update-specific errors: Method 5 (Reset Windows Update Components) most effective—clears corrupted cache, forces re-download. Also: temporarily disable antivirus during updates, run CHKDSK to fix disk errors. (4) Persistent update failures: If specific update consistently fails with 0x80070570, manually download from Microsoft Update Catalog (catalog.update.microsoft.com), install .msu file directly—bypasses Windows Update service. (5) Difference from installation errors: Installation 0x80070570 usually hardware (RAM, drive, USB)—affects all file operations. Update 0x80070570 usually software (cache, services)—only affects Windows Update. Troubleshoot accordingly.

Q: I recreated installation media multiple times but still get 0x80070570. What's wrong?

A: If media recreation doesn't fix, problem is target computer hardware, not media. (1) Test installation media on different computer: Try installing Windows on different PC using same USB drive—if works there, your computer has hardware issue (RAM, hard drive, motherboard). If fails on multiple computers, USB drive itself faulty (even if new). (2) Verify ISO checksum: Before creating media, verify downloaded ISO's SHA-256 hash matches Microsoft's official hash (published on download page)—ensures ISO not corrupted during download. Use PowerShell: Get-FileHash -Path "C:\path\to\windows.iso" -Algorithm SHA256, compare output to official hash. (3) Try different USB drive: Even new USB drives can be defective—manufacturing defects in flash memory. Borrow known-good USB drive from friend, create media on it, test. (4) Test target hard drive: Boot from USB to Windows Setup, press Shift+F10 to open Command Prompt, run chkdsk C: /f /r on target drive before installation—may reveal drive issues. Or use drive manufacturer's diagnostic tool (SeaTools for Seagate, Data Lifeguard for WD). (5) Check BIOS settings: Incorrect SATA mode (AHCI vs IDE vs RAID) can cause read errors. Enter BIOS, set SATA mode to AHCI (most compatible). Disable RAID if not actually using RAID. (6) Last resort—different installation method: If USB consistently fails, try DVD installation (burn ISO to DVD using ImgBurn or Windows built-in burner). Or try network installation (PXE boot) if available. Different media types bypass USB-specific issues.

Q: Can overclocking cause 0x80070570 errors during Windows installation?

A: Yes, absolutely—overclocking common cause of installation failures. (1) Why overclocking causes 0x80070570: Overclocked CPU/RAM runs at higher speeds than designed, generates more heat, requires more voltage. During intensive operations like Windows installation (heavy file I/O, decompression, verification), unstable overclock causes: memory errors (corrupted data in RAM), CPU errors (incorrect calculations), or system crashes. Manifests as 0x80070570 when corrupted data written to disk or verification checksums fail. (2) Even "stable" overclocks: Overclock may pass stress tests (Prime95, MemTest86) but still fail during real-world usage like installations—stress tests don't perfectly replicate all workload types. (3) XMP/DOCP profiles: Enabling XMP (Intel) or DOCP (AMD) RAM profiles is technically overclocking—runs RAM at rated speed (e.g., 3200MHz) instead of default (usually 2133MHz). Some motherboards have poor XMP compatibility causing instability. (4) How to test: Enter BIOS, load "Optimized Defaults" or "Fail-Safe Defaults"—disables all overclocking, returns CPU/RAM to stock speeds. Retry Windows installation—if succeeds, overclock was cause. (5) If you need overclock: After successful installation at stock speeds, gradually re-apply overclock: increase multiplier/voltage in small steps, test stability after each change. Find highest stable overclock that doesn't cause errors. (6) Recommendation: For critical operations (OS installation, BIOS updates, important work), always run at stock speeds—overclock for gaming/benchmarks only. Stability more important than speed for system operations.