



Disabling 8.3 filename creation has been a recommendation in the Best Practices Analyser since at least Server 2012, and possibly 2008R2.
Windows can still create an additional short 8.3 alias for a long file name.
O.m.g.
They should have removed this ancient handbrake long ago. Now I learn that it not just still exists, but is also still engaged by default.
Okay. Now go to File Explorer and right click to create a new text file and try to name it “con”. That’s three letters: con. You can’t do it. Not allowed. Because CON has been reserved (in every directory on every drive) for piping to and from console since MS-DOS 2 or so. (I think 2 is when they stole pipes from Unix)
Okay. Now, open just about any kind of desktop window and double click in its upper left corner. In > 9 windows out of 10 that action still closes the window even though the “close window” button was moved to the upper right corner by Windows 3. Even though a bunch of modern applications don’t even have any icon there at all any more.
“aux” is the same. And file ending doesn’t matter. Short version: I had this fun experience a few years back. I used cygwin and Vim for coding and used some old compiler for embedded systems. I created a file called “aux.c” in cygwin. No problem. I compiled my code. Got very strange error. Trouble shooted, tested a bunch of things. Wasted lots of hours before I figured out that “aux” was reserved on one abstraction later but not on another, so Vim/cygwin could access it. My dos compiler couldn’t. Fun times.
I still double-click the left corner every now and then. I’ve found myself using CTRL+INS and Shift+INS lately because CTRL+C/V keeps giving me very inconsistent results. Particularly in terminals. I remember using the the same hotkeys in MS-DOS editor.
What if I create the file con in wsl, will it also not be allowed?
Other DOS reserved names include PRN, LPT1, LPT2…
copy file.txt prn was an interesting shortcut for printing things 35 years ago.