Yes, these are the steps I attempted. They work like a champ on my windows 10 box, but my windows 11 box fails. I get PathTooLongException when I attempt to make deep paths in powershell. I'm lucky that I can do A/B testing on my 2 boxes, but this is ridiculous that windows 11 won't allow long path names.
According to that you can still do this in Windows 11.
View: https://www.reddit.com/r/Windows10/comments/aziyfm/win10_enable_long_paths_not_working/Yes, these are the steps I attempted. They work like a champ on my windows 10 box, but my windows 11 box fails. I get PathTooLongException when I attempt to make deep paths in powershell. I'm lucky that I can do A/B testing on my 2 boxes, but this is ridiculous that windows 11 won't allow long path names.
I'm a developer and added the <ws2:longPathAware>true</ws2:longPathAware> support into my manifest. This makes my program handle long path names in windows 10 perfectly. But, I ran into issues with my Windows 11 box. So, just to be clear my EXE handles long path names on my windows 10 box, but this same EXE fails on my windows 11 box.View: https://www.reddit.com/r/Windows10/comments/aziyfm/win10_enable_long_paths_not_working/
According to that reddit post and doing the same things as in the web site I posted, Windows 10 also seems to ignore the setting. But someone pointed out that it also requires the application to be aware of this.
There's also https://stackoverflow.com/questions/46308030/handling-path-too-long-exception-with-new-psdrive
In any case, this doesn't sound like a Windows problem. It sounds like an application problem.