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

Sua resposta é mais correta que a do "12 Prêmios inúteis de MVP" que não sabe responder e manda o usuário para um novo tópico, devem ganhar "Prêmios" por dar as resposta "Mais Vazias Possíveis" ou pelo número de postagens totalmente inúteis...

Voltando ao que interessa, também estou com o mesmo problema, tanto as configurações de registro, quanto as de política não funcionam nas compilações 22621.1900, 22621.2213 e nem na 22621.2215...

Mas Microsoft é microsoft mesmo, começa algo, contrata um bando de incompetente e depois "lança" algo com uma "Capa nova" e o interior cheio de buracos, é só ver o gerenciador de dispositivos e de discos é quase o mesmo do windows 98... Inovação não tem o nome microsoft, só inovam na capa...

Hi guys, I may have the trick.

I'm on Win11 22H2, build 22621.1778.

Enabling the Win32 long paths via gpedit alone not solve the issue if you're using Windows Explorer.

TL;DR

But just use 7-zip (as the file explorer) to move the files/folders does the trick, hope this helps you all.

Application manifest is described here: https://learn.microsoft.com/en-us/windows/win32/sbscs/application-manifests

While true, that's entirely irrelevant. No normal person is using Windows via the command line.

Even me, who knows my way around a cmd prompt would never want to have my daily/hourly/minutesly interactions go via the command line.

It's fine if you have a **** ton of files to copy over from path A to B and it contains deep nesting, etc.

That'll generally be a one-time thing, so fine to whip out the command line for that (with the added benefit that robocopy is much faster at doing this than WinExplorer).

It's entirely another thing if you're just going about your daily business of managing/organizing your files.

How often I don't hit this limit while simply organizing my files, it's just stupid and annoying in this day 'n age.

Worst of it is that, while Explorer shows the file that exceeds the character limit, it then doesn't allow you to rename said file (without even an error, just doesn't save the edit).

So overall, for many people WinExplorer == Windows. Having that one support long paths is the very least you could expect from them.

For such simple rename operations, to get files within the limits I've found that opening the folder in WinRAR allows me to properly rename the files in that folder that way. Though there's no way I'm gonna start using WinRAR as WinExplorer.

You'd pretty much have to replace WinExplorer by a 3rd party app to be able to fully do basic file management these days.

At this point it's obvious they don't care to fix it though.

had the same issue recently and robocopy did the job well. it's a command that you can run in cmd that will copy even the most deeply nested files.