TL;DR
A December 2025 Microsoft security update changed MSMQ folder permissions and has caused message queuing to fail on a range of older Windows 10 and Windows Server releases. Microsoft says the issue stems from tightened NTFS permissions and recommends contacting support; some organisations report uninstalling the update restores service but removes the security fixes.
What happened
Following the December 2025 security update, Microsoft confirmed that Message Queuing (MSMQ) can fail on certain Windows 10 and older Windows Server systems. Affected environments report queues going inactive, IIS sites returning "Insufficient resources to perform operation" errors, and applications unable to write to queues. Event logs are frequently filled with misleading messages indicating insufficient disk space or memory despite ample resources. Microsoft attributes the failures to recent changes in the MSMQ security model that require MSMQ users to have write access to the C:WindowsSystem32MSMQstorage folder — a directory typically limited to administrators. The change can also affect clustered MSMQ under load. Microsoft advised administrators to contact its support channel for workarounds. Some users say uninstalling the update restores queue functionality, but doing so also removes the security corrections that the update provided.
Why it matters
- MSMQ outage can halt inter-application messaging and disrupt enterprise workloads that depend on queued communication.
- The root cause is a permissions change, so fixes require careful coordination to avoid exposing system folders.
- Affected systems are primarily older, enterprise-managed Windows builds that organisations often keep for longer periods.
- Uninstalling the update restores functionality but abandons the security protections the patch delivered.
Key facts
- Microsoft confirmed MSMQ failures after its December 2025 security update.
- Symptoms include inactive queues, IIS errors stating "Insufficient resources to perform operation", and applications failing to write to queues.
- Event logs may show misleading "There is insufficient disk space or memory" entries despite available resources.
- The problem is caused by updated MSMQ security model and NTFS permissions on C:WindowsSystem32MSMQstorage, which now requires write access for MSMQ users.
- Clustered MSMQ deployments can experience issues under load.
- Impacted OS versions include Windows 10 22H2 and earlier (back to 1607) and Windows Server 2012 through 2019.
- Microsoft says consumer Home and Pro installations on personal devices are very unlikely to be affected.
- Microsoft recommended contacting support for a workaround; some administrators have reported that uninstalling the update restores MSMQ functionality but removes the security fixes.
What to watch next
- Whether Microsoft issues a targeted patch or updated guidance to resolve the permission change without removing security protections: not confirmed in the source.
- Organisations testing safe ways to grant MSMQ write access to the storage folder while preserving security controls.
- Reports of wider impact to newer Windows releases or additional server roles: not confirmed in the source.
Quick glossary
- MSMQ (Message Queuing): A Windows messaging protocol that lets applications asynchronously queue and exchange messages so communication can continue when endpoints are unavailable.
- NTFS permissions: Access control settings on the NTFS filesystem that determine which users or processes can read, write, or execute files and folders.
- IIS (Internet Information Services): Microsoft's web server software used to host websites and web applications on Windows servers.
- Clustered MSMQ: An MSMQ deployment configured across multiple servers for high availability and load handling.
Reader FAQ
Which Windows versions are affected?
Microsoft says Windows 10 22H2 and earlier (as far back as 1607) and Windows Server 2012 through 2019 are affected.
What caused the MSMQ failures?
A change to the MSMQ security model and NTFS permissions for C:WindowsSystem32MSMQstorage that now requires MSMQ users to have write access.
Is there a confirmed fix from Microsoft?
Microsoft suggested contacting support for a workaround; a full vendor-issued remediation is not confirmed in the source.
Can uninstalling the update restore service?
Some users reported that removing the update restores MSMQ functionality, but that also removes the security fixes the update provided.
OSES 16 Microsoft security update breaks MSMQ on older Win systems Folder permission changes cause queue failures and misleading error messages, no real fix yet Richard Speed Wed 17 Dec 2025 // 13:52 UTC…
Sources
- Microsoft security update breaks MSMQ on older Win systems
- Microsoft security update breaks MSMQ on older Win …
- Regarding problems with "MSMQ" in the December 2025 …
- Blowing up MSMQ: 2025-12 Cumulative Update for …
Related posts
- Microsoft faces UK tribunal over alleged multibillion‑pound cloud overcharges
- Microsoft to expand bug payouts across all services, even without programs
- Microsoft patches 9.9-rated Kestrel request-smuggling bug in ASP.NET Core