Applies To
Windows Server 2022

Release Date:

4/19/2026

Version:

OS Build 20348.5024

​​​​​​​Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices. 

Windows Secure Boot certificate expiration 

Important: Secure Boot certificates used by most Windows devices are set to expire starting in June 2026. This might affect the ability of certain personal and business devices to boot securely if not updated in time. To avoid disruption, we recommend reviewing the guidance and taking action to update certificates in advance.  

For details and preparation steps for Windows devices, see Windows Secure Boot certificate expiration and CA updates.

For details and preparation steps for Windows servers, see the following resources:

Change date

Change description

April 27, 2026

Corrected the known issue "Warnings related to Remote Desktop might not display correctly"

April 23, 2026

Known issues added: "Warnings related to Remote Desktop might not display correctly"

April 21, 2026

Known issue added: "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"

Summary

This out-of-band update for Windows Server 2022 (KB5091575) is cumulative. It includes fixes and improvements that are part of the following update:

The following is a summary of the issues that this out-of-band update addresses when you install this update. The bold text within the brackets indicates the item or area of the change we are documenting.

  • [Domain controllers (known issue)] Fixed: After installing the April 14, 2026, (KB5082142) Windows security update and restarting, domain controllers with multi-domain forests that use Privileged Access Management (PAM), might experience startup issues. In some cases, Local Security Authority Subsystem Service (LSASS) might stop responding, leading to repeated restarts, and preventing authentication and directory services, which can make the domain unavailable.

If you installed earlier updates, your device downloads and installs only the new updates contained in this package.

To view the latest updates about this release, visit the Windows release health dashboard or the update history page for Windows Server 2022. 

Windows Server 2022 servicing stack update (KB5082137) - 20348.5021

Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). SSUs improves the reliability of the update process and includes fixes to the servicing stack, the component that installs Windows updates. To learn more about SSUs, see Servicing stack updates.

Known issues in this update

Symptom

Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update.

This issue only affects a limited number of systems in which ALL of the following conditions are true. These conditions are unlikely to be found on personal devices not managed by IT departments.

  1. BitLocker is enabled on the OS drive.

  2. The Group Policy "Configure TPM platform validation profile for native UEFI firmware configurations" is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually).

  3. System Information (msinfo32.exe) reports Secure Boot State PCR7 Binding as "Not Possible".

  4. The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.

  5. The device is not already running the 2023-signed Windows Boot Manager.

In this scenario, the BitLocker recovery key only needs to be entered once -- subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged. For help finding your BitLocker recovery key, see the article, Find your BitLocker recovery key.

Enterprises are recommended to audit their BitLocker group policies for explicit PCR7 inclusion and check msinfo32.exe for their PCR7 binding status before installing this update. (See the Workaround below.)

Workaround 

Remove the Group Policy configuration before installing the update (Recommended) 

  1. Open Group Policy Editor (gpedit.msc) or your Group Policy Management Console.

  2. Navigate to: Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives.

  3. Set "Configure TPM platform validation profile for native UEFI firmware configurations" to "Not Configured".

  4. Run the following command on affected devices to propagate the policy change: gpupdate /force

  5. Run the following command to suspend BitLocker (where BitLocker is enabled on the C: drive): manage-bde -protectors -disable C: 

  6. Run the following command to resume BitLocker (where BitLocker is enabled on the C: drive): manage-bde -protectors -enable C: 

  7. ​​​​​​​This updates the BitLocker bindings to use the Windows-selected default PCR profile.

A permanent resolution for this issue is planned in a future Windows update. More information will be provided when it is available.

After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287. 

Symptoms

After installing this update, the security warning that appears when opening Remote Desktop (RDP) files might not display correctly in some cases.

This issue might occur when you use more than one monitor with different display scaling settings (for example, one display set to 100% and another set to 125%). When this happens, the warning window might show overlapping text or partially hidden buttons, which can make the message difficult to read or interact with.

Workaround

To help the warning window display correctly, set the same display scaling on all monitors.

  1. Open Display settings from the Start menu.

  2. Select each display.

  3. Under Scale & Layout, set the same Scale value for all displays.

Keyboard accessibility option

If buttons or text are difficult to select with a mouse, you can use the keyboard to interact with the warning message:

  • Press the Tab key to move keyboard focus between options.

  • When an option is highlighted, press the Spacebar to select it.

Microsoft will address this issue in a future Windows update.

How to get this update

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Available

Next Step

Not included

This update is only available from the Microsoft Update Catalog.

If you want to remove the LCU 

CAUTION Before you decide to remove this update, see Understanding the risks: Why you should not uninstall security updates.

To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File Information

For a list of the files provided in this update, download the file information for out-of-band update 55091575.. 

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5082137) - version 20348.5021. 

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center