ReactOS Adds NTFS Install Support, Clearing Path Toward Beta Release
The open-source Windows alternative can now install directly on NTFS partitions, removing a long-standing technical barrier for users.
Key points
- ReactOS can now install directly onto NTFS drive partitions, ending reliance on FAT32.
- The new driver lacks caching, journaling, and security support, limiting performance.
- Read-only NTFS support was added in 2016, but direct installation remained impossible until now.
The ReactOS project has announced that its open-source operating system can now be installed directly onto NTFS partitions. This development removes a significant technical hurdle that previously forced users to rely on FAT32 filesystems for installation procedures.
According to a report by Ars Technica, which cited Phoronix, this milestone brings the project closer to reaching a beta release status. The ability to use NTFS aligns ReactOS more closely with the Windows environment it aims to replicate, specifically targeting binary compatibility with Windows Server 2003.
View the original post on X
Context and Background
NTFS is a proprietary filesystem developed by Microsoft, originating with Windows NT 3.1 in 1993. The variant introduced with Windows XP in 2001 remains the standard for most modern Windows systems. For ReactOS, which seeks to reproduce the Windows environment, being confined to FAT32 partitions was a practical barrier to achieving its compatibility goals.
Read-only NTFS support was first added to ReactOS in 2016. Boot support for NTFS partitions landed in the FreeLoader bootloader in 2022. This meant the bootloader could read from NTFS, but the operating system itself could not be installed there. The new driver closes a development gap that had persisted for nearly a decade.
Who Is Affected
The ReactOS team warned that the new driver still lacks caching, which causes inferior performance. It also lacks journaling and security support, meaning the feature is not yet production-ready for general use. The project stated on X that there are potentially undiscovered bugs in the new implementation.
ReactOS is a community-developed project mostly driven by volunteers. Development is coordinated through public channels like GitHub and the project’s forums. The project has remained in alpha for decades, underscoring the difficulty of reimplementing an operating system from scratch.
What should you do?
Users interested in testing the new functionality should proceed with caution due to the lack of security support and potential bugs. The ReactOS team advises that even experienced tinkerers should tread carefully when using the new NTFS driver. Those who wish to support the project can visit the official website to learn how to contribute to development efforts.
What to do and how to stay safe: ReactOS
- Verify that your hardware and existing data are backed up before attempting to install ReactOS on an NTFS partition.
- Monitor the ReactOS forums and GitHub repositories for updates regarding the stability of the new NTFS driver.
- Avoid using NTFS partitions for sensitive data on ReactOS systems until journaling and security support are implemented.
- Check system logs for errors if you encounter performance issues, as the current driver lacks caching capabilities.
Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Can ReactOS now be installed on the same filesystem as Windows?
Yes, ReactOS can now be installed directly on NTFS partitions, which is the standard filesystem for Windows.
Is the new NTFS driver ready for daily use?
No, the driver lacks caching, journaling, and security support, and may contain undiscovered bugs.
When was NTFS support first added to ReactOS?
Read-only NTFS support was added in 2016, but direct installation support was not available until this recent update.
