The latest available Patch Tuesday (August 2025) updates for Windows 11 and Windows 10 have made quite an impact literally. There were reports of NVMe SSDs running into potentially fatal issues, which have since been denied by both Phison as well as Microsoft. KB5063878, the update that was said to be the root of the cause, in itself led to installation issues with 0x80240069 error.
So far, the Windows 10 August Patch did not spawn any major issues, though that is about to change as a new problem has been confirmed by Microsoft and this one impacts both Windows 11 as well as Windows 10. Server platforms are affected too.
The new bug is related to UAC (User Account Control) as Windows, after the August 2025 Patch, no longer allows non-administrator users to perform certain operations on the OS, including installation of some apps under certain scenarios. Microsoft gives the example of Office Professional Plus 2010 wherein it notes that trying to install it as a standard user will lead to failure "with Error 1730 during the configuration process." Thus, it is probably fair to say that the issue impacts a large number of users out there.
Microsoft notes that the issue is a result of a patch that was deployed with these updates as a means to address a Windows Installer (MSI) authentication vulnerability under CVE-2025-50173. In an entry on its Windows Health dashboard website, the company has described the problem in detail and highlighted the impacted scenarios:
.... after installing the August 2025 Windows security update and later updates, UAC prompts for administrator rights can appear for standard users in the following scenarios:
- Running MSI repair commands (such as msiexec /fu).
- Launching Autodesk applications, including some versions of AutoCAD, Civil 3D and Inventor CAM, or when installing an MSI file after a user signs into the app for the first time.
- Installing applications that configure themselves per user.
- Running Windows Installer during Active Setup.
- Deploying packages via Manager Configuration Manager (ConfigMgr) that rely on user-specific "advertising" configurations.
- Enabling Secure Desktop.
The workaround is fairly simple given the nature of the bug: run the app as an administrator, ie, with elevated privileges. In case that option is not available, Microsoft says that admins can resort to mitigate it by installing and configuring a special Group Policy using Known Issue Rollback (KIR).
Hopefully with the Windows Update deployment improvements Microsoft is adding next year, these issues would be caught before they are released widely.
You can find the issue entry here on Microsoft's official Windows Health dashboard website.
7 Comments
Load the comments and join the conversation!
Read the comments, ask the editors questions, show respect and join the conversation.