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.
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...
Cant comment on why updates got applied even after you were 'disabling' updates.
- ABeachyFeb 11, 2022Copper Contributorstephc_msft that is my question. Does disabling hotplug in VMWare config allow the installation of the new updates and not break ReFS on WS2012R2? Has anyone actually verified this?
- E3SMCFeb 11, 2022Copper ContributorI was finally able to test this in my lab with my Exchange 2016 server running on Server 2012 R2. I was able to apply the VMware workaround and install the patch without issue. Note that I have not completed this task on my live server yet, but I am confident it will work at this point.
1. Shutdown the server.
2. Follow the steps in this vmware KB article https://kb.vmware.com/s/article/1012225
3. Power up the machine (it took about 8 minutes for all of the virtual hardware to register with the server, but this may have been because I powered up the server for the first time in my lab which has different host hardware.)
4. Install the security patches (I ended up installing the February security patches)
5. Reboot.
6. Confirm that your REFS drives are operational.
7. Confirm that you can migrate the VM to a different host for HA purposes.- JGarcia1Feb 14, 2022Copper ContributorI have ESXi7.0 u2 on my hosts and Guest windwos 2012r2 VM's.
These steps also helped Windows 2012r2 VM to recognize the ReFS Volume.
1. Shutdown the server.
2. Follow the steps in this vmware KB article https://kb.vmware.com/s/article/1012225
3. Power up the machine
Thanks E3SMC