Microsoft has recently published documentation confirming that installing the extended security update KB5071546 on Windows 10 can cause failures in Microsoft Message Queuing (MSMQ). MSMQ is a service primarily used in enterprise environments; it is typically neither installed nor enabled on personal computers, and most consumer-grade applications do not depend on it.
The MSMQ component allows applications or services to send messages to queues, where they are processed asynchronously by other applications or services. In enterprise systems, message queues are commonly used to orchestrate background tasks. As a result, when the MSMQ service malfunctions, background processing can grind to a halt, ultimately blocking the primary application or website.
For example, if an enterprise application relies on MSMQ and the service becomes unavailable, organizations may find themselves unable to access applications or websites hosted on Microsoft IIS, which often serves as the local hosting platform. While not all enterprise applications depend on message queuing, the current issue arises after installing the December 2025 updates on Windows 10 or Windows Server 2019, where attempts to use MSMQ result in the following error:
System.Messaging.MessageQueueException: Insufficient resources to perform operation.
The root cause lies in a change introduced by the update: accounts using MSMQ now require write permissions to the message storage directory. In many real-world deployments, MSMQ runs under IIS application pool identities, LocalService, or NetworkService accounts, which frequently lack such write access by default.
When MSMQ is unable to create or write message files in its storage directory, the service fails to connect properly. Restarting MSMQ or even rebooting the server does not resolve the issue, as the underlying permission problem remains unaddressed.
In its support documentation, Microsoft states:
“After installing this update, users might face issues with the Message Queuing (MSMQ) functionality. This issue also impacts clustered MSMQ environments under load […] This issue is caused by the recent changes introduced to the MSMQ security model and NTFS permissions on the 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.”
At present, Microsoft has not provided a workaround. Consequently, organizations are effectively left with a single option: uninstall the update to restore functionality, then wait for Microsoft to release a corrective update in the following month before reinstalling the latest patches.