---
title: "Oldest GUI application that still runs on Windows 11"
slug: oldest-gui-application-that-still-runs-on-windows-11
url: https://listedarticles.com/articles/oldest-gui-application-that-still-runs-on-windows-11
canonical_url: https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/
content_type: blog_post
language: en
published_at: 2026-10-26T00:00:00.000Z
updated_at: 2026-10-26T20:16:40.504Z
author: "enlyth"
authored_by: human
publisher: "enlyth"
publisher_url: https://blog.enlyth.com/
topics: ["Windows", "Retro Computing", "Software History"]
license: all-rights-reserved
word_count: 525
reading_minutes: 2
citation: "enlyth, enlyth. \"Oldest GUI application that still runs on Windows 11.\" 26 Oct 2026. https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/ (all-rights-reserved)"
# The full text follows. The web page shows an extract and sends readers
# to the source above; quote the citation and link the canonical URL.
---

# Oldest GUI application that still runs on Windows 11

> enlyth investigates which is the oldest unmodified GUI application that still runs natively on 64-bit Windows 11, given that 16-bit programs are no longer supported, and shows Windows 1.01's REVERSI.EXE running via otvdm as a bonus.

26 October 2026·2 min read

- [#windows](https://blog.enlyth.com/tags/windows/)
- [#gui](https://blog.enlyth.com/tags/gui/)

# Early investigation

For a while I’ve been wondering about a silly question, which is, what’s the oldest application with a GUI that will still run on Windows 11 without modifications or emulation.

Given Windows’ excellent backwards compatibility, I expected the answer to be something impressively old.

Sadly, Windows 11 can’t run 16-bit Windows programs by itself, because 64-bit Windows has no [NTVDM](https://en.wikipedia.org/wiki/Virtual_DOS_machine#Windows_NTVDM), so we’re going to have to find something from the early NT era.

I remember asking this question a while ago on an anonymous forum, where someone pointed me to [Win32s](https://en.wikipedia.org/wiki/Win32s), and suggested to find an early release version of it with `FREECELL.exe`.

So I did exactly that, and lo and behold, `FREECELL.EXE` with a date modified of `22-Feb-93` running and fully playable, without any changes on the latest version of Windows 11:

![FREECELL.EXE from 1993](https://blog.enlyth.com/_astro/image.Bg57xYSH_1uh08L.webp)

At the time of this post, that’s a 33 years and 8 months old application, which is impressively almost as old as me.

So I kinda thought “cool”, considered this a solved mystery and forgot about it shortly afterwards. But for some reason, this question popped into my mind again lately and this time I decided to dig deeper to see if I can find something older.

# Further efforts

Digging through old Windows versions on the Internet Archive, I found some early NT 3.1 pre-release versions that seemed promising, but the main issue seemed to be either incompatibility with today’s executable format or API changes that came later in development.

The earliest 1991 versions used a draft PE format not compatible with modern Windows, and builds up to mid-1992 assumed the [`cdecl`](https://en.wikipedia.org/wiki/X86_calling_conventions#cdecl) calling convention instead of `stdcall` for Windows API calls, so arguments would get removed twice, as such:

```
push hwnd          ; 4 bytes of args
call [ShowWindow]  ; Win11 ShowWindow is stdcall, ends with "ret 4" and removes them
add  esp, 4        ; the 1992 caller removes them again
```

Which would understandably cause the program to crash.

There was one application that caught my eye though, from Build 347, and that was `CDPLAYER.EXE`, linked on `16-Nov-1992`. By then the calling convention was fixed, but the other programs in that build crash in their bundled C runtime. `CDPLAYER.EXE` avoids that by using the system’s `crtdll.dll`, and Windows 11 still ships a `crtdll.dll` in `SysWOW64`.

If you start the program, you get something like this:

![CDPLAYER.EXE no CD-ROM drive found](https://blog.enlyth.com/_astro/image-3.ccUj1wn8_1qfbsq.webp)

That is because, duh, my computer doesn’t have a CD-ROM drive. But you can use a small DLL (`cdemu.dll`) to emulate one with some fake audio data and actually get it to play audio:

![CDPLAYER.EXE with emulated CD-ROM](https://blog.enlyth.com/_astro/image-2.CW-t_DpM_vg2wv.webp)

Pretty cool for a program that’s almost 34 years old!

# What if we cheat?

So earlier I mentioned that 16-bit programs are out of the picture because they are no longer supported.

But if you want, you can use something like [otvdm](https://github.com/otya128/winevdm) to run older Windows applications.

Behold, a fully playable version of `REVERSI.EXE` dated `15-Nov-1985` running on Windows 11, taken from Windows 1.01:

![alt text](https://blog.enlyth.com/_astro/image-4.BUOY9wBP_ZSDHhX.webp)

And although using `otvdm` does feel like cheating, I thought it was cool enough to include in this post.