Windows NT Now Boots on the Nintendo GameCube: What the Homebrew Port Actually Runs

In brief — July 4, 2026 — A homebrew developer has coaxed Windows NT to boot on a stock Nintendo GameCube by reviving Microsoft's abandoned PowerPC build, and Hackaday's writeup is the maker scene's headline of the week.

Yes, you can now run Windows NT on a Nintendo GameCube — a homebrew port revived Microsoft's abandoned PowerPC NT build and got it to boot on the console's 485 MHz IBM Gekko chip in 2026. It is not a usable desktop. It is a boot-to-shell proof of concept that runs a handful of NT services, no meaningful drivers, no networking stack you would trust, and no path to Office 97. Treat it as a preservation milestone and a fascinating weekend read, not a Windows machine you can actually use.

The port lands squarely in the sweet spot the homebrew community loves: a piece of hardware nobody expected to run a general-purpose OS, an operating system Microsoft shipped for that CPU family thirty years ago, and just enough shared DNA between the two to make the impossible look inevitable in hindsight. Nintendo's GameCube uses IBM's Gekko processor, a 485 MHz PowerPC 750 derivative with a custom paired-single FPU extension. Windows NT 3.51 and Windows NT 4.0 both shipped official PowerPC builds in the mid-1990s targeting IBM's PReP and CHRP reference platforms — machines like the IBM RS/6000 40P and the Motorola PowerStack. When Microsoft killed PowerPC NT with the release of NT 4.0 SP2 in 1997, the code did not vanish; it went dormant. Homebrew tinkerers have been probing it ever since, and in 2026 someone finally bridged the gap between a 1996 workstation OS and a 2001 game console. As of July 4, 2026, the port is public, documented on Hackaday, and reproducible if you have a modded GameCube and patience measured in weekends.

Key takeaways

• Windows NT 4.0 shipped a PowerPC build in 1996; Microsoft killed it in 1997 after roughly 18 months on the market.
• The GameCube's IBM Gekko is a 485 MHz PowerPC 750 derivative — same instruction-set family as the workstations NT PowerPC originally targeted.
• The homebrew port boots to a shell on stock GameCube hardware but has no meaningful driver, network, or peripheral support in July 2026.
• Running it requires a softmodded or chipped console, an SD Media Launcher or memory card exploit, and a homebrew loader — Nintendo never sanctioned unsigned code on the GameCube.
• Beginners chasing the same tinkering itch get further faster on a Raspberry Pi 4 Model B 8GB or a Vilros Raspberry Pi Zero W Starter Kit — cheaper to brick, better documented, and legal to boot whatever you want.

What happened: Hackaday's PowerPC NT on GameCube coverage

Hackaday published the writeup at the end of June 2026, and it ricocheted through the retro-hardware corners of Reddit, Mastodon, and the GBAtemp forums within 48 hours. The developer's project revives Microsoft's discontinued Windows NT 4.0 PowerPC build — a version most Windows users have never seen, because it targeted expensive IBM and Motorola PReP workstations rather than PCs. Getting it to run on a GameCube meant three separate wins stacked on top of each other. First, extracting a working PowerPC NT image from an era when installer media was pressed onto CDs that expected a very specific hardware bootstrap. Second, coaxing that image through the GameCube's unusual boot path, which normally hands control to a signed game disc and rejects anything unsigned. Third, patching the kernel to talk to the Gekko's memory map, MMU, and interrupt controller instead of the PReP hardware it expected.

Hackaday's coverage links the developer's own notes, screenshots of the boot sequence, and a short video of NT's classic teal-and-gray boot logo materializing over the GameCube's video output — the kind of image the maker scene screenshots and shares for years. The report is careful about scope: NT boots, hits a shell, and shows the underlying kernel is alive. Peripherals, USB, controller input beyond the most basic keyboard hookup, sound, and networking are either unimplemented or deliberately stubbed. This is where the port sits in July 2026, and the developer has been transparent that pushing further is a matter of driver work rather than kernel patching.

Why it matters: PowerPC NT history and homebrew preservation

