A desktop monitor displays a Windows-style file explorer with case-varied app folders and warning icons beside CON and NUL.
Windows carries a handful of habits that date to the early PC era. Backslash paths, reserved device names, drive letters that start at C:, case-insensitive filenames and 8.3 short names all survive for the same reason: software still depends on them. How-To Geek's Umair Khurshid recently walked through these quirks and concluded that most are safe to leave alone. That conclusion holds up. A few details need tightening, and the reserved-name claim needs the most care.

A desktop monitor displays a Windows-style file explorer with case-varied app folders and warning icons beside CON and NUL. Backslashes: a compatibility decision, not an accident​

Windows paths use C:\Users\Name\Documents, while Linux and macOS use forward slashes. The MS-DOS 2.0 source README, which Microsoft archived on GitHub, gives a direct account of why. It says the user manual contained errors because of last-minute changes made for compatibility with IBM's implementation (PC DOS). That included using \ instead of / as the path separator, and / instead of - as the switch character.

So the usual "DOS already used / for switches" explanation is true but incomplete. Compatibility with IBM's version drove the swap.

Practical points for admins and developers:

  • Microsoft's .NET path documentation says forward slashes are converted to the standard backslash during path normalization. C:/Users/Name therefore works in many programming contexts.
  • That conversion happens in specific APIs. It is not a universal guarantee.
  • Command-line tools often treat / as the start of an option, so the same string can mean different things in different shells and utilities.
  • Use the separator the specific shell, command or API documents.

Reserved names: CON, NUL and the Windows 11 wrinkle​

You still can't create a folder called CON in File Explorer. The same goes for PRN, AUX, NUL, COM1 to COM9 and LPT1 to LPT9. Microsoft's Win32 naming guidance also lists superscript-digit variants such as COM¹ and LPT³. These names date to DOS, when they pointed at hardware: console, printer, auxiliary port, null device, and serial and parallel ports. They survive as part of the NT device namespace for backward compatibility.

How-To Geek says Windows 11 has relaxed the rule so that CON.txt and NUL.txt can now be created. Evidence on this is mixed, and it needs care.

What Microsoft's documentation says. The Win32 guidance says to avoid these names even when followed immediately by an extension. It states that NUL.txt and NUL.tar.gz are both equivalent to NUL.

What testing found. Windows Latest reported that on Windows 11 26H2, NUL.txt and CON.txt were created without complaint, even though Microsoft's documentation still says NUL.txt equals NUL. The same outlet's test also found that naming a new folder CON produced the message "The specified device name is invalid." A Microsoft Q&A thread reports similar behavior, where NUL is blocked in File Explorer but NUL.txt can still be created. The same thread notes that results vary by tool.

What developers still hit. MakeUseOf reports that CON.txt is still interpreted as the console, NUL.mp3 still points to the null device, and AUX.c is still treated as the reserved auxiliary device. It also says the Win32 API rejects the reserved name, so Git can't create the file on disk and the operation fails.

What Microsoft changed in .NET. Microsoft's .NET path-format page says that before Windows 11, Path.GetFullPath always treated a path starting with a legacy device name as that device. For example, CON.TXT became \\.\CON. The page says this no longer applies on Windows 11, and it advises specifying the full device path, such as \\.\CON, when you mean the device. That is a narrow API change. It isn't a general lifting of the naming rules.

The safest reading is that File Explorer on recent builds may accept some NAME.ext forms, but the documented rule hasn't changed and other tools may fail. Don't build a workflow on it. Treat reserved names, with or without extensions, as off limits, especially if files move between Linux, Git and Windows.

One related fact is worth knowing. The \\?\ prefix tells Windows file APIs to skip string parsing and pass the path straight to the file system. Microsoft says this applies to the APIs, and not all of it works from shell tools like File Explorer. It is specialized plumbing, not a casual fix. The .NET documentation warns that it is easy to create paths that ordinary applications struggle with.

Drive letters: C: is a habit, not a law​

The story that A: and B: were floppy drives is widely repeated, and it matches how How-To Geek tells it. The sources gathered here don't independently document that history, so treat it as common lore.

The compatibility advice is better supported. Microsoft's documentation says you can assign a drive letter to a local volume if that letter is free. It also warns that deleting a letter and assigning a new one can break paths such as desktop shortcuts, and can break the program making the change. So A: and B: aren't forbidden, but reassigning letters on a volume that holds Windows or applications is a bad idea.

