The Forbidden Windows Folder Name

Level 1: Breaking the Rules

Imagine you’re at a school where the teacher has a strict rule: no candy allowed in class at all. Now picture one cheeky kid who managed to sneak in a candy bar anyway. During recess, with a sly grin, he whispers to his friends, “Do you want to see the most illegal thing I have?” Then he pulls out that candy bar from his backpack like it’s some kind of forbidden treasure. All the other kids gasp and giggle, not because candy is dangerous, but because it’s not allowed and he still got away with it.

This meme is doing the same thing, but on a computer. The “candy bar” here is just a simple folder on a PC with the name “Con”, which Windows computers normally do not allow you to use. It’s a very small, harmless rule to break — kind of like sneaking candy into class. When the guy shows off that folder named “Con”, he’s joking that it’s the most illegal thing he owns, as if the computer police might bust down his door for it. Of course, nothing bad is really happening; it’s all pretend. He just found a clever way to break a funny little rule on his computer. The reason it makes tech folks laugh is the same reason the kids laugh about the candy: it’s silly and kind of daring, done just for the fun of getting around the rules.

Level 2: Forbidden Folder Names

On Windows computers, you can name your files and folders almost anything you want — with a few weird exceptions. “Con” is one of those forbidden names. If you try to create or rename a folder to Con in Windows, the system will refuse and say something like, “The directory name is invalid.” This isn’t a bug; it’s actually a rule that’s been around forever in the world of Microsoft operating systems.

The reason is a bit historical. A long time ago, before graphical Windows, there was an older system called MS-DOS that ran on text commands. In MS-DOS, certain short words were reserved because they referred to devices (like hardware parts of the computer) rather than normal files. For example, CON meant the console (which is basically the screen and keyboard, i.e., whatever you type and see), PRN meant the printer, and NUL meant “null” (a special sink for data, essentially a place to throw away output). These words were handy because you could do stuff like COPY CON FILE.TXT to create a file from keyboard input, or COPY FILE.TXT PRN to send a file straight to the printer. The computer would understand that CON wasn’t a real file on disk, but a keyword for your keyboard/screen, and PRN was your printer.

Fast forward to modern Windows 10 (built on the NT kernel and using the NTFS file system): those old names like CON are still reserved! Even though we rarely use them directly now, Windows keeps them blocked so that old software (and parts of the system) don’t get confused. This is part of Windows’ OperatingSystems legacy and its devotion to backward compatibility. It means when you’re naming a file or folder, the system quietly checks “Is this name on the forbidden list?” If yes, it won’t let you use it. Along with "Con", other banned names include "Aux", "PRN", "NUL", "COM1", "LPT1", and a few others. They’re all leftovers from those early days, like little artifacts hiding in the system. It’s an odd file naming convention, but it’s there for a reason (even if that reason is now mostly historical).

Now, the meme shows a guy proudly displaying a Windows Explorer window with a folder named Con (with a recent date and the type listed as “File folder”). If you know the Windows rules, this is immediately interesting because it shouldn’t be possible via normal methods. It’s like seeing a picture of someone breaking a minor law of physics. How did he do it? Well, there are some geeky tricks to force Windows to accept such a name — usually involving special command-line paths or developer tools that bypass the usual checks. For instance, one trick is using a special path prefix \\?\ that tells Windows to skip the name safety rules (essentially a loophole for advanced use). By doing that, a determined user can create a folder named “Con” on an NTFS drive.

For an average user or a newbie developer, this is surprising. It’s not something you encounter in everyday computer use. FileSystems usually just let you name things freely except for a few characters like * or ? which we all learn about. But Windows has this additional secret list of no-go words. So the meme is funny because the guy is treating his Con folder like some secret illegal treasure. In reality, it’s a harmless folder with a funny name, but it’s technically breaking the normal rules of the operating system. It’s as if he found a cheat code in a game or a secret menu item that no one is supposed to access, and he’s going, “Look what I got!”

The phrase “the most illegal thing I own” is of course an exaggeration for humor. Nothing illegal is truly happening; it just feels “illegal” in the sense of violating a rule that Windows usually enforces strictly. People who develop software or who have tinkered with Windows deeply will nod and laugh, because they remember how strict Windows normally is about these names. And people who didn’t know about the rule might learn something new (and weird) about Windows from this meme. It’s a classic bit of DeveloperHumor: turning an obscure technical fact into a joke, and maybe even a teachable moment. Now you know — naming a folder “Con” on Windows is like trying to name a folder “Keyboard” in a magical way. The computer says “No, that name is reserved for something else.” But with a bit of crafty know-how, someone managed to sneak past the guard at the gate. And that’s why in the screenshot, seeing that Con folder sitting there is both amusing and impressive if you understand the context. It’s the nerd equivalent of showing off a trick shot or a glitch in a game.

