Forum Discussion
Solved
ReFS volume appears RAW (version doesn't match expected value) after Windows Update
After Windows Update last night, Windows Server 2019 wouldn't mount a storage space volume as ReFS (it appears as RAW). The error in the ReFS event log is "ReFS failed to mount the volume. Version 1....
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.
All these tools scan drives for signatures and include deleted files and handle moved files extremely poorly. This turned my 4TB into 9.5TB one of the tools required. I had an intact volume and didn't need a scan, only for them to read the directory structure from v1.2. R-Studio was one of the worst - they couldn't even get a list of files working and their support had no idea. Other tools didn't even respond to support request, even after I paid for their tools. Microsoft should ether document ReFS publicly or provide much better set of recovery tools for these kind of things.
If you data is still RAW after installing all updates and uninstalling the defective one first, then it is very likely that your ReFS volume has been formatted pre Windows Server 2016 and is not yet on ReFS version 3.x
ReFS version gets upgraded with OS Inplace upgrades when the volume remains attached (this cannot be reverted)
https://gist.github.com/0xbadfca11/da0598e47dd643d933dc
In this case have an old Server 2012 R2 Update 1 without this bugged patch and mount this volume to this server to gain access to your data with earlier REFS version.
If you then execute and inplace upgrade from 2012 R2 to 2019 this ReFS volume would be upgraded to the specific version Microsoft supports and the patch would work with.
Hope this helps.
ReFS version gets upgraded with OS Inplace upgrades when the volume remains attached (this cannot be reverted)
https://gist.github.com/0xbadfca11/da0598e47dd643d933dc
In this case have an old Server 2012 R2 Update 1 without this bugged patch and mount this volume to this server to gain access to your data with earlier REFS version.
If you then execute and inplace upgrade from 2012 R2 to 2019 this ReFS volume would be upgraded to the specific version Microsoft supports and the patch would work with.
Hope this helps.