Windows Server 2016 Domain Controller Lookup Failure Issue Confirmed by Microsoft

Microsoft has officially acknowledged a new known problem impacting Windows Server 2016 systems, leading to domain controller lookups failing post the installation of the KB5087537 security update in May 2026.

Despite reaching the end of mainstream support in January 2022, Microsoft has extended the support end date by 5 years to facilitate customer migration to newer Windows Server versions.

According to an updated support document, this issue specifically affects devices with hostnames comprising exactly 15 characters.

“Following the installation of this update, domain controller discovery on Windows Server 2016 systems may encounter failures when the server hostname consists of 15 characters,” Microsoft explained.

“When the hostname is precisely 15 characters long, DCLocator calls (e.g., using nltest /dsgetdc:<domain> /pdc) will result in ERROR_INVALID_PARAMETER, hindering the location of a domain controller by applications and administrative tools.”

The company also highlighted that this known issue could impact specific administrative scenarios necessitating access to a domain controller.

“Consequently, administrative tasks reliant on domain controller lookup may fail, affecting areas like DFS Namespace management,” it added.

While investigating the domain controller lookup challenges, Microsoft has not yet provided a resolution timeline.

Recent Windows Server Issues Addressed by Microsoft

In recent times, Microsoft has also addressed Windows Update failures post the installation of optional non-security preview updates in January 2026 within restricted network environments. Additionally, it tackled deployment issues of Windows 11 security updates due to insufficient free space on the EFI System Partition (ESP).

Last month, administrators were cautioned about potential BitLocker recovery booting on some Windows Server 2025 devices. Emergency out-of-band updates were released to rectify issues causing Windows Server systems with domain controller roles to enter a restart loop.

In April, Microsoft finally resolved a bug that had been affecting Windows servers since September 2024. This bug led devices running Windows Server 2019 and Windows Server 2022 to upgrade unexpectedly to Windows Server 2025.