Why is the latest Windows update creating UAC problem and what can you do to fix it?

Is there a reliable way to stop the constant Windows admin prompts without removing the essential August 2025 security patch?

A recent Windows update from August 2025 has created a new problem for many users. You might see your computer asking for an administrator password more often than it should. This pop-up is called the User Account Control, or UAC, and it is appearing unexpectedly when you try to open certain programs. This issue happened because Microsoft tried to fix one security problem but accidentally created a different one. It affects nearly all modern versions of Windows, including Windows 10 and Windows 11.

The good news is that Microsoft knows about this problem. There are temporary ways to get around it while everyone waits for a permanent fix. This guide will explain in simple terms what is happening, who is affected, and what you can do about it right now.

Understanding the UAC Prompt Problem

The problem centers on the User Account Control (UAC) feature in Windows. UAC is a security guard for your computer. Its job is to protect your system from changes that could be harmful. When a program wants to make an important change, like installing software, UAC steps in and asks for your permission. It shows a pop-up window asking you to click “Yes” if you are an administrator. This stops unauthorized software from making changes without you knowing.

Normally, UAC only appears for major actions. But after the August 2025 security update, it started showing up for routine tasks. This happens most often when you open a program using a special kind of shortcut. These shortcuts, known as “advertised shortcuts,” are designed to run a quick health check or repair on the application before it starts. Before the update, these checks happened quietly in the background. Now, the update forces these small checks to ask for administrator permission, which is why you see the UAC pop-up.

This change came from Microsoft’s attempt to fix a serious security flaw. The flaw, tracked as CVE-2025-50173, could have allowed an attacker who already had limited access to a computer to gain full control. To close this security hole, Microsoft made the system that installs and repairs programs, called Windows Installer (MSI), much stricter. Unfortunately, this strictness is what now causes the constant UAC prompts for everyday programs.

Which Systems Are Affected?

This issue is widespread and impacts most currently supported versions of Windows. If your computer received the security updates released on or after August 12, 2025, it is likely affected.

• Windows 11: Versions 24H2 (KB5063878), 23H2 (KB5063875), and 22H2 (KB5063875).
• Windows 10: Version 22H2 and Enterprise LTSC 2021 (KB5063709).
• Windows Server: All currently supported versions, including Server 2016, 2019, 2022, and 2025.

Systems that are no longer supported, like the home version of Windows 10 21H2, are not affected because they did not receive the update. The problem appears on personal computers, laptops, and business workstations alike.

Symptoms and Error Messages

The most obvious sign of this problem is the unexpected UAC prompt. You might click on a program icon you use every day, and suddenly a window appears asking for administrator rights. If you are using a standard user account without administrator powers, you will be asked for an admin password.

Launching Specific Apps

The issue is very common with applications from Autodesk, such as AutoCAD, Civil 3D, and Inventor CAM. Users of older software, like Microsoft Office 2010, have also reported that the program fails to configure itself after installation.

Application Failures

If a standard user clicks “No” or cannot provide an administrator password at the UAC prompt, the application will fail to start.

Error Code 1730

When the process fails, you might see an error message. The most common one is Windows Installer error 1730. The message says, “You must be an Administrator to remove this application.” This message is confusing because you are trying to open a program, not remove it. It appears because the underlying repair action failed.

Users and IT administrators have shared their experiences online, describing the update as disruptive. Many have noted that their help desk phone lines have been busy with calls from confused users who can no longer access their work applications.

Solutions and Mitigation Strategies

Microsoft has acknowledged the issue and is working on a permanent solution. In the meantime, there are several workarounds you can use. The right choice depends on whether you are a home user or managing computers for a business.

Immediate Workaround for All Users

The simplest, most direct way to open an affected program is to give it the administrator rights it is asking for.

1. Right-click on the application’s shortcut.
2. From the menu, select Run as administrator.
3. If the UAC prompt appears, click “Yes.”

While this works, it is not an ideal long-term solution. Granting administrator rights to applications all the time goes against security best practices. It should only be used as a temporary measure for trusted programs you need to access.

Known Issue Rollback (KIR) for Businesses

For businesses and larger organizations, Microsoft has provided a more controlled solution called Known Issue Rollback (KIR). KIR is like a targeted undo button that lets an IT administrator turn off the specific change that caused the problem without uninstalling the entire security update.

What It Is

KIR is delivered through a special Group Policy file. This file tells the affected computers to go back to the old, pre-update behavior for the Windows Installer.

How to Get It

IT administrators can download the necessary KIR policy files directly from Microsoft’s website for their specific version of Windows. You do not need to contact Microsoft support to get them.

Deployment

These files can be deployed across the organization using standard management tools like Group Policy or Microsoft Intune. Once applied, the policy takes effect after the computers restart. This fixes the UAC problem while keeping the rest of the security update in place.

Uninstalling the Update (Use with Caution)

Another option is to completely remove the problematic update from your system. This will make the UAC prompts go away, but it comes with a significant risk. Uninstalling the update also removes the security fixes it contains, including the patch for the original vulnerability, leaving your computer exposed.

This method should be considered a last resort. If you must do it, you can use a command-line tool.

1. Open the Command Prompt or PowerShell as an administrator.
2. Use the DISM (Deployment Image Servicing and Management) tool to remove the package. The command looks like this: dism /online /remove-package /packagename:<package_name>. You need to replace <package_name> with the exact name of the update package for your system.
3. You must pause Windows updates afterward to prevent the system from automatically reinstalling the update.

This approach is complex and requires careful testing. Most users and organizations are better off using the “Run as administrator” method or the KIR policy.

The Bigger Picture and Future Fix

This situation highlights a constant challenge in the world of technology: the balance between security and compatibility. In its effort to make Windows more secure, Microsoft disrupted workflows that people have relied on for years. The company is now working on a better, more permanent fix.

The plan is to release another Windows update in the future. This update will give IT administrators more granular control. They will be able to create a list of trusted applications that are allowed to perform repair operations without triggering a UAC prompt. This would solve the problem for legitimate software while still blocking potentially malicious actions. However, Microsoft has not yet announced a specific date for this future update.

This UAC bug was not the only problem with the August 2025 updates. Users also reported performance issues with NDI video streaming and failures with the Windows reset and recovery tools. Together, these issues have created a significant burden for IT departments, who must spend time diagnosing and managing the fallout from the patches. For now, administrators and users must rely on the temporary workarounds while waiting for a complete resolution from Microsoft.