KB5045594

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 addressed in KB5046613. ​​

After installing this update, or subsequent updates, a small subset of Azure Virtual Desktop customers using multi-session hosts (AVD) may experience the following issues:  ​​​

• An extended 10-to-30-minute-long hang at a black screen following user logon.

• Office applications including Outlook and Teams experience single sign-on (SSO) failures, preventing users from connecting or synchronizing data.​​​​​​​

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.

This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue.