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.
MikeLabatt stephc_msft Stephen can you confirm that the remaining issue for ReFS 1.x is documented in the Windows Update History for affected Windows Server and Windows Clients?
If not, I'd propose including it in Windows Update History and link to a new techcommunity article or KB article explaining the situation and solutions, so briefly what we discussed here.
If affected people with ReFS 1.x have a large amount files / data to copy instead of robocopy they can also leverage other tools. I would recommend Gurusquad GSCopy which is infact more scaleable, around 40% faster and has better reporting, open file support etc.
I regularly use this for file server migrations.
If one want to stick with Microsoft Tools I would recommend to create a share on the root folder and use Windows Admin Center Storage Migration Service.
This is an easier process for those not being familiar with robocopy and it thas also good output. One needs to omit the last step to change servernames etc.
WAC SMS would only work if one creates a new machine (VM) with a ReFS 3.1 oder later volume. It is not designed to copy from one volume to another on the same machine.