September 10, 2024—KB5042881 (OS Build 20348.2700)

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 Server 2022, see its update history page. NoteFollow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Improvements

This security update includes quality improvements. Below is a summary of the key issues that this update addresses when you install this KB. 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.

• [Windows Installer] When it repairs an application, the User Account Control (UAC) does not prompt for your credentials. After you install this update, the UAC will prompt for them. Because of this, you must update your automation scripts. Application owners must add the Shield icon. It indicates that the process requires full administrator access. To turn off the UAC prompt, set theHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\DisableLUAInRepairregistry value to1. The changes in this update might affect automatic Windows Installer repairs; see Application Resiliency: Unlock the Hidden Features of Windows Installer.
• [IE mode] Pop-up windows open in the background instead of in the foreground.
• [AppContainer] Printers do not work as you expect when you use them in a restricted setting, like AppContainer.
• [BitLocker] You might not be able to decrypt a BitLocker data drive. This occurs when you move that drive from a newer version of Windows to an older version.
  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 Security Update Guide and the September 2024 Security Updates.

Windows Server 2022 servicing stack update (KB5043167) - 20348.2696

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.

Known issues in this update

Symptom	Workaround
After installing this update, you might be unable to change your user account profile picture.When attempting to change a profile picture by selecting the button Start>Settings > Account>Your info and, under** Create your picture**, clicking on**Browse for one, **you might receive an error message with error code 0x80070520.	We are working on a resolution and will provide an update in an upcoming release.
After installing this security update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device. Resulting from this issue, your device might fail to boot Linux and show the error message “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.”The August 2024 Windows security update applies a Secure Boot Advanced Targeting (SBAT) setting to devices that run Windows to block old, vulnerable boot managers. This SBAT update will not be applied to devices where dual booting is detected. On some devices, the dual-boot detection did not detect some customized methods of dual-booting and applied the SBAT value when it should not have been applied.	Please refer to the workaround mentioned in Windows release health site for this issue.
After installing the Windows update released on or after July 9, 2024, Windows Servers might affect Remote Desktop Connectivity across an organization. This issue might occur if legacy protocol (Remote Procedure Call over HTTP) is used in Remote Desktop Gateway. Resulting from this, remote desktop connections might be interrupted.This issue might occur intermittently, such as repeating every 30 minutes. At this interval, logon sessions are lost and users will need to reconnect to the server. IT administrators can track this as a termination of the TSGateway service which becomes unresponsive with exception code 0xc0000005.	To work around this issue, use one of the following options:Option 1: Disallow connections over pipe, and port \pipe\RpcProxy\3388 through the RD Gateway.This process will require the use of connection applications, such as firewall software. Consult the documentation for your connection and firewall software for guidance on disallowing and porting connections.Option 2: Edit the registry of client devices and set the value of RDGClientTransport to 0x00000000 (0)In Windows Registry Editor, navigate to the following registry location:HKEY_CURRENT_USER\Software\Microsoft\Terminal Server ClientFindRDGClientTransportand set its value to0(zero). This changes the value ofRDGClientTransportto0x00000000 (0).Next step: We are working on a resolution and will provide an update in an upcoming release.
After installing this update, container networking on Kubernetes might not operate as expected, preventing containers from reaching external networks or communicating between pods. It potentially impacts users setting up container networking on dev or production instances using Calico on Server 2022. Affected containers will not connect to the internet, and traffic will be blocked in host devices’ Firewall.Users may observe errors such as ‘General failure’ when pinging external addresses like ‘microsoft.com’ from within the container.People using devices with Windows Home and Pro editions are unlikely to be affected, as this issue mainly impacts servers and enterprise environments using container networking.	This documentation contains information about how to modify the registry. Make sure that you back up the registry before you modify it and that you know how to restore the registry if a problem occurs. For more information, see How to back up and restore the registry in Windows.To mitigate the issue temporarily until a resolution is available, please follow the below steps:a. Add a registry value to disable the changes by running the following command:`

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hns\State /v FwPerfImprovementChange /t REG_DWORD /d 0 /f

b. Restart the hns service by running the command:

Restart-service hns

`We are working on a resolution that will be available in a future Windows update.

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 and Servicing Stack Updates (SSU): Frequently Asked Questions.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).Install this updateTo install this update, use one of the following Windows and Microsoft release channels.

Windows UpdateBusinessCatalogServer Update Services

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

Available	Next Step
Yes	None. This update will be downloaded and installed automatically from Windows Update for Business in accordance with configured policies.

Available	Next Step
Yes	To get the standalone package for this update, go to the Microsoft Update Catalog website.

Available	Next Step
Yes	This update will automatically sync with Windows Server Update Services (WSUS) if you configure Products and Classifications as follows:Product: Microsoft Server operating system-21H2Classification: Security Updates

If you want to remove the LCUTo 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 InformationFor a list of the files that are provided in this update, download the file information for cumulative update 5042881. For a list of the files that are provided in the servicing stack update, download the file information for the SSU (KB5043167) - version 20348.2696.