Forum Discussion
ReFS volume appears RAW (version doesn't match expected value) after Windows Update
- Jan 13, 2022
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.
Has anyone verified that turning off hotplug drives in VMWare config enables Win 212R2 server to get the latest updates?
ABeachy We received the update via SCCM deployment to our server collection.
- JGarcia1Feb 10, 2022Copper ContributorWe had uninstall both KB5009595 and KB5009624 on our 2012r2 server. After the server rebooted the ReFS volume worked again with no data loss.
- ngruendlFeb 10, 2022Copper Contributor
Another hour of unexpected downtime to a mission critical server. Can MS stop pushing this update to my server please?
I had this issue now with REFS / RAW volume on my Exchange DB vol for the second time in a month. I'm running Exchange 2016, Win2012R2 box. I had even had the Windows Update Service Disabled to stop the server from rebooting to install updates just from logging into it. It rebooted to install updates anyway and installed this bug for the second time. I'm migrating off this box as quick as possible...