Windows CE on Nintendo 64: how WinCE64 turns the N64 into a tiny Microsoft PC

A developer called ThroatyMumbo has got Windows CE 2.11 running on real Nintendo 64 hardware through a GitHub project called WinCE64. That sentence sounds like something shouted across a forum in 2002 by someone who had not slept, but it is real, it boots, and it gives Nintendo’s cartridge-powered icon something it was never emotionally prepared for: a Start button.

The N64’s unexpected corporate phase

The Nintendo 64 was built for Super Mario 64, GoldenEye 007, Mario Kart 64 and the kind of living-room multiplayer arguments that could end friendships for an afternoon. It was not built to behave like a compact Windows machine. It had no keyboard, no mouse, no hard drive and a controller that looked as if Nintendo had briefly considered humans might evolve a third hand. Yet WinCE64 takes that machine and nudges it into the world of desktop windows, taskbars, file browsing and embedded operating systems.

The trick is not quite as impossible as it first sounds. The N64 used a MIPS-based processor, and Windows CE had support for MIPS hardware back in the late 1990s. That technical overlap gave ThroatyMumbo a tiny doorway into a very strange room. Windows CE was Microsoft’s lightweight operating system for handhelds, terminals, industrial devices and other small computers that needed Windows-like behaviour without becoming a full beige office tower. The N64, meanwhile, was designed to throw polygons at a CRT television and make children shout “screen-looking!” during four-player matches. Putting the two together feels like installing Outlook on a go-kart, but the underlying architecture gives the idea just enough plausibility to become dangerous. That is the wonderful thing about projects like this: they begin as a joke, then gradually reveal themselves as serious engineering wearing a clown nose. At first glance, “Windows on an N64” sounds like a novelty screenshot. Look closer, and it becomes a dense, stubborn, low-level hardware port that had to persuade a games console to act like a computer.

This is not just a fake Windows skin

WinCE64 is not a homebrew demo with a pretend desktop painted on top. It uses real Windows CE 2.11 components and combines them with custom N64-specific code to make the operating system work on Nintendo’s hardware. That distinction matters, because drawing a Start button is easy. Making an operating system boot, display graphics, handle input, access storage and keep running without collapsing into a black screen of despair is a very different beast.

The project has to provide the glue that Windows CE would normally expect from a supported hardware platform. That means low-level boot work, a hardware abstraction layer, display handling, controller input, storage support, audio output and all the unglamorous bits that only become visible when they fail. It is the kind of engineering where success looks deceptively simple. A desktop appears on screen and everyone says, “That’s neat.” Meanwhile, behind that desktop is a pile of code doing the digital equivalent of holding a wardrobe together with both hands while pretending everything is fine. That is what makes WinCE64 so satisfying. The absurdity is obvious, but the achievement is real. The Nintendo 64 was never meant to host a Microsoft operating system, so every working feature feels like a small act of persuasion. The console is not just wearing a Windows costume; it is actually being asked to do Windows things, which is much funnier and much more impressive.

The controller becomes a mouse, because of course it does

Since the Nintendo 64 did not come with a mouse, the controller has been promoted against its will. The analogue stick moves the cursor, the A button works as left click, and the B button works as right click. This is surprisingly logical and completely cursed at the same time.

There is something beautiful about using the same analogue stick that once guided Mario around Bob-omb Battlefield to move a Windows CE pointer across a desktop. That stick has survived platforming, racing, wrestling games, shooters, speedruns and the palm-destroying crimes of Mario Party. Now it has a quiet office job. Somewhere, a Microsoft ergonomics designer from 1998 has just woken up in a cold sweat wondering why the mouse has a Z trigger.

This input setup is also one of the details that makes the project feel properly alive. A fake desktop can look convincing in a still image, but the moment you can move a cursor, click icons and interact with the system, the whole thing becomes much more charming. The N64 is not merely showing Windows CE. It is participating. It is trying to be a computer with the tools it has available, like a golden retriever attempting tax returns.

Storage and sound on a machine that still thinks in cartridges

WinCE64 also supports SD card access through an EverDrive-64 X7, allowing storage to appear inside Windows CE as \SDCard. That means files and compatible Windows CE programs can be loaded from removable storage, which sounds ordinary until you remember this is happening on a console whose original idea of removable media was “large grey cartridge with a label and childhood fingerprints on it”.

