Fix "Cannot Copy File to Destination" in Windows 11/10

If Windows says it "cannot copy file to destination" and won't tell you why, the fix is almost always one of five things: the full file path is longer than 260 characters, the destination is out of space, the file name has a character Windows won't accept, the drive is formatted FAT32 (4 GB per-file limit), or a stuck antivirus scan is holding the file open. Try them in that order and you will clear this in under ten minutes. Here is the part almost nobody mentions: Windows has quietly been able to handle much longer file paths for years now — the 260-character wall you are hitting is not a hardware or filesystem limit at all. It is a setting, switched off by default, that Microsoft has never turned on for you.

Jake found this out the expensive way. A customer dropped off an old phone and asked him to pull four years of photos and videos onto a USB drive before trading it in. Jake plugged the phone in, dragged the whole camera folder across — and about a third of the way through, Windows stopped with "cannot copy file to destination directory," no further explanation, no obvious pattern to which files failed. He restarted the PC, tried again, got the same wall at a different file. Two hours and a very unhappy customer later, he called Ethan.

"The message is basically Windows shrugging," Ethan told him. "It's the single least informative error box Microsoft ships, and it covers at least six completely unrelated problems. Restarting fixes none of them — it only ever looked like it worked because you picked a different, shorter-named file on the second try."

Which cause is yours? A 30-second triage

Before you touch anything, look at what the failing files have in common. It narrows this down fast.

Fixing it on Windows 11

Work through these in order — they're arranged from "takes thirty seconds" to "takes longer but catches everything else."

1. The path is over 260 characters

Windows counts the entire path, not just the file name — the drive letter, every folder you clicked through, and the file name all get added together, and anything past roughly 260 characters gets rejected by programs that haven't been told to expect longer ones. It happens more than people expect because phone backups and cloud-synced folders love deeply nested, auto-generated folder names: C:\Users\Jake\Downloads\WhatsApp Images\Backup_2026\Camera_Roll_Export\IMG_20260714_143022_HDR_edited_final_v2.jpg adds up fast without anyone typing anything unusually long.

There are two ways to deal with it, and you don't need both:

The fast way, no settings changed: move the file (or the whole folder) two or three levels closer to the drive root before copying — onto the Desktop, or into a plain C:\Temp folder you create yourself — then copy from there. Shortening the path is often quicker than the fix below, especially for a one-off.

The permanent fix, once, for good: tell Windows to stop enforcing the old 260-character limit. Press Win + R — that's the Run box, a small "type a command and press Enter" window that's been part of Windows for decades and still the fastest route to anything buried in Settings. Type regedit and press Enter. You'll get a User Account Control prompt asking permission — that's normal, click Yes.

The Registry Editor that opens is where Windows stores its low-level configuration. You're only going to change one value, so don't go exploring elsewhere. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, find the value named LongPathsEnabled in the right-hand pane, double-click it, and set it to 1.

Restart the PC. Long paths are now allowed system-wide for programs that support the setting, which includes File Explorer.

On Windows 11 Pro, you can do the same thing without the registry: press Win + R, type gpedit.msc — the Group Policy Editor, a Pro-and-above tool for changing system settings that don't have a Settings-app toggle — and go to Computer Configuration > Administrative Templates > System > Filesystem, then enable "Enable Win32 long paths." Same result, different door.

2. The destination is out of space

Right-click the destination drive in File Explorer and choose Properties to see free space at a glance. Windows also needs headroom beyond the raw file size — on some file systems it briefly stages parts of a large copy, so a drive sitting at "just barely enough" can still fail mid-copy even though the numbers looked fine. If you're down to a few hundred megabytes free, that's very likely your answer, not corruption.

3. The file name has a character Windows won't allow

Windows file names can't contain \ / : * ? " < > |, and can't end in a space or a period. Files that arrived from a phone, a Mac, or a website sometimes carry one of these without you noticing — a colon in a timestamp, a trailing space auto-added by an export tool. Rename the file to strip the offending character (or just rename it to something plain, like test.jpg) and try the copy again. If it goes through, that confirms the cause and you can rename it back to whatever's usable, minus the bad character.

If renaming doesn't fix it, the file itself may be the problem, not its name — skip ahead to corruption and failing drives.

4. The drive is formatted FAT32 and the file is over 4 GB

