Long file names and max_path in explorer.exe

Toutes les réponses

• 

  

  0

  Connectez-vous pour voter

  Hi,

  Thanks for posting in our forum.

  Based on my research, I would suggest you try to enable policy setting "Enable Win32 long paths" to see if it helps.

  The policy setting is under Computer Configuration -- Administrative Templates -- System --Filesystem.

  Please understanding, due to our company policy, we couldn't test the policy in our lab.

  Best Regards,

  William

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  lundi 22 octobre 2018 12:16
• 

  

  1

  Connectez-vous pour voter

  https://serverfault.com/questions/847142/cant-use-long-path-names-in-windows-2016

  "This means that even after you turn this on, not every application is going to magically start being able to access long paths. Each specific application still has to be coded so as to "opt-in" to this support."

  Sorry. 

  lundi 22 octobre 2018 12:57
• 

  

  0

  Connectez-vous pour voter

  Hi,

  Thanks for posting in our forum.

  Based on my research, I would suggest you try to enable policy setting "Enable Win32 long paths" to see if it helps.

  The policy setting is under Computer Configuration -- Administrative Templates -- System --Filesystem.

  Please understanding, due to our company policy, we couldn't test the policy in our lab.

  Best Regards,

  William

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  Do you even read my post? Or you just kidding?

  mardi 23 octobre 2018 10:25
• 

  

  0

  Connectez-vous pour voter

  I understand that. Also, I understand that explorer was coded a long time ago.

  But maybe there is some way to force it to use max_path > 260, or at least to stop windows 2016 to check it's digital signature because maybe manifest is the only thing that prevents it to work normally.

  mardi 23 octobre 2018 10:28
• 

  

  0

  Connectez-vous pour voter

  I looked at this a few years ago and while my memory isn't the greatest, I recall that the problem was not just with explorer, but with all of the API's and supporting dll's that explorer calls. 

  • Marqué comme réponse iliya karin jeudi 25 octobre 2018 11:07

  mardi 23 octobre 2018 14:05
• 

  

  0

  Connectez-vous pour voter

  Ohh I see.

  Thank you for the answer.

  jeudi 25 octobre 2018 11:07
• 

  

  0

  Connectez-vous pour voter

  iliya, I enabled long file name support on my Windows 10 Home laptop and did some playing around. I found that explorer was able to navigate the folders. I could not rename them (past the MAX) or create new ones, but I could delete and copy the folders. I could also view, copy, and edit files in the long folder names. 

  I used this Powershell script to create my playground. The directory name length is 1073. 

  If nothing else, the script will verify that the PC has long file name support enabled. I thought that I had it turned on, but Powershell was giving me errors when the directory name length got above 330. 

  set-location "c:\temp"
  $alpha = 'abcdefghilkjmnopqrstuvwxyz'.ToCharArray()
  $alpha | %{
      $str = "$_" * 40
      md $str
      cd $str
  }
  "Edit me!" | out-file "TryToEditMe.txt"
  ""
  $x = Get-ChildItem
  "Directory name length is: $($x.DirectoryName.Length)"
  $x.DirectoryName
  set-location "c:\temp"  
  $x.DirectoryName | clip 
  "Directory name copied to clipboard."
  

  
  

  samedi 27 octobre 2018 18:58