Loading story…
Microsoft is dealing with administrator backlash over Windows update quality and lifecycle changes after cumulative update KB5094126 reportedly broke Word OLE and COM-based integrations used by line-of-business applications including CCH Engagement, with sysadmins also citing impacts on Dentrix and SoftDent workflows. Separate reports tied the same update to missing taskbar clock and hidden system tray behavior on some Windows 11 systems, with community workarounds ranging from uninstalling the patch to registry edits and system repair steps, while one discussion said Microsoft planned a follow-up update to address the CCH Engagement Word COM plugin issue.
At the same time, Microsoft clarified how Windows monthly releases, optional preview updates, hotpatching, and out-of-band fixes are delivered, while shipping Windows 10 ESU update KB5099539 with Remote Desktop security hardening and OLE Automation fixes. The company also warned that Windows 11 24H2 Home and Pro will stop receiving updates on October 13, 2026, while Windows 10 remains widely deployed despite rising exposure as support windows narrow and ESU coverage remains temporary, increasing pressure on enterprises to modernize systems without disrupting critical application dependencies.
See real exploitation activity before you spend the cycle.
5 events from the most recent confirmed update back to the earliest known activity.
Microsoft announced that Windows 11 version 24H2 Home and Pro, and Windows 10 Enterprise LTSB 2016, will stop receiving updates on 2026-10-13, and advised customers to move to Windows 11 25H2.
Microsoft published updated guidance explaining Patch Tuesday releases, optional non-security preview updates, hotpatching, out-of-band updates, and Controlled Feature Rollout for Windows.
Microsoft released cumulative update KB5099539 for Windows 10 ESU devices, adding RDP security-related changes, Secure Boot certificate rollout components, and fixes for several issues including OLE Automation problems.
A Microsoft Answers discussion cited in the source says the missing clock and hidden system tray issue was being discussed on 2026-06-26, before content from a May optional preview was later pushed into KB5094126.
Microsoft's lifecycle documentation states that Windows 11 version 24H2 Home and Pro editions reach end of servicing on 2026-10-13, while Enterprise and Education editions remain supported until 2027-10-12.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
8 references tracked. Mallory keeps watching after this page renders.
bleepingcomputer.com
Open sourcereddit.com
Open sourcetheregister.com
Open sourcewindowslatest.com
Open sourcewindowslatest.com
Open sourcereddit.com
Open sourcereddit.com
Open sourcelearn.microsoft.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft is warning organizations that **Windows Server 2016**, **Windows 10 Enterprise LTSB 2016**, and **Windows 10 IoT Enterprise 2016 LTSB** are approaching end of support, after which they will no longer receive security patches, bug fixes, or technical support. Reported lifecycle dates include **October 13, 2026** for the Windows 10 2016 LTSB variants and **January 12, 2027** for Windows Server 2016; Microsoft’s guidance is to prioritize upgrades (e.g., to **Windows Server 2025** and Windows 10/11 LTSC options where hardware permits) and, if migration timelines slip, to use the **Extended Security Updates (ESU)** program as a short-term bridge for up to three years with only “critical” and “important” security updates. Separately, Microsoft released the **Windows 11 KB5077241** optional (non-security) preview cumulative update with 29 quality changes, including **BitLocker reliability** improvements (addressing freezes after entering a recovery key) and new built-in capabilities such as a taskbar **network speed test** and **native Sysmon functionality** (disabled by default). The update also enables **Quick Machine Recovery (QMR)** by default on certain unmanaged Windows Pro devices and is positioned for admin testing ahead of the next Patch Tuesday release, but it does **not** include security fixes.
Jun 29, 2026
Microsoft’s January Windows security updates triggered an unusual **patch-break-patch** cycle that forced multiple out-of-band (OOB) releases after users reported significant regressions. Reporting indicates the Jan. 13 Patch Tuesday update (including `KB5074109`) was followed by an urgent Jan. 17 fix that introduced additional problems, leading to a second emergency OOB update on Jan. 24; impacts cited include Remote Desktop sign-in/authentication failures and broader stability issues such as Outlook freezing and file-system/compatibility problems affecting OneDrive and Dropbox integrations. Microsoft advised customers to move to the latest available update despite the disruption. Separate analysis highlighted that Windows’ long-standing commitment to **backwards compatibility** continues to create persistent exposure and operational risk: many exploited-in-the-wild Microsoft zero-days in 2025 were **elevation-of-privilege** issues rooted in legacy components, reinforcing that “traditional” exploit chains and accumulated Windows tech debt remain a primary driver of both security and patching complexity. Taken together, the coverage underscores that Windows defenders face a dual challenge: rapid deployment of security fixes to reduce exploitation risk, while managing the real possibility that emergency remediation can itself introduce enterprise-impacting outages.
Jun 29, 2026
Microsoft released an **optional, non-security** update for Windows 11 versions **25H2 and 24H2** (KB`5077241`), advancing OS builds to **26200.7922** and **26100.7922**. Reported changes focus on functionality and reliability, including UI updates (e.g., redesigned battery icons and a refreshed Start menu experience), updates to Windows AI-related components, and a servicing stack update (SSU) KB`5077371` intended to improve the robustness of future update installation; the rollout is described as phased/gradual before broader availability. Separately, Microsoft outlined approaching end-of-support deadlines for **Windows 10 Enterprise LTSB 2016**, **Windows 10 IoT Enterprise 2016 LTSB** (both ending **Oct 13, 2026**), and **Windows Server 2016** (ending **Jan 12, 2027**), after which only a paid **Extended Security Updates (ESU)** program can provide security patches for up to three additional years. Microsoft emphasized ESU provides *security updates only* (no new features, quality fixes, or technical support), with pricing starting at **$61/device** for year one (discounted to **$45/device** for Intune/Windows Autopatch-managed systems) and doubling each year; Windows Server 2016 ESU pricing was not disclosed, and Microsoft recommended upgrading to newer LTSC/LTS releases as the preferred path.
Jun 29, 2026