Microsoft security updates breaks MSMQ on older Win systems
(2025/12/17)
- Reference: 1765979525
- News link: https://www.theregister.co.uk/2025/12/17/microsoft_admits_that_message_queuing/
- Source link:
Microsoft has good news for administrators: while some organizations now pay for security updates on older Windows versions, the inconsistent quality remains free.
The company has [1]confirmed that Message Queuing (MSMQ) might fail on some Windows 10 devices and on older versions of Windows Server after installing the December 2025 Security update.
The problems include MSMQ queues becoming inactive, Internet Information Services (IIS) sites failing with "Insufficient resources to perform operation" errors, and applications failing to write to queues.
[2]
To compound the problem, logs are stuffed with misleading errors such as "There is insufficient disk space or memory" despite there being plenty of both.
[3]
[4]
The glitch is actually to do with folder permissions and where MSMQ wants write access. In its documentation for the issue, Microsoft said: "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."
[5]
It also impacts clustered MSMQ environments under load.
[6]Microsoft 365 boosts prices in 2026 … to pay for more AI and security
[7]Here we go again: Microsoft in UK court over cloud licensing
[8]Microsoft appears to move on from its most loyal 'customers' – Contoso and Fabrikam
[9]Microsoft promises more bug payouts, with or without a bounty program
According to Microsoft, the defect impacts Windows 10 22H2 and earlier (up to 1607), and Windows Server 2012 to 2019. "Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue. This issue primarily affects enterprise or managed IT environments."
Microsoft suggested contacting its support team for a workaround. Other users reported that uninstalling the update also did the trick, though doing so would mean losing the security fixes it contained.
MSMQ has been around for decades in one form or another, and can trace its lineage back to the days of Windows 95 and NT4. It is a messaging protocol that allows applications to communicate in a failsafe manner by queuing messages until they can be sent and received.
A failure of MSMQ can result in a raft of applications stopping working.
[10]
Fortunately, only Microsoft's older operating systems are affected. Unfortunately, these are the ones that tend to be kept alive by enterprises deferring the pain and expense of upgrading, or following the "if it ain't broke, don't fix it" philosophy.
Alas, the truism probably needs an update these days: "if it ain't broke, don't fix it. Until Microsoft breaks it…" ®
Get our [11]Tech Resources
[1] https://learn.microsoft.com/en-gb/windows/release-health/status-windows-10-22h2#message-queuing--msmq--might-fail-with-the-december-2025-windows-security-update
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://www.theregister.com/2025/12/05/microsoft_365_prices_up_2026/
[7] https://www.theregister.com/2025/12/12/microsoft_cat_cloud_licensing/
[8] https://www.theregister.com/2025/12/01/microsoft_contoso_fabrikam_zava/
[9] https://www.theregister.com/2025/12/12/microsoft_more_bug_payouts/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://whitepapers.theregister.com/
The company has [1]confirmed that Message Queuing (MSMQ) might fail on some Windows 10 devices and on older versions of Windows Server after installing the December 2025 Security update.
The problems include MSMQ queues becoming inactive, Internet Information Services (IIS) sites failing with "Insufficient resources to perform operation" errors, and applications failing to write to queues.
[2]
To compound the problem, logs are stuffed with misleading errors such as "There is insufficient disk space or memory" despite there being plenty of both.
[3]
[4]
The glitch is actually to do with folder permissions and where MSMQ wants write access. In its documentation for the issue, Microsoft said: "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."
[5]
It also impacts clustered MSMQ environments under load.
[6]Microsoft 365 boosts prices in 2026 … to pay for more AI and security
[7]Here we go again: Microsoft in UK court over cloud licensing
[8]Microsoft appears to move on from its most loyal 'customers' – Contoso and Fabrikam
[9]Microsoft promises more bug payouts, with or without a bounty program
According to Microsoft, the defect impacts Windows 10 22H2 and earlier (up to 1607), and Windows Server 2012 to 2019. "Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue. This issue primarily affects enterprise or managed IT environments."
Microsoft suggested contacting its support team for a workaround. Other users reported that uninstalling the update also did the trick, though doing so would mean losing the security fixes it contained.
MSMQ has been around for decades in one form or another, and can trace its lineage back to the days of Windows 95 and NT4. It is a messaging protocol that allows applications to communicate in a failsafe manner by queuing messages until they can be sent and received.
A failure of MSMQ can result in a raft of applications stopping working.
[10]
Fortunately, only Microsoft's older operating systems are affected. Unfortunately, these are the ones that tend to be kept alive by enterprises deferring the pain and expense of upgrading, or following the "if it ain't broke, don't fix it" philosophy.
Alas, the truism probably needs an update these days: "if it ain't broke, don't fix it. Until Microsoft breaks it…" ®
Get our [11]Tech Resources
[1] https://learn.microsoft.com/en-gb/windows/release-health/status-windows-10-22h2#message-queuing--msmq--might-fail-with-the-december-2025-windows-security-update
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://www.theregister.com/2025/12/05/microsoft_365_prices_up_2026/
[7] https://www.theregister.com/2025/12/12/microsoft_cat_cloud_licensing/
[8] https://www.theregister.com/2025/12/01/microsoft_contoso_fabrikam_zava/
[9] https://www.theregister.com/2025/12/12/microsoft_more_bug_payouts/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aULhqSgTh0tCvRuoCOFd8QAAAE0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://whitepapers.theregister.com/
Doctor Syntax
Internet Information Services (IIS) sites failing with "Insufficient resources to perform operation" errors
This must be a great inconvenience to those Chinese crews who have put a lot of work into using them as back doors into networks.
It's a good job Microsoft operate above the law.
Tron
It would have cost them a fortune over the years, if they had to pay compensation every time they broke peoples' stuff.
"It is a messaging protocol that allows applications to communicate in a failsafe manner"
El Duderino
Apparently not
lordminty
"the defect impacts Windows 10 22H2 and earlier (up to 1607)"
So basically every version of Windows 10, given 22H2 is the latest build!
Nematode
I knew I shouldn't have bothered with the extended updates programme.
Am I reading this correctly?
For higher security, we are giving write access to a system folder that didn't require it before?