Microsoft Confirms Windows Servers Enter Reboot Loops Following April Patches
\n \t
\n
<\/BR>
\n
\n \t
\n
<\/BR><\/p>\n
Microsoft has confirmed a critical known issue affecting Windows Server 2025 domain controllers following the deployment of the April 2026 Patch Tuesday cumulative update, KB5082063, where affected servers are entering repeated reboot loops after installation.<\/p>\n
Released on April 14, 2026, the cumulative update KB5082063<\/a> (OS Build 26100.32690) is the standard monthly security update for Windows Server 2025, bundling the latest security fixes along with non-security improvements from March\u2019s optional preview release.<\/p>\n However, Microsoft\u2019s official release changelog updated on April 16, 2026, now includes a known issue noting that \u201cDomain controllers might restart repeatedly after installing this update,\u201d flagging the reboot loop problem for enterprise IT administrators.<\/p>\n The issue is compounded by a secondary problem: a subset of Windows Server 2025 systems<\/a> is also failing to install the update entirely, throwing error code 0x800F0983 during deployment.<\/p>\n Microsoft acknowledged it is actively monitoring diagnostic telemetry tied to the recurring install failure and confirmed that \u201ca limited number of affected servers might experience an installation failure accompanied by the error code 800F0983\u201d.<\/p>\n Sysadmin reports on Reddit\u2019s Patch Tuesday megathread corroborate Microsoft\u2019s warning, with one administrator noting a domain controller became \u201cstuck in a reboot loop\u201d following KB5082063 installation.<\/p>\n Booting into Directory Services Restore Mode (DSRM) was reported as functional, and uninstalling the update allowed the affected domain controller to reboot normally.<\/p>\n This points squarely at the update as the root cause, particularly for non-Global Catalog (non-GC) domain controllers in complex Active Directory environments.<\/p>\n Separately, Microsoft warned that devices with unrecommended BitLocker Group Policy configurations may be forced to enter BitLocker recovery mode after installing KB5082063<\/a>, a known issue added to the changelog on April 14, 2026.<\/p>\n While this is unlikely to affect home users, enterprise-managed servers with specific BitLocker policies could face access disruptions requiring manual recovery key entry.<\/p>\n Despite the issues, the update delivers meaningful security and reliability improvements across several components:<\/p>\n Microsoft has not yet published a formal workaround or fix timeline for the reboot loop issue, and an investigation into the 0x800F0983 install failure is ongoing.<\/p>\n IT administrators are advised to monitor the Windows Server 2025 release health dashboard<\/a> for real-time updates, pause KB5082063 deployment on domain controllers until a resolution is available, and maintain offline BitLocker recovery keys ahead of patching.<\/p>\n The servicing stack update KB5082062 (Build 26100.32692) is bundled alongside this release to ensure update infrastructure reliability.<\/p>\n Follow us on Google News<\/a>, LinkedIn<\/a>, and X<\/a> for daily cybersecurity updates. Contact us<\/a> to feature your stories.<\/strong><\/p>\n The post Microsoft Confirms Windows Servers Enter Reboot Loops Following April Patches<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\nBitLocker Recovery Triggered<\/strong><\/h2>\n
What\u2019s Fixed in KB5082063<\/strong><\/h2>\n
\n
DefaultDomainSupportedEncTypes<\/code> value to AES-SHA1 for accounts lacking explicit AD encryption type definitions, tied to CVE-2026-20833<\/li>\nSet-GPPrefRegistryValue<\/code> cmdlet to correctly preserve all imported registry values<\/li>\n<\/ul>\n