Forum Discussion
ReFS volume appears RAW (version doesn't match expected value) after Windows Update
I solved this by uninstalling KB5009557. The ReFS volume came back working as it should, instead of appearing as RAW.
Update: since even the February 2022 Windows Update bricks ReFS in the same way, and hints from Microsoft are that ReFS 1.x is no longer supported, we copied everything to new disks, upgrading ReFS from 1.2 to 3.4 in the process. Such a (manual) ReFS upgrade should be the solution that everyone needs, allowing to re-enable Windows Update.
After almost attempting a FS repair, I found someone on reddit that mentioned your post. This saved me some headache. I tried to passthru a device and changed this option to TRUE. Changing it to FALSE and it came right back. Thank you.
Here is a new one, used external USB 2Tb drive with ReFS on Windows 10 for a year+ as some old CDs/DVDs backup
No issues
This PC has multiple OS installed (various 10, and 11)
It must have happened that I had the drive attached to 11 when some usual upgrade happened. And it also upgraded ReFS to version 3.9 (as confirmed by fsutil fsinfo refsinfo F: )
Now this dis is no longer usable in Windows 10 as per this: https://gist.github.com/0xbadfca11/da0598e47dd643d933dc
So the issue is not limited to Server 2012 etc
It is just a mess all together!
And another update is coming:
https://www.neowin.net/news/microsoft-silently-updates-windows-11-refs-file-system-version-in-latest-canary-build/
- This one is different, though. The original issue was that Windows failed to upgrade ReFS volumes under certain conditions (e.g. portable drives), so as new KB's and releases piled up, Windows stopped recognizing the volume and there was no way to get the data back without uninstalling the culprit KB or attaching the drive to an older Windows machine.
What you are describing is the opposite - Windows upgrades ReFS version automatically, causing ReFS volumes to be unreadable on older Windows releases, but you can still access your data on Windows 11.
I suggest moving your backup data to an NTFS volume. Less headache.- Correct on both counts!
