Microsoft’s December 2025 safety replace has launched a major compatibility challenge affecting Message Queuing (MSMQ) performance throughout Home windows Server and shopper environments.
The problematic replace, recognized as KB5071546 (OS Construct 19045.6691), was launched on December 9, 2025, and has already impacted organizations counting on MSMQ for inter-application communication, notably in Web Data Providers (IIS) deployments.
Organizations experiencing the problem are reporting a number of important failures affecting their messaging infrastructure.
MSMQ queues have gotten inactive, inflicting IIS websites to fail with “Inadequate sources to carry out operation” errors.
Functions trying to put in writing to message queues encounter failures, whereas system logs show deceptive error messages referencing inadequate disk house or reminiscence regardless of ample sources being obtainable.
Essentially the most regarding symptom includes the era of errors akin to “The message file ‘C:WindowsSystem32msmqstorage*.mq’ can’t be created” when trying to create message recordsdata.
Clustered MSMQ environments working below heavy load seem notably susceptible to those disruptions, probably affecting important enterprise operations throughout a number of servers concurrently.
Root Trigger Evaluation
Microsoft has recognized the foundation trigger as latest adjustments to the MSMQ safety mannequin and NTFS permissions utilized to the C:WindowsSystem32MSMQstorage folder.
The replace carried out stricter permission controls, now requiring write entry to this listing for traditional MSMQ operations.
Nevertheless, this folder stays restricted to directors by default, making a elementary entry battle that forestalls functions from writing messages to queues.
This permission mismatch represents a major oversight within the safety replace’s deployment, because it breaks present performance with out offering clear mitigation paths for affected customers.
The difficulty impacts Home windows 10 model 22H2 and Home windows Server environments together with Home windows Server 2019 and Home windows Server 2016.
Microsoft confirmed the problem on December 12, 2025, at 17:13 PT, indicating consciousness of the issue shortly after person experiences surfaced.
Microsoft is actively investigating the problem and has dedicated to offering up to date info because the investigation progresses.
Organizations experiencing MSMQ failures ought to consider short-term workarounds whereas awaiting an official patch.
Directors ought to monitor Microsoft’s safety replace portal for decision particulars and patch availability.
The incident underscores the significance of complete testing earlier than deploying safety updates in manufacturing environments, notably for methods counting on specialised messaging infrastructure.
Observe us on Google Information, LinkedIn, and X to Get Immediate Updates and Set GBH as a Most well-liked Supply in Google.
