How to Enable Long Path Support in the Windows 11 Registry

Quick fix: Open Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, set DWORD LongPathsEnabled to 1, reboot — Windows 11 now supports paths up to 32,767 characters in modern apps.

You hit the 260-character path limit when copying files, extracting archives, or working with deeply nested folder structures (node_modules, sync clients backing up other systems). Windows 10 1607+ supports long paths, but the support is opt-in. The single registry value enables it system-wide for apps that declare themselves long-path aware — and File Explorer in Windows 11 is one of them.

What causes this

The historical Windows API used a constant MAX_PATH = 260 as the maximum length of a path string. NTFS itself supports paths up to 32,767 characters, but the Win32 API truncates at MAX_PATH unless an app explicitly opts in to long-path support. Windows 10 version 1607 added a system-wide flag that, when enabled, lets opted-in apps handle full-length paths. Apps still need to declare themselves long-path aware in their manifest — most modern ones do, but legacy apps don’t.

Method 1: Enable via Registry Editor (Home edition friendly)

Works on every Windows 11 edition.

1. Press Win + R, type regedit, press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
3. Find LongPathsEnabled DWORD. If it doesn’t exist, create it:
   • Right-click in the right pane → New → DWORD (32-bit) Value.
   • Name it LongPathsEnabled.
4. Double-click the value. Set to 1. Click OK.
5. Close Registry Editor.
6. Reboot. Long path support is now active system-wide.

The reboot is required because the FileSystem subsystem reads the flag at boot, not on each file operation.

Method 2: Enable via PowerShell (scriptable)

For deployment scripts or fast scripted setup.

1. Open Terminal (Admin).
2. Set the registry value:

   New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWord -Force

3. Verify:

   Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled"

   Value should be 1.

4. Reboot.

Same effect as Method 1, faster for IT automation.

Method 3: Enable via Group Policy (Pro/Enterprise)

For managed environments and Group Policy deployment.

1. Press Win + R, type gpedit.msc, press Enter.
2. Navigate to Computer Configuration → Administrative Templates → System → Filesystem.
3. Find Enable Win32 long paths.
4. Double-click. Set to Enabled. Click Apply → OK.
5. Run gpupdate /force from elevated Terminal.
6. Reboot.

This is the cleanest path for organizations — the same policy can be pushed via Group Policy Management Console to all domain-joined PCs.

How to verify the fix worked

• Create a deeply nested folder structure exceeding 260 characters total path. Copy a file into it. Copy should succeed.
• Open the long-path file in Notepad — saves and opens correctly.
• Run (Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name LongPathsEnabled).LongPathsEnabled in PowerShell. Returns 1.
• Extract a long-path archive (e.g., a Node.js project with node_modules) — extraction completes without truncation.

If none of these work

If long paths still fail after enabling the registry flag and rebooting, the app you’re using isn’t long-path aware. Three cases. Notepad: works with long paths since Windows 10 1809. If your Notepad fails on long paths, you may be using an older Win32 version — use the Microsoft Store Notepad or the new Notepad app shipped with Windows 11. Older third-party apps: many older Win32 apps (Outlook 2010, Office 2013, older Adobe products) don’t declare long-path awareness even with the OS flag enabled. Workaround: use a shorter path. Move the deeply-nested folder closer to the drive root (e.g., from C:\Users\you\Documents\Projects\... to C:\P\ + subfolders). Destination filesystem: copying to FAT32 (most USB drives by default) caps paths at 260 chars regardless of OS flag. Reformat to exFAT or NTFS. For build tools and dev workflows, use the \\?\ prefix on full paths in your scripts — bypasses normalization entirely.

Bottom line: Long path support is a single registry DWORD plus reboot — flip the switch and File Explorer, modern apps, and dev tools all start handling paths up to 32,767 characters.