The Windows 11 update schedule kicked off 2026 with an uncomfortable episode for thousands of users—and, by extension, support teams and sysadmins: a security patch that, on certain systems with GeForce graphics cards, has coincided with black screens, flickering, visual corruption, and noticeable FPS drops in games.
The focus is on KB5074109, the security update released by Microsoft on January 13, 2026, for Windows 11 25H2 and 24H2, identified as builds 26200.7623 and 26100.7623. In theory, it’s just another “Patch Tuesday” with security fixes and cumulative improvements. In practice, a segment of the gaming and professional communities has seen their systems transition from “all good” to erratic experiences: black screens on startup, stuttering, artifacts, and performance dips that break any competitive or demanding session.
Reports have been accumulating across the usual channels: Feedback Hub on Windows, NVIDIA forums, and specialized media. In some cases, the crash has been described as a loss of 10 to 20 FPS in specific titles, with symptoms ranging from persistent micro-stutters to visual glitches during scene loads. For home users, it’s frustrating; for managed environments (labs, classrooms, creative studios, PC parks), the implications are clearer: tickets, uncertainty, and the classic question of “Do I patch or freeze?”
NVIDIA points to the root cause, and Microsoft downplays part of it… but not everything
What’s striking here is the distribution of responsibilities. NVIDIA has publicly acknowledged that it’s investigating the issues, although the trigger appears to be related to the Windows 11 update. According to information gathered from media sources, a community moderator on the GeForce forums mentioned that, at this time, the most effective way to restore normality is to uninstall KB5074109. It’s a pragmatic solution, but with caveats: we’re talking about a security patch, and uninstalling it entails risks or, at minimum, applying mitigating measures while awaiting a permanent fix.
Microsoft’s response has been partial. On January 29, 2026, they released KB5074105, an “Optional preview” update for Windows 11 (builds 26200.7705 and 26100.7705) that includes a specific fix: resolving black screens in “isolated multi-user environments,” typically after system updates. While this addresses one of the most visible symptoms, it doesn’t guarantee the disappearance of graphic artifacts or FPS drops in games.
Meanwhile, the public narrative has expanded beyond gaming, as KB5074109 also relates to other issues. Microsoft notes major changes such as the removal of legacy modem drivers, which has caused problems for users still relying on that hardware. It’s a reminder of how a “routine” patch can have a tangible impact on older peripherals or uncommon configurations.
What users and sysadmins should consider: the cost of rushing
The end-user pattern remains familiar: update, reboot, something breaks. But in 2026, that “something” weighs more and more because the PC is no longer just for recreation: it’s for hybrid work, content creation, CAD, simulation, development, and training. As a result, a graphics regression isn’t just “poor Forza performance”: it can lead to productivity losses, pipeline failures, and downtime, ultimately impacting IT departments.
For system administrators, this case highlights several practices—though they may seem mundane—that help prevent incidents:
- Deployment rings and pilot testing: don’t roll updates to all machines at once. If a patch is faulty, it’s caught before widespread deployment.
- Update management (via WSUS, Intune, policies): ability to pause, defer, or block specific updates based on criticality and compatibility.
- Scheduled maintenance windows with rollback plans: if an update affects GPUs or boot processes, a “Plan B” must exist, including procedures for uninstalling via recovery environment when the system won’t load.
- Monitoring and communication: gather evidence (GPU models, driver versions, exact Windows build) and deliver clear messages to users (“If X happens, don’t restart/ pause updates/ contact support”).
The biggest issue isn’t bugs themselves—which are almost unavoidable in a diverse ecosystem—it’s the perception of fragility: a security patch turning into an operational event.
What is known today, and what to expect
As of February 5, 2026, the situation is as follows:
- KB5074109 (January 13, 2026) is the reported inflection point for NVIDIA-equipped systems, with symptoms ranging from black screens to degraded gaming performance.
- NVIDIA is investigating, and for now, the workaround in affected cases is to uninstall the update.
- KB5074105 (January 29, 2026, preview) includes a fix for black screens in specific scenarios (“isolated multi-user environments”), but it is not a comprehensive solution for all artifacts or performance issues.
In short: there’s a patch addressing one symptom, ongoing investigation for others, and an inconvenient decision for those who just wanted to update seamlessly.
FAQs
What is KB5074109, and which versions of Windows 11 does it affect?
It’s the security update from January 13, 2026, for Windows 11 25H2 and 24H2, with builds 26200.7623 and 26100.7623.
How can I tell if FPS drops or black screens are related to KB5074109?
If issues started right after the January 2026 update and repeat in games (stuttering, artifacts, 10–20 FPS drops) or during startup, many reports link these problems to KB5074109 on systems with NVIDIA graphics.
Does KB5074105 definitively fix the problem?
KB5074105 (Preview, January 29, 2026) includes a fix for black screens in specific scenarios (“isolated multi-user environments”). However, it’s not a complete fix for all artifact issues or performance drops.
What measures can companies take to reduce the risk of problematic updates on NVIDIA systems?
Implement deployment rings, defer updates, maintain rollback procedures (including uninstalling from recovery environment if needed), and document driver/OS combinations per GPU model for faster diagnostics. Many analyses and guides recommend containment and rollback strategies while waiting for a full fix.
via: tweaktown