In Windows 10, some programs could not be started, the unpleasant situation was eliminated. Problems have been occurring since the optional update KB5043131which was released on September 24. Of course, optional updates are only installed by a limited group of users. It was therefore worse when the problems were transferred to the mandatory October update for Windows 10 22H2.
Applications such as Quick Helper, Teams or Narratorin accounts that were not administrative. So they were ordinary user accounts with a limited set of permissions.
The mentioned programs have in common that there is an attribute in the manifest UIAccess marked as active. Thanks to it, the application can apply for higher permissions. This is allowed for applications that run from selected directories that are considered safe. We are talking, among other things, about the Program Files folder, where we typically install programs.
But the applications were supposed to run at the wrong level of integrity. While they should have set Integrity:Mediumyou can find them Integrity:Low. The Medium level is standard for regular user accounts without administrative privileges. You can reveal attribute values with a tool, for example Process Monitor od Sysinternals.
When you run the program with administrator privileges, the problem is less likely to occur. Microsoft does not describe why the situation occurred. All we know is that it was, and that the Redmond folks rolled back some of the changes introduced in the last two service updates for the Tens.
The rollback mechanism is used automatically and you don’t need to do anything. The application will speed up by restarting the computer. Microsoft will offer the corrected new code in one of the next updates for Windows 10.
Resources: Microsoft / Learn
Windows 10 Troubles: They’ve Done It Again!
Ah, Windows 10, the operating system that promises to make our lives easier yet acts more like your eccentric uncle at a family reunion—unpredictable, occasionally prone to embarrassing outbursts, and always somehow managing to break that one thing you need to work.
What’s the Fuss?
So, here we are, just minding our own business when an optional update, labeled KB5043131, swoops in on September 24, 2024, like the Grim Reaper for your favorite apps! Users were soon scratching their heads as applications like Quick Helper, Teams, and Narrator suddenly decided to take early retirement—especially for those poor souls on non-admin accounts. You know, the ones with all the limited permissions? Not quite a VIP experience!
The Ugliness of UIAccess
Now, if you think this is just another Saturday night at the comedy club, think again. Here’s the kicker: these applications had an attribute in their manifest—UIAccess marked as active. With all the confidence of a toddler with a crayon, this attribute allows the application to swoop in and ask for higher permissions. Just like how I try to reserve the best parking spaces for my decidedly unimpressive little hatchback. But alas, despite all that self-proclaimed importance, the applications ended up running at the wrong integrity level. I mean, come on, it’s supposed to be Integrity: Medium, not Integrity: Low. Talk about shooting yourself in the foot.
Back to Basics
For those who are well versed in Tech-ese, everyone’s going to start piecing this together. Applications should run at Medium integrity, which is the norm for regular user accounts—not exactly groundbreaking stuff. But here we are, and if you’re falling into that technical abyss of confusion, worry not! A little tool named Process Monitor from Sysinternals can help unveil attribute values. It’s like giving your application the ol’ CSI treatment. Just don’t expect the app to appear on a reality TV show anytime soon!
What Now?
Now, I know what you’re thinking: “How do I fix this?” Well, Microsoft, in their infinite wisdom (and maybe a touch of embarrassment), did not divulge the reasons behind this calamity. A good ol’ retreat! And while it might sound like a bad breakup line, Microsoft has rolled back some of the more recent changes. So, if your apps are currently playing hide-and-seek, here’s the silver lining: the rollback mechanism takes care of all that for you. Just give your computer a restart, and voilà—like magic, it’s back to business!
What’s Coming Next?
Fear not, friends! Assuming you can contain your panic, Microsoft promises to deliver that corrected code in one of the next updates. No, it’s not a mythical treasure, but it’s close enough for Windows users—you know what I mean. Patience, young padawans!
In Conclusion
So there you have it: another day in the wonderful world of Windows 10, where updates come to pass like poorly timed jokes at a stand-up show. If you’ve been affected, just remember: you’re not alone! Grab your popcorn, give your system a reboot, and prepare for the inevitable saga of software misadventure. And if anyone asks, just shrug and say, “Ah, it’s just Windows being Windows!”
For more information, check out Microsoft’s resource: Microsoft / Learn.
In Windows 10, users experienced significant issues with launching specific applications, a frustrating situation that has now been addressed. These problems emerged following the release of the optional update KB5043131 on September 24. Since optional updates are selectively installed, the situation deteriorated when these issues carried over to the mandatory October update for Windows 10 version 22H2.
The applications affected include crucial tools such as Quick Helper, Teams, and Narrator, particularly when run from non-administrative accounts. These accounts are typically limited in their permissions and access, making the issue more significant for average users.
Common among these applications is the manifest attribute UIAccess marked as active. This attribute allows the application to request elevated permissions necessary for proper functionality. Applications are permitted to gain these higher privileges when they are launched from designated directories deemed safe, such as the Program Files folder, which is the standard installation location for most software.
Unfortunately, it appears that these applications were executing with an improper integrity level. Instead of operating at the required Integrity:Medium level, they were oddly found running at Integrity:Low. The medium integrity level is conventionally assigned to regular user accounts that lack administrative rights. Users can utilize tools like Process Monitor od Sysinternals to check these attribute values.
For those running the applications with administrative privileges, the likelihood of encountering these difficulties was significantly less. Microsoft has not publicly disclosed the underlying reasons for this integrity issue. However, it’s been confirmed that the company has retracted certain changes introduced in its last two service updates for Windows 10. This rollback process happens automatically, requiring no user intervention. Restarting the computer will expedite the application of these changes, and Microsoft plans to deliver newly corrected code in a future update for Windows 10.
Resources: Microsoft / Learn
PerAppRuntimeBroker
S marked as active, which allows them to request higher permissions when run from designated safe directories like Program Files. However, due to a bug, these applications were launched with the incorrect integrity level. Instead of operating under the expected **Integrity: Medium**—which is standard for non-admin user accounts—they were instead placed under **Integrity: Low**. This discrepancy caused the applications to misbehave and fail to start correctly.
To troubleshoot this issue, users can utilize **Process Monitor**, a tool from Sysinternals that can help reveal the integrity level and other attribute values of the running applications. This tool acts as a diagnostic utility, shedding light on the backend processes and attributes that might be causing problems.
In response to the widespread outages, Microsoft recognized the error but did not provide specific reasons for the oversight. However, they initiated a rollback process for the problematic changes introduced in recent service updates, which you do not need to manually trigger. A simple restart of your system will initiate the rollback, helping to restore the functionality of the affected applications.
Looking ahead, Microsoft has indicated that a fix will be included in a future update, which should resolve the integrity level issue once and for all.
### Summary
In the hectic landscape of Windows 10 updates, users encountered frustrating application launch issues stemming from an optional update KB5043131 that unintentionally carried over into the mandatory October update. Key applications like Quick Helper, Teams, and Narrator faced integrity level problems when run from non-admin accounts, but Microsoft’s rollback solution aims to quickly address these issues, assuring users that a permanent fix is on the way. Patience and a little help from Process Monitor will get users back on track.
