Microsoft has delivered some noteworthy updates for system administrators, particularly those managing older Windows versions. While certain organizations are currently investing in security updates for these legacy systems, the inconsistency in quality remains a complimentary service.
Recent Issues with MSMQ
The tech giant has acknowledged that Message Queuing (MSMQ) may encounter failures on select Windows 10 devices and older Windows Server versions following the December 2025 Security update. The issues reported include:
- MSMQ queues becoming inactive
- Internet Information Services (IIS) sites generating “Insufficient resources to perform operation” errors
- Applications failing to write to queues
Adding to the confusion, system logs are cluttered with misleading messages indicating “There is insufficient disk space or memory,” despite adequate resources being available. This perplexing situation stems from folder permissions and the specific write access requirements of MSMQ.
According to Microsoft’s documentation, the root of the issue lies in recent modifications to the MSMQ security model and NTFS permissions concerning the C:WindowsSystem32MSMQstorage folder. The documentation states, “This issue is caused by the recent changes introduced to the MSMQ security model and NTFS permissions on the C:WindowsSystem32MSMQstorage folder. MSMQ users now require write access to this folder, which is normally restricted to administrators.” Consequently, attempts to send messages via MSMQ APIs may fail, resulting in resource errors.
This defect also affects clustered MSMQ environments under heavy load, further complicating matters for IT departments.
Microsoft has indicated that the issue predominantly impacts Windows 10 versions 22H2 and earlier (up to 1607), as well as Windows Server versions 2012 to 2019. Users operating Windows Home or Pro editions on personal devices are unlikely to face these challenges, as the problem primarily affects enterprise or managed IT settings.
For those grappling with these issues, Microsoft recommends reaching out to their support team for potential workarounds. Some users have reported success in resolving the problem by uninstalling the update, although this action would forfeit the associated security enhancements.
MSMQ, a messaging protocol with roots tracing back to Windows 95 and NT4, has been a reliable means for applications to communicate seamlessly by queuing messages until they can be processed. A malfunction in MSMQ can lead to a cascade of application failures, disrupting operations significantly.
Fortunately, the current issues are confined to Microsoft’s older operating systems, which are often retained by enterprises that prefer to postpone the costs and challenges associated with upgrades. This approach aligns with the philosophy of “if it ain’t broke, don’t fix it.” However, in light of recent events, it may be time to reconsider this adage: “if it ain’t broke, don’t fix it. Until Microsoft breaks it…”