That one feature gives the whole project an alternate-history flavour. You can almost imagine Nintendo releasing some bizarre productivity bundle in the late 1990s: an official keyboard, a mouse shaped like Yoshi, a cartridge-based office suite, maybe a tiny printer that only worked when the moon was in the correct phase. It would have sold terribly, been reviewed with confusion, and now cost more than a used car on auction sites.

Audio support is there too, routed through the N64’s sound hardware. This means Microsoft’s embedded operating system can make noise through the same console that once delivered Ocarina of Time melodies and GoldenEye explosions. Whether that is a technical triumph or a mild spiritual disturbance depends on how you feel about Windows system sounds coming out of Nintendo hardware. Either way, it works, and in retro computing, “it works” is often the whole poem.

A familiar desktop in a deeply unfamiliar place

One of the cleverest parts of WinCE64 is the desktop environment itself. Windows CE provides the operating system foundations, but the familiar-looking desktop shell elements are part of the project’s own work. The taskbar, Start button, clock and file browser are custom-built around the Windows CE environment to create something that immediately reads as “Windows” even though it is running on hardware that once expected you to insert Wave Race 64.

That visual familiarity is what makes the whole thing so funny. The moment a taskbar appears at the bottom of the screen, your brain knows exactly what it is looking at. It does not matter that the machine underneath has four controller ports and a cartridge slot. It does not matter that there is no normal keyboard or mouse. The language of Windows is so recognisable that it overrides common sense for a second. Then common sense catches up and asks why a Nintendo 64 has a file browser. That tiny mental delay is the magic of the project. It looks normal just long enough to become deeply abnormal. It is a Windows-like desktop where no Windows-like desktop should be, and the more polished it looks, the stranger it becomes. A rough demo would be amusing. A working desktop is surreal.

Real hardware makes the madness better

The best part is that WinCE64 is aimed at real N64 hardware, not just a comfortable emulator environment where reality can be paused, inspected and quietly edited when it becomes inconvenient. Real hardware is rude. Real hardware has timing issues, memory behaviour, bus quirks and undocumented little habits that do not care how elegant your code looked in theory. If something goes wrong, the console will not explain itself. It will simply sit there, fail, and let you become a worse person for several hours.

That is why running on the actual machine matters. The project has to deal with the N64 as a physical console, with its real video interface, real controller input, real cartridge-side storage and real hardware constraints. It cannot simply rely on an emulator being generous. It has to make Nintendo’s original box cooperate. There is a special kind of satisfaction in that. Emulators are essential and brilliant, but original hardware adds drama. When something works on the real machine, it feels less like a simulation and more like a negotiation that ended peacefully. The N64 may not understand why it has been asked to become a Windows CE computer, but with enough custom code, it seems willing to give it a go.

No handy ROM download, sadly

Anyone hoping to grab a ready-made ROM and immediately turn their N64 into the world’s least practical workstation will need to lower their expectations. WinCE64 is available on GitHub, but the finished image depends on Microsoft Windows CE 2.11 components, so a complete prebuilt ROM is not distributed. That is not a fun-sponge decision; it is the legal reality of working with old Microsoft binaries.

Instead, the project provides the open-source work and build instructions, while anyone wanting to reproduce it needs to supply the required Windows CE development tools and components themselves. They also need the N64 homebrew toolchain and suitable flash cartridge hardware, such as an EverDrive-64 X7. In other words, this is not a casual “download and play” weekend project. This is more of a “summon old SDKs, argue with tooling from another century, stare into the abyss, and eventually emerge with a Nintendo 64 that thinks it is a small office terminal” situation. Which feels appropriate. Something this strange should not be too easy. There should be at least one moment where the builder wonders whether they are doing computing or archaeology.

Why do this? because that is how retro computing works

The obvious question is why anyone would put Windows CE on a Nintendo 64. The practical answer is: they probably should not. The better answer is: because the overlap was there, the hardware was interesting, and curiosity is one of computing’s most powerful renewable fuels. Retro hardware projects do not always need a sensible use case. Some exist to preserve knowledge. Some exist to test limits. Some exist because a developer noticed a technical possibility and could not stop thinking about it. WinCE64 lands beautifully in that category. It is a technical experiment, a retro computing joke, a hardware study and a love letter to old systems all at once.

