This month’s extended security update for Windows 10 has caused issues with Message Queuing (MSMQ), a service commonly used in enterprise environments to handle background processing and asynchronous tasks.
Microsoft confirmed that it has identified the root cause of the problem and has released a fix through an out-of-band (OOB) update, labeled KB5074976. The update is intended specifically to restore MSMQ functionality for affected systems.
Unlike regular monthly patches, this out-of-band release is not available through Windows Update or WSUS. Instead, it is being distributed exclusively via the Microsoft Update Catalog. Organizations experiencing MSMQ related disruptions are advised to manually download and install the update to resolve the issue.
What Caused the MSMQ Issues in Windows 10?
Following the installation of the December 9, 2025 updates for Windows 10, some organizations began reporting problems with Message Queuing (MSMQ) functionality.
According to Microsoft, the issue appears to stem from recent security related changes made to MSMQ. While intended to strengthen protection, one of these modifications unintentionally disrupted how the service operates in certain environments.
Affected systems may experience a range of errors, including inactive message queues, warnings about insufficient resources, applications failing to write to queues, errors stating that messages cannot be created, or alerts indicating a lack of disk space or memory. Microsoft’s internal testing also confirmed that the problem can impact clustered MSMQ deployments, particularly when operating under heavy load.
The company emphasized that the issue is unlikely to affect individual users running Windows 10 Home or Pro on personal devices. Instead, it primarily impacts enterprise and managed IT environments where MSMQ is actively used.
Microsoft added that the out of band fix is intended only for systems enrolled in the Windows 10 Extended Security Updates (ESU) program that are actively experiencing MSMQ related issues. Devices not affected by the problem are not expected to require the update.
Comments
Post a Comment