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.