ReactOS can now be installed straight onto an NTFS partition, the project announced this week. Until now, anyone wanting to run the open-source Windows clone needed a FAT32 partition to install it. That requirement is gone.
It's a milestone the team is framing as a step toward beta. It's also a driver with real gaps, which the announcement doesn't hide.
What the NTFS driver doesn't do
The new driver has no caching, no journaling, and no security support. Those aren't small omissions. Journaling is what helps a filesystem survive a crash or a power cut without corrupting data. Caching affects how fast reads and writes move. Security support is the permissions layer.
đź“Š Market Data Snapshot
The ReactOS team also warned that bugs may still be sitting in the driver, undiscovered. That's a frank caveat, and it puts the milestone in context: this is progress, not a finished product. Anyone installing now is doing it on a partition the project can't fully protect.
Why FAT32 was such a wall
FAT32 is old and simple, and it was the only path ReactOS offered until now. The trouble is that most Windows machines in the wild don't run on FAT32. They run on NTFS, the filesystem Microsoft introduced with Windows NT 3.1 in 1993. The version that shipped with Windows XP in 2001 is still the standard today.
That mismatch is why the FAT32 requirement mattered. A filesystem barrier doesn't look like much from the outside, but it's the kind of thing that quietly keeps people from trying software at all. Linux hit the same wall: read-only NTFS support for years, then write support through userspace tools that took time to trust. Kernel-native NTFS didn't land in Linux until 2021. Filesystem compatibility is a grind measured in decades, not a single release.
The beta target is a moving one
ReactOS aims for binary compatibility with Windows Server 2003. That's the destination. The gap is that every year spent chasing that target is a year the rest of the desktop world moves further away from it.
The competitive ground has shifted too. Wine and Valve's Proton now run a large share of Windows games and applications on Linux, and Microsoft's own WSL2 gives users a sanctioned way to run Linux inside Windows. ReactOS's niche is narrower than it was a decade ago, and the NTFS install support doesn't change that on its own.
None of this touches crypto markets, which are drifting slightly higher on their own logic. The only overlap is thematic. Crypto's reimplementation projects — zkEVMs, Bitcoin script layers, rollups rebuilding Ethereum's security model — face the same trade-off ReactOS just made: ship something that works before it's complete, then warn users about the edges. The difference is that a buggy rollup loses funds, and a buggy NTFS driver loses files.
What to watch
The honest test starts now. The team's own warning about undiscovered bugs means the next few months of real-world installs will decide whether the driver holds up under power loss and heavy writes. One high-profile data-loss report would set the project back further than the FAT32 requirement ever did. Until then, the milestone stands as announced: you can install to NTFS, and you should know what you're giving up.
