Windows 11 KB5074109 January Cumulative Update Triggers Gaming Performance and Stability Issues
Microsoft’s January Windows 11 cumulative update KB5074109 has been linked to gaming performance degradation and instability on systems using NVIDIA GeForce GPUs, with users reporting 15–20 FPS drops, black screens, and visual artifacting after installation. NVIDIA acknowledged the issue publicly via its GeForce forums, stating it is investigating and that uninstalling KB5074109 appears to be the only effective temporary mitigation; some users also report that installing Microsoft’s latest optional updates may resolve the problem without removing the security update.
The update is described as security-critical (reported as addressing 114 vulnerabilities), creating a tradeoff between stability and exposure if the patch is removed. Separately, Microsoft has been issuing multiple out-of-band (OOB) fixes following January Patch Tuesday to address regressions (e.g., Remote Desktop credential prompt failures and Outlook Classic .pst access issues on cloud storage) and also shipped an OOB fix for an Office zero-day (CVE-2026-21509, a security bypass), underscoring a broader pattern of post-release remediation activity around the January patch cycle.
Timeline
Feb 5, 2026
Nvidia recommends uninstalling KB5074109 as workaround
An Nvidia representative on the official GeForce forums advised affected users to uninstall Windows 11 update KB5074109 temporarily while the company investigates the gaming-related problems. Users reported that removing the update restored performance and stability.
Jan 1, 2026
Microsoft releases optional KB5074105 for black-screen issue
Microsoft released update KB5074105 as an optional fix for a black-screen problem linked to the January update, though it may require manual installation.
Jan 1, 2026
Users report boot failures and gaming issues after KB5074109
After KB5074109 was installed, users reported systems failing to boot properly as well as gaming instability on PCs with Nvidia GeForce GPUs, including framerate drops, visual artifacts, and black screens.
Jan 1, 2026
Microsoft releases Windows 11 security update KB5074109
Microsoft issued the January 2026 Windows 11 security update KB5074109 as a mandatory patch addressing 114 security vulnerabilities and other bugs, including battery drain on systems with NPUs.
See the full picture in Mallory
Mallory subscribers get deeper analysis on every story, including:
Who’s affected and how
Deep-dive technical analysis
Actionable next steps for your team
IPs, domains, hashes, and more
Ask questions and take action on every story
Filter by topic, classification, timeframe
Get matching stories delivered automatically
Sources
Related Stories
Windows 11 January Security Update KB5074109 Triggers Widespread Stability and Remote Desktop Issues
Microsoft’s January 2026 Patch Tuesday release for Windows 11 (notably **KB5074109** for 24H2/25H2) delivered roughly 100+ security fixes (including reported **zero-days**) but also introduced significant reliability regressions. Reported impacts include **system lockups**, **black screens** on systems with Nvidia/AMD GPUs, graphics-related hangs in GPU/DirectX-intensive applications, and application failures such as **Outlook Classic** freezing or failing to launch; additional issues were reported with File Explorer behavior and cloud-backed storage workflows (e.g., OneDrive/Dropbox) causing apps to become unresponsive when saving or syncing data.
1 months ago
Windows 11 KB5077181 Patch Tuesday Update Triggers and Fixes Boot Failures
Microsoft’s February 2026 Windows 11 cumulative security update **KB5077181** (for versions **24H2** and **25H2**) was associated with significant boot reliability issues reported shortly after deployment, including systems entering **infinite restart loops** and failing to reach the desktop. Reports described login-time errors (including **System Event Notification Service (SENS)** procedure errors) and network symptoms such as **DHCP failures**, while Microsoft’s public release notes and health dashboard were reported as not listing known issues at the time. The update also shipped broad security remediation, with reporting citing **58 vulnerabilities** addressed and **six actively exploited zero-days** referenced via CISA’s **Known Exploited Vulnerabilities** catalog, including fixes for issues such as SmartScreen bypass (`CVE-2026-21510`), Desktop Window Manager EoP (`CVE-2026-21519`), Remote Desktop Services EoP (`CVE-2026-21533`), and a Notepad RCE via crafted Markdown (`CVE-2026-20841`). Separately, Microsoft stated that **KB5077181** fully resolved a specific Windows 11 boot failure condition affecting a limited set of **commercial physical devices** on **24H2/25H2** that could become unbootable (e.g., **"UNMOUNTABLE_BOOT_VOLUME"**) after installing **KB5074109** or later updates when a **December 2025** security update had previously failed and rolled back, leaving the OS in an “improper state.” Microsoft indicated an earlier mitigation shipped in the optional preview update **KB5074105** (Jan 29, 2026) to prevent additional devices from being impacted, and that the February Patch Tuesday release delivered the complete fix; the issue was not reported as affecting home users or virtual machines.
1 months ago
Windows 11 Reliability Backlash and KB5074105 Preview Update Fixes
Microsoft reported **over 1 billion monthly active Windows 11 users**, but user sentiment remains negative, with prominent complaints focused on **buggy updates**, perceived reliability regressions, and unwanted feature changes (including AI-related additions). Microsoft leadership publicly acknowledged the feedback and said the company will prioritize **performance, reliability, and overall user experience** improvements to rebuild trust. Microsoft also released the **KB5074105** optional *non-security* preview cumulative update for Windows 11 (24H2/25H2), positioned as an end-of-month quality update ahead of the next Patch Tuesday. KB5074105 includes dozens of changes and targets operational issues including **boot problems** (e.g., startup hangs when Windows Boot Manager debugging is enabled and iSCSI boot failures with `Inaccessible Boot Device`), **sign-in issues** (including `Explorer.exe` hanging on first login under certain startup-app configurations), and **activation/license migration failures** during upgrades when devices cannot register with the Windows Activation server; the update is available via Windows Update or manual download from the Microsoft Update Catalog.
1 months ago