In a recent announcement, Microsoft has acknowledged that the December 2025 Patch update (KB5071546) for Windows 10 introduces a significant bug affecting Message Queuing (MSMQ).This issue predominantly impacts businesses utilizing MSMQ, which is not typically enabled on consumer PCs or required by consumer applications.

For those unfamiliar with it, MSMQ, or Microsoft Message Queuing, facilitates the exchange of messages between software applications, allowing them to queue messages for processing at a later time. This functionality is critical for enterprise applications that rely on background processing tasks. When MSMQ malfunctions, it can stall these tasks, blocking the primary application or website from functioning correctly.
If your application depends on MSMQ for message queuing, you might experience difficulties accessing sites or applications hosted via Internet Information Services (IIS).In such a case, users may encounter the following error:
System. Messaging. MessageQueueException: Insufficient resources to perform operation.
Understanding the MSMQ Issues Arising from the December 2025 Update
According to Windows Latest, the December 2025 update (KB5071546) – applicable solely to ESU (Extended Security Update) enrolled systems – has altered MSMQ’s operational characteristics, particularly its security framework. Notably, permission settings for the folder where MSMQ stores its queue data have been modified. The relevant directory is:
C:\Windows\System32\MSMQ\storage
Post-update, the account which interacts with MSMQ requires write access to this folder. However, in many organizational setups, MSMQ is accessed through IIS application pool identities, such as LocalService or NetworkService, or via restricted service accounts that typically lack write permissions for this directory.
This lack of access results in MSMQ’s inability to create or update its message files, leading to operational failures.
In practical scenarios, users have reported that their queues become unresponsive, displaying an “inactive”status, thereby indicating potential issues. Efforts to restart the service or even the server, as well as attempts to reinstall MSMQ through Control Panel’s optional features, have proven ineffective remedies.
However, users have discovered that uninstalling Windows 10 KB5071546 through the Windows Update history allows MSMQ to resume normal functioning. Additionally, reports suggest that similar problems have emerged on Windows Server 2019, though testing on Windows Server 2022 has not replicated the issue.
One affected user shared their experience on a Microsoft forum, noting that the NTFS Security Descriptor changed from D:P to D:PAI, indicating modifications in the DACLs that might prevent users such as iis_iusrs or NetworkService from accessing crucial directories.
Another system administrator who applied KB5071544 on Windows Server 2019 also encountered related challenges, including messages about “insufficient disk space or memory.”They reported disruptions to their IIS applications requiring MSMQ functionality, which ceased to operate and generated 500 errors.
Official Recognition of the MSMQ Issue by Microsoft
Microsoft has confirmed its awareness of the MSMQ issues following the installation of Windows 10 KB5071546 and is currently investigating the situation. As stated in a support document, the company noted:
“After installing this update, users might face issues with the Message Queuing (MSMQ) functionality. This issue also impacts clustered MSMQ environments under load.”
It is important to note that this problem does not extend to Windows 11, raising questions about how such vulnerabilities can arise in an operating system under extended security support, especially given that Windows 10’s development for new features has ceased.
Steps to Resolve MSMQ Issues in Windows 10
If you encounter any MSMQ-related problems following this update, the recommended action is to uninstall Windows 10 KB5071546. Additionally, consider pausing future updates until Microsoft releases a fix.
Leave a Reply