What the hell is going on with Windows Update? That’s the question I’ve been asking myself lately. Last week, Microsoft released the January 2026 update for Windows 11 (KB5074109), and let me tell you, it’s been a mess. This update hit Windows 11 versions 25H2 and 24H2, but similar problems affected other versions too, including Windows 11 23H2 Enterprise editions, Windows 10 Extended Security Updates, and Windows Server 2023 and 2025 under different KB numbers.
Now, this update was supposed to be important because it included 114 security patches addressing critical vulnerabilities. Security updates should be something we can trust and install without worrying about breaking our systems. But that’s not what happened this time.
Key Takeaways
- The January 2026 Windows update (KB5074109) bundled security patches with experimental features, causing widespread system issues including remote desktop failures, shutdown problems, and black screen errors.
- Microsoft’s policy of forcing feature updates through mandatory security releases removes user choice and makes it impossible to stay secure without accepting potentially buggy new functionality.
- If you’ve already installed the problematic update, you can download a fix from the Microsoft Update Catalog or uninstall the update entirely to restore system stability.
Requirements
- Windows 11 (versions 24H2, 25H2, or 23H2 Enterprise) or Windows 10 with Extended Security Updates
- Internet connection to download patches from Microsoft Update Catalog
- Administrator access to install or uninstall Windows updates
- Basic understanding of Windows Update settings
Why Are Windows Updates Bundling Features With Security Patches?
Here’s the thing that really bothers me about this whole situation. According to Microsoft’s own documentation, they’re bundling features with mandatory security updates. The update description specifically states it includes “non-security updates from last month’s optional preview release.” This is where I think the problem comes in.
I can’t say for certain that it’s the non-security updates that broke everything, but it makes sense. Microsoft has this setting in Windows Update called “Get the latest updates as soon as they’re available.” When you toggle this on, you’re basically giving Microsoft permission to push experimental updates and new features to your PC to test them. Then, if they’ve been tested long enough according to Microsoft, they get included in the next month’s security update.
The issue is that security updates are mandatory. You have to install them to stay secure. But now Microsoft is bundling features with those security patches, and that’s a huge problem. I should have a choice to get my system secure without accepting the features that Microsoft wants to push on me. Those two things should be completely separate.
What Problems Did This Windows Update Cause?
Following the release of the January 2026 update, Microsoft officially confirmed at least three major problems. But from what I’ve seen online and heard from people, there are way more issues than what they’ve admitted to.
Confirmed Issues by Microsoft
- Remote Desktop Connections Failing – This was fixed in a subsequent update that Microsoft rushed out
- Windows 11 23H2 Won’t Shut Down – This affected enterprise versions specifically and was also patched
- Classic Control Panel Crashes – This hasn’t been fixed yet
Unreported Issues Users Are Experiencing
I’ve also seen online that people are suffering from constant black screen issues or random black screens that just appear while they’re trying to use their PC. These are the problems Microsoft has admitted to, but there are likely more lurking that haven’t been widely reported yet.
Note: If you’re experiencing issues that aren’t listed here, you’re not alone. Windows Update problems have affected users differently depending on their hardware configurations and installed software.
How to Fix the January 2026 Windows Update Issues
If you’ve already installed KB5074109 and you’re experiencing problems, Microsoft released emergency patches to fix at least two of the issues. You’ll need to download and install these fixes manually from the Microsoft Update Catalog.
Installing the Fix From Microsoft Update Catalog
The fix is available through the Microsoft Update Catalog, but you have to choose the correct update that’s applicable to your computer. Here’s what you need to know:
- There’s a specific update for 24H2 64-bit systems
- A separate update for 25H2 ARM64 systems
- Another for 24H2 ARM64 systems
- And one for 25H2 x64 systems
You just click on the download link on the right side of the page for your specific version, and then install it like you would any other program. It’ll run through an installation wizard and then install the patch to your computer.
Important: You only need to do this if you’ve already installed KB5074109 for Windows 11 25H2 or 24H2. If you’re using Windows Server, Windows 11 23H2, or Windows 10 with Extended Security Updates, check for the corresponding KB number for your system on this WindowsLatest article.
Alternative Solution: Uninstall the Problematic Update
If the fix doesn’t work or you’d rather just remove the problematic update entirely, you can uninstall Windows 11 updates through your system settings. This will revert your system to its previous state before KB5074109 was installed.
If You Haven’t Installed the Update Yet
If the problematic update hasn’t been installed on your system yet, you’re in a better position. My recommendation is to pause Windows updates for a week or two until this mess gets sorted out. You can do this through Windows Update settings, and it’ll prevent the buggy update from being installed automatically.
But here’s the thing – we don’t have any guarantees that the next Windows update for February 2026 is going to be any different or more stable than this one. Windows updates have been really bad for a while now.
A History of Buggy Windows Updates
2025 was a terrible year for Windows updates, especially on Windows 11. There were so many bugs released in updates throughout the year. Let me walk you through some of the major issues:
July 2025: Core Components Breaking
Back in July 2025, there were issues with the Start menu, taskbar, File Explorer, and system settings just breaking because some of the core components didn’t function properly after an update.
October 2025: The Task Manager Bug
In October 2025, there was the Task Manager bug where Task Manager just wouldn’t close. If you pressed the X icon to close it, the window would disappear but Task Manager would still be running in the background, causing a ghost process. This ate up a ton of system resources over time.
USB Devices in Recovery Environment
USB keyboards and mice stopped working in the Windows recovery environment, making it impossible to access the recovery tools and actually fix your PC. Ironically, the issues were most probably caused by the Windows update in the first place.
November 2025: Nvidia Driver Issues
In November of 2025, there was a bad update released for Nvidia that caused a lot of gaming and performance issues.
And now in January of 2026, we’ve got this current mess with all these issues in Windows Update. I don’t see a good future ahead for updates on Windows 11.
My Personal Approach to Windows Updates
To be quite honest with you, I don’t install the latest updates as soon as they’re released because they’re always buggy. And I definitely do not turn on the setting to get the latest updates as soon as they’re available.
I only enable that setting in a virtual machine so I can get the latest updates for Windows 11 installed and test my software Winhance to make sure it works on the latest builds. I also use it when I need to create videos about new features for my viewers on YouTube.
For my main production systems, I wait to see what breaks before I install anything. It’s not an ideal situation, but it’s the reality of Windows updates in 2026.
The Bigger Problem: Continuous Innovation
I want to address a larger issue here with the Windows update system. Microsoft calls it “continuous innovation,” but what it really means is that they’re constantly pushing new features through the update mechanism, whether you want them or not.
According to their documentation, experiences may be introduced in an optional non-security preview release before being made available broadly via a monthly security update or via controlled feature rollout technology. This is exactly what I think the problem is.
I’m not saying the security updates themselves aren’t causing bugs, but I don’t think bundling security updates and features together is the right approach when rolling out updates. Security and features should be separate. I should have a choice to secure my system without accepting Microsoft’s new features.
Remember Windows 7?
Do you remember in Windows 7 when you could choose the updates you wanted to install and the updates you didn’t want to install? You could even ignore specific updates so you weren’t bothered by them again. That level of control is completely gone now.
Bugs in Windows Update have existed for a long time. It’s not just related to Windows 11 updates – previous versions of Windows had issues too. But I really do believe that bundling features with security updates is a problem in today’s day and age, and they need to be separated like they were in Windows 7.
My Take: If you’re experiencing similar frustrations with how Microsoft handles Windows updates, you might want to read about the problems with stock Windows 11 installations that go beyond just update issues.
Conclusion
The January 2026 Windows update situation is just another example of Microsoft’s problematic approach to updates. By bundling experimental features with critical security patches, they’re forcing users to choose between staying secure and maintaining system stability. That’s not a choice anyone should have to make.
If you’ve already installed KB5074109, head to the Microsoft Update Catalog and download the appropriate fix for your system. If you haven’t installed it yet, consider pausing your updates for a week or two until things settle down. And whatever you do, don’t enable that “get the latest updates as soon as they’re available” setting unless you’re running a test machine.
Microsoft needs to go back to separating security updates from feature updates. Users deserve the ability to keep their systems secure without being forced to accept potentially buggy new functionality. Until that happens, we’re stuck in this cycle of problematic updates followed by emergency patches.
Frequently Asked Questions (FAQ)
Is it safe to uninstall the January 2026 Windows update?
Yes, you can safely uninstall KB5074109 if it’s causing problems on your system. While the update includes security patches, Microsoft has released separate fixes for the most critical issues. If you uninstall the problematic update, make sure to pause Windows updates temporarily to prevent it from reinstalling automatically. You can always install it later once Microsoft has resolved the bugs.
What should I do if the fix from Microsoft Update Catalog doesn’t work?
If the emergency patch doesn’t resolve your issues, your best option is to completely uninstall the January 2026 update. You can do this through Settings > Windows Update > Update history > Uninstall updates. Find KB5074109 in the list and remove it. After uninstalling, restart your computer and pause updates for at least a week to give Microsoft time to release a more stable version.
Why does Microsoft bundle features with security updates?
Microsoft calls this approach “continuous innovation,” which allows them to deliver new features more frequently through their servicing technology. They test these features in optional preview updates first, then include them in the following month’s mandatory security release. The problem is that this removes user choice – you can’t get security patches without also accepting the new features, even if those features are buggy or unwanted.
How can I prevent buggy Windows updates from installing automatically?
You have a few options to control when updates install. The simplest is to pause updates through Windows Update settings for up to five weeks at a time. You can also use registry modifications to lock your Windows version and prevent major feature updates while still receiving security patches. For more granular control over which updates install, you’ll need to use Group Policy settings or third-party tools like Winhance.
What other issues have Windows 11 updates caused in the past year?
Windows 11 had a terrible track record throughout 2025. Some of the major issues included broken Start menus and taskbars in July, a Task Manager ghost process bug in October that consumed system resources, USB devices not working in the recovery environment, and problematic Nvidia driver updates in November that caused gaming performance issues. The January 2026 update continues this unfortunate pattern of buggy releases followed by emergency patches.
