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.
stephc_msft
Microsoft
MicrosoftYes, refs v3.1 on WS2016 will be ok after Feb updates. Note that if still using v1.2 refs disk on WS2016 or later, then the v1.2 disks will still be affected, it they are detected as removable/hoypluggable.
The issue still persists for some, and it will reappear in the future whenever old volumes are mounted. This is quite annoying, as ReFS was supposed to be the best long-term preservation solution to contrast bitrot, etc.
This thread started with my post for a scenario with Windows Server 2019 and a ReFS 1.2 volume (on storage space, not removable). This has not been solved. It was not fixed with the January hotfix, nor in February (tried that, had to uninstall updates again). The "solution" was to copy the data to a new ReFS volume.
stephc_msft remember we had a direct exchange, also using your diagnostic tool to confirm that the volume was not flagged as removable.
By now, everyone who was affected probably already copied their data from ReFS 1.x to a newer version. Still, as many could be affected in the future they could show a helpful error message rather than volumes turning RAW, which also misleads many into thinking that the data has been lost forever (already happened this year, as seen on various other forums).
This thread started with my post for a scenario with Windows Server 2019 and a ReFS 1.2 volume (on storage space, not removable). This has not been solved. It was not fixed with the January hotfix, nor in February (tried that, had to uninstall updates again). The "solution" was to copy the data to a new ReFS volume.
stephc_msft remember we had a direct exchange, also using your diagnostic tool to confirm that the volume was not flagged as removable.
By now, everyone who was affected probably already copied their data from ReFS 1.x to a newer version. Still, as many could be affected in the future they could show a helpful error message rather than volumes turning RAW, which also misleads many into thinking that the data has been lost forever (already happened this year, as seen on various other forums).