It also shows how much depth remains inside machines people think they already understand. The N64 is not just a games console frozen in 1996. It is a MIPS-based computer with unusual hardware, specific constraints and enough flexibility to surprise people nearly three decades later. In the hands of homebrew developers, old consoles stop being closed boxes and become puzzles. Sometimes the puzzle is “can we make a new game?” Sometimes it is “can we improve video output?” Sometimes, apparently, it is “can we make this thing boot a Microsoft embedded operating system and click around with the A button?” The answer, wonderfully, is yes.

The productivity console nobody asked for

Once you see Windows CE on an N64, it is hard not to imagine the alternate universe where Nintendo took this seriously. Perhaps there would have been a keyboard accessory, an official mouse, a memory expansion marketed for business users, and a cartridge called Nintendo Office 64. It would include a calendar, a calculator, a basic word processor and a spreadsheet program where every formula error played the Mario Kart item-box sound.

Imagine writing a document on the same machine that hosted Banjo-Kazooie. Imagine saving a file through an EverDrive while holding a three-pronged controller. Imagine telling someone you cannot send the report yet because your N64 is still booting. Imagine a workplace where the IT department has to ask whether the problem is with Windows CE or the Rumble Pak. Then there is the inevitable thought of Clippy. You cannot put Windows on the wrong machine and not summon the paperclip spiritually. “It looks like you’re trying to defeat Bowser. Would you like help?” No, Clippy. Not now. “It looks like you’re trying to configure Joybus input.” Actually, yes, that one might be useful. Sit down, we have work to do.

A joke that becomes more impressive the longer you stare at it

The finest thing about WinCE64 is that it does not stop being funny once you understand it better. It becomes funnier and more impressive at the same time. At first, it is simply Windows CE on an N64, which is already enough to raise an eyebrow. Then the details arrive: real hardware, MIPS compatibility, a custom hardware layer, controller-based mouse input, SD card access, audio support, a custom desktop shell, old Microsoft tooling and a build process that politely filters out anyone who is not deeply committed.

That is the ideal shape for a retro project. The surface-level gag brings you in, and the engineering keeps you there. It is not just a screenshot designed for social media. It is a working demonstration of how much patience and technical understanding can be poured into an idea that is, on the face of it, completely ridiculous. And that is not a criticism. Ridiculous projects are often where the best learning happens. They force people to understand systems deeply, because there is no official path and no sensible manual saying, “Chapter 4: Installing Windows CE on Your Nintendo 64.” Every working feature represents a problem solved from first principles or near enough.

The N64 still has surprises left

The Nintendo 64 has been studied, emulated, repaired, modded, expanded and celebrated for decades, but WinCE64 shows that old hardware can still be made to do things that feel fresh. That is the joy of the retro scene. These machines are not dead objects in a museum case. They are still being explored by people with soldering irons, flash carts, source code, patience and a worrying tolerance for obscure bugs.

WinCE64 is not going to make the N64 useful as a modern computer. Nobody is replacing their laptop with a console from 1996 and a controller mouse, unless they are making a point so aggressively that friends should check on them. But usefulness is not the only measure of value. Sometimes a project matters because it is clever, because it is funny, because it documents old technology, because it teaches people something, or because it makes a familiar machine feel strange again. That is exactly what this does. It takes one of the most recognisable consoles ever made and gives it a second identity as a tiny embedded Windows box. It turns a living-room games machine into something that looks like it might ask you to browse a directory, check the clock and launch a small utility from storage. It makes the N64 feel both nostalgic and new, which is not easy.

Final thoughts

WinCE64 is a beautiful piece of nonsense in the best possible sense. It is technically serious, culturally absurd and instantly memorable. It takes two very different pieces of late-1990s technology — Nintendo’s playful cartridge console and Microsoft’s compact embedded operating system — and smashes them together until a desktop appears. No one needed Windows CE on the Nintendo 64. That is part of the charm. The history of computing is full of unnecessary experiments that later become beloved because they reveal something about the machines, the people working on them and the sheer joy of making hardware do unexpected things.

The N64 already gave the world 3D Mario, four-player chaos, legendary Rare games and one of the strangest controllers ever mass-produced. Thanks to ThroatyMumbo’s WinCE64 project on GitHub, it can now add another achievement to the list: becoming a tiny Windows CE computer. Should a Nintendo 64 have a Start button? Probably not. Is it wonderful that one now can? Absolutely.