Long file path issues in Windows 11 Pro with Microsoft VS Code and File Explorer

Anonymous

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.

0 comments

77 answers

Anonymous

2022-12-15T16:20:44+00:00

I've heard nothing from them since 9th Dec
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2022-12-15T09:00:49+00:00

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
Was this answer helpful?

5 people found this answer helpful.

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2022-12-09T17:01:49+00:00

With no status for almost a week, I pinged the Microsoft support guy. I just got an email from his supervisor: apologized for delayed response and they're working on it. No idea if they've tried reproducing it or not.
Was this answer helpful?

10+ people found this answer helpful.

0 comments No comments
Anonymous

2022-12-02T18:29:08+00:00

I actually talked with Microsoft yesterday. Apparently they needed more info before they were willing to attempt to reproduce the issue.

So, I ran a few scripts that they gave me on a clean and fully patched Windows 11 VM. Gave them those logs and now they're looking into whether they can reproduce the issue at their end.

Hopefully they'll make their reproduction attempt soon...

Awesome! Really hope they recognize it as a bug and fix in a cumulative update or something. It is starting to get in my way as I migrated over to Windows 11.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments