Why Are AutoCAD, Firefox, SAP Apps Suddenly Asking for Admin Rights After the August 2025 Windows Update, and Is There an Easy Fix?

It can be confusing when your computer suddenly starts acting differently. You might have noticed a problem after installing the Windows security updates from August 2025. All of a sudden, programs that worked fine before are asking for an administrator password. This has been happening with software like AutoCAD, Mozilla Firefox, and even SAP applications.

If you see a pop-up asking for admin rights or an error message with the code 1730, you are not alone. This issue stems from changes Microsoft made to improve security. The good news is that there is an explanation for this behavior and a way to fix it. This guide will walk you through why this is happening and what you can do about it, using simple language and clear steps.

Understanding the Administrator Rights Problem

After the security updates released on August 12, 2025, many users found they could not open certain programs without administrator credentials. This issue specifically affects software that has been newly installed on a computer that already has the August updates. If you were using AutoCAD or Firefox before updating Windows, you likely will not experience this problem.

The problem occurs during the very first time you launch the program. A User Account Control (UAC) window appears, requesting an administrator’s username and password. If you close this window without entering credentials, the program will fail to open and may show an MSI error 1730.

The cause lies in security-hardening measures within the recent Windows updates. Some programs, when installed, have a process that runs on their first launch to finalize the setup. This is often a function of the Windows Installer (MSI). Before the update, this process would run in the background without issue. Now, the tightened security in Windows flags this action and demands administrator approval to proceed. It is an unintended side effect of making the system more secure.

Which Software and Windows Versions Are Affected?

This issue is not limited to a single program. However, it has been most widely reported with specific applications used by many businesses and individuals. The problem appears across several recent versions of Windows and Windows Server.

Commonly Affected Software:

• Autodesk AutoCAD: Versions from 2022 to 2026 have been confirmed to have this issue.
• Mozilla Firefox: The popular web browser is also affected.
• SAP: Users of SAP enterprise software have reported the same behavior.

Affected Windows Operating Systems

The problem is directly linked to the security updates released in August 2025. If your system has one of the following updates installed, you may face this issue:

Windows 11

• Versions 22H2/23H2 (Update KB5063875)
• Version 24H2 (Update KB5063878)

Windows 10

• Versions 21H2/22H2 (Update KB5063709)
• Version 2019 LTSC (Update KB5063877)

Windows Server

• Windows Server 2019
• Windows Server 2022
• It is presumed that Windows Server 2016 and 2025 are also impacted.

The common thread is that the software is often deployed through a distribution system in the user context, which is a typical practice in many corporate environments.

How to Fix the Issue with a Registry Edit

The most reliable workaround available involves making a small change to the Windows Registry. This change tells the Windows Installer not to trigger the administrator prompt for this specific type of first-launch task.

It is important to be very careful when editing the registry. An incorrect change can cause system instability. If you work for a company, it is best to consult your IT department before proceeding. If this is your personal computer, follow these steps exactly.

1. Open the Registry Editor. Press the Windows + R on your keyboard to open the Run dialog box. Type regedit into the box and press Enter or click OK. You may be asked for administrator permission to open the editor; grant it.
2. Navigate to the Installer Key. In the Registry Editor, use the folders on the left side to navigate to the following location. You can also copy and paste this path into the address bar at the top of the editor window:
   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
3. Create a New DWORD Value. Once you are in the “Installer” key, right-click on the empty white space in the right-hand panel. From the context menu, select New, and then choose DWORD (32-bit) Value.
4. Name the New Value. A new value will appear in the list, ready for you to name it. Type the following name exactly as it is written:
   DisableLUAInRepair
5. Modify the Value’s Data. Double-click on the DisableLUAInRepair value you just created. A small window will open. In the “Value data” field, enter the number 1. Click OK.
6. Restart Your Computer. Close the Registry Editor. After the change has been made, restart your computer to ensure the new setting takes effect.

After restarting, the affected programs like AutoCAD and Firefox should launch for the first time without prompting for administrator rights. This registry edit disables the repair function for Limited User Accounts (LUA), which is what the update was blocking.

Other Options and Future Solutions

Editing the registry might not be an option for everyone. There are other ways to think about the problem, though they come with their own trade-offs.

Uninstalling the Update

You could uninstall the specific August 2025 Windows update that is causing the problem. However, this is not recommended. These are security updates designed to protect your computer from threats. Removing them could leave your system vulnerable.

Run as Administrator (One Time)

In some cases, an administrator can log into the machine, launch the program once, and complete the initial setup. After that, the standard user may be able to open the application without any issues. This is not a practical solution for large organizations but may work for a single user.

Wait for an Official Fix

Microsoft and software vendors like Autodesk are aware of this issue. They are investigating the behavior to determine if a better, more permanent solution can be provided. It is possible that a future Windows update or a patch from the software makers will resolve this problem, making the registry workaround unnecessary. Keep your software and Windows system updated and watch for announcements from the vendors.