May 12, 2026—KB5087544 (OS Builds 19045.7291 and 19044.7291)

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:

Summary

This article lists the security issues and quality improvements included in this cumulative security update.

Applies to: Windows 10 ESU

Important: Use EKB KB5015684 to update to Windows 10, version 22H2.

This security update includes fixes and quality improvements that are part of the following updates:

April 14, 2026—KB5082200 (OS Builds 19045.7184 and 19044.7184)

The following is a summary of the issues that this update addresses when you install this update. If there are new features, it lists them as well. The bold text within the brackets indicates the item or area of the change we are documenting.

[Remote Desktop security warnings (known issue)] Fixed: The Remote Desktop Connection security warning dialog might render incorrectly in multi-monitor configurations with different display scaling settings. This issue might occur after installing the Windows security update released on April 14, 2026 (KB5082200).
[Secure Boot]
- This update enables dynamic status reporting for Secure Boot states in Windows Security App.
- With this update, Windows quality updates include additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout.
[Daylight Savings Time] Update for Arab Republic of Egypt to support the government DST change order in 2023.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

For more information about security vulnerabilities, please refer to the new Security Update Guide website and the May 2026 Security Updates.

For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 22H2, see its update history page.

Known issues in this update

Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key Symptoms

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 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.

Resolution

We are working on a resolution and will provide more information when it is available.

To temporarily work around this issue, 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.

Windows 10 servicing stack update (KB5084130) - version 19041.7183

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.

Note: This servicing stack update (SSU) includes enhanced logic to verify whether a device is hosted on Azure, leveraging an updated certificate chain for validation. To ensure that the device can access the required certificate update domains to successfully download and install certificate updates, see Certificate downloads and revocation lists and Azure Certificate Authority details. To learn more about SSUs, see Servicing stack updates.

How to get this update

Before you install this update

Important You must have the latest servicing stack update (SSU) installed. Not installing the latest SSU before applying Windows updates might result in the Windows update not being offered until the latest SSU is installed.

Deployment

If you deploy this update, choose one of the following based on your installation scenario:

For offline OS image servicing

If your image does not have the July 25, 2023 (KB5028244) or later LCU, you must install the special standalone October 13, 2023 SSU (KB5031539) before installing this update.

For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog

If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021, SSU (KB5005260) before installing this update.

Get and install this update

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

Available	Next Step
	This update will be downloaded and installed automatically from Windows Update.

File information

A list of the files that are included in this update are provided in a CSV (Comma delimited) (*.csv) file. The file can be opened in a text editor such as Notepad or in Microsoft Excel.

Note: The English (United States) version of this software update might contain files for additional languages.

Download Icon Download the file information for this cumulative update KB5087544.

Download Icon Download the file information for the SSU (KB5084130) - versions 19041.7183 update.

Related information

If you want to remove this update

CAUTION Before you decide to remove this update, please 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.

Notice for Microsoft Store application updates

Windows updates do not install Microsoft Store application updates. If you are an enterprise user, see Microsoft Store apps - Configuration Manager. If you are a consumer user, see Get updates for apps and games in Microsoft Store.

End of support information

Windows 10, versions 21H2/22H2 and Windows 10 Enterprise LTSC 2021 end of support

Microsoft will no longer provide free software updates from Windows Update, technical assistance, or security fixes on the following end dates:

♦ Windows 10, version 21H2: Support ended on June 13, 2023

♦ Windows 10, version 22H2: Support ended on October 14, 2025

♦ Windows 10 Enterprise LTSC 2021: January 12, 2027

♦ Windows 10 IoT Enterprise LTSC 2021: January 13, 2032

Note: To continue to receive critical and important security updates for Windows 10, see Windows 10 Extended Security Updates (ESU). Otherwise, we recommend you upgrade to a later version of Windows.

May 12, 2026—KB5087544 (OS Builds 19045.7291 and 19044.7291)