Why Windows 11 still won’t let you name a file CON, and Microsoft’s explanation goes back to MS-DOS
windowslatest.com Oct 19, 2026

Why Windows 11 still won’t let you name a file CON, and Microsoft’s explanation goes back to MS-DOS

AI-summarised brief · reviewed before publication

Windows 11 still blocks the creation of files or folders named CON, PRN, AUX, NUL, COM1‑COM9 or LPT1‑LPT9, treating them as legacy device identifiers inherited from MS‑DOS. Testing on a 26H2 build showed the rule works for bare names but fails for extensions: NUL.txt and CON.txt are accepted despite Microsoft’s documentation claiming they map to the device names. Engineer Raymond Chen traced the restriction to DOS 1.0, when a single directory existed and these names served as shortcuts to the console, printer, serial ports and a null sink. He explains that the rule persists because countless scripts, batch files and utilities still rely on it for redirection and existence checks. Removing it would break those workflows in modern Windows environments today.

💡 Why It Matters

  • · Because scripts still depend on these reserved names for redirection, an accidental removal would silently corrupt automation pipelines across enterprises.