In summary, the meme is highlighting a specific Windows quirk: reserved device names that you normally can’t use for files/folders. The guy in the meme found a way to create a forbidden-named folder and is jokingly proud of it. It’s a humorous nod to how even modern tech carries some strange rules from the past, and how breaking those rules (even in a trivial way) can feel like a mischievous accomplishment.

Level 3: Con Artist

For a seasoned Windows developer or IT veteran, seeing a folder named Con in an Explorer window immediately prompts a double-take and a chuckle. It’s the kind of inside joke you earn after years of bumping into oddball OS restrictions. Everyone in the Windows world eventually learns the unwritten rule: you cannot name a file or folder “CON”. It’s a small but memorable part of the lore of Microsoft products. The meme plays on this perfectly. The top image shows a guy, in classic YouTube-dramatic fashion, asking:

“Do you wanna see the most illegal thing I own?”

Seasoned devs know that line isn’t setting up a pirated movie or some confidential source code — it’s setting up a FileSystem party trick. The big reveal is that in his Windows Explorer, there’s a directory literally named “Con”. To the uninitiated, that might look utterly mundane (“it’s just a folder named con, so what?”), but to those in the know, it’s like someone showing off they cracked an Operating System taboo. It’s digital contraband, a forbidden name, shown off like a prized butterfly caught in the wild.

Why is this so funny to developers? Because it taps into that shared experience of battling against computers’ odd rules. Any Windows programmer or power user has likely encountered those cryptic errors when trying to use a “bad” filename. Maybe you tried to save a file as LPT1.txt or named a variable “nul” in a script, only to have Windows throw a fit. It’s a rite of passage: you discover that names like CON or PRN are reserved, usually at the most inconvenient time. Suddenly you’re Googling why your code can’t create “report.con” or why renaming a vacation photo to prn.jpg isn’t working. Eventually, someone tells you, “Oh yeah, Windows just doesn’t allow those names... it’s an old legacy thing.” And you’re left feeling both enlightened and slightly absurd – like the computer pulled a prank on you with an ancient rule.

The meme captures that absurdity by exaggerating it. The phrase “the most illegal thing I own” is obviously hyperbole – there’s nothing genuinely illegal about a folder name – but it frames the joke. It’s implying, “Look, I’ve done something that by all normal standards should never be done. I’m basically a digital outlaw.” The humor comes from treating a nerdy hack with the gravitas of a crime. It resonates with developers because we’ve all seen how seriously an OS can enforce its rules. (Ever try to use a filename with a : or * and see Windows scold you? Those moments stick with you.) Here, someone found a way around the rules, and it’s gloriously pointless and impressive at the same time.

The image of the bearded guy (which many recognize from a popular science YouTube channel, adding to the comedic effect) sells it with a mischievous grin. In our minds, he might as well be opening a treasure chest of pirated software or a stash of banned snacks, but nope — it’s just a screenshot of a folder named Con with a timestamp. The banality of the “treasure” makes it even funnier. It’s the ultimate nerd flex: showing off knowledge of filesystem quirks as if it’s a clandestine superpower.

Experienced devs also appreciate the subtle nostalgia. That Con folder is a reminder of the MS-DOS legacy underpinning Windows. It’s a throwback to the days of command-line tricks and config sys files, when these reserved names were actual tools in our kit. Over time, they’ve become more of a trap for unaware programmers than a feature. So there’s a mix of fondness and exasperation when we see something like this. We grin because we remember the frustration of dealing with these names, and now we get to laugh at the whole thing. It’s like an inside joke among Windows geeks: “Heh, remember how NUL is basically a black hole? And remember how you can’t name your kid (or folder) CON because of a 40-year-old operating system quirk?”

By dubbing the folder a “most illegal thing,” the meme also pokes fun at how seriously the OS treats this rule. It’s as if Windows is some stern authority figure: “Thou shalt not name anything 'CON'!” Creating that folder is akin to cheekily sticking a flag on forbidden land. And every long-time Windows user knows that feeling of being just a bit of a rebel by bending the computer to our will. In reality, no police are coming for you when you make a “Con” folder — but it does feel like you’ve defied the sheriff in a one-horse town 😅. The DeveloperHumor here lies in turning an esoteric technical restriction into a moment of drama and glory. We’ve taken a boring constraint and elevated it to legend: “Behold, I have done what Windows forbids!”

