Microsoft: Domain Controller lookup may fail on Windows Server 2016
Source: Bleeping Computer
Issue Overview
Microsoft has confirmed a new known issue affecting Windows Server 2016 systems that causes domain controller lookups to fail after installing the KB5087537 May 2026 security update.
Affected Systems
- Windows Server 2016 (extended support has been extended by five years to give customers more time to migrate).
- The issue occurs only on devices whose hostnames are exactly 15 characters long.
“After installing this update, domain controller discovery might fail on Windows Server 2016 systems when the server hostname is 15 characters long,” Microsoft said.
When the hostname is 15 characters, DCLocator calls (e.g., using nltest /dsgetdc: /pdc) return ERROR_INVALID_PARAMETER, preventing applications and administrative tools from locating a domain controller.
nltest /dsgetdc: /pdcImpact
Microsoft noted that the issue may also affect certain administrative scenarios that require access to a domain controller:
“Administrative operations that rely on domain controller lookup might fail, impacting scenarios such as DFS Namespace management.”
Microsoft’s Response
The company is investigating the domain controller lookup problem and has not yet provided a timeline for a fix.
Related Recent Issues
- Windows Update failures after installing the January 2026 optional non‑security preview updates in restricted network environments – see BleepingComputer’s coverage here.
- Windows 11 security update deployment issues caused by insufficient free space on the EFI System Partition (ESP) – details here.
- BitLocker recovery prompts on some Windows Server 2025 devices after April updates – see the warning here.
- Emergency out‑of‑band updates released to fix restart loops on Windows Server systems with domain controller roles – read more here.
- Automatic upgrade bug affecting Windows Server 2019 and Windows Server 2022 devices that unintentionally upgraded to Windows Server 2025 – see the fix announcement here.