The new known issue occurs not only in Windows 11 version 24H2 because the task manager shows the wrong number of running programs and processes. It has been confirmed that the bug is also present in the latest Windows 10 version 22H2 updates. But this time things are a little more serious.

Microsoft has acknowledged that after installing KB5043131, one of the latest Windows 10 security updates (released in September), users may experience issues running applications from non-administrator accounts. Microsoft says affected apps include Quick Assist, Microsoft Teams, Windows Narrator, and more. In fact, any application with UIAccess set to “true” will fail when launched from a non-administrator profile.

After installing the previous September 2024 update (KB5043131) released on or after September 24, 2024, you will be able to access Quick Assist, Microsoft Teams, Windows Narrator, etc. unless you are an administrator. You may notice that applications may not start. This issue can occur with any application that sets UIAccess=true when trying to run the application as a non-admin user. The uiAccess=true property in an application’s manifest file is used to request that the application be granted elevated privileges. Programs that use this feature are launched in a safe way as follows:

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

The bug affects systems running client versions of Windows 10 version 22H2. To alleviate the problem, Microsoft has implemented a robust known issue rollback feature that can roll back problematic update bits without requiring any action from the end user. However, the workaround may take up to 24 hours to propagate; Therefore, if it fails to launch certain applications, the best course of action is to reboot the system.

For managed devices, IT administrators must implement specific policies to revert changes that cause apps to stop working after the latest updates. The policy can be downloaded from this link. A permanent solution will be available in a future update.