What actually changed
ReactOS said on X that, after nearly a decade, its NTFS driver got major improvements. The project says you can now install and use ReactOS with it. It also says NTFS formatting support has been added and is Windows compatible. The X post is dated October 17. Phoronix reported it the same day, and Ars Technica followed on October 19.
Until now, ReactOS's default installation guidance asked for FAT16 or FAT32 on both the active boot partition and the installation partition. FAT is old, simple and well understood. That is why it was the safe choice. It is also why a project aiming for Windows NT-family compatibility was installing onto a filesystem that NT-era systems had long since moved past.
The NTFS work is a long-running one:
- Ars Technica says read-only NTFS support arrived in ReactOS in 2016.
- NTFS boot support was added to FreeLoader in 2022. That let the bootloader read an NTFS partition, but the OS itself could not be installed there.
- Experimental write support was already in development years ago. A 2017-era report said it could be switched on through a registry change and might cause data loss.
The caveats
ReactOS says the NTFS driver still lacks caching, which causes inferior performance. It also lacks journaling and security support, and may have undiscovered bugs. The project adds that read/write support is greatly enhanced.
Here is what each missing piece means in practice:
- No caching: Disk operations are slower than they should be. Phoronix describes the performance as worse than other NTFS drivers and platforms.
- No journaling: NTFS normally keeps a log of metadata changes so it can recover after a crash or power loss. Without it, an unclean shutdown carries more risk. This is general filesystem knowledge, not something ReactOS has spelled out.
- No security support: The driver does not implement NTFS access-control and permission handling. In a Windows-compatible OS, that is a significant gap.
"Installable" is not the same as "complete." The sources say nothing about full NTFS feature parity or benchmarks, and they don't claim the driver works with every NTFS volume.
What this means for testers
ReactOS's own repository calls the OS alpha quality. It warns that it may corrupt data on a hard disk and recommends a virtual machine or a computer with no critical data. Combined with the driver's stated gaps, the advice is simple:
- Use a disposable virtual machine or a spare drive.
- Keep anything you care about off the target disk.
- Treat any NTFS-related misbehavior as a possible driver bug and report it to the project.
The sources don't identify a release number, a build, an installer option or a step-by-step procedure for the NTFS path, so I won't invent one. Neowin's coverage ties the NTFS work to a gradual shift toward NT 6-style architecture, including the Users folder layout. That is a separate effort, though. The sources don't say how the two fit together.
How this fits with ReactOS 0.4.16
ReactOS 0.4.16 was announced on August 29, 2026. Its headline items were a graphical installer, a combined boot and live CD image, and improved video, audio, networking and storage support. The announcement didn't list NTFS installation as a feature of that release. So the NTFS milestone should not be read as part of 0.4.16. Whether it reaches a numbered release or only development builds first is something the sources don't answer.
The 0.4.16 announcement does help explain the timing. It describes a new ATA driver, which it says lets ReactOS boot in many more environments. It also mentions a repaired FAT check-disk routine and a new disk cleanup utility. Storage has been a major focus this year, and the NTFS work fits that pattern.
Why Windows and IT readers should care
ReactOS is not a replacement for managed Windows endpoints or servers, and nothing in the evidence suggests it is one. The project's stated compatibility target is Windows Server 2003, and it is still alpha. As Ars Technica puts it, ReactOS may never be a truly viable Windows alternative for most users. The same piece notes that it can now at least be installed on the same filesystem as the real thing.
The milestone does matter in two ways:
- Compatibility: An OS that wants to run Windows applications and drivers needs to handle the filesystem those programs expect. FAT-only installs couldn't do that fully.
- Beta progress: Both Phoronix and the ReactOS team describe this as a step toward beta. How far off that is, the sources don't say.
A fair counterpoint is that ReactOS's own post is promotional in tone. It says "BREAKING NEWS" and calls NTFS "another dream" of a developer. That tone is normal for a volunteer project celebrating a long-awaited result. The same post still discloses the missing caching, journaling and security support. That is a more honest limitations statement than many commercial announcements manage.
Bottom line
ReactOS's NTFS driver has grown from read-only support into something that can host the operating system and format volumes. It is still missing the features that make NTFS fast, resilient and secure. It is worth watching if you follow open-source Windows compatibility. It is worth trying only in a VM or on a disposable disk.