"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."
"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. Nevertheless, it is frequently used in corporate environments for network communication between applications. The service provides asynchronous messaging, which is essential for many line-of-business applications and IIS-based web applications."
December 2025 Windows security updates caused Message Queuing (MSMQ) failures on Windows 10 22H2, Windows Server 2019, and Windows Server 2016 systems installed with KB5071546, KB5071544, and KB5071543. Reported symptoms include inactive MSMQ queues, IIS sites failing with "insufficient resources" messages, and applications unable to write messages to queues. The updates modified permissions on C:WindowsSystem32msmqstorage, now requiring MSMQ users to have write access that is normally restricted to administrators. Clustered MSMQ under load is affected, while systems with users running as full administrators avoid the issue. Microsoft is investigating with no timeline or confirmed emergency update.
Read at Techzine Global
Unable to calculate read time
Collection
[
|
...
]