FIX Attribute with UIAccess True Apps Fail to Launch for Non-Admin Users Issue

Discuss FIX Attribute with UIAccess True Apps Fail to Launch for Non-Admin Users Issue. The UIAccess=true attribute in an app’s settings requests higher permissions for the app.

This is very important for every app in our operating system. Sometimes, these uiAccess=true will have issues with non-administrative users. This will raise problems, such as preventing apps from launching. Microsoft knew about this issue and would suggest some tips to solve it.

Applications with `UIAccess=true` can work with protected sections of the Windows system, such as the Windows shell, desktop, and others. UIAccess=true is an essential and powerful option for the apps section, and it will be one of the best options for users for system-level tasks.

This issue happens because apps with UIAccess=true in their settings need extra permissions to run correctly. In this post, we can look at an overview of apps that set UIAccess=true and might fail to start for non-admin users.

Sign up to get the best of How To Manage Devices straight to your inbox!

FIX Attribute with UIAccess True Apps Fail to Launch for Non-Admin Users Issue

Above, we discussed an overall view on this topic of pps that set UIAccess=true might fail to start for non-admin users. This is a crucial issue for non-admin users, and the non-admin users must be launched from a secure location.

• According to Microsoft, this issue is caused by installing the September 2024 preview update KB5043131.
• If you are a non-admin user, you should know that Quick Assist, Microsoft Teams, and Windows Narrator are undergoing some changes.
• After the September 2024 preview update, Quick Assist, Microsoft Teams, and Windows Narrator will not start.

• KB5046613 Windows 10 November 2024 Patch and 4 Zero Day Vulnerabilities 91 Flaws
• Windows 10 Version Numbers Build Numbers Major Minor Build Rev
• Updated Windows 10 End-of-Life Dates
  

Procmon After this Issue

As you know, Procmon (Process Monitor) is a critical monitoring tool. After this issue, if you install this tool into your system, you may notice that it runs at the wrong security level. So, we must understand that if you run the application with administrator power, the issue will happen to the tool at a very low level.

Resolution by Microsoft

This issue was fixed in the Windows updates released on November 12, 2024, KB5046613. According to Microsoft, you can fix the problem and ensure your device is updated to the latest security patch. For an enterprise, If you’ve installed the update from November 12, 2024 (KB5046613) or later, you don’t need to use a Known Issue Rollback (KIR) or special Group Policy to fix this issue.

• For an IT Admin– You must Apply the special Group Policy under Computer Configuration > Administrative Templates.
• Then, you can restart your device, and the GPO setting will applied to your device.

Note: The screenshot below shows how known Issue Rollback works for the end user.

Need Further Assistance or Have Technical Questions?

Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.

Author

Anoop C Nair has been Microsoft MVP from 2015 onwards for ten consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and leader of the Local User Group Community. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.