Windows Server January Update causes Netlogon error

Microsoft has just announced that the Windows Server security updates that have just been released in the January 2022 Patch Tuesday package can prevent applications and network devices from creating Netlogon secure channels if installed on a domain controller.

Netlogon is a remote procedure call (RPC) interface and Windows Server process that authenticates services and users on Windows domain-based networks.

Affected applications or network devices, such as the Riverbed SteelHead WAN Optimizer, may experience problems with domain joins or limitations after joining a Windows domain.

According to Microsoft, "situations that rely on a Read-only domain controller (RODC) or a general RODC machine account may not be able to establish a Netlogon secure channel." On affected devices, the RODC account must have an associated and compliant KRBTGT account in order to successfully establish secure Netlogon channels.

"To fix this issue, affected apps and network devices will need an update from their developer or manufacturer." Microsoft shared.

Windows Server January Update causes Netlogon error Picture 1Windows Server January Update causes Netlogon error Picture 1

Affected versions of Windows Server include:

  1. Windows Server 2022
  2. Windows Server 2019
  3. Windows Server 2016
  4. Windows Server 2012 R2
  5. Windows Server 2012
  6. Windows Server 2008 R2 SP1
  7. Windows Server 2008 SP2

Microsoft and Riverbed are currently investigating this issue and will update as soon as new information becomes available.

Two weeks ago, Microsoft also fixed a Windows Active Directory bug that also appeared after rolling out the January updates. This issue affects .NET applications when purchasing or setting up Active Directory Forest Trust Information .

Last month, Microsoft also released a series of emergency updates to address many of the issues caused by the January 2022 Patch Tuesday updates.

Fixed issues include Windows Server Domain Controllers restart issues, VPN connection issues, Virtual Machines failure issues, and ReFS formatted drives failing to handle errors.

4.2 ★ | 16 Vote