Windows 10: Why isn't long paths enabled by default in windows 11.

Why isn't long paths enabled by default in windows 11? The 260 character limit has been crippling to the user over the years. It only takes someone to change lengthen a folder name further up the path to make access to some file impossible. I know the restriction was removed in Win 10, but only by Registry and Group Policy Mods - This is beyond the average user - so why isn't it enabled by default. Thanks.

:)

 

Is it risky to enable long file paths on Windows 10?

Windows 10 has an option to allow for longer file paths (background). Is it risky to enable this option?

I ask because I've heard mixed comments about how there can be bugs related to long file names.

From a recent (2016-07-30) MSDN blog post:

• A comment:
  
  
• The response:
  
  

Another question on SuperUser (2016-08-17) seems to suggest that there're known issues.

Question: Does enabling long file paths increase the risk of file loss or corruption on Windows 10?

 

Printer isn´t working after latest update.

After the latest update from Windows, my Canon Pixma ip6600 printer isnt working. In Device Manager it shows up as working properly but when I go to print it isn´t listed as an option in any programs. Troubleshoot suggests it´s a USB 2 printer on a USB
3 port and that that´s the problem but that cant be since it worked fine before the update. I´ve tried to uninstall and plug it back in but that doesn´t work either.

 

GPO: enable win32 long paths

I saw that the Windows 10 Anniversary Update was supposed to address the limitation of long file paths and names. According to what I found, the new GPO entry of "enable NTFS long paths" was supposed to be added, but I didn't see it. Upon further research,
I did find the "enable win32 long paths" option one level up in the GPO.

Question: Was this supposed to address the problem? After I enabled it, rebooted the computer and confirmed that the setting was still enabled, I tried to copy a file (via File Explorer) from a local hard drive (G:\*.*) to a server share (\\SERVER\SHARE),
but it failed for the same old reason that the pathname was too long. Does this only work locally, or does it only work with specific capabilities, like PowerShell?