0x8007007B

Fix 'Cannot Copy File Path Too Long' Error on Windows

Hardware – Hard Drives Beginner 👁 12 views 📅 Jun 20, 2026

Windows can't copy files with paths over 260 characters. Quick fix is to shorten the path or enable long path support in Windows 10/11. Happens a lot with deep folder structures.

Quick answer: Shorten the file or folder name, or move the file to a location with a shorter path (like C:\temp). If that fails, enable long file path support in Windows 10/11 via Group Policy or Registry.

Why This Error Happens

Windows has a dumb limit from the DOS days: file paths can't be more than 260 characters. That includes the drive letter, folders, and file name. So if you have something like C:\Users\John\Documents\Projects\2025\Client Reports\Q1\Final\subfolder\really-long-filename-here.docx, you're way over that limit. This error shows up when you try to copy, move, or delete the file. I had a client last month whose entire legal folder structure was 500+ characters deep. Every time they tried to back up, Windows screamed “cannot copy file path too long.” Drove them crazy.

Step-by-Step Fix

  1. Shorten the path manually. Right-click the file or folder and rename it to something short like "x.docx" or "temp". Or move the file to a root folder like C:\temp. This is the fastest fix. Remove spaces and special characters—they count toward the limit.
  2. Use Robocopy. Open Command Prompt as admin and run this:
    robocopy C:\source\folder D:\destination /E /COPYALL /R:0 /W:0
    Robocopy ignores the 260-character limit. It's a built-in tool. I use it all the time for deep directory structures.
  3. Enable long paths in Windows 10/11.
    • Press Win+R, type gpedit.msc (Pro/Enterprise only) and hit Enter.
    • Go to Computer Configuration > Administrative Templates > System > Filesystem.
    • Double-click "Enable Win32 long paths" and set it to Enabled.
    • Click OK and restart your PC.
    If you don't have Group Policy Editor (Home edition), use Registry:
    • Press Win+R, type regedit and hit Enter.
    • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
    • Find LongPathsEnabled, set its value to 1.
    • Restart.

Alternative Fixes

If the main fix doesn't work—maybe you can't rename because it's a system file—try these:

  • Use a file manager like 7-Zip. Open 7-Zip and drag the folder to a new location. It bypasses the path limit. Works like magic.
  • Map a network drive. If the file is on a server, map a drive to a short folder path and copy from there. For example, map \\server\share\short to Z: and then copy.
  • Create a symbolic link. Run mklink /J C:\shortlink D:\long\path\of\death in an admin Command Prompt. Then copy from C:\shortlink. This works for moving files too.

Prevention Tips

To avoid this headache in the future:

  • Keep folder names short. Use "2025Q1" instead of "2025 Quarter 1 Financial Reports".
  • Don't nest folders more than 4-5 levels deep. Flat structures are easier to manage anyway.
  • Enable long paths on all office PCs from the start. Takes 2 minutes and saves hours.
  • Use a naming convention with underscores instead of spaces—underscores don't count extra bytes.

And if you're backing up to cloud storage, some services like Google Drive or OneDrive have their own path limits (usually 400 characters). Plan ahead. I learned that the hard way with a client's Dropbox sync.

Was this solution helpful?