October 22, 2024—KB5045594 (OS Build 19045.5073) Preview

^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

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

[Start menu] New! This update starts the roll out of the new account manager on the Start menu. The new design makes it easy to view your account and access account settings. To change to a different user, select the ellipses (...) next to Sign out. The Lock command is now on the power menu. Note This change might not be available to all users because it will roll out gradually.
[ Multi-Function Printer (MFP) ]
- Fixed: When you use a USB cable to connect to it, it prints specific network command text when you do want it to.
- Fixed: A scanner driver fails to install when you use a USB cable to connect to an MFP.

Improvements

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

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

[vmswitch] Fixed: A vmswitch triggers a stop error. This occurs when you use Load Balancing and Failover (LBFO) teaming with two virtual switches on a virtual machine (VM). In this case, one virtual switch uses single root Input/Output virtualization (SR-IOV).
[Upgrade to Windows 11] Fixed: A race condition causes stop error 0x3B. This might occur when you upgrade from Windows 10 to Windows 11.
[Product activation phone numbers] Fixed: This adds new phone numbers for several regions.
[Country and Operator Settings Asset (COSA)] Fixed: This update brings profiles up to date for certain mobile operators.
[WebView2 apps] Fixed: They do not detect input from Xbox 360 and Bluetooth controllers.
[Azure Virtual Desktop (AVD) (known issue)] Fixed: You might see a black screen when you sign in to AVD. You might also notice that you cannot sign out of your account. The black screen persists even after you disconnect and reconnect to AVD. The application event log displays Event ID:1000, which indicates a fault in svchost.exe_AppXSvc.

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

Windows 10 servicing stack update (KB5046823) - 19045.5071

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 or later, you might observe that apps such as Quick Assist, Microsoft Teams, Windows Narrator, etc. might fail to start if you are a non-admin user. You might experience this issue on any app that sets UIAccess=true while trying to run the app as a non-admin user. The uiAccess=true attribute in an application's manifest file is used to request that the application be granted higher privileges. Apps using this attribute launch from a secure path, such as: %ProgramFiles% (including subdirectories) %ProgramFiles(x86)% (including subdirectories for 64-bit versions of Windows) %systemroot%\system32 %systemroot%\syswow64 (for 64-bit versions of Windows) If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator.	This issue is mitigated using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices and business devices that are not managed by IT departments. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT administrators can resolve it by applying the KIR mentioned in the resolution section of Windows release health dashboard for this issue.
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 or later, you might observe that apps such as Quick Assist, Microsoft Teams, Windows Narrator, etc. might fail to start if you are a non-admin user. You might experience this issue on any app that sets UIAccess=true while trying to run the app as a non-admin user. The uiAccess=true attribute in an application's manifest file is used to request that the application be granted higher privileges. Apps using this attribute launch from a secure path, such as:

%ProgramFiles% (including subdirectories)
%ProgramFiles(x86)% (including subdirectories for 64-bit versions of Windows)
%systemroot%\system32
%systemroot%\syswow64 (for 64-bit versions of Windows)

If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator.

This issue is mitigated using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices and business devices that are not managed by IT departments. Restarting your Windows device might help the resolution apply to your device faster.

For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT administrators can resolve it by applying the KIR mentioned in the resolution section of Windows release health dashboard for this issue.

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 July 25, 2023 (KB5028244) or later LCU, you must install the special standalone Oct 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.

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	Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you will find the link to download and install the update.

Available	Next Step
No	None. These changes will be included in the next security update to Windows Update for Business.

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

Available	Next Step
No	You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions.

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

For a list of the files that are provided in the servicing stack update, download the file information for the SSU (KB5046823) - version 19045.5071.

October 22, 2024—KB5045594 (OS Build 19045.5073) Preview

Highlights

Improvements

Windows 10 servicing stack update (KB5046823) - 19045.5071

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!

Highlights

​​​​​​​Improvements

Windows 10 servicing stack update (KB5046823) - 19045.5071

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!

Improvements

Known issues in this update