Table of Contents
Why does the latest Windows update keep asking for admin rights?
You might have noticed a disruption in your workflow recently. Users launching applications like AutoCAD, Civil 3D, or SAP are suddenly facing User Account Control (UAC) prompts. These prompts demand administrator credentials. This behavior blocks standard users. The issue stems from the August 12, 2025 security updates for Windows. Microsoft confirmed this friction affects various software packages relying on the Windows Installer (MSI) for self-repair processes.
The Cause: Closing CVE-2025-50173
This change was intentional. Microsoft released the August update (KB5063878) to fix a critical vulnerability tracked as CVE-2025-50173. This flaw involved weak authentication within the Windows Installer. Attackers could exploit this weakness. They could escalate local privileges to the SYSTEM level during MSI repair operations. To close this gap, the update enforced strict UAC verification. It requires explicit administrative approval for any MSI repair action, even those running in a user context.
The Fix Timeline: From Broken to Resolved
Microsoft refined this security enforcement over three months.
August 2025
The initial security patch (KB5063878) applied a blanket restriction. All MSI repairs triggered UAC prompts.
September 2025
Microsoft released an adjustment (KB5065426). This update limited UAC prompts. Windows only requested credentials if the specific MSI file contained an elevated custom action.
October 2025
A preview update further optimized the detection logic. The system now checks if the repair process actually executes that custom action.
Final Resolution: Install the November Updates
The issue is resolved. Microsoft updated their support documentation on November 26, 2025. The latest cumulative updates incorporate the refined logic. Applications that do not perform advanced custom actions—such as standard AutoCAD installations—will no longer trigger UAC prompts. You should deploy the November 2025 updates immediately. This restores standard user functionality while maintaining the security patch for CVE-2025-50173.
Advisor Note: Avoid Dangerous Workarounds
You may find older forum posts suggesting a registry edit. Some users recommend setting DisableLUAInRepair to 1. Do not do this. This setting disables the security verification. It reopens the CVE-2025-50173 vulnerability on your network. Stick to the official Windows cumulative updates for a safe resolution.