Fix ERROR_CANNOT_COPY (0X0000010A) on Windows 10/11

You’re copying a file from a network share—say, a mapped drive at work or a USB hard drive plugged into your router—and halfway through, Windows pops up: ERROR_CANNOT_COPY (0X0000010A). The copy just stops. You try again, same thing. Maybe the file is small, maybe it’s huge, but the result is always the same: Windows tells you the copy functions cannot be used.

I’ve seen this most often with:
- A mapped network drive that’s been idle for a while
- A USB 3.0 external drive connected through a hub
- Copying from an older NAS (Network Attached Storage) device
- And sometimes, a corrupted file in the middle of a batch copy

The root cause is almost always a communication hiccup between Windows and the source device. The file system on the source gets confused—maybe the connection dropped for a second, or the device went to sleep, or there’s a permissions mismatch. Windows then refuses to proceed because it can’t guarantee the data is coming through cleanly.

Let’s fix it. I’ll give you the steps I use on every help desk call. Start with step 1; skip to step 3 if you’re in a hurry and already tried a reboot.

Step 1: Disconnect and reconnect the source

1. If it’s a USB drive, safely eject it (right-click the drive in File Explorer > Eject). Then unplug it physically.
2. Wait 10 seconds. Plug it back in. After the USB chime, check if the drive shows up in File Explorer.
3. If it’s a network drive, disconnect the mapped drive: open File Explorer, right-click the drive > Disconnect.
4. Reconnect it: open File Explorer, right-click This PC > Map network drive. Pick a drive letter, type the path (like \server\share), check Reconnect at sign-in, and click Finish.
5. Try copying the file again. If the error is gone, you’re done. If not, move to step 2.

Step 2: Copy in smaller batches

Sometimes the issue is just that Windows chokes on a large transfer. Cut the job into pieces.

1. Instead of copying the whole folder, copy one file at a time. Start with the smallest file.
2. If one specific file fails every time, that file is probably corrupt. Skip it or download it fresh from the source.
3. If you’re moving a folder, drag individual files—not the entire folder—to the destination.
4. After each successful file, wait a second before starting the next one.

Step 3: Use robocopy (the real fix)

The built-in Windows copy dialog is fragile. robocopy is tougher and handles interruptions better. I use it all the time for network copies.

1. Open Command Prompt as administrator: press Win + R, type cmd, right-click it, and choose Run as administrator.
2. Type this command, changing the paths to your source and destination:
   

   robocopy "C:\source" "D:\destination" /E /R:3 /W:5

   Replace C:\source with your source folder, D:\destination with where you want it. /E copies subfolders. /R:3 retries 3 times on failure. /W:5 waits 5 seconds between retries.
3. Press Enter. You’ll see a live progress report. If robocopy finishes with “ERROR 5” or something, move to step 4.

Step 4: Run the SFC and DISM tools

If even robocopy fails, Windows system files might be damaged. This is less common but happens after a bad update.

1. Open Command Prompt as administrator again (same as step 1 of step 3).
2. Run System File Checker:
   

   sfc /scannow

   Wait until it finishes (usually 5-15 minutes). It will say if it fixed anything. After it’s done, restart your PC.
3. If SFC found nothing, run DISM:
   

   DISM /Online /Cleanup-Image /RestoreHealth

   This takes longer—maybe 20 minutes. Let it finish. Restart again.
4. Try copying the file again using the normal method or robocopy.

Step 5: Check file permissions on the source

On a network drive, the account you’re signed into might not have full read access to every file. This triggers the 0X0000010A error on some files.

1. Go to the source file or folder on the network share. Right-click it > Properties > Security tab.
2. Check if your username or a group you belong to (like Domain Users) appears in the list.
3. If not, click Edit > Add, type your username, then allow Read & execute. Click OK.
4. If you can’t change permissions (because you’re not the admin of the share), contact the person who manages that server.

What to check if it still fails

If you’ve done all five steps and the error still shows up, it’s time to be more aggressive. Here’s what I check next:

• Antivirus real-time scanning: Temporarily disable your antivirus (just during the copy), then try again. I’ve seen AV software block network file transfers for no good reason. Re-enable it right after.
• Third-party shell extensions: Programs like Dropbox, Google Drive, or OneDrive that add overlay icons in File Explorer sometimes corrupt the copy operation. Uninstall the shell extension (look in Programs and Features) and restart.
• Hardware cable or port: For USB drives, try a different port—especially a port directly on the motherboard, not through a hub. For network drives, check the Ethernet cable or switch.
• Source device health: On a USB drive, run chkdsk X: /f (replace X with the drive letter) to fix file system errors. On a NAS, run its manufacturer’s disk check.
• Last resort: Use a third-party copy tool like TeraCopy or FastCopy. They often handle the 0X0000010A error where Windows fails. It’s not a real fix, but it gets the job done.

The 0X0000010A error is stubborn, but 9 times out of 10, step 1 (reconnecting the source) or step 3 (robocopy) clears it. Don’t let it slow you down too long.