2022 2026-04 CU (KB5082142) April any known issue

Good day Nawab Jan Shaikh

For the April 2026 Cumulative Update (KB5082142) on Windows Server 2022, there aren’t any widespread “show‑stopper” issues being reported right now, but there are a couple of things worth keeping an eye on. Some admins have noticed that after installing the CU, certain Group Policy settings around printer redirection and credential delegation can behave differently, so it’s smart to re‑validate those if you rely on them. Also, there have been scattered reports of slower startup times on VMs after patching, though nothing officially acknowledged as a bug yet.

As always, I’d recommend testing the CU in a staging environment before rolling it out broadly, especially if you’re running workloads that depend on RDP or Azure AD authentication. If you’re using third‑party endpoint protection, double‑check compatibility since updates sometimes trigger false positives. And of course, make sure you’ve got backups and a rollback plan in place before patching production servers.

Bottom line: no major red flags, but a few quirks to watch for. If this helps clear things up, please hit “Accept Answer” so we know you’re good to go.

For Windows Server 2022, the April 2026 Cumulative Update KB5082142 has the following documented issues and status:

1. Domain controllers may restart repeatedly after installing KB5082142
   • Scenario: In forests with multiple domains that use Privileged Access Management (PAM), after installing KB5082142 and rebooting, LSASS can crash during startup on domain controllers.
   • Impact: Affected DCs can enter a restart loop, breaking authentication and directory services and potentially making the domain unavailable.
   • Scope: Windows Server only; not consumer PCs or unmanaged individual devices.
   • Resolution: This issue is resolved by out-of-band (OOB) updates released on April 19, 2026:
     • Standard OOB: KB5091575 (downloadable from the Microsoft Update Catalog).
     • For servers enrolled in hotpatching: KB5091576 (delivered via Windows Update, no restart required).
2. Windows Server 2022 and Server 2019 unexpectedly upgraded to Windows Server 2025
   • Scenario: Some Windows Server 2022 and 2019 systems were unexpectedly upgraded to Windows Server 2025 when updates were managed through certain third‑party applications.
   • Status: Marked as resolved and associated in the release health documentation with KB5082142.

These are the KB5082142-related issues called out for Windows Server 2022 in the provided release health and resolved-issues documentation.

References:

• Windows Server 2022
• Resolved issues in Windows Server 2022