October 27, 2026 — Evening

A 34-Year-Old Program Running on Windows 11

Windows has always been praised for backwards compatibility, but a blogger at Enlyth just demonstrated it in the most literal way possible: they got a program compiled in November 1992 running on the latest Windows 11, unmodified, with no emulation.

The program is CDPLAYER.EXE, linked on November 16, 1992, from an early Windows NT 3.1 pre-release build (Build 347). It is almost 34 years old. It runs on Windows 11 today because of a chain of design decisions that could have broken at any point in the intervening three decades and did not.

Why most early NT apps crash on Windows 11

The investigation started with a simple question: what is the oldest GUI application that still runs on Windows 11 without modification or emulation?

Windows 11 cannot run 16-bit programs at all because 64-bit Windows dropped NTVDM, the virtual DOS machine. So the search was limited to 32-bit Windows programs from the early NT era.

Most early NT 3.1 programs fail for one of two reasons:

• Draft PE format: Builds from 1991 used a pre-release Portable Executable format that modern Windows no longer understands.
• Calling convention mismatch: Builds up to mid-1992 assumed the cdecl calling convention for Windows API calls instead of stdcall. When a 1992-era caller pushes arguments and calls ShowWindow, the modern stdcall implementation cleans up the stack with ret 4, and then the old caller cleans up the same stack space again. The arguments get removed twice, and the program crashes.

Why CDPLAYER.EXE survives

CDPLAYER.EXE from Build 347 (November 16, 1992) dodges both bullets. By that build, the calling convention had been fixed to stdcall. And while other programs in the same build crash because their bundled C runtime is incompatible, CDPLAYER.EXE links against the system's crtdll.dll instead of shipping its own.

Windows 11 still ships crtdll.dll in SysWOW64.

That is the entire chain. A program from 1992 calls a system DLL that Microsoft has kept shipping for 34 years, and it works. When you launch it, you get a CD player interface, which looks confused because the test machine has no CD-ROM drive. But with a small emulation DLL (cdemu.dll) providing fake audio data, it actually plays.

The FreeCell baseline

Before finding CDPLAYER.EXE, the previous best result was FREECELL.EXE from the Win32s pack, dated February 22, 1993. That is 33 years and 8 months old. It runs and is fully playable on Windows 11 without any changes.

CDPLAYER.EXE beats it by about 10 months.

Cheating with otvdm

If you are willing to bend the rules, the otvdm project (an open-source 16-bit Windows emulator for 64-bit Windows) opens up a much older category. The blogger demonstrated REVERSI.EXE from Windows 1.01, dated November 15, 1985, running on Windows 11 through otvdm. That is a 41-year-old GUI program.

It is cheating in the same way that running a DOS game through DOSBox is cheating, but it is a nice reminder that Windows 1.01 shipped with games, and one of them still works if you give it a bridge.

Why this matters

Backwards compatibility is a feature that costs enormous engineering effort and produces no visible benefit until someone tries to run a 34-year-old CD player on a machine that has never seen a physical disc. Microsoft has maintained crtdll.dll, SysWOW64, and the Win32 ABI across four decades of architecture shifts, from x86 to x64 to ARM, because breaking it would break customers whose software is older than some of their employees.

The result is that a program compiled when Windows NT was a pre-release product, when the World Wide Web had just been invented, runs on a machine that can run GLM-5.2 locally. That is not nostalgia. That is engineering discipline sustained for 34 years.

Sources:

[1] enlyth, "Oldest GUI application that still runs on Windows 11," Enlyth Blog, October 26, 2026. https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/

[2] otya128, winevdm — 16-bit Windows emulator for 64-bit Windows, GitHub. https://github.com/otya128/winevdm