KB5041585 Causing serious problems for ordinary users.
The latest Windows 11 August 2025 security update (KB5041585), released on August 13, 2025, has created issues for users, especially non-admin users, who experience User Account Control (UAC) alerts appearing unexpectedly when running certain applications, including some apps that suddenly stop working.
According to a report from Tom’s Hardware This issue occurs in Windows 11 versions 23H2 and 22H2, with UAC, the Windows security system, repeatedly displaying a window asking for permission even if the user has not changed system settings, or is using an app that was previously allowed, such as Battle.net or a program that requires internal updates, which is very annoying, especially while playing games or watching media.
In addition, some users have found that certain applications, such as those that require access to system files or network settings, are not the same as those that require access to system files or network settings. Crashes after this update This issue is especially prevalent in users who do not have admin privileges, which can be caused by an error in the way KB5041585 handles application access and permission controls.
Microsoft acknowledged this issue through the Windows Release Health Dashboard and stated that KB5041585 may interfere with the operation of applications that require special permissions. Especially in environments that use standard user accounts. The company is currently reviewing and developing a fix, which is expected to be included in the next update in September 2025.
For a workaround, Microsoft recommends that users with admin privileges temporarily adjust the UAC setting to the lowest level via Control Panel > User Accounts > Change User Account Control settings, or uninstall KB5041585 via Settings > Windows Update > Update History > Uninstall Updates.
Affected users can follow for additional updates on the Windows Release Health Dashboard page or the Microsoft Support Community, and should check for future updates to permanently resolve this issue. origin
Origin: tomshardware
