locked
Maximum path depth

    Question

  • Will this still remain to be an issue in Windows 8?

    While NTFS allows much a longer path (as we can see, if users create folder hierarchies on shared folders on servers), Windows Explorer is still limited to accept only 260 characters, as just tested.

    In which Windows version will this ancient limit fall?

    Best greetings from Germany
    Olaf

    Thursday, September 29, 2011 11:36 AM

All replies

  • Yes, as long as ANSI programs are still expected to run correctly on Windows, I don't see Windows abandon the limit. 

    Besides, there are a lot of Unicode programs that do not allocate more than 260 characters for path too.



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Thursday, September 29, 2011 7:03 PM
  • When, if not with a new version of an OS can outdated limits be cut in best manner?

    And if an application has an limit, which Windows does not have, it is a problem of the application to deal with that.

    If this would not be the case, we would still live with 8:3 file names, because Norton Commander could only deal with them.

    I am an network administrator, and often enough users run into this situation - or worse - they create deeper path (deeper local to the server due to folders mounted to drive letters for the users), which are not accessible by backup software, Virus Scanner, local Explorer running on the server.

    So this limit causes problems and needs to be removed not only for showing, that Windows 8 has something new..

    Best greetings from Germany
    Olaf

    Thursday, September 29, 2011 8:56 PM
  • Microsoft has been pushing Unicode in .Net and Visual C++ for a while now. But as you may know a single app can be a deal-breaker for a company-wide upgrade. And app developers often do not feel the need to upgrade to Unicode or extend their buffer for the sake of long file names.

    You can send requests to authors of apps running in your company. Maybe one day Microsoft can give up ANSI API support, but it is not now.

    Besides, are you going to train every user to start typing path like \\?\UNC\server\share in the address bar?



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Thursday, September 29, 2011 9:43 PM
  • Thank you for posting your feedback, we want to make sure we get the right info including your log files. Can you also submit feedback using the Windows Feedback Tool from the Connect Site associated with your Windows Developer Preview program? If you’re an MSDN subscriber, the information on how to join the Connect program is included on the download page where you installed Windows Developer Preview. There’s a link to the Connect site and an invitation code that you can click on to join using a Windows Live ID account. If you’re not an MSDN subscriber follow this limited use link to join the Connect program and then follow the steps here.
    Marilyn
    Wednesday, October 05, 2011 10:43 PM
    Moderator