Applies To
Windows Server 2022

Release Date:

6/9/2026

Version:

OS Build 20348.5256

This cumulative update for Windows Server 2022 (KB5094128), includes the latest security fixes and improvements, along with non-security updates from last month’s optional preview release. To learn more about differences between security updates, optional non-security preview updates, out-of-band (OOB) updates, and continuous innovation, see Windows monthly updates explained. For information on Windows update terminology, see the different types of Windows software updates. 

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

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. Microsoft has been updating these certificates on consumer and non-managed business devices over the past several months. Devices that haven’t received the newer certificates will continue to start and operate normally, and standard Windows updates will continue to install. Updated certificates will continue to be delivered through Windows Update in the coming months.

Change date

Change description

June 10, 2026

Update: Folder customization added.

Improvements

​​​​​​​This security update contains fixes and quality improvements from KB5087545 ​​​​​​​(released May 12, 2026). The following summary outlines key issues addressed by this update. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.

  • [Secure Boot]

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

    • This update adds the LimitSecureBootRequiredServiceData Group Policy and mobile device management (MDM) setting under Computer Configuration > Administrative Templates > Windows Components > Secure Boot. When enabled, Windows limits the Secure Boot service data it sends by suppressing the event normally sent to Microsoft. This policy is included in the Windows Restricted Traffic Limited Functionality Baseline. For information about the policy, see Manage connections from Windows 10 and Windows 11 operating system components to Microsoft services. 

  • [App] This update improves visibility and reliability of device security by enabling real-time status updates for Secure Boot within the Windows Security app.

  • [File Explorer] This update improves File Explorer search, including support for Chinese text, and UTF 8–encoded files without a byte order mark (BOM). Text now displays more clearly and consistently across search results, Content view, and tooltips.

  • [Texts and Fonts] This update improves Windows fonts by adding the new Saudi Riyal currency symbol. This change helps keep text clear, accurate, and visually consistent across your Windows apps and experiences.

  • [Folder customization] This update introduces a security hardening change to how Windows processes desktop.ini files. As a result, some users might notice missing custom folder icons or localized folder names for content from downloaded or remote locations. Note that access to folders is not affected. For more information, see Custom folder icons or localized folder names might not appear after installing the June 2026 Windows security update.

If you've already installed previous updates, your device will download and install only the new updates included in this package.

For more information about security vulnerabilities, see the Security Update Guide and the June 2026 Security Updates.

Windows Server 2022 servicing stack update (KB5094147) -20348.5251

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. To learn more about SSUs, see Simplifying on-premises deployment of 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. 

How to get this update

Before you install this update

​​​​​​​Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Prerequisite for offline OS image servicing:

​​​​​​​Make sure that your image includes KB5030216 (09/12/2023) or a later LCU. If not, install it on your offline media before you install the latest update. This LCU updates the SSU version to 20348.1960. That is the minimum SSU version you must have to prevent error 0x800f0823 (CBS_E_NEW_SERVICING_STACK_REQUIRED).

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note: The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

  • Use the Update WinPE script to update an existing Windows image. (Recommended)

  • Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.​​​​​​​

Install this update

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

Available

Next Step

Included

This update downloads and installs automatically from Windows Update and Microsoft Update.

File Information

For a list of the files provided in this update, download the file information for cumulative update 5094128​​​​​​​​​​​​​​​​​​​​​​​​​. 

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

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