Why You Can't Name A File CON In Windows

Channel:Tom Scott · Length:8:03 · Published:2020-04-20 · Views:7799076

Watch on YouTube

Summary

Tom Scott explains why Windows does not let you name a file CON, tracing the reserved device names back to backwards compatibility with DOS.

Why HN recommends it

Linked as a relevant explainer in threads about Windows quirks and reserved names.

relevant video — HN, 2020

Operating systems & kernels · History of computing

Subtitles (excerpt)

Normally, when I film these videos, I’m at the Centre for Computing History in Cambridge. Unfortunately, it is April 2020 as I record this, and times being as they are, I have to make do with a green-screen. But why simulate that same location? I could be anywhere with this, right? Well, first, this would have been a great subject to film at the computer museum. But also: if I change things too much, it’ll break the style, and people don’t like change. Actually, that’s not true: people like just the right combination of novelty and familiarity. On that note: did you know that you can’t name a file “Con” in Windows 10? ...I promise that’s related. If you’re running a Windows machine, try it right now. Go to File Explorer, create a new folder, call it “Con”. C-O-N. The system is not going to let you do it. You also can’t name a text file “con.txt” or an image “con.jpg”. Con is a first name, not a common English one, but it’s a variant of Cornelius, Conrad, Connor, Konstantinos. There are a good few people who go by the name Con. So if you’re trying to save a photo of one of them using their name on Windows, you can’t. In fact, the system won't let you call a file or folder CON, AUX, PRN, LST, COM0 through COM9, LPT0 through LPT9, or NUL.

On Hacker News

It's wild to me some of the things I never knew, even though I've been using Windows or DOS for probably 35 years. For example, I recently learned you can't name a file CON. Try it. Somehow over all those decades, I've never tried to do this until Tom Scott made a video about it: [VIDEO] — RajT88, 2023-05
can't speak about the very recent updates, but windows have been consistent and adamant on keeping the backward compatibility. they still use reserved file names for io devices so that 30+ year old printers can still work, and you can still open a 2000s doc file in office 365. (I'm looking at you Apple, who made many of the 32 bit apps I loved useless) relevant video: [VIDEO] (Tom Scott: Why you … — irshadshalu, 2020-06
Excel also has a deliberate bug where it thinks 1900 is a leap year because they wanted compatibility with Lotus 123, where the bug was actually a bug! [0] [0] [VIDEO] — gresrun, 2020-04
Don't think this will ever happen, especially since this is Microsoft you are talking about [0] [0] [VIDEO] — cardboard9926, 2026-06

Related videos