Microsoft patches bug causing multiple Message Queuing errors
Briefly

Microsoft patches bug causing multiple Message Queuing errors
"Microsoft has confirmed that the December 2025 security updates are causing problems with Message Queuing (MSMQ). Business applications and IIS websites are experiencing malfunctions after installing the patches. The known issue affects Windows 10 22H2, Windows Server 2019, and Windows Server 2016 systems on which updates KB5071546, KB5071544, and KB5071543 have been installed. These patches were released during this month's Patch Tuesday."
"Users are reporting various symptoms: MSMQ queues remain inactive, IIS sites fail with "insufficient resources" messages, and applications can no longer write messages to queues. Some systems display misleading error messages about insufficient disk space or memory, even though sufficient resources are available. According to Microsoft, the cause lies in changes to the MSMQ security model. The updates have modified the permissions on the system folder C:WindowsSystem32msmqstorage. MSMQ users now need write access to this folder, which is normally restricted to administrators."
"Attempts to send messages via MSMQ APIs may now fail with resource error messages. Clustered MSMQ environments under load are also experiencing problems. Systems where users are logged in with full admin rights do not experience the problem. However, for many enterprise environments, this is not a workable solution due to security best practices. The MSMQ service is available as an optional component on all Windows operating systems."
An out-of-band update (KB5074976) was released on December 19 via the Update Catalog to fix Message Queuing (MSMQ) errors introduced by December 2025 security updates. Systems with KB5071546, KB5071544, or KB5071543 installed on Windows 10 22H2, Windows Server 2019, and Windows Server 2016 experienced MSMQ and IIS failures. Reported symptoms include inactive MSMQ queues, IIS "insufficient resources" errors, and inability for applications to write messages, sometimes with misleading disk-space or memory errors. The cause is a change to the MSMQ security model that altered permissions on C:WindowsSystem32msmqstorage, requiring write access for MSMQ users normally restricted to administrators. Full-admin logins avoid the issue, but that is unsuitable for many enterprises. MSMQ is widely used for asynchronous messaging in business applications and IIS web apps.
Read at Techzine Global
Unable to calculate read time
[
|
]