This one is worth knowing cold because it looks exactly like every other version of this error, and it's extremely common on USB sticks and older SD cards. FAT32 — an older file system still used as the default on a lot of budget flash drives because it's readable by almost anything, including game consoles and car stereos — cannot store a single file larger than 4 GB, full stop, no workaround. A single long 4K video or a large backup archive will trip this every time, on any version of Windows.

Check the format: right-click the drive in File Explorer > Properties, and look at "File system." If it says FAT32 and your file is close to or over 4 GB, that's it. The fix is to reformat the drive as exFAT (right-click > Format > File system: exFAT), which removes the 4 GB ceiling and still works across Windows, macOS, and most modern devices.

5. Security software is holding the file open

Real-time antivirus scanning intercepts files as they're written. On a slower machine or a very large batch, a scan can genuinely still be locking a file when Explorer tries to finish writing it — and Explorer reports that as a generic copy failure.

Pause real-time protection for a few minutes (every major antivirus has a "pause protection" option in its own app, not in Windows Settings) and try the copy again. If it goes through, don't leave protection off. Turn it back on, and instead exclude the specific destination folder from scanning if you do this kind of large transfer often.

6. File system corruption or a failing drive

If none of the above explains it — especially if it's random files, on a source drive that's making noise, running hot, or has failed before — run chkdsk against the source drive. Open the Start menu, type cmd, right-click Command Prompt and choose "Run as administrator" (Windows 11 sometimes shows this as an option inside "Show more options" — see the UI traps section below), then run chkdsk C: /f /r for your system drive, or substitute the correct letter for an external one. It will likely ask to schedule the scan for next restart if the drive is currently in use; type Y and restart. This checks the drive's internal bookkeeping and file structure and repairs what it safely can.

Also worth running: sfc /scannow in the same administrator Command Prompt, which checks Windows's own system files for corruption — unrelated to your drive's file system, but a common secondary cause of odd copy failures on a PC that's been crashing or losing power unexpectedly.

Windows 11 UI traps that get in the way

A few things about Windows 11's redesigned interface trip people up while working through the steps above:

The right-click menu is condensed by default. Right-clicking a file or folder in Windows 11 shows a short row of icons plus a shortened list, and options like "Run as administrator" for some items live under Show more options at the bottom (or hold Shift and right-click, which shows the full classic menu directly).

File Explorer opens to "Home," not a folder you chose. Home mixes pinned folders (labeled Quick access), pinned files (Favorites), and Recent files in one scrolling view. If you're navigating to C:\ to create a Temp folder for the path-length workaround, click "This PC" in the left sidebar first.

Fixing it on Windows 10

Every method above works identically on Windows 10 — same registry key, same chkdsk command, same FAT32 limit, same antivirus behavior. The only differences are cosmetic: Windows 10's right-click menu is the full classic list already, with no "Show more options" step to hunt for, and File Explorer opens to "Quick access" rather than "Home." Everything else in the steps above applies exactly as written.

If you're still on Windows 10 for now, that's a fine reason to be extra careful about the drive-health causes above — you're not getting new security patches, so a corrupted file system is one more thing worth catching early with chkdsk rather than working around indefinitely.

What it looks like when the fix doesn't work

Knowing what failure looks like at each step saves you from repeating a fix that was never going to work:

You set LongPathsEnabled to 1 and restarted, but it still fails on the same file. That file's path probably wasn't actually the cause — go back to the triage table and check free space and file system next. Long paths enabled doesn't help a full drive.

You ran chkdsk and it reports "Windows has made corrections" but the same file still won't copy. Chkdsk repairs the file system's bookkeeping; it can't un-corrupt a file whose actual data is already damaged. Try opening that specific file directly (a photo that won't open, a video that won't play) — if it won't open on its own, it's the file, not the copy process, and you're looking at recovering it from a backup or a recovery tool rather than fixing the transfer.

Chkdsk keeps finding new errors every time you run it, or the drive disappears and reappears in File Explorer. That pattern points at failing hardware, not a fixable file system issue. Stop copying to or from that drive as your primary step, copy whatever you can reach onto a different drive immediately, and treat the original as unreliable from here.

Advice you'll see that doesn't actually help

"Just restart your computer" is the most repeated advice for this error, and it's almost never the actual fix — what usually happens is you restart, try again, and either pick a different (shorter, smaller) file without realizing it, or the antivirus scan that was holding a file has since finished on its own. The restart gets the credit; the real cause was one of the six above.

"Copy fewer files at a time" is another one that treats a symptom instead of a cause. It can dodge the destination-space problem by luck, but it does nothing for path length, FAT32's 4 GB ceiling, or a bad character in a name — you'll just hit the same wall on a smaller batch.

