Windows 11 KB5074109 & KB5073455 Cumulative Updates Released

Why It Matters

The patches close multiple zero‑day flaws and resolve enterprise‑critical connectivity bugs, making timely deployment essential for security and operational continuity.

Key Takeaways

• KB5074109 and KB5073455 address critical security flaws
• Updates remove legacy modem drivers, breaking compatibility
• Fixes WSL networking and Azure Virtual Desktop RemoteApp issues
• NPU devices no longer stay powered on when idle
• Secure Boot certificates now phased in via device‑targeting data

Pulse Analysis

The January 2026 Patch Tuesday marks Microsoft’s third cumulative update for Windows 11 25H2, yet it carries heightened urgency because it bundles high‑confidence security fixes across all supported editions. By advancing the 25H2/24H2 builds to 26200.7623 (or 26100.7462) and the 23H2 build to 226x1.6050, the updates ensure that devices receive the latest mitigations for vulnerabilities disclosed in recent months. For IT administrators, the mandatory nature of these updates means that any device lagging behind will be flagged as non‑compliant in most corporate security baselines, prompting immediate remediation.

Beyond the core security patches, the update introduces several functional changes that directly affect enterprise workloads. Legacy modem drivers (agrsm64.sys, agrsm.sys, smserl64.sys, smserial.sys) are removed, which may disrupt legacy telephony equipment still in use. More critically, networking stability improves: mirrored networking failures in Windows Subsystem for Linux that broke VPN access are resolved, and RemoteApp connections in Azure Virtual Desktop no longer drop after prior updates. Power efficiency also benefits from a fix that prevents Neural Processing Unit‑enabled devices from staying powered on when idle. Additionally, Secure Boot now leverages device‑targeting data to phase in new certificates, and Windows Deployment Services disables hands‑free deployment by default, prompting admins to review deployment strategies.

For businesses, the combined security and reliability enhancements translate into reduced risk exposure and smoother remote‑work experiences. Organizations should prioritize the rollout through automated update pipelines, verify that any dependent modem hardware is replaced or re‑configured, and test WSL‑dependent workflows in staging environments before full deployment. Monitoring tools should be updated to recognize the new build numbers and Secure Boot certificate rollout status. Proactive compliance with these updates not only safeguards against emerging threats but also positions enterprises to adopt future Windows innovations with confidence.