This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I spent way too long debugging a compile error in MS VS Code (64bit version 1.66.2). It would fail with 'file not found' or 'unable to access file' errors. The workspace is located in "C:\Users\UserName\Documents\My Workspaces\firmware", with several levels of nested source folders below.
Initially, I got several linking errors due to Controlled Folder Access protection using the Ransomware protection built-in to Windows Security. I whitelisted ar.exe and as. exe, but the errors persisted. I even turned off Ransomware protection. Seeing a thread online about long file paths reminded me I hadn't enabled that on Windows 11 yet (fresh install), so I changed the following settings and rebooted the PC:
Registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled set to 1.
Group Policy: System "Configuration>Administrative Templates>System>Filesystem>Enable Win32 long paths" enabled.
About that time I noticed an issue with not being able to delete or rename files on an SMB share that were in a deep path. If I went to the other system and moved them up a few folders I was again able to rename the files.
Both of these scenarios work fine from my Windows 10 Pro PC. My Windows 11 Pro PC is a fresh install (Version 21H2 Build 22000.613).
So I believe Windows 11 isn't respecting my Long Paths settings. As a final test, I moved my VS Code Workspace folder to system drive root (C:\firmware) and it compiled without error.
I've seen other questions on here about Windows 11 path length issues that were brushed away because they were encountered using non-Microsoft 3rd Party software, but this is all built-in File Explorer and Microsoft's own VS Code product.
My question is, how do I actually allow long file paths in Windows 11 Pro?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Don't suppose you've had any more word on this? It would be a lovely christmas present if they resolved it, or found a work around! It's causing me serious problems running terragrunt in powershell with multiple levels of nested folders and if there's not a resolution or workaround coming I may have to downgrade to windows 10 or switch to linux.
Thanks for raising with and dealing with Microsoft for us!
G
I've heard nothing from them since 9th Dec
This is actually outrageous. It's 20 friggin' 22 and they still have problems counting to 261.
I'm also encountering the issue, using a C# app writing XML files in a VS debug session (e.g. paths here are fairly structured and on the long side).
But even if I try to create that same file with File Explorer, it won't let me create the file. It just stops accepting characters at some point.
I enabled the feature via GP editor. Checked RegEdit and value is also at 1.
Just did a reboot & just got a major WinOS update --> No Dice.
I have the same problem in windows 11 fully patched. I have just enabled long paths with gpedit.msc (the Local Group Policy Editor) and restarted my PC twice, and still long names are not enabled.
Am I skipping some step in the process?
Thanks for your support.
Update: after enabling longpaths with gpedit, as described above (and double-checking the enablement setting was on), I have checked the registry and I was disappointed to see that the longpath parameter was still set to 0 there. I have then set the longpath registry parameter to 1 and restarted the PC. After that it seems that longpaths are enabled. It seems that there is a disconnection between gpedit and the registry. Hope this information can help the group here.
Trouble is that no one in this discussion can get long paths to work on windows 11. We can get it working great with windows 10, but no one here can get it working on Windows 11.
If you do get it working, please let us know how.
