Unfortunately just finding out about this. Entire ReFS volume appears to be shot even after uninstalling the update. Anyone else run into uninstalling not resolving the issue?

***Update - after uninstalling BOTH KB5009624 and KB5009595 our ReFS volumes are back. Running Server 2012 R2 Datacenter

Just had the ReFS issue on Server 2016 with KB5009546.  After install, reboot, target USB repository was RAW.  Uninstalled update and drive is visible again with all data.

UGH.  This has been a known issue for a week, why hasn’t MS pulled it?

the bottom in quality management does not seem to have been reached yet

Out of curiosity, is anyone getting failed to create snapshot on Hyper-V after the Jan 11 patch?

Boot, login and VMs are fine, but I can’t get any backups to work post-update.

You say it. We get the updates for free, so the least we can do is giving something back to Microsoft; fixing bugs, QA, …

Oh.my.god…. 🤯🤯🤯

That’s crazy talk! What next, QA testing?

But no mention of the ReFS issues. Sigh….

What else should they do...fix the update?

You are right: https://support.microsoft.com/en-us/topic/january-11-2022-kb5009557-os-build-17763-2452-c3ee4073-1e7f-488b-86c9-d050672437ae

All they’ve done is add the problems as known issues… oh Microsoft…

That’s because Microsoft released them AGAIN on a FRIDAY 🤯

https://www.bleepingcomputer.com/news/microsoft/microsoft-resumes-rollout-of-january-windows-server-updates/

We decided to decline the updates from our WSUS after seeing the thread on Reddit before MS pulled them. 
https://www.reddit.com/r/sysadmin/comments/s1jcue/patch_tuesday_megathread_20220112/
 

The servers that got patched don’t show any errors.

KB5009555 for Windows 2022 doesn’t seem to have been pulled. My test server still downloads this update from Windows Update. However, this is the faulty update which causes the raw ReFS issue.

aww bad patch MS

//VPN /IPSec Issue: Certain IPSEC connections might fail

• https://docs.microsoft.com/en-us/windows/release-health/status-windows-11-21h2#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-21h2#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-21h1#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1909#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1809-and-windows-server-2019#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1607-and-windows-server-2016#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1507#2773msgdesc
• https://docs.microsoft.com/en-us/windows/release-health/status-windows-server-2022#2773msgdesc

//Domain Controller rebooting issue

• https://docs.microsoft.com/en-us/windows/release-health/stat...
• https://docs.microsoft.com/en-us/windows/release-health/stat...

//Hyper V issue

• https://docs.microsoft.com/en-us/windows/release-health/stat...
• https://docs.microsoft.com/en-us/windows/release-health/stat...

Windows ah windows… Well apart from the this REFS fun (remember the REFS issues when it first came out and those poor souls who ventured into the 4k block settings), I believe there was some completely data wipeouts there. Huge thread in the forums if I remember correctly. That aside can you believe that you need to do this to get NFS write permissions on a nfs share? Or have I really gotten confused :)

“Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default.
Create a new New DWORD (32-bit) Value inside the Default folder named AnonymousUid and assign the UID found on the Linux directory as shared by the NFS system. This is the UID of the user that has the write access to that directory on Linux system.
Create a new New DWORD (32-bit) Value inside the Default folder named AnonymousGid and assign the GID found on the Linux directory as shared by the NFS system. This is the GID of the group that has the write access on the directory on Linux system.Windows 10: Regedit NFS AnonymousUid and AnonymousGid
Restart the NFS client or reboot the machine to apply the changes.
Now run the mount command and you will get the write access.”

Think it’s for the best…

Microsoft has pulled now the updates from the update servers:

https://www.bleepingcomputer.com/news/microsoft/microsoft-pulls-new-windows-server-updates-due-to-critical-bugs/amp/

Thanks for sharing. Passed this along to our ops team as today is patching day. Make sure these are not applied to our ReFS servers that are repos. Good old MS.

 You’re definetly right with that

Better check with a different person, just to be sure

But perhaps it’s a security feature? Microphones and webcams can spy on you, so better throw it all away

@Iams3leI’m sure this won’t be the last time we see such issues; just hope it won’t be in January…

@vNote42Reboots tend to solve problems and make the system more stable; so you’re spot on with “it’s a feature”

Thanks for sharing @regnor! Really bad bugs that shouldn't exist! 

These days a customer told me he was suffering from regular reboots of his new 2022 test server. The guess was it had to do with trial-version. No its a feature … eh … bug

But too many bad things this month, such as

• Windows KB5009543, KB5009566 updates break L2TP VPN
• New critical Windows HTTP vulnerability is wormable etc…

Therefore, I agree with @regnor assertion on this issue! but like I said before, they are still not recognised by Microsoft at this moment of writing this comment: https://msrc.microsoft.com/update-guide/ 

I can confirm that at the point in writing this piece, Microsoft hasn't recognised this vulnerability

• https://support.microsoft.com/en-us/topic/january-11-2022-kb5009557-os-build-17763-2452-c3ee4073-1e7f-488b-86c9-d050672437ae 

haha :D

Nope that’s it, Microsoft took it too far this morning! Decided my headset and webcam were untrustworthy (or maybe they meant the person on them, aka me!)