The next thing you'll need: copying without babysitting it

Once the underlying cause is fixed, the next question people ask is how to move a large batch of files without standing there watching for the next failure. Windows has a built-in answer that most people never touch: Robocopy, a command-line copy tool that's been part of Windows for years, built specifically to survive exactly this kind of interruption. Unlike a normal drag-and-drop, it can resume a failed batch instead of restarting from file one, skip files it can't copy and log them for you instead of stopping the whole job, and it handles long paths natively without needing the registry change above for its own operation.

A basic example, run from an administrator Command Prompt: robocopy "C:\source folder" "D:\destination folder" /E /R:3 /W:5 — /E copies subfolders including empty ones, /R:3 retries a failed file three times before giving up on it and moving on, and /W:5 waits five seconds between retries, which is usually enough for a brief antivirus lock to clear on its own.

Third-party tools: worth it or not

You'll see copy-manager utilities like TeraCopy and FastCopy recommended for exactly this problem. They do add real value — a persistent queue, pause-and-resume, and a clearer error report than Explorer gives you — and if you move large files often, one is a reasonable install. But they don't fix any of the six causes above; they just report failures more clearly and let you retry without restarting the whole batch. If your actual cause is the FAT32 4 GB limit or a genuinely corrupted file, a nicer error dialog doesn't change the outcome. Fix the real cause first; add a copy manager afterward if the volume of transfers justifies it.

Automating it so you never babysit a copy again

If Jake's shop does this kind of transfer every week — pulling photos off a trade-in phone, backing up a customer's old drive before a repair — it's worth setting Robocopy up once instead of retyping the command every time. Task Scheduler, the built-in Windows tool for running a command automatically on a schedule or trigger, can run the same Robocopy line on its own.

Open Task Scheduler (type task scheduler in the Start menu), choose "Create Basic Task" in the right-hand panel, give it a name, and pick a trigger — "When I log on" is the simplest option for a shop PC that gets used daily. On the Action step, choose "Start a program," put robocopy in the Program field, and put your source, destination, and flags in the Arguments field, for example "C:\Incoming" "D:\Backups" /E /R:3 /W:5 /LOG+:C:\Temp\copylog.txt. The /LOG+: flag appends every run's results to a text file instead of just flashing a window and disappearing, so you can check what happened after the fact without watching it run.

One flag worth knowing but using carefully: /MIR makes the destination an exact mirror of the source, deleting anything in the destination that no longer exists in the source. That's genuinely useful for keeping a backup folder in sync, but it means a mistake in the source folder gets copied into your "backup" too. Don't reach for /MIR until you've run the same command with /E a few times and trust the folders you've pointed it at.

Before you copy sensitive files to a shared or external drive

If this error happened while you were backing up someone else's files — a customer's phone, a shared family drive — it's worth a second's thought before you hand the drive back. A USB stick with no password protection is readable by anyone who plugs it in. Windows 11 and 10 Pro can encrypt a whole drive with BitLocker; Home editions get Device Encryption automatically on most modern PCs, but that protects your internal drive, not a USB stick you're handing to someone else. For anything genuinely sensitive going onto removable media, a drive with hardware encryption or at minimum a password-protected archive is the safer habit.

Edge cases worth knowing about

Copying to or from a cloud-synced folder

If your source or destination folder lives inside OneDrive, Google Drive, or Dropbox, and files there are set to "free up space" (stored only in the cloud, not actually on your disk), Explorer has to download the full file before it can copy it — a slow connection can make that look identical to a stuck copy. Right-click the folder and choose "Always keep on this device" before a large transfer if this applies to you.

Copying over a network or Remote Desktop session

The same six causes apply, plus one more: a dropped or slow network connection can produce the identical generic error. If it's a network drive, try the same copy locally first (drive to drive on the same PC) to rule the network out before chasing the other causes.

Copying inside a virtual machine

Drag-and-drop between a host PC and a VM depends on the VM's guest tools/additions being installed and up to date; if drag-and-drop is flaky in a VM, copy through a shared folder instead of drag-and-drop, which is more reliable and gives you the same "cannot copy" error reporting as a normal local copy if something's actually wrong with the file.

No admin rights on the PC

If it's a work or school PC and you can't open Registry Editor or an administrator Command Prompt, you don't have the permissions for the LongPathsEnabled fix or chkdsk. The path-shortening workaround (move the file closer to the drive root before copying) still works without admin rights, and is your best first move on a locked-down machine.