Microsoft also notes that a volume gets at most one drive letter. C:\ and F:\ can't point at the same volume.

Case-insensitive filenames and the Linux cross-over​

By default, Windows treats FOO.txt and foo.txt as the same file but preserves the capitalization you typed. Microsoft's naming guidance tells developers not to assume case sensitivity. This is a common cause of "works on my machine" failures. Code that asks for Config.json runs on Windows even if the file is config.json, then fails on a case-sensitive Linux deployment.

NTFS can mark individual directories as case-sensitive. Microsoft's WSL documentation covers the details:

  • Per-directory support began in Windows 10 build 17107.
  • To enable it, run an elevated PowerShell and use fsutil.exe file setCaseSensitiveInfo <path> enable.
  • To check the current state, use fsutil.exe file queryCaseSensitiveInfo <path>.
  • The directory must be empty to change the flag.
  • You need write-attributes, create-files, create-folders and delete-subfolders-and-files permissions.
  • New subdirectories inherit the setting, except in WSL 1 mode.

Microsoft's warning is the important part. Many Windows applications assume case-insensitivity and may lose access to files in a case-sensitive directory. Windows-created subfolders in such trees may not be case-sensitive. For ordinary desktop use, leave the default alone. For repositories that must match Linux behavior, a dedicated case-sensitive directory is a reasonable and documented tool.

8.3 short names: PROGRA~1 and why it exists​

Early DOS file systems allowed eight characters, a period and three more characters. When Windows added long filenames, it could also create a short alias so older programs could still open the files. PROGRA~1 is the classic example.

Microsoft's documentation adds important qualifiers:

  • Windows may create the alias, and you shouldn't assume it exists on disk.
  • Alias creation can be disabled for performance reasons, system-wide or per volume.
  • dir /x shows short names where they exist.
  • fsutil 8dot3name query shows the current behavior. If you give no volume, it shows the default setting for all volumes.

The fsutil 8dot3name set values for the default are:

ValueMeaning
0Enable 8dot3 name creation for all volumes
1Disable it for all volumes
2Set it per volume
3Disable it for all volumes except the system volume

You must set the default to 2 before changing individual volumes.

Be careful with strip. Microsoft's warning is blunt: permanently removing 8dot3 names without updating registry keys that reference them can cause application failures, including being unable to uninstall a program. The tooling gives you safer steps:

  • Back up the directory or volume first.
  • Run fsutil 8dot3name scan on the directory to find registry keys that could be affected.
  • Use /t with strip for a test run, which does everything except the removal.
  • Only then consider a real run, and avoid /f unless you accept the risk.

Is the headline's "45 years" accurate?​

Roughly. The backslash change landed with MS-DOS 2.0 in 1983, which puts it about 43 years before this November 2026 article. The 8.3 format and drive-letter conventions go back to similar early-1980s roots. "More than four decades" is the safer description.

What to take away​

  • Backslashes: a compatibility choice tied to IBM's implementation. Use whichever separator your shell or API documents.
  • Reserved names: don't use them, with or without an extension. Some builds' File Explorer behavior appears looser than the documentation, but the documented rule is unchanged and other tools may break.
  • Drive letters: assignable, but don't change the letter of a volume holding Windows or applications.
  • Case sensitivity: keep the default. Use per-directory case sensitivity only for Linux-compatible workflows.
  • 8.3 names: check with dir /x and fsutil 8dot3name query. Scan and test before stripping anything.

These quirks persist because Windows's value rests on running old software reliably, not because nobody noticed them. Most of them are indeed best left alone. The ones worth understanding are the ones that bite when files cross between Windows and Linux.


Correction (November 19, 2026): The article misquoted the Windows error shown when renaming a folder to CON as "The specified device name is not valid." The actual message, as reported by Windows Latest and MakeUseOf, is "The specified device name is invalid."

 

References

  1. Windows still has 45-year-old quirks, and most are safe to leave alone - How-To Geek How-To Geek 2026-11-19T21:00:15+00:00
  2. MS-DOS/v2.0/source/README.txt at main · microsoft/MS-DOS · GitHub github.com
  3. Windows still won’t let you use this name for a folder — and DOS is why makeuseof.com