Forum Discussion
Why Windows Should Adopt ReFS as a Bootable Filesystem
ReFS could become a bootable filesystem — it only needs a few missing layers.
No need to copy NTFS, just implement what the Windows boot process requires.
Key missing pieces:
System‑level journaling (not only metadata)
Full hardlink + extended attribute support
EFS, ACLs, USN Journal for security + Windows Update
Boot‑critical atomicity for safe system file updates
Bootloader‑compatible APIs (BCD, BitLocker pre‑boot, WinRE, Secure Boot)
Goals:
Use NTFS as a reference map, add the missing capabilities to ReFS,
and optimize them using ReFS features (copy‑on‑write, integrity streams, block cloning).
Result:
A modern, resilient filesystem that can finally boot Windows - without losing its benefits.
3 Replies
Its very interesthing to learn to how to improve Windows that misssing parts need to be integrated to ensure its benefits and we need to make the Windows more resillient to Malware and file corruption and its essetial if they want a safe Windows boot
ReFS offers superior data integrity, automatic error correction, and resilience against corruption, making it ideal for critical system files.
Thanks for the insight. ReFS absolutely delivers stronger integrity and resilience — no argument there. The challenge is that the current implementation still isn’t fully aligned with all system‑level requirements for a bootable filesystem. NTFS has decades of deep integration with legacy components, low‑level APIs, and boot‑critical paths that ReFS doesn’t yet replicate. Once ReFS reaches full compatibility and performance parity in those areas, it will be a much stronger candidate for system boot.✌🏻
