ReactOS NTFS Driver Matures, Enabling Installation on NTFS

ReactOS’s NTFS file system driver has matured to a level where it can be used to install and use ReactOS itself. According to reporting by Phoronix’s Michael Larabel, the project announced this achievement in a post on X. Installation onto NTFS partitions has become a realistic option, and formatting NTFS with the driver is now possible.

ReactOS posted on X today that a major goal has been achieved: its NTFS driver has matured enough to handle ReactOS installation. (Quoted from the Phoronix article; original in English)

For ReactOS, which aims to reimplement the Windows NT family, NTFS support is directly tied to architectural coherence. It can be seen as one of the indicators of a compatible OS’s completeness having moved.

Installing on NTFS Becomes a Reality

Until now, the realistic options for installing ReactOS were limited to FAT-family file systems and ext2. NTFS partitions are the format Windows uses by default, and this had been an obstacle for users who wanted to reuse their existing disk layout. This milestone makes it possible to install ReactOS on existing NTFS partitions.

Generally, for an OS to read and write another OS’s standard file system, it must have its own implementation that interprets that format’s specifications. NTFS specifications are not fully public, and compatible implementations have been built through accumulated observation and verification. Such work has the character of proceeding in stages: from read support to write support, and then to installation and booting.

NTFS Formatting Also Implemented

The support for formatting NTFS should not be overlooked either. Even with read/write capability, if partitions cannot be created or initialized, installation would depend on another OS or another tool. This means the entire flow—preparing an NTFS partition with ReactOS alone, installing onto it, and booting—has become possible.

It is a change that also affects installer design and testing procedures. It means NTFS has reached a level where it can be presented as an option in the step for choosing the installation target file system. This is why the project described it in its post as a “major goal.”

Constraints Remaining in the NTFS Driver

However, ReactOS’s NTFS driver still has unimplemented features. Because it lacks a caching mechanism, its performance is lower than other NTFS implementations. Journaling and security features are also unsupported. The project itself mentions the possibility of undiscovered bugs.

The lack of journaling affects consistency recovery after abnormal termination. The NTFS journal keeps records of metadata updates and is used to restore the file system state after power loss or forced shutdown. Without this support, situations remain in which the post-crash state cannot be guaranteed. The lack of security features also imposes constraints on permission control intended for multiple users.

The performance gap directly affects the user experience. In an implementation without caching, the frequency of disk access increases each time metadata is referenced. This is expected to have an impact on installation time, boot time, and situations involving many small files.

How Installation Scenarios Change

From a practical standpoint, the way test environments are built will change. Preparing a virtual machine’s virtual disk as NTFS and installing ReactOS onto it becomes more realistic. When setting up a dual-boot configuration on an existing Windows machine, it is also no longer necessary to convert the partition format.

On the other hand, careful judgment is required for long-term data retention. Lacking journaling and security features, it is functionally at the “can be installed” stage, not the “can be used daily with confidence” stage. Trial use for evaluation and operation with real data should be considered separately.

The Remaining Distance to Beta

The project positions this milestone as a step toward the long-awaited beta. ReactOS has been in alpha for a long time, and the move to beta has repeatedly been set as a goal. The file system is a prerequisite for installation, and the significance of it approaching a practical level is not small.

However, the beta decision is not determined by a single file system factor. Multiple conditions are involved, including the stability of drivers overall, application compatibility, and regression management. This announcement is progress, but it is not seen as directly indicating when beta will be declared.

ReactOS’s Progress in 2026

ReactOS has accumulated achievements in 2026. Our site has also reported on ReactOS Achieves Half-Life 2 Compatibility: 30 Years of the Open-Source Windows-Compatible OS, ReactOS Achieves Half-Life Compatibility After Nearly 30 Years of Development, and ReactOS Overhauls DirectX and Expands Support with Wine 10.0 Integration.

Game and application compatibility are indicators that users can easily see. The file system is an unglamorous element that supports the installation foundation. The fact that advances of different natures have lined up in the same year is seen as reflecting the project’s current momentum.

The Technical Weight of the NTFS Driver

File system drivers occupy a position that determines OS reliability. Because bugs directly affect user data, verification takes time. That ReactOS’s NTFS driver has come this far is evidence of years of accumulated verification.

Michael Larabel of Phoronix frames this milestone as a landmark for the project while explicitly noting the lack of caching, journaling, and security, as well as the possibility of unknown bugs. The reporting style itself, which notes both the achievement and the constraints, accurately conveys the current assessment.

Testing Regime and Future Focus

Future focus will be on adding features and eliminating bugs. Implementing caching directly improves performance, while journaling and security broaden the range of uses. All are changes involving the core of the file system and carry a risk of regressions.

What users can do is try it for evaluation purposes and report bugs. However, deciding to put real data on it at this point is not recommended. There is a gap between the fact that it can be installed and the judgment that it can withstand operation.

Editorial Opinion

In the short term, we see a possibility that ReactOS installation testing will be reorganized around NTFS partitions. Trial procedures and documentation for virtual environments will likely be updated, broadening the base of testing. However, due to performance and fault-tolerance constraints, deployment for business use will remain limited.

In the long term, the completeness of NTFS support will become one of the axes for evaluating ReactOS. If journaling and security are implemented, testing premised on data sharing with Windows environments will become more realistic. It could also affect the decision on reaching beta.

The question from the editorial desk is where to set the standard for calling a driver that lacks caching and journaling “practical.” To what extent does file system completeness in a compatible OS influence user trust? Discussion is needed, including disclosure of the testing scope and the design of bug reporting.

References

• “ReactOS Can Now Be Installed & Used With Its NTFS Driver”, by Michael Larabel — Phoronix, 2026-10-17T22:01:16.000Z (ARR)
• Source URL: https://www.phoronix.com/news/ReactOS-NTFS-Driver