To enable long file paths in Windows 10 or 11, open the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, and set the LongPathsEnabled value to 1. This removes the 260-character MAX_PATH limit that Windows has enforced since its early days, letting you work with deeply nested folder structures without hitting path-too-long errors.
Applies to: Windows 10 (1607 and later, including 22H2) and Windows 11 (23H2, 24H2, 25H2) | Last updated: May 27, 2026
Key Takeaways
- Windows caps file paths at 260 characters by default — this is the MAX_PATH limit that dates back to early Windows versions and causes errors when working with deeply nested folders
- The fix is a single registry value: set
LongPathsEnabledto1atHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - Works on Windows 10 version 1607 and all Windows 11 versions — once enabled, paths up to 32,767 characters are supported
- Windows Home users must use the registry method — Group Policy Editor is only available on Pro, Enterprise, and Education editions
- A full restart is required after making the change — signing out and back in is not enough
In This Guide
This guide covers two methods to enable long file paths on Windows 10 and 11:
- Method 1: Registry Editor — Works on all Windows editions including Home. One DWORD value change.
- Method 2: Group Policy Editor — Available on Windows 10/11 Pro, Enterprise, and Education only.
Quick Steps
- Press Windows + R, type
regedit, and press Enter - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - Double-click
LongPathsEnabledand set the value to1 - Click OK, close Registry Editor, and restart your PC
Why Does Windows Limit File Path Length?
Windows has enforced a 260-character file path limit — known as MAX_PATH — since the early versions of the OS. At the time it was a reasonable design constraint, but today it causes real problems. If you work with deeply nested folder structures, long project names, or tools that automatically generate complex directory hierarchies (Node.js projects, Python packages, Git repositories), you’ve probably run into “path too long” errors.
One of the most common places I used to see this was when extracting compressed archives. If you’ve ever tried to unzip a file on Windows and got an error saying the path is too long, that 260-character limit is exactly what’s causing it. The fix is straightforward — you just need to tell Windows to lift that restriction.
This setting is available on Windows 10 version 1607 and all versions of Windows 11. Once enabled, Windows supports file paths up to 32,767 characters, which is more than enough for any real-world use case.
Method 1: Enable Long Paths via Registry Editor
This method works on all editions of Windows 10 and 11, including Home. It requires changing a single DWORD value in the registry.
Step 1: Open Registry Editor
Press Windows + R to open the Run dialog, type regedit, and press Enter. If a UAC prompt appears, click Yes to allow the change.
Step 2: Navigate to the FileSystem Key
Navigate to the following path. The fastest way is to click in the address bar at the top of Registry Editor, paste the path, and press Enter:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystemStep 3: Set LongPathsEnabled to 1
On the right side of the Registry Editor, look for a DWORD value called LongPathsEnabled. Double-click it, change the value data from 0 to 1, and click OK.
If the value doesn’t exist, right-click in the empty area on the right panel, select New > DWORD (32-bit) Value, name it LongPathsEnabled exactly as written, and then set it to 1.
Step 4: Restart Your PC
Close Registry Editor and restart your PC. The change won’t take effect until you do a full reboot — signing out and back in isn’t enough. After the restart, Windows will support long file paths for any application that has been updated to use them.
One-Line Command Alternative
You can apply the same registry change with a single command. Open Command Prompt or PowerShell as Administrator and run:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /fRestart your PC after running it. To reverse the change, run the same command with /d 0 instead of /d 1.
Method 2: Enable Long Paths via Group Policy Editor
If you’re on Windows 10 or 11 Pro, Enterprise, or Education, you can make this change through the Group Policy Editor. This does exactly the same thing as the registry edit — it’s just a different interface for the same underlying setting.
Press Windows + R, type gpedit.msc, and press Enter. Navigate to:
Computer Configuration > Administrative Templates > System > Filesystem
Double-click Enable Win32 long paths, set it to Enabled, and click OK. Restart your PC for the change to take effect.
Note: Windows Home does not include the Group Policy Editor. If you’re on Home edition, use the registry method above instead.
Want to Skip the Registry Entirely?
If you find yourself making a lot of registry tweaks like this and want a simpler way to manage Windows settings, Winhance is a free open-source tool I built that lets you apply many of these changes through a clean interface — no registry editing required. Enabling long file paths is one of the settings it covers.
For related file-handling tips, I also have guides on how to zip and unzip files on Windows, force-delete files that won’t delete, and password-protect folders on Windows 10 and 11.
Frequently Asked Questions
Does enabling long file paths affect all apps on my PC?
Not automatically. The registry change enables long path support at the system level, but each application also needs to be built to take advantage of it. Most modern software and development tools already support long paths. Older or legacy apps may still enforce the 260-character limit on their end even after you’ve made this change.
Is it safe to make this registry change?
Yes, this is one of the safer registry edits you can make. You’re modifying a single DWORD value that Microsoft specifically designed to be toggled by users and administrators. There’s no risk of breaking Windows by setting this to 1.
Does this work on Windows 10 Home?
Yes, the registry method works on all editions of Windows 10 (version 1607 and later) and all editions of Windows 11. The Group Policy method is the only approach restricted to Pro, Enterprise, and Education editions.
Do I have to restart after enabling long file paths?
Yes, a full restart is required. Closing Registry Editor or restarting an individual application won’t apply the change — Windows needs to reboot for the new path limit to take effect system-wide.
Can I undo this change?
Yes. Go back to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem in Registry Editor, double-click LongPathsEnabled, and change the value back to 0. Restart your PC and the default 260-character limit will be restored. You can also run reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 0 /f from an elevated prompt.
