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.
addendum: native powershell stuff is still broken. But, running a .BAT from powershell appears to handle long paths ok. (I suspect it launches cmd console to process the .BAT)
So, new theory: Just powershell in windows 11 is broken for long paths. Win10 powershell works great with long paths.
win11 powershell wont tab complete long pathnames, whereas win10 powershell does. So perhaps Microsoft just goofed up the powershell manifest.
It doesn't seem to work for any version of Windows 11, be it Pro, Education or Home
It doesn't seem to work for any version of Windows 11, be it Pro, Education or Home
I certainly have long paths working in 22H2 Windows 11 (22621.1105) today. All of these versions work: Home, Pro and Enterprise.
For the Home version: Windows 11 Home does not come with GPEdit.MSC. But, I tried the registry key and without even rebooting the long paths started working in a new cmd console window that I opened after making that registry change.
To test long paths I made a long.BAT with contents:
md o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs100bytes
cd o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs100bytes
md o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs200bytes
cd o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs200bytes
md o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs300bytes
cd o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs300bytes
md o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs400bytes
cd o123456789o123456789o123456789o123456789o123456789o123456789o123456789o123456789o1234_ThisIs400bytes
I then ran the long.bat in my user folder. This correctly made a 400+ path
I don't have easy access to the education version. You could try hitting the windows key + "R" to try running gpedit.msc to enable long paths. If that doesn't work then I assume the above trick that works for Windows 11 Home edition might work.
Thanks very much! I ran the long.bat successfully but after that I still can't rename the files.
My system information: Windows 11 pro, version 22H2 x64
Same probleme here, multiple clients can't add or change files. With bat script it will work but in Windows explorer only errors. MS need te update this.
