"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.""
"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."
Microsoft confirmed that Message Queuing (MSMQ) might fail on some Windows 10 devices and on older versions of Windows Server after the December 2025 security update. Reported problems include MSMQ queues becoming inactive, IIS sites failing with "Insufficient resources to perform operation" errors, and applications failing to write to queues. Logs can display misleading "There is insufficient disk space or memory" messages despite adequate resources. The root cause is changes to the MSMQ security model and NTFS permissions on C:\Windows\System32\MSMQ\storage requiring MSMQ users to have write access. The defect affects Windows 10 22H2 and earlier and Windows Server 2012–2019, mainly in enterprise environments. Microsoft recommended contacting support for a workaround; uninstalling the update restores functionality but removes its security fixes.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]