Valve's 1998 classic Half-Life ran natively in-game on ReactOS, the open-source Windows NT clone, on June 10, 2026, using actual hardware—a Dell OptiPlex with a Sandy Bridge Core i5 processor. The demo, captured on video and shared by project developers, shows the game not merely launching but playing through the hazard course at stable frame rates, with sound, input, and 3D acceleration all functioning. It marks the first documented instance of a demanding Windows DirectX title running on ReactOS outside of a virtual machine, and it signals major advancements in the operating system's kernel driver compatibility and Win32 subsystem.

The achievement arrives years after ReactOS first booted to a desktop and ran simpler applications. The project, which began in 1996 as a free reimplementation of Windows NT 4.0, has long struggled with the sheer complexity of Microsoft's driver model and the graphics stack. Gaming, in particular, has been a torment: even when DirectX runtime libraries were ported, the underlying kernel interfaces often missed subtle behaviors that games expect. The Half-Life run changes that narrative.

The Demonstration

The video, posted to the ReactOS Community YouTube channel, shows a developer inserting a USB drive into the OptiPlex, booting ReactOS, navigating to the Half-Life directory, and launching the executable. The game's menu appears, and within seconds the player is inside the training room. Movement is smooth, the HUD renders correctly, and audio prompts play without stutter. The developer completes several puzzles, fires weapons, and moves through the level, demonstrating that both input handling and the rendering pipeline remain stable over minutes of gameplay.

System information overlaid on the video confirms the hardware: a Dell OptiPlex 390 with an Intel Core i5-2400 CPU, 4 GB of DDR3 RAM, and integrated Intel HD Graphics 2000. No third-party GPU was installed. ReactOS build details were not disclosed in the video description, but the desktop watermark indicates a recent trunk build, likely compiled within days of the demonstration.

Why This Matters

ReactOS has always been able to run Win32 console tools and basic GUI applications like Notepad or older office suites. But games stress the operating system in ways that productivity software rarely does. They demand real-time scheduling, low-latency I/O, DirectDraw/Direct3D surface management, and precise thread synchronization. On real hardware, they also require functional device drivers for sound, network, and GPU.

Previous successful gaming demos on ReactOS relied on virtual machines with emulated hardware—where many driver complexities are abstracted away. Running Half-Life on bare metal proves that ReactOS can now correctly load and manage the Windows driver for Intel's integrated GPU, handle PCI enumeration, and map GPU memory into user space. It also demonstrates that the kernel's DirectX graphics kernel subsystem (dxgkrnl) and the Win32 graphics device interface (GDI) can survive sustained, high-frequency calls from a game engine.

The Graphics Driver Puzzle

ReactOS does not ship with its own GPGPU drivers. Instead, it relies on binary compatibility with Windows drivers. For the demo to work, the operating system had to accept the Intel HD Graphics driver package intended for Windows 7 or later, install it, and hand over rendering commands without crashing. That process involves layers: the kernel-mode display driver, the user-mode driver DLL, and the DirectX runtime. Each layer must match expectations—otherwise, the stack collapses with a blue screen or a frozen desktop.

Open-source enthusiasts have previously managed to get basic 2D acceleration on ReactOS by patching framebuffer drivers, but 3D has been a black spot. The Half-Life run suggests that the ReactOS team has resolved long-standing issues in the memory manager and the object manager that prevented correct GPU resource allocation. The game uses Direct3D 6.0, an API from 1998, but that still requires functional vertex buffers, texture mapping, and lighting—all of which worked.

Sound and Input: The Unsung Heroes

Beyond graphics, Half-Life relies on DirectSound and the legacy Windows multimedia API for audio. Many ReactOS users report distorted or missing sound in games because the kernel’s mixer and audio device drivers fall out of sync. In the demo, audio was clear and lipsync with the training announcer was perfect, indicating improvements in the PortCls audio driver framework.

Input handling also performed without fault. The game received keyboard and mouse events through the standard Win32 message loop, and the video shows no dropped keystrokes or mouse lag. That may seem trivial, but ReactOS’s input stack has historically suffered from slow dispatch and priority inversion under load—problems that ruin any hope of fluid gameplay.

Community Reaction and Next Steps

The ReactOS forum and subreddit lit up within hours of the video’s release. Longtime contributors pointed out that the demo vindicates years of slow, methodical work on the NT kernel’s Object Manager and the I/O Manager. “This is the moment we finally see the payoff of all those driver compatibility commits,” one developer wrote. Others noted that the OptiPlex hardware is officially unsupported by modern Windows versions, while ReactOS—with its NT 5.2 (Server 2003) target compatibility—handles it gracefully.

