[German]I'll summarize two known bugs in Windows 10 22H2 that Microsoft documented on October 22 and 30, 2024 and fixed or at least mitigated via KIR. It's about a black screen in Azure Virtual Desktop. And it's about apps that cannot be started by standard users. Here's what Microsoft has documented so far.
Advertising
Black screen for Azure Virtual Desktop login
The first bug was already documented on October 14, 2024 in the support articleAzure Virtual Desktop users might experience black screen during login by Microsoft in the Windows 10 22H2 Release Health Dashboard under "Known Issues" and marked as solved on October 22, 2024.
After installing the preview update KB5040525 from July 23, 2024 (or later updates), a login to Azure Virtual Desktop (AVD) may show a black screen. The user may also be able to log out of the account, but the black screen will persist afterwards and when reconnecting to AVD. The Event Viewer log indicates an application error with event ID:1000 for applications, which indicates an error in the application "svchost.exe_AppXSvc".
This issue was fixed by the preview update KB5045594 from October 22, 2024 (and subsequent updates) (see also Windows 10 22H2 Preview Update KB5045594 (October 22, 2024)).
Apps do not start for standard users
The second problem was documented in the "Known Issues" section of the Windows 10 22H2 Release Health Dashboard as of October 30, 2024 by Microsoft in the support article Apps that set UIAccess=true might fail to start for non-admin users.
After installing the preview update KB5043131 from September 24, 2024 (or later updates), applications such as Quick Assist, Microsoft Teams, Windows Narrator, etc. may fail to start under standard accounts. The problem can occur with any application that sets UIAccess=true and this app is to be run as a non-administrator.
The attribute uiAccess=true in the manifest file of an application is used to request or grant elevated privileges for the application. Applications that use this attribute start from a secure path, such as :
Advertising
%ProgramFiles% (and subdirectories)
%ProgramFiles(x86)% (and subdirectories for 64-bit Windows)
%systemroot%\system32
%systemroot%\syswow64 (for 64-bit Window)
In Procmon you can see that the application is running with the wrong integrity level (Integrity:Low instead of the expected Integrity:Medium). This problem should not occur if the application is run as administrator.
This problem is mitigated by Known Issue Rollback (KIR). In unmanaged environments, KIR should already have been applied. In managed environments, administrators must install the group policy:
Download for Windows 10, version 22H2 – Windows 10 20H2, 21H1, 21H2 and 22H2 KB5041582 241027_11353 Known Issue Rollback
Advertising
