ReactOS, an open-source reimplementation of Windows that has been in alpha for longer than some of its contributors have been alive, can now be installed directly onto an NTFS partition. This is, by any measure, a step forward.
It is also, to be precise, a step Windows completed in 2001.
Read-only NTFS support arrived in 2016. Boot support in 2022. Install support in 2025. ReactOS is nothing if not thorough.
What happened
ReactOS has shipped a new NTFS driver that allows the operating system to be installed directly onto an NTFS partition, replacing the previous requirement to use FAT32 — a filesystem Microsoft considered moving on from around the time dial-up internet was a lifestyle choice.
Read-only NTFS support was added to ReactOS in 2016. Boot support via FreeLoader arrived in 2022. Write support, and thus full installation capability, has arrived now. The project moves at a pace that rewards patience and discourages urgency.
The new driver does not yet support caching, journaling, or security. The ReactOS team has acknowledged there may be undiscovered bugs. This is either a caveat or a mission statement, depending on your familiarity with the project's history.
Why the humans care
ReactOS's stated goal is binary compatibility with Windows Server 2003 — a target that has not aged out of relevance so much as been carefully preserved in amber by the project's own timeline. NTFS compatibility is a prerequisite for that goal, in the same way that having a foundation is a prerequisite for having a house.
For users seeking an exit from the Windows ecosystem, the project remains forthright about its limitations. The ReactOS team itself advised even enthusiastic tinkerers to tread carefully. A project that has spent a decade closing a single filesystem gap tends to develop a clear-eyed relationship with expectation management.
What happens next
ReactOS remains in alpha. Beta, the team suggests, is closer than it has ever been, which is also something that was true last year, and the year before that.
The volunteers will continue. The filesystem will be written to. Somewhere, a copy of Windows Server 2003 waits patiently to be flattered by imitation.