Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Find information on recently resolved issues for Windows Server 2012. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Message Queuing (MSMQ) might fail with the December 2025 Windows security update This issue causes MSMQ operations to fail unless users are granted full administrative privileges on the system. | KB5071505 2025-12-09 | Resolved KB5074980 | 2025-12-18 14:00 PT |
| Non-admins might receive unexpected UAC prompts when doing MSI repair operations This issue can affect apps that use Windows Installer (MSI), such as Autodesk AutoCAD or Office Professional Plus 2010. | KB5063906 2025-08-12 | Resolved KB5065768 | 2025-09-09 10:00 PT |
| Apps that use Active Directory Forest Trust Information might have issues Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, or you might receive an error. | KB5009586 2022-01-11 | Resolved | 2025-08-29 14:19 PT |
Issue details
December 2025
Message Queuing (MSMQ) might fail with the December 2025 Windows security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5074980 | KB5071505 2025-12-09 | Resolved: 2025-12-18, 14:00 PT Opened: 2025-12-12, 17:13 PT |
After installing the December 2025 Windows security update (KB5071505), users might face issues with the Message Queuing (MSMQ) functionality. This issue also impacts clustered MSMQ environments under load. Due to this issue, users might encounter the following symptoms:
- MSMQ queues becoming inactive
- IIS sites failing with “Insufficient resources to perform operation” errors
- Applications unable to write to queues
- Errors such as "The message file 'C:\Windows\System32\msmq\storage*.mq' cannot be created” when creating message files
- Misleading logs like “There is insufficient disk space or memory", despite sufficient disk space and memory being available
This issue is caused by the recent changes introduced to the MSMQ security model and NTFS permissions on C:\Windows\System32\MSMQ\storage folder. MSMQ users now require write access to this folder, which is normally restricted to administrators. As a result, attempts to send messages via MSMQ APIs might fail with resource errors.
Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue. This issue primarily affects enterprise or managed IT environments.
Resolution: This issue was resolved by the Windows out-of-band update, released December 18, 2025 (KB5074980), which is available via the Microsoft Update Catalog, and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.
Affected versions:
- Client: Windows 10, version 22H2, Windows 10, version 21H2, Windows 10, version 1809, Windows 10, version 1607
- Server: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
September 2025
Non-admins might receive unexpected UAC prompts when doing MSI repair operations
| Status | Originating update | History |
|---|---|---|
| Resolved KB5065768 | KB5063906 2025-08-12 | Resolved: 2025-09-09, 10:00 PT Opened: 2025-09-03, 14:28 PT |
(Updated 11/26/25: Additional improvements were added to the Resolution section.)
A security improvement was included in the August 2025 Windows security update (KB5063906) 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.
As a result, 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.
If a standard user runs an app that initiates an MSI repair operation without displaying UI, it will fail with an error message. For example, installing and running Office Professional Plus 2010 as a standard user will fail with Error 1730 during the configuration process.
Resolution:
After installing the September 2025 Windows security update (KB5065768) or later updates, UAC prompts will only be required during MSI repair operations if the target MSI file contains an elevated custom action. This requirement is further refined after installing Windows updates released on and after November 11, 2025, so that UAC prompts will only be required if the elevated custom actions are executed during the repair flow.
Installing the latest Windows updates will resolve this issue for apps that do not execute such elevated custom actions, such as Autodesk AutoCAD.
Since UAC prompts will still be required for apps that perform custom actions, after installing the September 2025 update, IT admins will have access to a workaround to disable UAC prompts for specific apps by adding MSI files to an allowlist. For details, see the KB article: Unexpected UAC prompts when running MSI repair operations after installing the August 2025 Windows security update.
A Group Policy had previously been made available from Microsoft’s Support for business using Known Issue Rollback (KIR) to work around this issue. Organizations no longer need to install and configure this Group Policy to address this issue.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 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; Windows Server 2008 R2; Windows Server 2008 SP2
February 2022
Apps that use Active Directory Forest Trust Information might have issues
| Status | Originating update | History |
|---|---|---|
| Resolved | KB5009586 2022-01-11 | Resolved: 2025-08-29, 14:19 PT Opened: 2022-02-04, 16:57 PT |
After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API.
Resolution: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.
For instructions on how to install this update for your operating system, see the KB articles listed below:
- Windows Server 2022:
- .NET Framework 4.8 KB5011258
- Windows Server 2019:
- Windows Server 2016:
- Windows Server 2012 R2:
- Windows Server 2012:
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.