Even with LongPathsEnabled set to 1, Windows 10 Explorer doesn't seem to support long paths

Question

In Windows 10 21H2 have LongPathsEnabled set to 1 in the registry, via group policy, but even though that's supposed to allow paths up to 32K characters, Windows Explorer is unable to create them—even though PowerShell can, but if you create deeper folders or files in PS, they aren't viewable in Explorer. If I create C:\Users\UserName\OneDrive - Company Name\Documents 1\TestLongFolder-FileName-Folder1-12345678901234567890123456789012345678901234567890\TestLongFolder-FileName-Folder2-12345678901234567890123456789012345678901234567890\TestLongFolder-FileN\New Document.txt It won't let me make either the laster folder or document name any longer, nor nest another folder in them with a name longer than that last file. While this is 269 characters, which is more than the 260 that is allowed without LongPathsEnabled, it's far less than the 32,000+ characters that are supposed to be allowed with it enabled. Please let me know this limitation been fixed in Windows 11, or is there a way around it in Win 10? Thanks, Ralph.

Answer 1

I got up to 343 characters then ran into the same problem. You can create longer directories in the CMD prompt using the MD command, but not in Windows Explorer. My application would either need a rewrite or at the least to use an alias of some kind. The internet browser temporary cache does not seem to have this limitation.

Answer 2

The only way I have found around this so far is to zip up files and then unzip them into the deeper directory.

I know this doesn't really help in a lot of cases but might be helpful to someone.