> ## Content Index
> Fetch the complete content index at: https://www.blackvoid.club/llms.txt
> Use this file to discover other available public pages before exploring further.

# Windows January update problems - KB5009557, KB5009546, KB5009555
- URL: https://www.blackvoid.club/windows-january-update-problems-kb5009557-kb5009546-kb5009555/
- Published: 2022-01-23T22:29:29.000Z
- Updated: 2022-02-18T15:10:32.000Z
- Author: Luka Manestar
- Tags: dsm, dsm7

📢

**UPDATE** \- patch KB5009557 replaced with **[KB5010791](https://support.microsoft.com/en-au/topic/january-18-2022-kb5010791-os-build-17763-2458-out-of-band-43697313-d8e0-4918-b6df-7f64d4d9a8cd?ref=blackvoid.club)**; patch KB5009546 replaced with **[KB5010790](https://support.microsoft.com/en-us/topic/january-17-2022-kb5010790-os-build-14393-4889-out-of-band-567c392a-b10c-4dba-bed5-d3648af05164?ref=blackvoid.club)**; patch KB5009555 replaced with **[KB5010796](https://support.microsoft.com/en-us/topic/january-17-2022-kb5010796-os-build-20348-473-out-of-band-2e0408ba-10d4-4c68-9b3d-cc5fb8d6f4a8?ref=blackvoid.club)**

I know what you are thinking. Windows post, on this blog? Considering how important it is, let's leave it at that.

About a week ago as the **new Windows updates for January arrived**, so did new problems for system administrators, and users for that matter.

Depending on the OS, Windows Server 2012R2, 2019, 2022, you probably got one of the patches from the title: **KB5009557, KB5009546, KB5009555**.

‼️

If you have them installed already, **remove them** until Microsoft pushes new updates to replace those. 

Issues with those updates translate to the following:

- **Boot loops on the server after installing the security updates**. Post-installation of the security update, your servers are unable to boot properly. Uninstalling the patch resolves the boot loop issue on the affected servers. The issue, chiefly, affects domain controllers.
- Hyper VM V may break on the server. This may cause the virtual servers to fail on the server. Break in the virtualization layer can be resolved by uninstalling the security update KB5009557.
- ReFS volumes, internal as well as external, may turn RAW after installing the security update. Uninstalling the patch resolves the issue and the ReFS volume drives regain their original state.
- VPN connections, L2TP, and IPSEC tunnels may fail after installing the patch on the servers.
- **LDAP bindings may fail on the servers**.

So why is this important, and why am I writing an article about it? Well, the point is that if you **try and add your Synology NAS into Active Directory** backed up by servers with those patches, **you will, get this, reboot the servers**. Not bad right?

So once you start adding your NAS using the procedure it will be all well until DSM starts talking to your domain.

![](https://www.blackvoid.club/content/images/2022/01/image-1.jpeg)

So far so good

But then on the server-side, this happens.

![](https://www.blackvoid.club/content/images/2022/01/image-2.jpeg)

Server reboots

At the same time, DSM reports the following.

![](https://www.blackvoid.club/content/images/2022/01/image-3.jpeg)

This is when you start asking questions about what happened

To make matter worse, **your server will loop-reboot until you disjoin the NAS from the domain**.

So, before you start looking for reasons in all the wrong places, roll back your servers, and hold off with January patches for now. Thank you Microsoft (again).