Windows NT was designed from day one to be portable across CPU architectures — that was David Cutler's core insight when he brought his DEC VMS team to Microsoft in 1988. The Windows NT hardware abstraction layer meant Microsoft could ship the same OS on Intel x86, MIPS R4000, DEC Alpha, and PowerPC without rewriting the kernel. Between 1993 and 1997, NT genuinely was a multi-architecture operating system. NT 3.1 shipped for x86 and MIPS in 1993; NT 3.5 added Alpha in 1994; NT 3.51 added PowerPC in 1995; NT 4.0 kept all four alive through 1996. Then the market decided. MIPS died first with NT 4.0 SP1. PowerPC died with SP2 in late 1997. Alpha lingered until NT 4.0 SP6 in 1999 before Compaq's acquisition of DEC and Microsoft's Itanium bet killed it. By Windows 2000, NT was x86-only for the desktop, and would stay that way until Windows on ARM shipped nearly two decades later.

That brief PowerPC window matters because it is the only reason a GameCube can run NT at all. The homebrew scene has spent twenty years reverse-engineering the console's IBM Gekko chip, its ATI Flipper GPU, and its idiosyncratic boot ROM. The knowledge base at WiiBrew — carried over from the Wii but rooted in GameCube-era research at sites like gc-forever — is deep enough that a determined developer can now bring up an OS the console was never meant to run. Preservation is the underlying motive. Windows NT PowerPC is functionally lost media: original install CDs sell for hundreds of dollars on eBay when they surface at all, and Microsoft has never re-released the PowerPC build. Every working boot on new hardware is an argument for keeping the code alive.

The homebrew community loves the GameCube specifically because it punches above its weight for tinkering. The Gekko's 485 MHz PowerPC 750 core is well documented thanks to Apple's Power Mac G3 lineage, which used the same base architecture. The 24 MB of 1T-SRAM main memory is small but coherent and fast. The optical drive can be bypassed with an SD card loader. The controller ports carry a serial protocol that has been fully decoded. All of that turns the console into a compact, cheap, legally-owned PowerPC development board — one that costs $30-$60 used in 2026 versus hundreds for a period-correct IBM RS/6000 workstation. That accessibility is why the port matters beyond the novelty.

PowerPC Windows NT ports over the years

Here is where the GameCube port sits in the broader history of NT on PowerPC hardware:

A useful comparison sits one column over: DEC Alpha NT. Alpha shipped on hardware like the DEC Multia and AlphaStation 200 through 1999, and homebrew Alpha-NT projects still surface on modern FPGA implementations and emulators. The GameCube port is philosophically identical — an abandoned NT architecture kept breathing on hardware Microsoft never sanctioned. Both scenes trade the same tools: leaked kernel debug builds, third-party HAL rewrites, and a lot of patience.

The source, and a friendlier sandbox for newcomers

Hackaday's original writeup is the canonical entry point. The developer's own project notes cover the boot chain in detail — how the Gekko's exception vectors get remapped, how the initial ramdisk lands in the 24 MB main memory pool, and where the current implementation stubs out hardware NT expects to find. If you want the background on NT's architecture-portability years, the Wikipedia Windows NT history is a straightforward overview, and the archived Microsoft documentation on BetaArchive preserves the original PowerPC HAL notes if you dig. For GameCube-specific homebrew tooling, WiiBrew is where the ecosystem lives — GameCube and Wii share enough that most Wii-era tools work on the older console with minor adjustments.

Actually running the port is another matter. You need a GameCube with either an SD Media Launcher, an SD Gecko adapter, or a modchip; a homebrew loader like Swiss; the patched NT image; and enough tolerance for cryptic error messages to enjoy the process. For anyone who reads the Hackaday piece and thinks "I want to tinker with vintage OS ports without hunting eBay for a modded console," the honest recommendation is a Raspberry Pi. A Raspberry Pi 4 Model B 8GB will happily run PiCorePlayer, RISC OS, Haiku, Plan 9, and dozens of retro emulators — you can boot a different obscure OS every weekend for a year without breaking the hardware. It is the closest modern equivalent to what the GameCube homebrew scene loves about their console: cheap, well documented, hackable at the boot level, and legal to run anything on. Add a SanDisk Ultra 3D NAND 1TB SSD over USB 3.0 and you have room for every archived vintage OS image you can find plus a mirror of the Internet Archive's software collection. For an even cheaper on-ramp, the Vilros Raspberry Pi Zero W Starter Kit is under $40 in 2026, comes with a case, HDMI adapter, and power supply, and is enough for lightweight retro-OS experiments and headless projects — perfect for a first bootloader hack before you commit to soldering a modchip into a twenty-year-old game console.

