LongPathsEnabled DWORD is correctly set in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem and restart your computer. Additionally, verify that your file system supports long paths and consider using native tools like PowerShell for operations exceeding the legacy limit.
Verifying the Registry Configuration
The most common cause of this issue is an incorrect or missing registry entry. While many users edit the registry, they may miss critical details or apply the fix to the wrong hive. The primary setting controlling path length limits is located within the system configuration key. You need to open the Registry Editor by pressingWin + R, typing regedit, and confirming administrative privileges. Navigate to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Look for a value named LongPathsEnabled. If it does not exist, you must create it. Right-click in the right pane, select New, then choose DWORD (32-bit) Value. Name this new entry LongPathsEnabled. Double-click it to modify its data. Ensure the base is set to Hexadecimal and the value data is 1. This single digit enables support for paths up to 32,767 characters. If the value is already present but set to 0, change it to 1. After making this change, close the Registry Editor completely. It is crucial to understand that this change does not take effect immediately for all running processes.
Applying Group Policy Settings
In some enterprise environments or specific Windows 11 configurations, the registry setting alone is insufficient because the Group Policy overrides local settings. Even on personal editions of Windows, checking these policies ensures no background rules are blocking long path access. Open the Run dialog again withWin + R and type gpedit.msc to launch the Local Group Policy Editor. Note that this tool is fully available on Windows 11 Pro, Enterprise, and Education, but may require workarounds on Home editions.
Navigate to Computer Configuration > Administrative Templates > System > Filesystem. In the right-hand pane, locate the policy named Enable NTFS long paths. Double-click this policy to open its properties. Select the Enabled radio button. Click Apply and then OK to save the changes. This step forces the operating system to recognize the extended path capabilities at a deeper system level than the standard registry tweak. If you are unable to access gpedit.msc due to using Windows 11 Home, you can refer to our guide on how to enable long paths on Windows 11 Home via alternative methods.
Restarting Services and Explorers
After modifying both the registry and group policies, the changes must be loaded into the active kernel and user session. The simplest method is to restart your computer entirely. This ensures that all file system drivers and Explorer instances reload with the new configuration. However, if you wish to avoid a full reboot, you can manually restart the Windows Explorer process. PressCtrl + Shift + Esc to open Task Manager. Find Windows Explorer under the Processes tab, right-click it, and select Restart. This refreshes the shell interface but may not clear all cached path limits in third-party applications. For a more thorough reset, use PowerShell as an administrator and execute commands to restart relevant services, though a full restart is generally more reliable for this specific issue.
Alternative Solutions for Extreme Cases
If the problem persists despite correct registry and policy settings, the issue may lie with the application itself rather than Windows Explorer. Some older software strictly enforces the 260-character limit regardless of OS settings. In such cases, consider using native command-line tools which often bypass GUI limitations. For example, using PowerShell'sCopy-Item or Move-Item cmdlets can sometimes succeed where File Explorer fails. Another effective strategy is to shorten the directory structure by moving files closer to the root drive, such as C:\Data instead of C:\Users\Name\Documents\Projects\.... This reduces the total character count below the threshold. Additionally, ensure your antivirus software is not interfering with deep directory scans, as security suites can sometimes mimic path-length errors during real-time protection checks.
Frequently Asked Questions
Why does the error return after I restart my PC?
This usually indicates that the registry value was not saved correctly or was overwritten by a system update. Verify that LongPathsEnabled is still set to 1 after the reboot. If it reverted, check for conflicting group policies or third-party optimization tools that might reset system keys.
Can I use third-party tools to bypass this limit?
Yes, utilities like Directory Opus or specialized file managers often implement their own path handling logic that exceeds the standard Windows limits. These tools can manage deeply nested folders without triggering the error, providing a workaround if native Explorer remains problematic.
Does this issue affect USB drives differently?
USB drives formatted with FAT32 have a strict 255-character limit per path component, unlike NTFS which supports 32,767 characters globally. If your external drive is FAT32, enabling long paths in Windows will not help; you must reformat the drive to NTFS or exFAT to support longer paths.
How do I check if my current path is actually too long?
You can calculate the total length by adding the drive letter, colon, backslashes, and all folder/file names. If the sum exceeds 260 characters, it hits the legacy limit. Modern Windows 11 builds handle longer paths natively if enabled, so aim to keep paths under 200 characters for maximum compatibility with older software.
Is regedit safe to use for this fix?
Editing the registry is generally safe if you follow the exact path provided. Always export a backup of the FileSystem key before making changes. Incorrect modifications to other keys can cause system instability, so stick strictly to the LongPathsEnabled DWORD in the specified location.