Windows 10: Able to find directory with 8dot3 naming convention but not files

I have a very strange problem - I have a script that's been running for years on other windows, using the 8dot3 convention. Both the directory and the file name have ~ in them. It finds the directory ok, but can't find the file, even though it exists. I've checked, and 8dot3 is enabled. Anyone else see this problem? Any ideas how to solve this? Or where I can go for help?
Thanks!

:)

 

Able to find directory with 8dot3 naming convention but not files

It didn't help, unfortunately.

 

Able to find directory with 8dot3 naming convention but not files

OK sorry about that.

I think the best is to reroute this directly to Microsoft and see if they can come up with a solution.

Are you OK with that?

 

You can check short names for folders and files.

Below command checks the short name for winaero.txt file. If no short name is present, blanks are displayed in its place.

Code: Dir "E:\My_Notes\winaero.txt" /x[/quote]
To check if short names are disabled on a given volume, run the following as an administrator in a cmd prompt:

Code: fsutil 8dot3name query c:[/quote] Enabling it is then just a case of running the following:

Code: fsutil 8dot3name set c: 0[/quote] However, any file or folder created when short name creation was disabled will still have no short name since they are only created at initial file/folder creation, not on subsequent accesses to the file even if short name creation has subsequently been enabled.

All is not lost as we can add short names for items that are missing them using the fsutil command again, for example:

Code: fsutil file setshortname "c:\program files" PROGRA~1[/quote] Code: fsutil file setshortname "c:\program files (x86)" PROGRA~2[/quote] This approach can also be used to “repair” short names when they are incorrect.

 

I've checked and 8dot3name is set correctly.
C:\Windows\system32>fsutil behavior query disable8dot3 c:
The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 2 (Per volume setting - the default).
Based on the above two settings,8dot3 name creation is enabled on c:

I can see the file when I do a dir /X, both short name and regular name, but I can't access the file using it's short name.

 

If it file has a short name and you can't access it then check to see if you are executing correct command for the file short name.

Which command do you use to access files with short names?

 

It's a batch script so I just run it from the command line, but I can't even do a dir on the short filename. Thank you so much for responding.

 

I'm able to run the same on another windows 10 machine, just not on this one.

 

Execute below command to replace or add a new short name to a file/folder.


Code: fsutil file setshortname "c:\MyLongFileName.txt" MyLong~1[/quote]

 

I can't change the file name or it's short name, this is being executed by automation unfortunately. I need to figure out why it's able to read directory names that are short names, but not file names *Sad

 

I'm sorry i could not found the way to only read directory names that are short names, but not file names. But i think you can use For command for this job. You use %~fsI modifier to expands %I to a full path name with short names only.

 

I want to be able to successfully do the following:
dir C:\Users\xxx0523\AppData\Local\Temp\CCS_C1~1\util\7ZAEXE~1.BAT
Even though 7ZAEXE~1.BAT exists, I'm unable to list it. I'm able to do dir C:\Users\xxx0523\AppData\Local\Temp\CCS_C1~1\util successfully. I think there's some setting that's missing on this machine, because I can do it successfully on another windows 10. Sigh!

 

Do you get any error message when you use Dir command with 7ZAEXE~1.BAT short name?

Are you running the batch script or Command Prompt as a administrator?

What happens when you execute below command?


Code: Dir C:\PROGRA~1[/quote]

Lets also repair any NTFS file system errors.

Please open the Command Prompt by typing cmd.exe into Start Menu, right-click on Cmd.exe, and open it as an administrator.

Execute below command:


Code: Chkdsk C: \f[/quote]

 

I get the directory listing when I do dir c:\progra~1.

 

That means there is a problem with 7ZAEXE~1.BAT short name.

Also execute Chkdsk tool maybe its a file system error.