What the port actually runs (and doesn't)

Be realistic about what "NT on GameCube" means in July 2026. The port boots the NT 4.0 kernel, initializes memory management, spins up a handful of core NT services, and drops you at a shell prompt over composite video output. That is the ceiling right now. What does not work: USB, because the GameCube has no USB controller and NT's USB stack shipped in Windows 2000. Networking, because the console's Broadband Adapter is rare and NT's PowerPC network drivers targeted PReP-era Ethernet chips that have zero overlap with the GameCube's Realtek-derived NIC. Sound, because Nintendo's custom DSP is undocumented territory nobody has bridged to NT's audio stack. GPU acceleration, because the Flipper GPU is a fixed-function chip from 2001 with no NT drivers on any planet. Game controllers, because the Nintendo controller port protocol is not a standard NT input device and the current port stubs the input HAL entirely.

What you get is exactly what the Hackaday demo shows: a boot logo, a kernel initialization sequence, a shell, and confirmation that NT is genuinely running on the Gekko. For a preservation project that is enough. For a daily driver it is nowhere close, and the developer has been clear the goal is documentation and educational value rather than a usable console-based Windows machine.

Common pitfalls if you try to reproduce it

Five failure modes trip up first-time GameCube homebrew tinkerers, and they all apply doubly to NT experiments:

• Wrong disc region or drive revision. GameCube drive controllers changed at least twice in the console's lifetime; some homebrew loaders only work on specific board revisions. Check your motherboard revision (DOL-001 vs DOL-101) before buying an SD adapter.
• Bad SD card. The console is picky about SD cards. Stick to Class 10 cards from major brands, formatted FAT32 with a small cluster size. Modern high-capacity UHS-II cards often fail to enumerate.
• Skipping the homebrew loader. You cannot boot NT directly from a game disc. You need Swiss or a similar loader as an intermediate stage that hands off to the NT bootstrap.
• Expecting NT install media to Just Work. The PowerPC NT installer targeted PReP hardware. The GameCube port bypasses installation entirely and boots a pre-configured image; do not waste hours trying to install NT from period CDs.
• Ignoring heat. A GameCube left booting into NT with no game running still consumes about 20 W and gets warm. Keep the vents clear, especially if you are experimenting for hours at a time.

When NOT to try this on real hardware

Skip the GameCube route if any of the following apply. You do not already own a modded console — spending $80-$150 on eBay for a chipped or SD-Media-Launcher-ready GameCube in 2026 to boot an unusable OS is a strange purchase. You do not enjoy the process itself — the boot output is the reward; there is no game, no productivity tool, no reason to keep the OS running once you have taken the screenshot. You are hoping to actually run Windows software — even period NT PowerPC applications will not run without the full driver stack, and there is no path to running x86 Windows binaries. In every one of those cases, the Raspberry Pi route gets you 90% of the tinkering satisfaction at 10% of the hardware risk, and the Pi has a legitimate second life as a home lab node afterwards.

Related guides

• Agent PCs: hardware to run AI agents locally in 2026
• 8BitDo SN30 Pro on SNES Classic and Genesis Mini in 2026
• AI memory bandwidth: from HBM to GDDR6 for local inference in 2026
• 8BitDo Pro 2 vs GameSir G7 SE for PC emulation in 2026

Sources

1. Hackaday — Running Windows NT on the Nintendo GameCube
2. Wikipedia — Windows NT
3. Raspberry Pi 4 Model B product page
4. WiiBrew — Homebrew documentation for GameCube and Wii
5. BetaArchive — Archived Windows NT PowerPC documentation