ReactOS, the open-source rebuild of Microsoft Windows, merged two long-stalled changes the same week of May 2026: a unified BootCD that combines the old text-mode installer with the separate LiveCD into a single image, and a fresh ATA storage driver that finally speaks SATA, PATA, ATAPI, and AHCI through one plug-and-play stack. Both pull requests had crawled through review for more than a year. Together, they reshape how new users meet ReactOS and which machines it can actually boot.
The work lands as the project marks three decades since its first commit in January 1996, and as the 0.4.16 release tree branches off master.
The Unified BootCD Lands After Fourteen Months In Review
The merge kills a download choice that had confused new users for years. One ISO now does everything: install in text mode, install in a future GUI mode, or boot a live demo without writing to disk. The pull request had been open since September 2024.
Lead developer Hermès Bélusca-Maïto, hired full-time by ReactOS Deutschland e.V. in late 2023 to finish the graphical first-stage installer, drove the consolidation through. His own December 2023 testing notes pointed at the duplication problem the merge fixes: when the GUI setup ran from the LiveCD’s read-only filesystem, “attempting to create or write a file to this destination will inevitably fail,” he wrote on the ReactOS blog. The unified image solves that by letting the same boot menu route the user into install or live mode without juggling two ISOs.
Two older build targets quietly died in the merge. The “hybridcd” target, which wrapped a RAM-disk-friendly variant of the live image, gets absorbed into the new BootCD. The “livecd” target shrinks to a stripped, non-bootable component that exists only to compose the unified ISO.
| Item | Pre-merge layout | Unified BootCD |
|---|---|---|
| Number of ISOs | BootCD plus LiveCD plus HybridCD | One all-in-one image |
| Install path | Text-mode only on BootCD | Text-mode now, GUI installer next |
| Live demo | Separate non-installable LiveCD | Same ISO, picked from boot menu |
| Build targets | bootcd, livecd, hybridcd | bootcd absorbs the rest |
A Fresh ATA Stack Aimed At The Disks ReactOS Always Tripped On
The second merge tackles ReactOS’s oldest reliability complaint: storage. The new ATA driver, in development since early 2024, is plug-and-play aware and folds four interface types into a single stack.
- SATA. The dominant consumer and server interface since the mid-2000s.
- PATA. The legacy parallel ATA bus on older desktops, industrial PCs, and embedded boards.
- ATAPI. The protocol behind optical drives, tape, and other removable media.
- AHCI. The mode most modern UEFI firmware exposes for SATA controllers.
Until now, ReactOS shipped UniATA, a monolithic third-party driver. UniATA worked. It also bundled the full storage stack into one binary, which made it nearly impossible to slot in alternative drivers or load unmodified hardware-vendor Windows binaries the way ReactOS aspires to. The new in-tree stack splits storport, ataport, and classpnp roles the way Windows itself does, opening room for hybrid driver setups.
An earlier attempt at a clean AHCI miniport ran during a Google Summer of Code project documented on the ReactOS engineering blog, but that 2016 code never reached production. The 2026 driver is a different animal: written from the start to be plug-and-play, structured around the NT 5.2 storage interfaces, and tested across real boards rather than only QEMU.
Storage detection has been the difference between ReactOS booting on a given laptop and hanging at the firmware screen. Broadening reach across SATA, PATA, ATAPI, and AHCI directly changes the install-success rate on real hardware.
Version 0.4.16 Has Branched, And 0.4.17 Nightlies Are Already Cooking
Branching happened the same week the BootCD and ATA changes hit master. Release candidates are due shortly. The current shipping version, ReactOS 0.4.15 from March 2025, has been the user-channel build for over a year, the longest stable cadence the project has run in some time.
Master nightlies on what will become 0.4.17 are already publishing through the project’s automated BuildBot system. Testers can pull daily ISO snapshots and run them on metal or in a hypervisor.
Why The Boring Plumbing Decides Whether ReactOS Stays A Hobby
ReactOS gets dismissed as a curiosity because, on the surface, the headline target has not changed: binary compatibility with Windows Server 2003. Underneath, the project is quietly drifting toward NT 6 territory.
In January 2026, ReactOS synchronized its MSVCRT C runtime against Wine 10.0, cutting API test failures by roughly 30% and unlocking improved support for newer apps, Phoronix reported. BuildBot can now compile NT6-export-enabled images, which means experimental Vista-era and Windows 7-era binaries will sometimes load. Combined with the new ATA driver and the unified installer, the 2026 trajectory points to easier first-time setup, broader hardware reach, and a slow climb toward modern app compatibility.
None of this makes ReactOS production-ready. Current builds remain alpha software, with file system, USB, and SMP gaps that crash daily. But the install funnel matters. A single ISO with a future GUI setup and a storage stack that handles SATA out of the box is the gap between losing curious testers at the boot menu and getting them all the way to the desktop.
The merged work also matters for downstream redistributors. Repair-CD projects like UWBCD, which package a ReactOS live image as a free replacement for the discontinued Ultimate Boot CD 4 Windows, can now build against one upstream image instead of stitching two together.
Three Decades Old, Still Officially Alpha
ReactOS turned 30 in January 2026. Volunteer-led, donation-funded, and hosted on the reactos/reactos main code repository, it has built up a body of work most kernel projects only reach with corporate backing.
- 14.9 million lines of code in the main tree at the 30-year mark.
- 88,198 commits since the first one on 23 January 1996.
- 301 unique contributors over the project’s history.
- 30 years from first commit to the 0.4.16 branch this week.
Eric Kohl, who joined in 1998 and wrote much of the original storage driver stack the new ATA driver now succeeds, recalled the early years in the project’s anniversary post. “Initially there was not a review process at all. You write some code, test it and fix it until it works. Then you commit it,” Kohl said. The 14-month review on the unified BootCD pull request is, by that measure, the opposite problem.
Long-running rewrites are also paying off around the merge. New NTFS work, a modernized build environment, kernel and user-mode ASLR, UEFI Class 3 booting, and groundwork for WDDM-based GPU drivers are all in flight. Some are years from shipping. The unified BootCD and the ATA driver are the ones that crossed the line this week. The argument for both is laid out at length in the ros-dev mailing list thread on merging the LiveCD and Install CD, a conversation that started years before the pull request did.
Frequently Asked Questions
What is the ReactOS unified BootCD?
It is a single ISO image that replaces ReactOS’s previously separate BootCD, LiveCD, and HybridCD downloads. The unified image lets users boot a live desktop, run the existing text-mode installer, or run the future graphical first-stage installer from one boot menu, and absorbs the older hybridcd build target entirely.
Which storage interfaces does the new ReactOS ATA driver support?
The new in-tree ATA driver is plug-and-play aware and supports SATA, PATA, ATAPI, and AHCI devices through one stack. It replaces the older monolithic UniATA driver, splits storport, ataport, and classpnp responsibilities the way Windows does, and is intended to make ReactOS boot on a much wider range of laptops, desktops, and embedded boards.
When will ReactOS 0.4.16 be released?
ReactOS 0.4.16 was branched from master in early May 2026, and release candidate builds are expected to start shortly after. The project has not committed to a final release date. The previous stable version, 0.4.15, shipped on 21 March 2025, so 0.4.16 ends an unusually long stable cadence for the project.
Where can I download ReactOS nightly builds?
Nightly ISO builds for the 0.4.17 development line and ongoing 0.4.16 release candidates are produced automatically by ReactOS’s BuildBot infrastructure. Daily snapshots are listed on the official ReactOS getbuilds page, with both x86 GCC and x64 MSVC images available, and can be run on bare metal or inside QEMU, VirtualBox, or VMware.
Is ReactOS ready to replace Windows in 2026?
No. ReactOS is still classified as alpha software in 2026, and the project itself recommends it only for testing and experimentation. File system stability, USB support, SMP, and modern application compatibility all have known gaps. The 2026 work expands hardware reach and lowers the install bar, but daily-driver use on a primary machine is not supported.
How is ReactOS different from Wine?
Wine is a compatibility layer that runs Windows applications on top of Linux, macOS, or BSD kernels. ReactOS is a from-scratch reimplementation of the Windows NT kernel, drivers, and userland, intended to run as the operating system itself. The two projects share code: ReactOS regularly imports Wine’s user-mode DLLs, including the January 2026 sync of MSVCRT against Wine 10.0.
For a 30-year-old project that still ships alpha builds, ReactOS’s May 2026 week is the kind of grind-it-out progress that matters more than another splashy compatibility headline. One ISO, one storage stack, and a release branch open for business.
Leave a Comment