September 10, 2024—KB5043064 (OS Builds 19044.4894 and 19045.4894)

^11/17/20

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.

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

This update addresses security issues for your Windows operating system.

Improvements

Note To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

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

This security update includes quality improvements. Key changes include:

This build includes all the improvements from the supported Windows 10, version 21H2 editions.
No additional issues are documented for this release.

Important: Use EKB KB5003791 to update to Windows 10, version 21H2 on supported editions.

This security update includes quality improvements that were a part of update KB5041582 (released August 27, 2024). 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 the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\DisableLUAInRepair registry value to 1. The changes in this update might affect automatic Windows Installer repairs; see Application Resiliency: Unlock the Hidden Features of Windows Installer.
[Dual boot of Windows and Linux (known issue)] Linux might fail to start up when you turn on dual-boot setup for Windows and Linux on your device. The error message is, “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.” See the full guidance in CVE-2022-2601 and CVE-2023-40547.

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 September 2024 Security Updates.

Windows 10 servicing stack update (KB5043935) - 19044.4892 and 19045.4892

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.

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.	After further investigation, we concluded this issue has very limited or no impact for this Windows version. If you encounter this issue on your device, please contact Windows support for help
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 this update, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’. Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues. If you are observing the ‘svchost.exe_AppXSvc’ faulting application name in your application event logs, please apply the Known Issue Rollback (KIR) mentioned in the resolution section before trying to troubleshoot other symptoms.	This issue is addressed in KB5045594.
After installing this update, or subsequent updates, you might experience an extended black screen that stays between 10 to 30 mins when you login to Azure Virtual Desktop (AVD). Additional symptoms you might experience include: Failures related to single sign-on (SSO) experience on Office applications such as Outlook and Teams, which could prevent you from connecting to backend services or synchronizing data. Office apps display losing network connectivity even though other applications, such as Edge, retain intranet and internet access. This issue is caused by a deadlock in the interactions between the Azure Active Directory (AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service. You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops. Please note that this issue is different from the scenario where the AppX Deployment Service (AppxSvc) was in an invalid state, causing a black screen. That issue was resolved with Windows updates released on October 22, 2024 (KB5045594), and later.	We are investigating the issue and provide an update where more information is available.

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.

After further investigation, we concluded this issue has very limited or no impact for this Windows version.

If you encounter this issue on your device, please contact Windows support for help

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 this update, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’.

Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues. If you are observing the ‘svchost.exe_AppXSvc’ faulting application name in your application event logs, please apply the Known Issue Rollback (KIR) mentioned in the resolution section before trying to troubleshoot other symptoms.

This issue is addressed in KB5045594.

After installing this update, or subsequent updates, you might experience an extended black screen that stays between 10 to 30 mins when you login to Azure Virtual Desktop (AVD). Additional symptoms you might experience include:

Failures related to single sign-on (SSO) experience on Office applications such as Outlook and Teams, which could prevent you from connecting to backend services or synchronizing data.
Office apps display losing network connectivity even though other applications, such as Edge, retain intranet and internet access.

This issue is caused by a deadlock in the interactions between the Azure Active Directory (AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service. You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.

Please note that this issue is different from the scenario where the AppX Deployment Service (AppxSvc) was in an invalid state, causing a black screen. That issue was resolved with Windows updates released on October 22, 2024 (KB5045594), and later.

We are investigating the issue and provide an update where more information is available.

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:

Based on your installation scenario, choose one of the following:

For offline OS image servicing:

If your image does not have the March 22, 2022 (KB5011543) or later LCU, you must install the special standalone May 10, 2022 SSU (KB5014032) 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.

Install this update

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

Windows Update Business Catalog Server 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: Windows 10, version 1903 and later

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 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 that are provided in this update, download the file information for cumulative update 5043064.

For a list of the files that are provided in the servicing stack update, download the file information for the SSU (KB5043935) - versions 19044.4892 and 19045.4892.

September 10, 2024—KB5043064 (OS Builds 19044.4894 and 19045.4894)

Highlights

Improvements

Windows 10 servicing stack update (KB5043935) - 19044.4892 and 19045.4892

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!

Highlights

Improvements

Windows 10, version 22H2

Windows 10, version 21H2 editions: Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021

Windows 10 servicing stack update (KB5043935) - 19044.4892 and 19045.4892

Known issues in this update

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!