Hackaday's Jenny List reported on an investigation by a developer who goes by Enlyth. It found a November 1992 CD Player binary that runs on Windows 11, and it separately showed a November 1985 program running through a third-party layer. This article explains both results and what each one does and doesn't prove.
Why the question has a hard floor
Open-source software gets recompiled for each new distribution, so old code keeps moving forward. Windows software usually ships as a compiled binary. That binary only works if the host OS still provides the APIs it calls.
Windows 11 has no native 16-bit support, so the search for the oldest runnable app starts in the 32-bit world. Hackaday describes two entry points:
- Windows NT, the lineage that leads to Windows 11.
- Win32s, the extension that let Windows 3.1 run some 32-bit programs.
The direct-run results
1993 FreeCell (Win32s). A Win32s build of FreeCell from 1993 runs happily on Windows 11. But it wasn't the oldest program that worked.
Pre-release Windows NT 3.1 binaries. The investigation then went into early NT builds. Their APIs were incompatible with later ones, so many binaries crashed.
November 1992 CD Player. This is the oldest official binary reported to run. It works because it calls a DLL that is still present in Windows 11. It also needs another DLL to emulate a CD drive. The report doesn't name either DLL.
Hackaday doesn't specify the Windows 11 build tested. It also doesn't give a full test log. So "oldest" here means the oldest found by this investigation. It doesn't prove that no older binary can run.
The 1985 example needs WineVDM
Windows 11 has no built-in 16-bit subsystem, but Hackaday notes that a WineVDM exists to fill that gap. It then shows Reversi from Windows 1.01, dated November 1985, running on Windows 11.
This is not native execution. The project's GitHub page describes an altered version of winevdm, a 16-bit Windows emulator, ported to 64-bit Windows. Its repository covers Windows 1.x, 2.x, 3.0 and 3.1. A third-party guide describes the project as an open-source compatibility layer, based on Wine components, that runs 16-bit Windows apps on 64-bit Windows without virtualization.
So the fair summary is:
| Result | Date | How it runs |
|---|---|---|
| Oldest official binary found | November 1992 | Directly, using DLLs still present in Windows 11 |
| Oldest cited example | November 1985 | With WineVDM, a third-party layer |
Trying WineVDM yourself
The project's documentation gives these basics. They are not part of Hackaday's testing.
- Download the stable release from the project's GitHub page, or compile it.
- Extract it to a folder. One guide suggests a folder such as C:\OTVDM.
- Run the install shortcut, or right-click install.inf and choose Install. Another guide mentions an "Install (no console)" option.
- Launch a 16-bit program by dragging it onto otvdm.exe. Alternatively, run otvdmw.exe, which lets you pick a 16-bit executable through the Open File dialog.
Common failure points, per the project's notes:
- If Windows reports that VCRUNTIME140.dll is missing, install the 32-bit Visual C++ Redistributable for Visual Studio 2017.
- If Windows Update resets the registry entries, repeat the installation.
- A registry file, uninstall.reg, is provided for removal.
Expect imperfect results. Mendelson's guide says simple DOS programs may run, but anything more complicated needs vDos or DOSBox. WineVDM's own documentation also calls its DOS emulation incomplete.
What this does and doesn't tell you
The result shows that Windows 11 still carries some deep 32-bit compatibility. One Hackaday commenter reported that late-1990s Delphi programs still run fine. That is anecdotal, but it fits the picture.
It doesn't mean old software is safe to depend on. A launch doesn't prove that installers, hardware access, copy protection, or every API a program uses will work. The CD Player's reliance on an emulation DLL is a reminder that a successful start can depend on specific surviving components. Anyone planning to keep legacy business software alive should test their own applications. A VM or a compatibility layer is a workaround, not a guarantee.