Still, the community tempered expectations. The game crashed once during the video, requiring a restart. The developer acknowledged that the GPU driver occasionally fails to recover from a lost device, a known issue in ReactOS’s Dxgkrnl subsystem. And Half-Life is a relatively old title; modern games using DirectX 11 or 12 remain far out of reach because ReactOS lacks the WDDM driver model entirely.

But the team celebrated the victory. “We set out to prove that the NT architecture can be fully replicated, and that includes running the software that defined the platform,” said a project maintainer in a forum post. “Half-Life is iconic, and seeing it run on real hardware closes a chapter of doubt.”

Technical Details for the Curious

The Dell OptiPlex 390 used in the demo sports the Intel H61 Express chipset and a Realtek ALC269Q audio codec. Both components require Windows drivers that talk to the platform's ACPI and PCI bus enumerators—subsystems that ReactOS has partially rewritten over the past two years. The Core i5-2400's integrated GPU communicates via the PEG (PCI Express Graphics) link, and ReactOS had to negotiate that link correctly for the driver to detect the card.

To get the game running, the developer likely copied a pre-installed Half-Life folder from a Windows partition and launched hl.exe with the -nofbo parameter, which disables OpenGL framebuffer objects that can choke early Direct3D wrappers. The game itself ran in software vertex processing mode, a fallback that keeps the graphics pipeline alive even when hardware T&L is unavailable.

Frame rates appeared to hover around 30–45 fps during indoor scenes, dipping to 20 fps in larger areas—acceptable for the 1998 title, though far below what the hardware could achieve under Windows.

What This Means for the Windows Ecosystem

ReactOS isn't just a curiosity. With Microsoft tightening Windows 11's hardware requirements and ending support for older CPUs, a fully compatible open-source alternative could extend the life of millions of perfectly functional machines. The ability to run legacy Windows software—including games—on those machines without a Microsoft license has obvious appeal for education, industrial control, and cash-strapped governments.

The project's developers are careful not to promise a drop-in replacement, but each milestone like this shrinks the gap. Half-Life's success indicates that DirectX 6–8 titles might be broadly playable once the driver stability issues are ironed out. That alone covers a vast library of late-1990s and early-2000s games that refuse to work on modern Windows without elaborate patches.

Roadblocks Remain

Despite the progress, ReactOS is still alpha software. Its official website carries a warning not to use it on production machines, and the installer can destroy existing boot records if mishandled. The codebase is perennially understaffed, with fewer than a dozen regular contributors maintaining a kernel that spans over 8 million lines of C and assembly.

Microsoft's continued evolution of the NT kernel also poses a moving target. While ReactOS aims for compatibility with Windows Server 2003 and Windows 7 APIs, modern drivers increasingly require WDDM 2.0+ interfaces that are absent. The team has experimented with a compatibility layer that translates WDDM calls to XPDM (the Windows XP display driver model), but results are rudimentary.

Nevertheless, the June 10 demo is a morale injection. “We now have a concrete benchmark,” one contributor wrote. “Every regression test suite will include launching Half-Life and playing for five minutes. If that breaks, we know something fundamental went wrong.”

How to Try It Yourself

Adventurous users can download ReactOS 0.4.15-dev from the project's nightly builds page and attempt the same. The process requires a USB flash drive, the Half-Life game files (Steam or retail), and compatible hardware. Extensive forum threads detail which chipsets are most likely to succeed—currently, Intel 6-series and 7-series platforms show the best results. AMD GPUs remain problematic due to the lack of a functional Catalyst driver stack, though older Radeon cards with open-source community drivers show promise.

The ReactOS team cautions that the experience will be buggy. Expect crashes, missing textures, and occasional freezes. But for the first time, seeing Gordon Freeman in the hazard course under a free NT clone is not a fantasy.

Looking Forward

The demo opens the door to a broader compatibility push. With Half-Life as a reference point, developers can now identify the exact kernel paths that games stress and begin systematic hardening. Future targets include Quake III Arena, Diablo II, and the original Deus Ex—titles that collectively represent the DirectX 7/8 era.

Longer term, the project hopes to attract more contributors by showcasing these tangible successes. “Nobody wants to write kernel code for the sake of it,” a developer said. “They want to see the results. Half-Life running is the kind of result that makes people say, ‘I want to be part of that.’”

The June 10, 2026 video will stand as a historical marker: the day a free Windows NT clone stopped being a theoretical exercise and started playing the games that defined a generation.