Windows Server: Emergency updates finally fix restart loops
Endless restarts, broken system services and cryptic error codes: An unsuccessful security update for Windows Server forces Microsoft to take immediate action. Special emergency patches are now intended to protect company networks from collapse.
Emergency patches for servers
Microsoft has therefore released unscheduled updates for several versions of Windows Server. The so-called out-of-band updates fix problems that were caused by the regular security update in April. Network environments in which authentication processes failed are particularly affected. The cause is a compatibility issue after installing the previous patches. For domain controllers with special access management such as Privileged Access Management, the Local Security Authority Subsystem Service crashed. The service is responsible for authentication and manages, among other things, login attempts and password changes. The consequences were restart loops, which meant that directory services were temporarily unavailable.
As Neowin reports, there were also installation errors with update KB5082063 on some systems with Windows Server 2025. The error codes 0x800F0983 and 0x80073712 occurred, which usually indicate missing or damaged update files.
OOB patches offer a quick fix
To fix this, Microsoft is releasing new packages for Windows Server 2025, 2022 and 23H2. Out-of-band updates appear outside of regular Patch Tuesday and are only released if there are urgent issues. The KB5091157 update for Windows Server 2025 fixes both the installation errors and the restart issues. Patches for older versions focus on stabilizing systems. The updates are available via the Microsoft Update Catalog and are not distributed automatically.
Available updates include:
- Windows Server 2025: KB5091157
- Windows Server 23H2: KB5091571
- Windows Server 2022: KB5091575
- Windows Server 2019: KB5091573
The updates enable rapid restoration of operations on affected networks, but create additional workload for IT departments. A known issue related to BitLocker recovery persists.