In short, the meme hits home with anyone who’s had to deal with Windows’ weird naming conventions. It’s an ode to the crafty developer who knows the system’s secrets. Only a true Con Artist (pun fully intended) 😜 could pull off making a CON folder and then brag about it. And we absolutely love it, because it’s both incredibly silly and technically intriguing. This is the kind of joke you share in the team chat at 2 AM when deployments are running, and instantly at least one person will reply: “Haha, I remember trying that as a kid and thinking I’d broken my computer!” It’s a small piece of hacker triumph over an archaic rule, packaged as a harmless, relatable gag.

Level 4: Ghosts of DOS Past

Deep inside Windows’ architecture lurk relics of the 1980s — curious ghosts of MS-DOS that still haunt our modern Operating System. One such specter is the reserved name CON. In the early PC days, device files were accessed by special names. An OS like CP/M (an ancestor to MS-DOS) and later MS-DOS itself didn’t have fancy directories for devices; instead, it treated certain magic filenames as gateways to hardware. For example, typing CON meant the console (keyboard + screen), and PRN meant the printer. These weren’t files on disk at all, but built-in aliases the OS would intercept. This design allowed simple redirection of input/output streams, but it also meant those names became off-limits for real files. Windows, built with a strong concern for backward compatibility, preserves this quirk to this day. The Win32 API’s naming conventions explicitly forbid creating files or folders with those legacy device names. It’s as if the NTFS file system has a list of sacred words you’re not allowed to use (even though, under the hood, the file system could handle them — it’s the higher-level API enforcing the rule).

To appreciate the joke, one must understand the roster of these reserved words. MS-DOS and Windows set aside several short names (often used with an optional colon) as device references. Some of the classic reserved device names include:

• CON – the console (display and keyboard input)
• PRN – the default printer (parallel port LPT1)
• AUX – the auxiliary device (usually the first serial port COM1)
• NUL – the “null” device (bit-bucket that discards all data, like /dev/null in Unix)
• COM1, COM2, … COM9 – serial communication ports
• LPT1, LPT2, … LPT9 – parallel printer ports (line printers)

These magic names were baked into the OS’s DNA. If a program tries to open CON (with or without a file extension), the system doesn’t look on disk for a file — it summons the console device driver. Because of this, naming a file or directory "CON" (or "PRN", "AUX", etc.) is normally impossible through standard means. The Windows environment will outright refuse, protecting those names for its own device I/O purposes. It’s a constraint born from a very different era of computing that has cascaded into every modern Windows release.

Now, how on earth do you end up with a folder actually named Con? This is where some NT internals and arcane file path sorcery come in. Under the covers, Windows has an NT Object Manager namespace where devices and files live. Normally, when you use an everyday path like C:\Folder\File.txt, the Win32 layer parses it and checks for these special names. But if you use a special prefix \\?\ (the **NT path** prefix for extended-length paths), you tell Windows: “Skip the usual dos-style checks; take this path raw to the kernel.” In this mode, the usual rules (including the reserved name checks and path length limits) are bypassed. That’s the loophole hackers (the playful kind) exploit to create a forbidden CON directory. For example, using a command prompt one could run:

C:\> mkdir con  
# Error: The directory name is invalid.

C:\> mkdir \\?\C:\Temp\Con  
# (No error — "Con" folder created via the NT path prefix!)

In the first attempt, the FileSystem parser screams in protest (because "con" is reserved). In the second, the special \\?\ prefix bypasses the usual parser, and the NT kernel dutifully creates a directory literally named "Con". This folder is an anomaly: Windows Explorer and normal commands usually won’t let you create or even easily interact with it, because any reference to “Con” without the magic prefix gets interpreted as the console device. It’s like sneaking contraband past a security checkpoint by using a secret back door.

For operating system aficionados, this is a delightful example of how historical design decisions carry forward. The reserved name CON is basically a hard-coded ghost from the DOS era, still prioritized by modern Windows for the sake of compatibility. In fact, these ghosts have caused real mischief in the past — there were infamous cases where trying to open a path like C:\con\con on Windows 95/98 would freeze the system, as the poor OS got caught in a loop talking to its own console device. 🙃 These days it won’t crash Windows NT, but the rule against “Con” remains ironclad. The meme’s forbidden folder is a perfect illustration of how deeply these rules are ingrained. It’s essentially flaunting a filesystem quirk that by all rights should be impossible. In academic terms, it’s a demonstration of an edge case in the Windows I/O subsystem; in practical terms, it’s like holding a piece of digital contraband from a bygone computing age.