The "path too long," "file name too long," and "destination path is too long" errors all share one root cause: Windows' 260-character path limit. This guide covers five ways to fix them — from quick manual workarounds to the fastest bulk solution for drives with dozens or hundreds of problem paths.
Windows uses a legacy path length limit inherited from early versions of the NTFS file system. The practical limit for most file operations is 260 characters for any absolute path — meaning the full string from the drive letter to the file name, including every backslash and folder name in between.
The limit compounds quickly. A folder structure like this:
…is 153 characters at the root. Add a few more nested folders, and you're over the limit before the file name is even long. This is especially common in:
Legal and government archives — full department names, case numbers, and date-based folder hierarchies
Network and SharePoint-synced drives — where paths are often longer than local equivalents
Migrated file systems — when folders from a flat structure are imported into a deeply nested new one
IT environments — where years of inconsistent naming conventions accumulate into unmanageable paths
When a path exceeds the limit, Windows returns errors like "path too long," "file name too long," "the file name you specified is not valid or too long," or "destination path is too long." The affected files cannot be opened, copied, moved, or deleted through Windows Explorer or the command line.
Windows 10 (version 1607+) and Windows 11 include a registry setting that allows the Windows API to handle paths up to 32,767 characters. Enabling it removes the system-level restriction for applications that are programmed to use the extended-length path API.
Press Win + R, type regedit, and press Enter.
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Find the value named LongPathsEnabled and double-click it.
Change the value from 0 to 1 and click OK.
Restart Windows for the change to take effect.
Important limitation: This setting only helps applications that explicitly opt in to the extended path API. Most older applications, Windows Explorer, and the standard Command Prompt will still hit the old limit. It also does not shorten existing paths — files that are already over 260 characters remain inaccessible until the path itself is shortened.
If you're on Windows 10/11 Pro or Enterprise, you can make the same change through the Local Group Policy Editor — useful for enforcing the setting across multiple machines in a domain environment.
Press Win + R, type gpedit.msc, and press Enter.
Navigate to: Local Computer Policy → Computer Configuration → Administrative Templates → System → Filesystem
Find "Enable Win32 long paths" and double-click it.
Select Enabled and click OK.
Run gpupdate /force in Command Prompt or restart Windows.
Same limitation applies: Group Policy makes the same underlying change as the registry edit — it enables the API flag, but does not fix existing long paths. Files that are already inaccessible remain inaccessible.
The SUBST command lets you assign a drive letter to a deeply nested folder, effectively shortening the path from that point onward. This is useful for accessing or copying specific files without needing admin rights or renaming anything.
Limitation: SUBST mappings are temporary — they are removed when you restart Windows. This method is good for accessing a specific stuck file, but is not practical for fixing a drive full of long paths. The underlying paths remain unchanged.
For a small number of problem paths, the most direct fix is to rename the offending folders and files so that the total path drops below 260 characters. Start from the shallowest level (the folders closest to the root) and work inward — shortening a parent folder shortens every child path in it simultaneously.
In Windows Explorer, navigate to the problem folder (you may need to use short paths or SUBST to reach it).
Right-click the shallowest folder with a long name and choose Rename.
Shorten the name — e.g. "Department of Justice" → "DOJ".
Work inward through subfolders until all paths are under 260 characters.
Limitation: On a drive with hundreds or thousands of long paths, this approach is impractical. It also requires you to already know which paths are too long — finding them is half the work. For bulk fixes, Method 5 is far faster.
LPFE was built specifically for this problem. It scans your entire drive (local or network), surfaces every path over 260 characters, and lets you apply renaming rules in bulk — with a full live preview before anything is changed. No registry edits. No admin rights required for scanning.
Add your folder. Click "Add Folder" and select any root directory. LPFE recursively scans every subfolder and file and flags anything over the limit in red.
Set your rules. Toggle rules like "Remove Spaces," "Remove Brackets," or load a Find/Replace text file to replace long phrases like "Department of Justice" with "DOJ" automatically across every path.
Preview the changes. The "Proposed Path" column updates live as you adjust rules — you see the exact before-and-after for every file before touching your disk.
Commit. Click "Commit Changes." LPFE renames shallowest-first, automatically. A CSV log is written. Undo is always available.
Free trial includes all 9 rules, capped at 25 entries. Full version is $49 one-time — no subscription, ever.
Download Free →| Method | Fixes existing paths? | Admin required? | Works at scale? | Best for |
|---|---|---|---|---|
| Registry / Group Policy | No | Yes | Partial | Future-proofing for new apps |
| SUBST command | No (workaround) | No | No | Accessing one stuck file |
| Manual renaming | Yes | No | No — very slow | 1–5 problem paths |
| LPFE (bulk tool) | Yes | No | Yes — entire drives | IT cleanup, large archives, network drives |
Windows limits any file or folder path to 260 characters. When a path exceeds this limit — often from deeply nested folders or long folder names — you get a "path too long" error and cannot open, copy, move, or delete the affected file through normal means.
If you don't have admin rights, your best options are: (1) Map the deep folder to a shorter drive letter using the SUBST command in Command Prompt, or (2) Use a long path tool like LPFE that doesn't require system changes — it renames the files and folders themselves so the path falls within the limit. LPFE does not require admin rights to scan and rename files.
Enabling the LongPathsEnabled registry key allows Windows APIs to handle paths up to 32,767 characters, but only for applications that explicitly opt in to the extended-length path API. It does not fix existing paths that are already too long, and most applications — including Windows Explorer — will still hit the old limit. For a permanent fix, you need to shorten the actual paths.
The Windows API path limit (MAX_PATH) is 260 characters — this counts the drive letter, every folder name, every backslash, and the terminating null character, leaving 259 usable characters for the path itself. Individual file or folder names within that path are limited to 255 characters each. These limits apply to the full absolute path, so deeply nested folders compound quickly.
Yes. LPFE scans both local and mapped network drives. You point it at any root folder — including a drive letter mapped to a network share — and it walks the entire tree, finds every violation, and lets you rename paths in bulk with a full preview.