<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw" -->

---
title: Oldest GUI application that still runs on Windows 11
description: FREECELL.EXE dated 22-Feb-93 from an early Win32s release still runs unmodified on Windows 11, making it roughly 33 years and 8 months old. Digging into early...
canonical: https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Oldest GUI application that still runs on Windows 11 | daily.dev
og:description: FREECELL.EXE dated 22-Feb-93 from an early Win32s release still runs unmodified on Windows 11, making it roughly 33 years and 8 months old. Digging into early...
og:url: https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw
og:image: https://api.daily.dev/og/posts/Lm1ZLZKUw.png
og:image:alt: Oldest GUI application that still runs on Windows 11
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Oldest GUI application that still runs on Windows 11

**[Hacker News](https://daily.dev/sources/hn)** · 3 min read · 0 upvotes · 0 comments

## Summary

FREECELL.EXE dated 22-Feb-93 from an early Win32s release still runs unmodified on Windows 11, making it roughly 33 years and 8 months old. Digging into early NT 3.1 pre-release builds turned up promising versions, but 1991 builds use an incompatible PE format and builds up to mid-1992 use the wrong calling convention, causing crashes. CDPLAYER.EXE from Build 347, linked 16-Nov-1992, avoids the bundled C runtime crash by using the system's crtdll.dll, which Windows 11 still ships in SysWOW64; a small DLL called cdemu.dll can emulate a CD-ROM to get it playing fake audio. Using otvdm to bypass 16-bit restrictions, REVERSI.EXE dated 15-Nov-1985 from Windows 1.01 also runs.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11>

## Questions this post answers

### Why can't Windows 11 run old 16-bit Windows programs natively?

64-bit Windows 11 has no NTVDM (NT Virtual DOS Machine), the subsystem that previously translated 16-bit Windows calls for execution. Without it, 16-bit executables cannot run without emulation. Tools like otvdm can work around this by emulating the needed environment, as demonstrated by getting REVERSI.EXE from 1985's Windows 1.01 running on Windows 11.

_Anyone chasing legacy Windows compatibility quirks can find more deep dives like this on daily.dev._

### What is the oldest unmodified GUI application that still runs on Windows 11?

FREECELL.EXE, dated 22-Feb-1993 and from an early Win32s release, runs fully playable and unmodified on Windows 11, making it about 33 years and 8 months old. An even older candidate, CDPLAYER.EXE from Build 347 (linked 16-Nov-1992), also runs because it uses the system's crtdll.dll, which Windows 11 still ships in SysWOW64.

_Developers curious about Windows' backwards compatibility limits can track similar findings on daily.dev._

### Why did early 1990s Windows NT builds crash when run on modern Windows due to calling convention issues?

Builds up to mid-1992 assumed the cdecl calling convention for Windows API calls instead of stdcall. Since modern Windows API functions like ShowWindow use stdcall and already remove their own arguments with a 'ret 4' instruction, the old cdecl-style caller would remove the arguments a second time with an extra 'add esp, 4', corrupting the stack and crashing the program.

_Developers debugging calling-convention mismatches in old binaries can find similar technical breakdowns on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 131 comments across hackernews, lobsters (as of 2026-10-26).

**TL;DR:** The technical backward-compatibility story itself is widely admired, but the discussion mostly spirals into a long, contentious debate about whether desktop UI design has improved or regressed since Windows 95.

**Sentiment:** 40% positive · 15% mixed · 45% skeptical

**The case for**

- Long-term binary compatibility in Windows is seen as remarkable and commendable, likened to nesting-doll architecture.
- Several people enjoyed nostalgic tangents, like custom FreeCell variants, old CD player UIs, and a touching personal anecdote about preserving a parent's FreeCell score.
- One commenter shared a related real-world effort (patching a 90s Windows 3.1 CD-ROM game) that reinforced how thorough Windows backward compatibility generally is.

**The pushback**

- Many argue that modern UI/UX has regressed due to 'mobile first' and minimalist/flat design trends replacing menu bars and native controls.
- Others strongly push back, saying nostalgia is overrated and that Windows 95-era UI would be unusable for how people multitask today.
- Some see current app UI consistency as worse than in the past due to cross-platform frameworks like Electron, though others dispute this was ever truly consistent.
- Debate over whether classic Win32 API development is still worthwhile versus cross-platform or modern frameworks like WinUI/.NET, with complaints about tooling pain points.

**By community**

- hackernews (heated): A large share of the thread turns into an extended, often testy argument about whether desktop UI has improved or declined since the 90s, alongside smaller side-threads on Win32 development and OS backward compatibility.
- lobsters (positive): The single comment is a brief, approving personal anecdote about having written Win32s software from that era.

**Hottest debate:** Whether desktop/UI design has gotten better or worse since Windows 95, with sharp disagreement over nostalgia versus practical usability today.

**Open questions**

- Could an even older GUI binary (e.g., from early X11/Unix systems) be found that still runs unmodified today?
- Is there a definitively 'best' era of Windows UI design, or does this depend heavily on personal workflow needs?

**Highlights**

> One crucial part of my role as my family's de facto IT support was making sure my mom's FreeCell score record (which was just a Windows registry value) made it from each computer to the next across countless upgrades. She hated the new version that came out somewhere along the way because the card decks changed. (Windows 7? Windows 10? I switched to Linux full time in the XP era so my memory is a little fuzzy.) So I made sure to keep a backup of the Win32 version she was used to, and loaded it onto every machine she ever owned. It wasn't quite the 33 years of its lifetime, but probably close to 30. Mom passed earlier this year, so the FreeCell score record won't ever increment again, but I still made a point to back it up one last time when going through her desktop this summer.
> — [anticorporate on hackernews · 2 comments](https://news.ycombinator.com/item?id=50251964)

> Windows 95 was the last release that had serious user testing in controlled environments. (They were also cribbing lots of notes from NeXT, which helped.) Something fundamentally switched around 1998-2002 in how interface design was viewed and approached. I started my career in software as a design summer intern at a company that made a Windows “groupware” application in 1997. They took pride in following the platform’s guidelines and actually testing their designs with real users being videotaped trying to use it. The company’s UI design department was tiny, but employed both an industrial designer and a cognitive scientist. Five years later, everybody I met in UI design was a graphic designer who was drawing glossy website mockups in Photoshop. The elder lore of science-based UI design was completely lost when Web 2.0 happened and app designs became vibes-based. Even Apple couldn’t resist the tide. (Indeed Steve Jobs’s return to Apple in 1997 was a major contributor because he had developed a taste for user-hostile skeuomorphism like the brushed metal QuickTime Player.)
> — [pavlov on hackernews · 1 comments](https://news.ycombinator.com/item?id=50250896)

> https://xkcd.com/1909/ It is amazing, though. Wintel is basically a Matryoshka doll (Russian nesting dolls), where each version contains all the previous versions. (Just look at how a PC boots up!) The dedication to compatibility is commendable, and you don't really see it on the other OS's. On that note, this is one of my favorite articles: Win32 is the only stable ABI on Linux https://blog.hiler.eu/win32-the-only-stable-abi/ I think that's very funny. Speaking of which, EasyToon also runs in WINE, of course :) https://news.ycombinator.com/item?id=50250809
> — [andai on hackernews](https://news.ycombinator.com/item?id=50250838)

> I just resurrected a 90s kids CD-ROM game that shipped for Windows 3.1 - https://github.com/matthewbloch/orlys-draw-a-story-fixes The finished patch DLL ended up being a tour of the stuff that broke. The game did launch on Windows 11 but the main issue was that the 8-bit pre-DirectDraw behaviour was broken - for 256 colour screens, Windows 11 resolvesld palette indices only once, but the game relies on being able to change the palette for fades etc. Most of the screeen ended up black, but you could see the animated parts just fine. So most of fix ended up being to hook every draw call and implement a virtual GDI that acted like a graphics card of the day. There was a 32-bit disc space check that overflowed, a couple of use-after-free crashes and some racey threading calls that can't have been tested on a machine with 2 CPUs. Backwards compatibility from Microsoft was almost all there, and probably would have kept Orly running for a couple of subsequent Windows releases. But it relies on a developer meeting them half-way, it's not an emulation layer.
> — [mattbee on hackernews · 1 comments](https://news.ycombinator.com/item?id=50250806)

> Speaking of FreeCell, a couple weeks ago I was visiting my 95yr-old grandmother and noticed she still plays oldschool FreeCell, specifically a variant that's really hard to track down now called FreeCell Pro [https://cards.fandom.com/wiki/FreeCell_Pro] It inspired a weekend project. I always liked that you could swap the card backs in OG FreeCell and play with different "themed" decks, so I vibecoded something a little more modern. I got carried away and added a roguelite mode too (yeah I know how "Roguelite FreeCell" sounds). Anyway, it's free to play on the web, no ads: [https://freecellworlds.com/]
> — [capnjngl on hackernews · 2 comments](https://news.ycombinator.com/item?id=50249468)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50248055) · 204 points · 130 comments
- [lobsters](https://lobste.rs/s/rwubks/oldest_gui_application_still_runs_on) · 19 points · 1 comments

## Similar posts on daily.dev

- [Windows 1.0 and the WinAPI, 40 Years Later](https://daily.dev/posts/windows-1-0-and-the-winapi-40-years-later-neh5lkqwf) · Two Stop Bits · 1 upvotes · 0 comments
- [4 20-year-old Windows utilities that still do things Windows 11 can't](https://daily.dev/posts/4-20-year-old-windows-utilities-that-still-do-things-windows-11-can-t-9kcwy7pek) · XDA Developers · 0 upvotes · 0 comments
- [A trip down shareware lane](https://daily.dev/posts/a-trip-down-shareware-lane-yw6uwnlpz) · InfoWorld · 0 upvotes · 0 comments
- [Why Windows 11 still ships with Windows 95's memory manager hidden inside it](https://daily.dev/posts/why-windows-11-still-ships-with-windows-95-s-memory-manager-hidden-inside-it-bdhv6j8kx) · Hacker News · 0 upvotes · 0 comments
- [November 11, 2025](https://daily.dev/posts/november-11-2025-bknlgh1d0) · DevBlogs · 0 upvotes · 0 comments

---

Tags: [#windows](https://daily.dev/tags/windows), [#reverse-engineering](https://daily.dev/tags/reverse-engineering), [#retrocomputing](https://daily.dev/tags/retrocomputing)

[View this post on daily.dev](https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Oldest GUI application that still runs on Windows 11","url":"https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw"},"datePublished":"2026-10-26T19:54:40.233Z","dateModified":"2026-10-26T22:52:30.104Z","description":"FREECELL.EXE dated 22-Feb-93 from an early Win32s release still runs unmodified on Windows 11, making it roughly 33 years and 8 months old. Digging into early...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"windows,reverse-engineering,retrocomputing","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Oldest GUI application that still runs on Windows 11"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/oldest-gui-application-that-still-runs-on-windows-11-lm1zlzkuw#faq","mainEntity":[{"@type":"Question","name":"Why can't Windows 11 run old 16-bit Windows programs natively?","acceptedAnswer":{"@type":"Answer","text":"64-bit Windows 11 has no NTVDM (NT Virtual DOS Machine), the subsystem that previously translated 16-bit Windows calls for execution. Without it, 16-bit executables cannot run without emulation. Tools like otvdm can work around this by emulating the needed environment, as demonstrated by getting REVERSI.EXE from 1985's Windows 1.01 running on Windows 11. Anyone chasing legacy Windows compatibility quirks can find more deep dives like this on daily.dev."}},{"@type":"Question","name":"What is the oldest unmodified GUI application that still runs on Windows 11?","acceptedAnswer":{"@type":"Answer","text":"FREECELL.EXE, dated 22-Feb-1993 and from an early Win32s release, runs fully playable and unmodified on Windows 11, making it about 33 years and 8 months old. An even older candidate, CDPLAYER.EXE from Build 347 (linked 16-Nov-1992), also runs because it uses the system's crtdll.dll, which Windows 11 still ships in SysWOW64. Developers curious about Windows' backwards compatibility limits can track similar findings on daily.dev."}},{"@type":"Question","name":"Why did early 1990s Windows NT builds crash when run on modern Windows due to calling convention issues?","acceptedAnswer":{"@type":"Answer","text":"Builds up to mid-1992 assumed the cdecl calling convention for Windows API calls instead of stdcall. Since modern Windows API functions like ShowWindow use stdcall and already remove their own arguments with a 'ret 4' instruction, the old cdecl-style caller would remove the arguments a second time with an extra 'add esp, 4', corrupting the stack and crashing the program. Developers debugging calling-convention mismatches in old binaries can find similar technical breakdowns on daily.dev."}}]}
```

