"Administrators already dealing with the MSMQ issue can install this update to resolve it. The problem mainly affected enterprise environments - according to Microsoft, users on Pro and Home editions of Windows were "very unlikely" to encounter the issue. The cause was a change that required MSMQ to have write access to areas where administrative restrictions usually apply. The result was that message queuing could stop working, leading to some distinctly unhelpful errors."
"It took Microsoft a few days to acknowledge there was a problem - the known issue was added to affected versions on December 12, 2025, during which time affected administrators were forced to deploy workarounds that involved either granting modified permissions to the storage folder or rolling back the update. The out-of-band (OOB) update resolves the issue, though it calls into question Microsoft’s quality practices once again, since a lot of corporate infrastructure depends on MSMQ."
Microsoft released an out-of-band update to fix a Message Queuing (MSMQ) failure caused by the December 2025 update. Patches were issued for Windows 10 22H2 ESU, Windows 10 Enterprise LTSC 2021, Windows 10 LTSB 2016, and multiple Windows Server releases from 2008 through 2019. The December 9, 2025 changes required MSMQ to have write access to administratively restricted locations, causing MSMQ to stop working and producing misleading errors such as "There is insufficient disk space or memory." The issue mainly affected enterprise environments and required administrators to apply workarounds or roll back updates until the OOB patch restored MSMQ functionality. The incident raises concerns about update quality for legacy components.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]