Microsoft has confirmed a pressing issue impacting Windows 10 users that restricts certain applications from launching when initiated by non-admin users. This challenge primarily arises for systems updated with the latest preview build.
Issue Overview
The core of the problem lies in Windows 10 installations with the KB5043131 update. Microsoft identifies several applications, notably:
- Quick Assist
- Microsoft Teams
- Windows Narrator
- Other related applications
What’s Going Wrong?
Only apps launching from “secure paths”that require elevated privileges (marked with uiAccess=true) are impacted. This problem manifests solely for users without admin rights, although needless to say, admins can also encounter the issue under certain conditions.
Secure Path Locations
The following directory paths are categorized as secure in Windows 10, and any applications launched from these folders can trigger the problem:
- %ProgramFiles% (and all corresponding subdirectories)
- %ProgramFiles(x86)% (including subdirectories for 64-bit applications)
- %systemroot%\system32
- %systemroot%\syswow64 (specifically for 64-bit systems)
Applications launched from any of these paths that request elevated access will experience launch failures.
Monitoring the Situation
Administrators can track the situation using the Procmon tool. By checking if the app runs at a low integrity level instead of medium, they can diagnose the extent of the problem.
Resolution Steps
To remedy this issue, Microsoft has enacted a Known Issue Rollback (KIR), which involves removing the problematic code affecting app launches. Notably:
- This fix is automatically applied to non-managed devices, including typical consumer systems.
- For unmonitored business devices, users should expect to receive the resolution within the next 24 hours.
- Managed devices, however, require a specific policy setting to apply the fix. More details can be found in the official Microsoft policy guide.
Staying informed on these updates is essential for ensuring seamless application functionality across Windows 10 systems.
Additional Insights
1. What should I do if my apps are still not launching after the rollback?
If you’re experiencing persistent issues, ensure that your device has received the latest updates from Microsoft and verify that any necessary policies for managed devices are correctly configured.
2. How can I check if my Windows 10 version is affected?
You can check if you’re running KB5043131 by navigating to Settings > Update & Security > Windows Update > View update history to confirm the details of installed updates.
3. Is there a way to manually launch the affected applications?
While affected apps may not launch using standard methods, running them with admin privileges may bypass the issue. Right-click the app and select Run as administrator as a temporary workaround.
Leave a Reply