8
2
I have a machine that initially had 8.3 filename creation disabled. However, this was causing issues with some legacy software, so it was re-enabled. I'm wondering if it's possible to go back and "add" 8.3 filenames to certain existing directories.
For example, say I have a directory named "C:\name with spaces" and I get the following output when I run "dir /x":
C:\>dir /x
Volume in drive C has no label.
Volume Serial Number is 6873-65B8
Directory of C:\
04/09/2010 01:57 PM <DIR> name with spaces
...
I'd like to somehow add an 8.3 name for the directory without recreating it, and then get the following:
C:\>dir /x
Volume in drive C has no label.
Volume Serial Number is 6873-65B8
Directory of C:\
04/09/2010 01:57 PM <DIR> NAMEWI~1 name with spaces
...
I tried the 'rename' command but it didn't do the trick.
3Just to be clear,
fsutil behavior set disable8dot3 0
is the command that requires a reboot to take effect.fsutil file setshortname <PathName> <shortname>
does not. – Doin – 2015-12-05T17:26:36.357I don't know about setting the behavior with fsutil requires a reboot, but directly setting the registry variable NtfsDisable8dot3NameCreation to 0 did not require a reboot for me on Win 7. Immediately, short file names began to be created from new files with long names.
(In my case, some poorly written Intel or Microsoft system update had set it to 1 a week ago. Silently even. $#@%&# !!) – MicrosoftShouldBeKickedInNuts – 2018-06-19T06:55:47.143