ReactOS, the open-source operating system designed to run Windows-compatible software and drivers, has reached a significant development milestone: its NTFS filesystem driver can now support installing and running the operating system directly from an NTFS partition. The driver can also format NTFS volumes, overcoming a long-standing technical obstacle. However, missing performance, recovery, and security features mean the achievement does not make ReactOS ready for everyday use.
What ReactOS Has Achieved With NTFS Support
The ReactOS development team has reported that its NTFS driver is now capable of handling the installation and operation of ReactOS itself. The milestone was highlighted by Phoronix on October 17, 2026, with additional coverage from Ars Technica on October 19.
The development is significant because supporting NTFS during installation requires more than simply recognizing or reading files stored on an NTFS partition. The operating system must also be able to create, modify, and manage filesystem structures throughout installation and subsequent operation.
ReactOS has been working toward that capability for years. Read-only NTFS support arrived in 2016, followed by NTFS boot support through the FreeLoader bootloader in 2022. That earlier improvement allowed the bootloader to access NTFS volumes, but it did not provide everything needed to install and operate ReactOS directly on them.
The latest advance brings those previously separate capabilities closer together. ReactOS can now reportedly format an NTFS partition and use its developing driver to install and run the operating system.
Why NTFS Support Matters for ReactOS
NTFS, short for New Technology File System, is the filesystem commonly used by modern Windows installations. Introduced with the Windows NT family, it supports features such as file permissions, journaling, and the management of large files and storage volumes.
ReactOS aims to recreate a Windows-compatible operating system through an independently developed, open-source implementation of Windows NT technologies. Its compatibility objectives have historically focused on Windows Server 2003-era architecture and interfaces.
For a project pursuing that goal, NTFS support is more than a convenient storage option. It removes a technical mismatch between ReactOS and the Windows environments it seeks to support.
Traditional ReactOS installations have primarily relied on FAT filesystems, although experimental Btrfs installation support has also existed. NTFS installation support expands the project's filesystem capabilities and provides developers with another area for compatibility testing.
Nevertheless, using the same filesystem as Windows does not automatically make ReactOS compatible with every Windows application, device driver, or NTFS feature. Those capabilities depend on other components of the operating system and require separate development and testing.
Important NTFS Driver Limitations Remain
Despite the installation milestone, several important parts of ReactOS's NTFS implementation remain unfinished. According to the development announcement described by Phoronix, the driver still lacks caching, journaling, and NTFS security support. Developers also acknowledge that additional bugs may remain undiscovered.
Caching: Filesystem caching reduces repeated storage operations by retaining frequently accessed information in memory. Without adequate caching, file operations can require more direct storage access, reducing performance. The ReactOS team has identified inferior performance as a consequence, although the reporting does not establish independently measured performance differences.
Journaling: NTFS normally uses journaling to record certain filesystem changes and assist recovery after interruptions. Without comparable support, ReactOS's driver lacks an important mechanism for handling filesystem consistency following unexpected shutdowns or system failures. This does not establish that corruption will occur in every such situation, but it remains a meaningful reliability limitation.
Security support: NTFS includes access-control functionality that Windows uses to manage file and directory permissions. Incomplete support means ReactOS cannot yet be assumed to reproduce the full security behavior expected from a mature NTFS implementation.
These missing capabilities help explain why successful installation is an engineering milestone rather than proof that the driver is suitable for protecting important data.
Can Users Install ReactOS on NTFS Now?
The distinction between a reported development capability and a publicly released feature matters for anyone interested in trying ReactOS.
The project's official ReactOS 0.4.16 release announcement, published on August 29, 2026, introduced improvements including a graphical installer, combined installation and live media, and changes to the storage stack. However, that release predates the October NTFS milestone, so its release announcement does not establish that the newly reported NTFS installation capability is included.
ReactOS's official GitHub documentation also continues to describe FAT-based installation as the default, with experimental Btrfs support. The documentation therefore should not be interpreted as confirmation that every publicly available installer supports the newly announced NTFS functionality.
ReactOS provides development builds for testing newer changes, but the exact build requirements and availability of the NTFS installation feature should be confirmed against current project documentation before attempting an installation.
More importantly, ReactOS remains alpha-quality software. Its developers warn that the operating system may contain serious defects, including problems that could affect stored data. A virtual machine or a dedicated test system without valuable files is consequently a more appropriate environment for experimentation than a primary computer.
What Comes Next for ReactOS?
The NTFS milestone removes one obstacle from ReactOS's long-term development roadmap, but several challenges remain before the filesystem driver can be considered mature.
Improving caching, implementing journaling, completing security functionality, and identifying remaining compatibility defects are important areas for further work. Developers will also need to validate the driver's behavior across installation scenarios, routine file operations, and unexpected system interruptions.
The achievement is relevant to ReactOS's broader ambition of eventually reaching beta quality, but no confirmed beta-release date follows from the NTFS announcement.
For developers and operating-system enthusiasts, the progress demonstrates that ReactOS continues to overcome difficult compatibility challenges. For everyday users, the distinction remains clear: NTFS installation support is a meaningful technical advance, not yet evidence that ReactOS is a dependable replacement for Windows.
0 Comments