October 8, 2024—KB5044273 (OS Builds 19044.5011 and 19045.5011)

Symptom

Workaround

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

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.