Microsoft has acknowledged that the security updates rolled out for Windows in August have led to a series of complications for many users, primarily manifesting as unexpected User Account Control (UAC) prompts. This issue is not confined to a specific version; rather, it spans across all supported iterations of Windows that received the August 2025 security update.
The scope of the problem is extensive, impacting:
- Client: Windows 11 (versions 24H2, 23H2, 22H2), Windows 10 (versions 22H2, 21H2, 1809, Enterprise LTSC 2019, Enterprise LTSC 2016, 1607, Enterprise 2015 LTSB)
- Server: Windows Server 2025, Windows Server 2022, Windows Server (version 1809), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
In a message posted on the Windows release health pages, Microsoft explained that the August 2025 Windows security update (KB5063878) included a security enhancement aimed at enforcing UAC prompts for administrator credentials during Windows Installer (MSI) repair and related operations. This change was implemented to address the security vulnerability identified as CVE-2025-50173.
A security improvement was included in the August 2025 Windows security update (KB5063878) and later updates to enforce the requirement that User Account Control (UAC) prompt for administrator credentials when performing Windows Installer (MSI) repair and related operations. This improvement addressed security vulnerability CVE-2025-50173.
While Microsoft has not disclosed the exact number of affected users, the company has outlined various scenarios that could trigger UAC prompts for non-administrative users. These include:
- Executing MSI repair commands (e.g., msiexec /fu).
- Launching Autodesk applications, such as AutoCAD, Civil 3D, and Inventor CAM, or installing an MSI file after the initial sign-in.
- Installing applications that require user-specific configurations.
- Running Windows Installer during Active Setup.
- Deploying packages via Configuration Manager that depend on user-specific “advertising” configurations.
- Enabling Secure Desktop.
For standard users attempting to run applications that initiate MSI repair operations without a user interface, the process will fail, often resulting in an error message. For instance, trying to install and run Office Professional Plus 2010 as a standard user will yield Error 1730 during configuration.
Microsoft does it again
At present, a definitive fix has not been made available. Microsoft has, however, assured users that they are working on a solution that will allow IT administrators to permit specific applications to perform MSI repair operations without triggering UAC prompts. This enhancement is expected to be included in a future Windows update, with further details to be provided as they become available.
In the meantime, Microsoft suggests a workaround: when feasible, users should run applications as an administrator. This can be done by right-clicking the app from the Start menu or search results and selecting “Run as administrator.”
When possible, run the app as an administrator. (From the Start menu or Search results, right-click the app and select Run as administrator.)
Additionally, for standard users who cannot run applications as administrators, IT admins can alleviate the issue by installing and configuring a special Group Policy using Known Issue Rollback (KIR) for the affected versions of Windows.
When standard users cannot run apps as an administrator, IT admins can mitigate this issue by installing and configuring a special Group Policy using Known Issue Rollback (KIR) for […] Windows Server 2025, Windows Server 2022, Windows 11, versions 22H2, 23H2, 24H2, Windows 10, versions 21H2, 22H2.
Users are encouraged to reach out to Microsoft Support for business-related inquiries regarding this issue.
Have you encountered difficulties with the latest Windows update? Your experiences and thoughts on Microsoft’s quality control regarding updates are welcome in the comments below.
Image credit: Alexey Novikov / Dreamstime.com
Microsoft fesses up to Windows update that caused UAC prompts
Microsoft has acknowledged that the security updates rolled out for Windows in August have led to a series of complications for many users, primarily manifesting as unexpected User Account Control (UAC) prompts. This issue is not confined to a specific version; rather, it spans across all supported iterations of Windows that received the August 2025 security update.
The scope of the problem is extensive, impacting:
In a message posted on the Windows release health pages, Microsoft explained that the August 2025 Windows security update (KB5063878) included a security enhancement aimed at enforcing UAC prompts for administrator credentials during Windows Installer (MSI) repair and related operations. This change was implemented to address the security vulnerability identified as CVE-2025-50173.
While Microsoft has not disclosed the exact number of affected users, the company has outlined various scenarios that could trigger UAC prompts for non-administrative users. These include:
For standard users attempting to run applications that initiate MSI repair operations without a user interface, the process will fail, often resulting in an error message. For instance, trying to install and run Office Professional Plus 2010 as a standard user will yield Error 1730 during configuration.
Microsoft does it again
At present, a definitive fix has not been made available. Microsoft has, however, assured users that they are working on a solution that will allow IT administrators to permit specific applications to perform MSI repair operations without triggering UAC prompts. This enhancement is expected to be included in a future Windows update, with further details to be provided as they become available.
In the meantime, Microsoft suggests a workaround: when feasible, users should run applications as an administrator. This can be done by right-clicking the app from the Start menu or search results and selecting “Run as administrator.”
Additionally, for standard users who cannot run applications as administrators, IT admins can alleviate the issue by installing and configuring a special Group Policy using Known Issue Rollback (KIR) for the affected versions of Windows.
Users are encouraged to reach out to Microsoft Support for business-related inquiries regarding this issue.
Have you encountered difficulties with the latest Windows update? Your experiences and thoughts on Microsoft’s quality control regarding updates are welcome in the comments below.
Image credit: Alexey Novikov / Dreamstime.com