Quick reference: which method, and when

Frequently asked questions

Is "cannot copy file to destination directory" the same error as "file too large for destination"?

No, though they're easy to confuse. "File too large for destination" is Windows's specific message for the FAT32 4 GB limit and it names the cause directly. "Cannot copy file to destination directory" is the generic version, used for the other five causes above, which is exactly why it's harder to diagnose.

Will enabling long paths in the registry cause any problems later?

For the vast majority of people, no — File Explorer, PowerShell, and current mainstream software handle it fine once enabled. The rare exception is older, unmaintained desktop software that assumes the 260-character limit; if you hit an odd error in one specific old program after making the change, that program is the exception, not a sign the setting itself is broken.

Can I just turn off User Account Control instead of dealing with admin prompts?

You can, but don't for this. User Account Control is what stops a lot of malware from silently making system changes; turning it off to save a few clicks trades a minor inconvenience for a real, ongoing security downgrade. Click "Yes" on the prompts instead.

My external hard drive shows the wrong free space or won't let me format it. What now?

That combination — incorrect reported capacity plus a format that won't complete — usually points at a failing or counterfeit drive rather than anything you did. Copy off whatever you can reach immediately and don't rely on that drive going forward.

Does this happen on Mac or only Windows?

macOS has its own path-length limits and its own version of this error, but the causes and fixes here are Windows-specific — the registry key, chkdsk, and the exact 260-character number don't apply on a Mac.

Why does it fail on my PC but the same drive works fine on someone else's computer?

If the other PC already has long paths enabled, or simply has more free space, or is running different (or no) antivirus, it can succeed where yours fails on the exact same drive and files. This is a very reliable sign your cause is one of the settings above, not the drive or files themselves.

Is it safe to just keep retrying the same copy?

It's not dangerous, but it wastes time on causes that a retry can't fix — path length, FAT32's limit, and a genuinely corrupted file will fail identically every time you retry without changing anything. Retrying is only worth trying first for a possible antivirus lock, where a short wait can genuinely resolve it.

Does Safe Mode fix this?

Sometimes, indirectly — Safe Mode starts Windows with most third-party software, including antivirus, disabled, so if a security tool is your actual cause, copying in Safe Mode can work around it. It's not a real fix though; you're just temporarily removing the thing that was blocking you, and you'll want to identify which antivirus setting caused it once you're back in normal mode.

I don't have Windows 11 Pro. Does the Group Policy method matter to me?

No — skip it entirely. The Group Policy Editor is Pro/Enterprise/Education only; Home edition doesn't have it. The registry method (LongPathsEnabled) does the identical job and works on every edition, including Home, so it's the one to use if you're not sure which edition you have.

Can a full System Restore or reinstalling Windows fix this?

It can accidentally fix an antivirus-related cause by removing the software that was interfering, but it does nothing for path length, FAT32's limit, destination space, or a damaged file — and it's a lot of disruption for something a single registry value usually solves in under a minute. Save it as a last resort, not a first move.

Why did this never happen to me until recently?

The most common trigger is a change in what you're copying, not a change in Windows: phones now generate longer, more deeply nested file and folder names in their backups than they used to, and video files have grown well past the 4 GB mark that used to be rare. The underlying limits haven't moved; what you're copying has grown into them.

Should I just copy files one at a time to avoid this entirely?

It can dodge the error by luck on any single attempt, but it doesn't fix anything, it's much slower for a real batch, and you'll still hit the same wall on whichever file actually has the underlying problem. Fixing the real cause once is faster than babysitting every individual file forever.

What does Robocopy's log actually tell me that Explorer doesn't?

Explorer just stops and shows one error box. Robocopy keeps going, records exactly which files it couldn't copy and why, and finishes the rest of the batch instead of aborting the whole job over one bad file — which is the main reason it's worth learning for anything more than a handful of files.

Revision note. Originally published May 24, 2016, as a video-only walkthrough for Windows 10. We had republished on August 17, 2026, covering Windows 11 alongside Windows 10 for the first time, with Windows 10 now past its October 14, 2025 end-of-support date. The causes behind this error haven't really changed in ten years — what's changed is how often people hit them, as phones and cameras have quietly outgrown the limits Windows was built around. If you're still stuck after working through this, you're not missing something obvious; this error has always been unusually bad at explaining itself, and that's on Windows, not on you.