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.
For me, this has just reared its head when installing KB5014738 (2022-06 Security Monthly Quality Rollup). The exact symptoms as above, showing a RAW partition on an ReFS volume on Windows Server 2012 R2 on the Xen HV. I asked the HV host to make changes to the configuration of our VM to be xe vm-param-set uuid=<vm_uuid of the problematic vm> platform:device-model=qemu-trad but they refused so I have had to rollback the install of this KB.
No idea why this didn't impact us the first time round but just in case anyone comes across this thread and doesn't see their KB listed.
stephc_msft Your suggested command to see the ReFS version number doesn't seem to work on Server 2012 R2. Is there a suitable command for this version instead of fsutil fsinfo refsinfo x:
WS2012R2 does not have the refsinfo option in fsutil, but doesnt matter too much, as if using ReFS on 2012R2 it will always be ReFS V1.2
If you can examine the first sector of the ReFS volume with a disk/hex editor then the version number is 'obvious' at offset 28 hex