According to a notice published on the Windows Health Dashboard, Microsoft has confirmed that the routine security updates released in August are causing unexpected UAC (User Account Control) prompts and application installation issues across all supported versions of Windows.
The issue stems from a fix for CVE-2025-50173, a Windows Installer privilege escalation vulnerability. Due to weak authentication, an authenticated attacker could elevate privileges to SYSTEM.
To mitigate this flaw, Microsoft implemented a change requiring UAC prompts in certain scenarios, compelling users to enter administrator credentials before proceeding with specific actions.
These actions include using MSI repair commands, installing applications configured for a single user, and running Windows Installer during active installations. In each case, administrator credentials must be entered to continue.
However, this modification may block standard (non-administrator) users from installing routine software—or even from launching applications such as AutoDesk—which may now be intercepted by the system. Microsoft has acknowledged the problem and is preparing a fix, expected to be released later this month.
Affected systems include:
- All versions of Windows 11 (including LTSC)
- Windows 10 version 22H2
- Windows 10 LTSB 2015/2016
- Windows 10 LTSB 2019/2022
- Windows Server 2016/2019/2022/2025
- Windows Server 2012/2012 R2
Microsoft noted that when a standard user initiates an MSI repair operation for an application without a visible UI, the operation fails with an error message. For instance, when installing Office Professional Plus 2010 under standard user privileges, the configuration process fails with error code 1730.
The company suggests a temporary workaround: running applications with administrator privileges. The challenge, however, is that many enterprise users lack such rights, making it impractical to involve IT administrators for every operation.
For enterprise environments, Microsoft offers Known Issue Rollback (KIR) to revert the problematic changes. Organizations can work with their Microsoft support teams to obtain the KIR package and configure special Group Policy settings to mitigate the issue.
Home and personal users encountering this problem can resolve it simply by running the affected application with administrator privileges.
Related Posts:
- Stealthy Remcos RAT Campaign Uses PowerShell to Evade Antivirus Detection
- Beware of LinkedIn: Ducktail Malware’s Sneaky ZIP Attack Revealed
- ChatGPT and Sora Go Offline: OpenAI Scrambles to Restore Service Amid Global Outage
- Beware Katz Stealer: Sophisticated Malware-as-a-Service Steals Everything
- Phishing Campaign Delivers Winos 4.0: Keyloggers, UAC Bypass, and More