Having the need to discuss this topic in 2022 is something I would not have dreamed of - but still, we're here to address the elephant in the room: Yes, Windows 10 does support long path names - no, it does not support it by default.
You need to enable it using the AD config or the registry.
* launch regedit with admin rights
* navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
* Add a new DWORD (32-bit) named LongPathsEnabled with value 1
* rebootAlternatively, you can also have the same result by enabling this value in the Group Policy (Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long path).
However, this will only help with your explorer and "new" applications, some old apps can still suffer from issues (and we're not going to talk about potential WSL/WSLv2/Docker issues here by mounting paths...)
Another interesting thing is to find files / paths which are "a little abundant". There is a nice tool called TLPD for this, HOWEVER (warning), I need to highlight that only the version 4.6 is considered ok ( https://sourceforge.net/projects/tlpd/files/v4.6/ ). The latest version 4.6.0.1 is infected by some kind of Trojan - and about half of all scanners on Virus Total are also confirming this issue. So if you want to use this tool - please only download the 4.6 version - and for good measure scan it before use. Just to be sure that in the future not someone plays around with the files...