Microsoft Removes 260 Characters Path Length Limit in Windows 10 RS

Page 3 of 3 FirstFirst 123

  1. Posts : 414
    Windows 10 Pro
       #20

    BahBoh said:
    I enabled long file paths using the policy editor but then I could NOT BELIEVE that File Explorer - Microsoft's File Explorer - in 2016 does NOT support long file paths !
    Well, it doesn't take a rocket scientist to realize that support for long path names is still a work in progress. It is not even enabled by default.

    BahBoh said:
    How can Microsoft do that ?!
    We stopped asking such questions after the infamous recent blunder with Regedit, which crashed during Search operations because of exceedingly long registry key names.
      My Computer


  2. Posts : 93
    Windows
       #21

    BahBoh said:
    Can anyone tell me if the manifest hack above works for File Explorer ?
    It's not great... Explorer uses hard-coded buffers in various places that don't allow paths greater than 256 characters and there are a bunch of shell extensions (including some in Windows) that are affected.

    You would be better off finding an alternative file browser.

    Mystere said:
    rumor has it that the next release (Redstone 2) is going to have a new Universal File Manger application
    Rumor you say?

    https://i.imgur.com/pgASs0x.png
      My Computer


  3. Posts : 3,257
    Windows 10 Pro
       #22

    dmex said:
    It's rumor that it will be in RS2, not that they're working on one (one never knows when or if it will actually make it into the build, or if it will replace the desktop File Explorer)
      My Computer


  4. Posts : 2
    Win 10 au
       #23

    dmex said:
    It's not great... Explorer uses hard-coded buffers in various places that don't allow paths greater than 256 characters and there are a bunch of shell extensions (including some in Windows) that are affected.
    If only there were some developers at Microsoft.
      My Computer


  5. Posts : 3
    Win 10
       #24

    dmex said:
    FYI this setting doesn't do what you guys think it does...

    Applications need to have <longPathAware>true</longPathAware> in their app.manifest before it's able to take advantage of this setting and at present there are no apps that have done this - other than Windows Store apps.

    E.g. Explorer and every other last application will still have a 260 character limit even after you enable the setting.

    You will need to force older applications to use this setting by enabling an option to force windows to load external manifests from the application folder overriding the manifest that's compiled into the executable:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. Type PreferExternalManifest, and then press ENTER.
    5. Right-click PreferExternalManifest, and then click Modify.
    6. In the Edit DWORD Value dialog box, click Decimal under Base.
    7. In the Value data box, type 1, and then click OK.
    8. On the File menu, click Exit to close Registry Editor.
    9. Reboot.

    Then in the application folder:
    1. In the same folder as the executable, create a file with the same name: photoshop.exe.manifest or notepad.exe.manifest etc...
    2. Paste the following XML: Long Path Aware sample manifest · GitHub
    3. Save and exit the file.
    4. Try running the application.

    The problem with overriding the manifest that's been compiled into the executable is that you might omit critical dependencies or other configuration that the application requires from its internal manifest... You might need to use a PE editor to find the manifest inside the executable, copy the XML into the external.exe.manifest that you created then add <longPathAware>true</longPathAware> instead before it'll work properly...
    does this still work?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:54.
Find Us




Windows 10 Forums