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.
The main hard drive (the one C:\ is on) is showing as raw
OS: Windows 10 Enterprise The main hard drive (the one C:\ is on) is showing as raw. I got a bluescreen (wish I had recorded what it said on it before I restarted, but it's probably a moot point now) and tried to restart, but the laptop froze before Windows loaded. I did some diagnostic stuff using a recovery drive and it became apparent that something had happened to C (it was showing as a Raw drive named D). I reassigned the drive letters back to the correct ones but I can't find any way of indicating that the drive is not raw. The partitions are all there according to DISKPART (Recovery 300mb, System 100mb, Reserved 128mb, Primary 237gb, Recovery 663mb), and the System partition is still formatted, as when I list the volumes, I get a FAT32 with 100MB, but everything else is raw. Much of the drive is Bitlocker encrypted. I know there are 3rd party tools that claim to be able to recover things, but I am wary that it will render the drive inoperable, even if it will get my data back. I have most of my data backed up, I just want a functioning OS that has all of my applications.
