Error 0x80070002 is Windows for file not found, and when the Media Creation Tool throws it, the tool cannot assemble the files it needs. It might fail during the download, during verification, or when writing to your USB drive. Each stage has different culprits, but they all share a theme: something between Microsoft’s servers and your machine is breaking the file pipeline.
The frustrating part is that the tool gives you the code and nothing else. No log location, no hint about which file went missing. This guide supplies the missing diagnostics: how to tell which stage failed, how to fix each stage’s common causes, and the alternative paths when the tool itself refuses to cooperate.
Why this happens
- Corrupted tool download: The Media Creation Tool executable itself downloaded incompletely and misbehaves from the start.
- Broken Windows Update services: The tool relies on the same BITS and update services as Windows Update, and their failure breaks downloads.
- Antivirus quarantining files: Security software flags or locks downloaded installer files mid-assembly.
- Insufficient permissions: The tool lacks write access to its working folders or the target USB drive.
- Failing USB drive: Bad flash memory corrupts writes, producing file-not-found errors during the media creation stage.
- Corrupted system files: Damaged servicing components on your laptop break the download and verification pipeline.
- Network interference: Proxies, VPNs, or unstable connections corrupt large downloads silently.
- Insufficient disk space: The tool needs several gigabytes of working space beyond the final USB image.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Identify which stage failed
- Note exactly when the error appears: during the download percentage, during verification, or during USB writing. Each stage points at different fixes below.
- Download-phase failures implicate services, network, or antivirus. USB-phase failures implicate the drive or permissions.
- If the tool fails instantly on launch, the executable itself is likely corrupt. Re-download it before anything else.
- Write down the stage. This two-minute observation prevents you from fixing the wrong half of the pipeline.
Fix 2: Re-download the Media Creation Tool cleanly
- Delete the existing Media Creation Tool executable completely.
- Download a fresh copy from the Windows 11 download page , preferably in a different browser or with extensions disabled.
- Right-click the new file, choose Run as administrator, and accept the license terms.
- A surprising number of 0x80070002 cases are simply a damaged tool binary. Fresh downloads with admin rights clear them immediately.
Fix 3: Repair the Windows Update services
- The tool downloads through BITS and the update stack. Open an admin Command Prompt and run
net stop bitsandnet stop wuauserv. - Rename
C:\Windows\SoftwareDistributiontoSoftwareDistribution.old, then restart both services withnet startcommands. - Verify the Background Intelligent Transfer Service is running in
services.mscwith startup type Manual. - Retry the tool. When downloads were failing because the underlying services were broken, this repair unblocks them. The update service troubleshooting guide covers deeper service damage.
Fix 4: Temporarily disable antivirus and firewall
- Turn off real-time protection in your antivirus, or in Windows Security under Virus & threat protection > Manage settings.
- If you run a third-party firewall, disable it temporarily as well. Overzealous firewalls can interrupt the tool’s large downloads mid-stream.
- Re-run the Media Creation Tool with protection paused. Many 0x80070002 failures vanish the moment scanning stops interfering with downloaded chunks.
- Re-enable everything afterward. If antivirus was quarantining tool files, add the tool’s folder to exclusions before your next attempt.
Fix 5: Run from a clean local account with full permissions
- Create a temporary local administrator account in Settings > Accounts > Other users and sign into it.
- Copy the Media Creation Tool to the desktop of the new account and run it as administrator from there.
- Profile-specific corruption, broken permissions, or misconfigured user folders in your main account can all produce file-not-found errors that vanish in a clean profile.
- If the tool works in the new account, your main profile has the problem. You can migrate to the new profile or repair the old one’s permissions.
Fix 6: Try a different USB drive
- If the error hits during the USB writing stage, the drive is suspect. Use a different USB stick with at least 8 GB capacity from a known brand.
- Format it as FAT32 before starting, using Disk Management or the format option in File Explorer.
- Avoid USB hubs for this operation. Plug the drive directly into the laptop, preferably into a USB port on the opposite side from the one that failed.
- If you only need an upgrade rather than bootable media, choose the ISO option instead and mount it directly, skipping USB entirely.
Fix 7: Repair system files and free space
- Run
sfc /scannowin an admin Command Prompt to repair protected system files the tool depends on. - Follow with
DISM /Online /Cleanup-Image /RestoreHealthto fix the component store. - Ensure at least 15 GB free on the system drive. The tool stages the full Windows image locally before writing media.
- Disconnect from VPNs and disable proxy settings during the download. Direct connections produce the cleanest large downloads. Microsoft documents the tool’s requirements on the Windows support hub .
Fix 8: Use the alternatives that bypass the tool
- For an in-place upgrade, download the Windows 11 Installation Assistant from the same Microsoft download page and run it instead.
- For bootable media, download the ISO directly from Microsoft’s site, right-click it, and choose Mount, then run
setup.exefrom the virtual drive. - For stubborn update failures that drove you to the tool in the first place, the standalone KB installer from the Microsoft Update Catalog may be all you needed.
- If the underlying problem is a failing feature update rather than the tool, the 23H2 failure fix guide addresses that directly.
Closing
Media Creation Tool error 0x80070002 is a file-pipeline problem, and the fix depends on which stage breaks: re-download the tool for launch failures, repair update services for download failures, and swap the USB drive for media failures. When the tool itself will not cooperate, the Installation Assistant and direct ISO downloads get you to the same destination by a different road.
