CyberHappenings logo

Track cybersecurity events as they unfold. Sourced timelines. Filter, sort, and browse. Fast, privacy‑respecting. No invasive ads, no tracking.

Microsoft December 2025 Updates Break Message Queuing Functionality

First reported
Last updated
1 unique sources, 3 articles

Summary

Hide ▲

Microsoft's December 2025 security updates caused Message Queuing (MSMQ) failures across Windows 10 22H2, Windows Server 2019, and Windows Server 2016 systems. The issue arose from security model changes that modified permissions on a critical system folder, leading to errors in MSMQ queues and IIS sites. Affected systems experienced inactive queues, resource errors, and application failures. Microsoft has released an out-of-band update (KB5074976) via Update Catalog to address the issue. The company initially advised enterprise customers to contact support for a temporary workaround, and the update is now available for download.

Timeline

  1. 19.12.2025 03:15 1 articles · 23h ago

    Microsoft Releases Out-of-Band Update for MSMQ Issues

    Microsoft has released an out-of-band update (KB5074976) via Update Catalog to address the MSMQ issues. The update is not available via Windows Update or WSUS and is only offered via Update Catalog. The issue also impacts a clustered MSMQ environment under load.

    Show sources
  2. 15.12.2025 11:04 3 articles · 4d ago

    Microsoft December 2025 Updates Cause MSMQ Failures

    Microsoft's December 2025 security updates caused widespread MSMQ failures due to changes in the security model and NTFS permissions. Affected systems experienced inactive queues, resource errors, and application failures. Microsoft has released an out-of-band update (KB5074976) via Update Catalog to address the issue. The company initially advised enterprise customers to contact support for a temporary workaround, and the update is now available for download.

    Show sources

Information Snippets

Similar Happenings

Windows Updates Cause RemoteApp Connection Failures in Azure Virtual Desktop

Recent Windows updates, including the November 2025 KB5070311 non-security update, are causing RemoteApp connection failures in Azure Virtual Desktop environments on Windows 11 24H2/25H2 and Windows Server 2025 devices. This issue primarily affects enterprise users, leaving full desktop sessions unaffected. Microsoft has provided a temporary mitigation involving a registry key modification and a Known Issue Rollback (KIR) for Windows Pro and Enterprise devices. Affected organizations can manually add a registry key and restart the system to mitigate the issue. Microsoft is working on a permanent fix but has not provided a timeline.

Windows 11 KB5070311 Update Addresses File Explorer and Search Issues

Microsoft has released the KB5070311 optional preview cumulative update for Windows 11, addressing File Explorer freezes, search issues, and other bugs. The update includes 49 changes and is part of the monthly preview updates that precede Patch Tuesday releases. It fixes issues with explorer.exe process responsiveness, SMB share search problems, and LSASS instability. However, the update also introduced a new bug causing bright white flashes when launching File Explorer in dark mode. Microsoft has since fixed this issue with the December KB5072033 Patch Tuesday cumulative update. The update is available for manual installation and updates Windows 11 25H2 and 24H2 devices to builds 26200.7309 and 26100.7309, respectively. Additionally, Microsoft announced there will be no preview update in December 2025 due to minimal operations during the Western holidays, with normal updates resuming in January 2026.

Windows 11 24H2 Bug Causes Critical System Component Crashes

Microsoft has confirmed a critical bug in Windows 11 24H2 that causes File Explorer, Start Menu, and other key system components to crash after installing cumulative updates released since July 2025. The issue arises from XAML dependency packages failing to register properly, affecting both regular and non-persistent OS installations. Users experience crashes in essential shell components, leading to partially functional systems. Microsoft is working on a resolution and has provided temporary workarounds.

Windows Task Manager Bug Fixed in November Update

Microsoft has resolved a bug in the Windows 11 Task Manager that prevented it from fully terminating after being closed. The issue, introduced by the optional KB5067036 update, caused multiple instances of Task Manager to run in the background, leading to performance degradation. The fix is included in the November KB5068861 security update.

Windows 10 update bug triggers incorrect end-of-support alerts

A bug in the October 2025 Windows 10 updates triggers incorrect end-of-support alerts on systems running Windows 10 Enterprise LTSC 2021, Windows 10 IoT Enterprise LTSC 2021, and Windows 10 22H2 enrolled in the Extended Security Updates program. The bug causes affected devices to display 'Your version of Windows has reached the end of support' messages, despite the systems still being under active support or security coverage. Microsoft has deployed a cloud configuration update to correct the erroneous message, but some devices may not receive it due to connectivity or configuration issues. IT administrators can use Known Issue Rollback (KIR) to remove the incorrect messages on enterprise-managed devices. Microsoft released the first Windows 10 extended security update (KB5068781) on November 11, 2025, to address the bug for all customers enrolled in the Extended Security Updates (ESU) program. However, the KB5068781 update was failing to install with 0x800f0922 errors on devices with corporate licensing. Microsoft has now released an emergency Windows 10 KB5072653 out-of-band update on November 17, 2025, to resolve these installation issues. Some corporate Windows admins have reported that WSUS and SCCM are not correctly indicating that a Windows 10 device needs the extended security update, even when it is correctly enrolled in the program. Microsoft plans to release a new Scan Cab with updated metadata to address this issue.