Release Date:
8/13/2024
Version:
OS Build 20348.2655
Forinformation about Windows update terminology, see the articleabout thetypes of Windows updatesand themonthly quality update types.For an overview of Windows Server 2022, see itsupdate history page.
NoteFollow@WindowsUpdateto 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.
-
[Remote Desktop Session Host (RDSH)]Users cannot connect to the RDSH, and the host loses data. This occurs because win32kbase.sys stops responding.
-
[Windows Defender Application Control (WDAC)]A memory leak occurs that might exhaust system memory as time goes by. This issue occurs when you provision a device.
-
[Protected Process Light (PPL) protections] You can bypass them.
-
[Windows Kernel Vulnerable Driver Blocklist file (DriverSiPolicy.p7b)] This update adds to the list of drivers that are at risk for Bring Your Own Vulnerable Driver (BYOVD) attacks.
-
[Microsoft 365 Defender (known issue] The Network Detection and Response (NDR) service might encounter issues. This interrupts network data reporting. If this issue affects you, a message appears on the service health page of the Microsoft 365 admin center. You can also view the status of NDR on the service health page.
-
[BitLocker (known issue)] A BitLocker recovery screen shows when you start up your device. This occurs after you install the July 9, 2024, update. This issue is more likely to occur if device encryption is on. Go to Settings > Privacy & Security > Device encryption. To unlock your drive, Windows might ask you to enter the recovery key from your Microsoft account.
-
[Lock screen]This update addresses CVE-2024-38143. Because of this, the “Use my Windows user account” checkbox is not available on the lock screen to connect to Wi-Fi.
-
[NetJoinLegacyAccountReuse] This update removes this registry key. For more information refer to KB5020276—Netjoin: Domain join hardening changes.
-
[Secure Boot Advanced Targeting (SBAT) and Linux Extensible Firmware Interface (EFI)] This update applies SBAT to systems that run Windows. This stops vulnerable Linux EFI (Shim bootloaders) from running. This SBAT update will not apply to systems that dual-boot Windows and Linux. After the SBAT update is applied, older Linux ISO images might not boot. If this occurs, work with your Linux vendor to get an updated ISO image.
-
[Domain Name System (DNS)] This update hardens DNS server security to address CVE-2024-37968. If the configurations of your domains are not up to date, you might get the SERVFAIL error or time out.
-
[Line Printer Daemon (LPD) protocol] Using this deprecated protocol to print might not work as you expect or fail. This issue occurs after you install the July 9, 2024, and later updates.
Note When it is no longer available, clients, like UNIX, that use it will not connect to a server to print. UNIX clients should use the Internet Printing Protocol (IPP). Windows clients can connect to shared UNIX printers using the Windows Standard Port Monitor.
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 theSecurity Update Guideand the August 2024 Security Updates.
Windows Server 2022 servicing stack update (KB5041590) - 20348.2641
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 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 Client Find RDGClientTransport and set its value to 0 (zero). This changes the value of RDGClientTransport to 0x00000000 (0). We are working on a resolution and will provide an update in an upcoming release. |
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 updatesandServicing Stack Updates (SSU): Frequently Asked Questions.
Install this update
To 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 theMicrosoft Update Catalogwebsite. |
Available | Next Step |
Yes | This update will automatically syncwith Windows Server Update Services (WSUS) if you configure Products and Classifications as follows: Product: Microsoft Server operating system-21H2 Classification: Security Updates |
If you want to remove the LCU
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 nameby 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 that are provided in this update, download thefile information for cumulative update 5041160.
For a list of the files that are provided in the servicing stack update, download thefile information for the SSU (KB5041590) - version 20348.2641.