Windows 10 中是否仍然存在 MAX_PATH 问题 [英] Does MAX_PATH issue still exists in Windows 10

问题描述

如果

应用程序清单中必须有一个类似于 DPIAware 的条目 longPathAware.

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" ><asmv3:应用程序><asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings"><longPathAware>true</longPathAware></asmv3:windowsSettings></asmv3:application></组装>

Can someone please tell us/me if the MAX_PATH issue still exists in (the technical preview of) Windows 10. And if it exists: How many characters can a path and an individual file name have?

解决方案

The issue will be always present in Windows, to keep compatibility with old software. Use the NT-style name syntax "\?D:very long path" to workaround this issue.

In Windows 10 (Version 1607 - Anniversary Update) and Windows Server 2016 you seem to have an option to ignore the MAX_PATH issue by overriding a group policy entry enable NTFS long paths under Computer Configuration -> Admin Templates -> System -> FileSystem:

The applications must have an entry longPathAware similar to DPIAware in the application manifest.

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
  <asmv3:application>
    <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
      <longPathAware>true</longPathAware>
    </asmv3:windowsSettings>
  </asmv3:application>
</assembly>

这篇关于Windows 10 中是否仍然存在 MAX_PATH 问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！