Windows Update Fixes Message Queuing Issues – Heise Online

Microsoft Rushes Out Emergency Updates to Fix Faulty windows Security Patches

Microsoft is scrambling to address critical issues stemming from its december security updates for Windows, which have disrupted application interaction and caused software failures. The company released emergency updates Friday night to mitigate the problems affecting Message Queuing (MSMQ), a core component used by many applications.

The issues first surfaced earlier this week, with reports indicating that MSMQ would be disrupted on Windows 10 and Windows Servers until 2019.This disruption could lead to widespread software malfunctions, prompting Microsoft to expedite the release of fixes.

According to a Microsoft update to its Windows release health notes, the updates – identified as KB5074976 (Windows 10), KB5074975 (Windows Server 2019), and KB5074974 (Windows Server 2016) – are now available. These cumulative updates raise Windows 10 build numbers to 19044.6693 and 19045.6693 and incorporate other changes from the December Patchday.

Did you know? – Message Queuing (MSMQ) facilitates application communication by enabling asynchronous message delivery. It’s a vital component for many enterprise applications and services.

However, the rollout hasn’t been seamless. IT administrators are currently receiving the updates exclusively through the Windows Update Catalog, requiring a search using the relevant KB number. While Microsoft links to the catalog in its KB entries, the server updates were not immediately available for download at the time of reporting.

The scope of the problem has also expanded as the initial reports. Microsoft now identifies a broader range of affected operating systems, including Windows 10 versions 22H2, 21H2, 1809, and 1607, and also server versions 2019, 2016, 2012 R2, and 2012.

Pro tip – Before deploying any Windows update, especially critical security patches, test them in a non-production environment to identify potential compatibility issues.

The root cause of the issue lies in changes made to the MSMQ security model and NTFS access rights to the C:WindowsSystem32MSMQstorage folder. MSMQ users now require write access to this folder, which is typically restricted to administrators. As a result, applications attempting to send messages using MSMQ APIs may encounter resource errors.

The swift response from Microsoft underscores the importance of thorough testing before widespread deployment of security updates.While security patches are crucial for protecting systems, unintended consequences can disrupt operations and necessitate emergency interventions.

Reader question – Have you experienced issues with Windows updates in your environment? What steps do you take to mitigate risks during deployment?