Events2HVAC MSMQ Error "Insufficient resources to perform operation."

If you are receiving command queue errors for all of your commands with error message "Insufficient resources to perform operation." after December 9th, 2025, this is most likely due to one or more Windows updates that are affecting Microsoft Message Queue software.

MSMQ is a critical component to Events2HVAC since it uses it to send every command out from E2H to external systems.  Your Events2HVAC system will not schedule or send commands if you are receiving this error.

The following Windows updates released Dec 9, 2025 are the cause of this issue.

KB5071543 released on Dec 9, 2025 affects Windows 10 and Windows Server 2016 systems.

KB5071544 released on Dec 9, 2025 affects Windows 10 version 1809 and Windows Server 2019.

KB5071546 released on Dec 9, 2025 affects Windows 10 21H2 / 22H2.

All of these windows updates report this known issue after applying this update.

More details:

KB5071544 is a Windows 10 cumulative update released on December 9, 2025, as part of Microsoft's monthly Patch Tuesday updates.^1•2 This specific update is for Windows 10 version 1809 and brings the OS to build number 17763.8146.^1•3

The update includes miscellaneous security improvements and fixes to enhance overall system reliability and user experience.³ Notably, this release is part of the Extended Security Update (ESU) program, which provides critical security patches for Windows 10 devices until October 2026 for systems that are not compatible with Windows 11.³

A significant issue has been reported with this update. Some users, particularly on Windows 10 LTSC, have experienced problems with dual-monitor setups after installation. The symptoms include the desktop failing to load due to an issue with Explorer.exe, which can be temporarily resolved by disabling one of the monitors.⁴ Additionally, there are reports of issues with Microsoft Message Queuing (MSMQ) on Windows Server 2019, where the update may cause errors related to insufficient disk space or memory, similar to problems seen with a previous update (KB5071543) on Server 2016.⁵

Microsoft has also included an important notice regarding Secure Boot certificates, which are set to expire starting in June 2026. Users are advised to update these certificates in advance to prevent potential boot issues.^1•6•5

KB5071543 is a Windows update released on December 9, 2025, as part of Microsoft's monthly Patch Tuesday security updates. This update specifically targets older Windows 10 versions, bringing the OS Build to 14393.8688^2,6.

Key details about KB5071543 include:

• Release Date: December 9, 2025^2,6.
• Target OS: This update is for Windows 10 systems based on OS Build 14393, which corresponds to the original Windows 10 version released in 2016 (Anniversary Update)^2^^.
• Primary Focus: It is a cumulative security update designed to address vulnerabilities and improve system stability for this older branch of Windows 10^2,6.
• Important Security Context: This update, along with other releases from this period, includes a critical warning about Secure Boot certificates used by most Windows devices. These certificates are set to expire starting in June 2026, which could prevent devices from booting securely if not updated in time^2,3,7.

It is also part of a broader set of December 2025 updates for Windows 10, which included KB5071544 and KB5071546 for other versions of the operating system⁶.

Note on Known Issues: Based on community reports, some users have experienced issues with Microsoft Message Queuing (MSMQ) after installing this update on systems running Windows Server 2016. The error messages indicate problems with creating message files, citing insufficient disk space or memory, even when resources are available. Similar issues have been reported with the subsequent update, KB5071544, on Windows Server 2019¹.

Microsoft released the subsequent updates on Dec 18^th to fix these MSMQ issues.  Please refer to the corresponding Microsoft support page:

Otherwise, uninstall KB5071543 and/or KB5071543 and reboot the server.