Yeah, I've seen this one a lot. It's annoying as hell. But here's the thing — 80% of the time, you can fix it in under a minute by clearing Explorer's thumbnail and icon cache. Let's get to it.
The Quick Fix: Clear Explorer Cache
Open File Explorer, then go to this folder:
%LocalAppData%\Microsoft\Windows\ExplorerIn there, you'll see files like iconcache_32.db, thumbcache_256.db, and similar. Close all File Explorer windows first, then select them all and hit delete. If Windows says they're in use, open Task Manager, right-click Windows Explorer, and select Restart, then delete them again.
After that, restart your PC or just relaunch Explorer. Try copying the file again. This clears out the cached metadata that's often corrupted and causing the false error.
I've fixed this exact issue on a hundred machines with this simple step. Don't skip it.
Why This Works
Windows stashes thumbnail and icon data in those .db files. When they get corrupted — usually after a crash, a forced shutdown, or a weird USB eject — Explorer starts throwing phantom errors. The file itself might be perfectly fine, but Windows thinks it can't read it because the cached info is junk. Clearing the cache forces a fresh read.
When That Doesn't Do It
If you're still seeing the error, it's not the cache. Try these in order.
1. Check File Attributes
Right-click the file, select Properties, and uncheck Read-only and Hidden if they're checked. Sometimes a file gets marked read-only by an old backup or a sync client like OneDrive, and Windows gets confused about permissions.
2. Copy to a Different Location
Try copying to your Desktop or a different drive. If it works there, the problem is the destination folder. That folder might have a corrupted index or a permission issue. Create a new folder on the same drive and try again.
3. Use Robocopy
If the file is huge or the copy keeps failing halfway, use robocopy from an elevated Command Prompt:
robocopy "C:\source" "D:\destination" "filename.ext" /R:3 /W:5Robocopy handles retries better than Explorer's built-in copy. It won't give up at the first hiccup.
4. Run SFC and DISM
This is the slower route, but it's worth it if the issue spans multiple locations. Open Command Prompt as administrator and run:
sfc /scannowThen, after that finishes, run:
DISM /Online /Cleanup-Image /RestoreHealthThese check for system file corruption that might be affecting file operations globally. I've seen DISM fix weird Explorer behavior that SFC alone missed.
Less Common Variations
Sometimes the error appears only with specific file types — like HEIC photos or AVIF images. That's a codec issue. Windows can't read the file to create a thumbnail, so it assumes the whole copy is broken. Install the HEIF Image Extensions from the Microsoft Store. Same goes for Raw files from cameras — install the manufacturer's codec pack.
Another variant: the error shows up when copying from a network drive or a phone connected via MTP. That's usually a driver or connection issue. Update your network adapter driver or try a different USB cable. MTP is finicky, so if possible, use adb pull for Android devices — it's way more reliable.
Prevention: Stop It Before It Starts
You can't avoid every corrupted cache, but you can reduce the odds.
- Shut down properly. Force-shutting down during heavy file operations is a one-way ticket to cache corruption. Give it a few extra seconds.
- Eject USB drives safely. I know you're impatient, but that "Safely Remove Hardware" icon exists for a reason. Yanking a drive mid-transfer corrupts more than just the file — it corrupts Explorer's view of it.
- Keep your system clean. Run
sfc /scannowmonthly and clear your temp files. It's boring, but it works.
Most people don't need anything beyond the cache clear. That's your first move, and it'll be your last 8 out of 10 times.