Windows 10 and Windows 11 have had their share of problems. According to the Microsoft Security Response Center (MSRC), the operating system experienced 11791 security vulnerabilities throughout 2025 (Jan-December 2025), a record 845% increase compared to the previous year. 2024.
Microsoft quickly moves in to fix many of these security holes in the system, so it’s essential to stay up to date. Yet, Windows updates can bring their own problems. This guide shows what to do when an update does more harm than good.
Note: if a problem here is marked as “FIXED,” it means Microsoft has rolled out an update that fixes the problem, and the solution is simply to make sure your system is fully updated. If a problem is not yet “FIXED,” then either read that entry for workarounds to that specific problem or scroll down the page for advice on how to roll back updates.
Starting November 2025, Microsoft has simplified Windows 11 update titles. This means version numbers such as 24H2/25H2 will not appear in the update name in Settings app. The new updates are named directly after a KB number and the OS build number. However, if you’re on an outdated 22H2/23H2 version, you should migrate to the supported version numbers, 24H2/25H2.
Table of Contents
- [Not Fixed] January 24, 2026, Windows 11, KB5078127 (Builds 26200.7628 and 26100.7628) Out-of-Band (OOB) Update
- [Partially Fixed] January 17, 2026, Windows 11 KB5077744 (Builds 26200.7627 and 26100.7627) Out-of-Band Update
- [Partially Fixed] January 13, 2026, Windows 11 KB5074109 (Builds 26200.7623 and 26100.7623) Security Update
- [Fixed] December 9, 2025, Windows 11, KB5072033 (Builds 26200.7462 and 26100.7462) Security Update
- [Fixed] December 1, 2025, Windows 11, KB5070311 (Builds 26200.7309 and 26100.7309) Non-Security Update
- [Not Fixed] January 24, 2026, Windows 10 Version 22H2, KB5078129 Out-of-Band (OOB) Update
- [Partially Fixed] January 17, 2026, Windows 10 Version 22H2, KB5077796 Out-of-Band (OOB) Update
- [Fixed] January 13, 2026, Windows 10 Version 22H2, KB5073724 ESU Update
- [No Issues] December 18, 2025, Windows 10 Version 22H2, KB5074976 Out-of-Band (OOB) Update
- Fix and Avoid Broken Windows Updates
- Install Optional Updates
- Uninstall Windows Updates
- How to Roll Back Windows Builds
- Check Your Windows Build
- Pause Windows Updates
- Completely Block Windows Updates
[Not Fixed] January 24, 2026, Windows 11, KB5078127 (Builds 26200.7628 and 26100.7628) Out-of-Band (OOB) Update
Problems: Outlook glitches | Missing password icon | Black screens | Broken file explorer
It is rare for Microsoft to issue a second emergency out-of-band update within the same month, which is what makes KB5078127 a bit of an anomaly. While it did manage to solve a few problems for Outlook hangs and freezes, such as issues due to a corrupt PST file, some users continued to report a broken Outlook. We have a guide that addresses this very error on how to repair corrupt Outlook data files.
The missing password icon issue has been persistent all month in January, 2026. Somehow, the issue could not be resolved. this problem can only be addressed in subsequent patches. Users have also reported issues due to black screens and broken file explorers, for which we have provided solutions a bit below this.
[Partially Fixed] January 17, 2026, Windows 11 KB5077744 (Builds 26200.7627 and 26100.7627) Out-of-Band Update
Problems: Installation failures | DRM Playback performance issues | Missing password icon
KB5077744 was supposed to be an out-of-band (OOB) update but it was reported to be so “borked” that another OOB had to be released to fix its errors. It did resolve a few errors in earlier updates, for example, there are no longer any sign-in failures with Remote Desktop.
On the flipside, some users reported password icon missing in the lockscreen. If you’re using playback software, you might run into DRM performance issues. For the most part, however, installation failures are a major sideshow of KB5077744. If you didn’t receive this update patch, you are good to go as you can directly move on to the next OOB update. Failure to install was a big problem with this update.
In the past, Windows users have experienced installation failures with other 0x800 error codes such as 0x800F0991, 0x800F0922, 0x80071A2D, and 0x800F081F. For such errors, there are many solutions which you can find on Microsoft website. For example, with 0x80070570, you can do Startup Repair and empty the SoftwareDistribution folder.
If you’ve been struggling with persistent update installation problems in Windows, try using Quick Assist to reach Microsoft Support. They will use this app to create a restore point, and fix the bugs to restart your update process. It’s an amazing way to troubleshoot any Windows update problems, as you just have to sit back and let an official Microsoft support agent solve your problem.
To deal with update failures, you may want to pause the update for a few weeks until next month when the issues are no longer a concern. Opting for a cloud-based device reset (while keeping your files) is the best way to deal with any installation errors, but it consumes a lot of time.
Apart from Quick Assist, it’s also a good idea to run the Windows 11 Update Troubleshooter from System -> Troubleshoot -> Other troubleshooters. It will fix any issues that were preventing installation, but mostly security settings, missing or corrupt files, or problems with Service Registration. Other issues could be connected to Windows Network Diagnostics, IsPostback_RC_PendingUpdates, WaaSMedicService, and BITS service.
If you can’t install an update on your PC on your normal schedule, it’s always easier to do it from the Microsoft Update Catalog. Remember to choose the correct download version (x64 or ARM) in the pop-up menu. The download files are usually more than a gigabyte. To run them, you just have to double-click once. In case you’re dealing with a frozen or stuck update in Windows, we have many solutions.
Note: if you’ve missed many updates, we recommend reinstalling Windows 11 from the cloud via Windows installation assistant, ISO, media creation, or another tool. Gong for a cloud download reset does the same job, but in much less time.
While Windows 11 is supporting 23H2 updates simultaneously, it is currently force installing 24H2 on the users in the previous version. 22H2 updates are no longer supported. You will need to have the Get the latest updates as soon as they’re available option active. If your PC is facing a “compatibility hold” while migrating from 23H2 to 24H2 or 25H2, follow one of our fixes to ensure a smooth migration.
Note: Migrating from 24H2 to 25H2 would require an enablement package which you can keep track of on the official Windows blog.
The biggest problem with latest Windows 11 updates is that they may not be supported on 23H2 or 22H2 devices. If you have not yet migrated to 24H2, we recommend you to do so. A clean install could yield better results. Do note that some Microsoft devices have transitioned to a new Administrator Protection feature.
Additionally, you can try resetting Windows update components using commands like net stop wuauserv. If the update keeps reinstalling, apply the same fixes as you would for a Windows infinite reboot loop problem.
For the first time ever, Windows 11 users can access a new disaster recovery feature, Quick Machine Recovery from Settings -> System -> Recovery. It is quite helpful as it sends your PC to the Windows Recovery Environment any moment it fails to boot properly. You can say goodbye to boot failures with this detailed guide on QMR.
[Partially Fixed] January 13, 2026, Windows 11 KB5074109 (Builds 26200.7623 and 26100.7623) Security Update
Problems: Unresponsive applications | Authentication errors | Remote desktop failures | Boot failures | File Explorer glitches | Hardware issues
KB5074109, the first Patch Tuesday security update for 2026, has been instead given a less attractive label, of a “disaster patch.” Firstly, the update contains many fixes and improvements in compatibility and networking, and secure boot problems, and it also overcomes the update problems last month with WSL.
However, on the other hand, black screen issues and boot failures were widely reported. We have many tutorials to deal with black screen problems which can sometimes be due to screen brightness or graphic drivers. For blue screen of death issues (BSoD), several straightforward solutions are available. If your taskbar icons are missing, follow these simple tips to fix the issue.
Application freezes and crashes were the next big challenge. The classic version of Outlook hung up on many users, especially when using POP accounts or clicking PST files.
There were minor File Explorer issues with system glitches during Folder naming. Some users were unable to format USB drives with FAT32. We have addressed the solutions to a wide variety of File Explorer issues. A few other issues such as Remote Desktop access problems with Azure and Microsoft 365 were addressed in subsequent OOB updates.
[Fixed] December 9, 2025, Windows 11, KB5072033 (Builds 26200.7462 and 26100.7462) Security Update
Problems: WSL errors | Installation failures | Dell PC freezes and BIOS conflicts | Start menu errors
KB5072033 is a security update that addresses various fixes for Copilot, white flash displaying in File Explorer, problems with physical network adapter (NIC) bindings after a host restart, PowerShell 5.1 not having a web request confirmation, and the lack of an automatic update backup.
Other issues with this update include WSL problems and black screens, which have been addressed in higher updates.
[Fixed] December 1, 2025, Windows 11, KB5070311 (Builds 26200.7309 and 26100.7309) Non-Security Update
Problems: White flash bug in File Explorer | Language pack errors | Password icon missing in lock screen sign-in options | Installation failures
KB5070311, the month-end update for November 2025 was released late on December 1, 2025. It provides simplified Windows update titles, Windows Secure Boot certificate expirations which will expire in June 2026, a new Recommended section in File Explorer (which many are finding annoying), animations in app groups on the taskbar, and many AI features for Copilot+ PCs.
The biggest known issue with KB5070311 is a File Explorer error where it might flash with a white screen in dark mode. The error was promptly rectified in the Patch Tuesday update for December 2025.
Tip: also, follow our detailed guide to identify and resolve the most common Windows errors. Other ways to deal with frozen updates are the Memory Diagnostic tool. The problem is also connected to your RAM performance. In many cases, dual-channel RAM boosts a PC’s performance,
Note: Microsoft has recently announced that it will officially stop sending free software updates to all Windows 10 devices. However, there are certain conditions and exceptions such as ESU notifications which you should keep track of.
[Not Fixed] January 24, 2026, Windows 10 Version 22H2, KB5078129 Out-of-Band (OOB) Update
Problems: Outlook continues to hang and freeze | Azure/WVD failures | Applications unresponsive due to cloud storage failures | Email redownloading
KB5078129 was the second OOB update for January, partly brought in to resolve the problems of KB50777796, but also the earlier Windows 10 ESU updates. While certain problems such as Shutdown and restart issues in the previous update as well as system instability were addressed, it has brought back those same issues.
While KB5078129 was expected to resolve the problems due to Azure Virtual Desktop and Microsoft 365 not logging in properly, somehow that very issue resurfaced. With the Outlook app, unresponsiveness continued with users facing missing sent emails and previous emails being downloaded all over again. Some of the Outlook issue fixes have been covered in this guide.
[Partially Fixed] January 17, 2026, Windows 10 Version 22H2, KB5077796 Out-of-Band (OOB) Update
Problems: Shutdown and restart issues | Installation problems | Remote desktop issues
To address issues due to Remote Desktop, Azure Virtual Desktop authentication failures, and a few others, the OOB update KB5077796 was released. While resolving the problems of earlier updates, KB5077796 had its own failures, such as a failure to install with error code 0x80070643, shutdown and restart problems in which your Windows 10 laptop may fail to shut down or restart entirely. Clearing your Windows update cache is a proper way to solve the last one.
[Fixed] January 13, 2026, Windows 10 Version 22H2, KB5073724 ESU Update
Problems: Azure connection and authentication failures | Unresponsive apps during cloud storage | System stability and installation failures
If you’ve enrolled into the Windows ESU program, you will receive the latest security updates detailing security fixes and improvements for Windows 10. To migrate to ESU successfully, ensure your Windows 10 device is not in kiosk mode, joined to an Active Directory domain or Microsoft Entra and isn’t a Microsoft child account.
Once you complete this update successfully, you will see a message that says “Your version of Windows has reached the end of support” displayed correctly in the Windows Update Settings page.
KB5073724 is Windows 10’s first ESU update for 2026. It primarily removed drivers such as agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys (x86), as they will not be supported by modern hardware. It issues new Secure Boot certificates and updates a Windows core component, WinSqlite3.dll.
Some of the well-known issues in the KB5073724 updates are connection and authentication failures in Microsoft 365 and Azure Virtual Desktop. Luckily, it was addressed in a subsequent OOB update. In addition, certain apps like Outlook have been acting unresponsive while saving files in cloud storage locations. Some users have also reported system instability due to computer freezes and failures to installation, with certain installations hanging at 20% level.
[No Issues] December 18, 2025, Windows 10 Version 22H2, KB5074976 Out-of-Band (OOB) Update
KB5074976 is an out-of-band Windows 10 update under its ESU program that aims to address some of the issues raised in the earlier KB5071546 update. The problems due to Message queuing (MSMQ) in Windows server environments which became inactive under heavy load, has been corrected.
Fix and Avoid Broken Windows Updates
If the problem you’ve encountered with a new Windows update is that the install stops at a certain percentage, or more generally, that it’s failing to install altogether, try installing the update from PowerShell.
Open PowerShell as administrator by typing it into the Start menu search. In PowerShell, use this command:
Install-Module PSWindowsUpdate
It may ask you to install and import the NuGet provider. Press Y for Yes, and let it install the package.
You may get a warning that you are installing the modules from an untrusted repository. Type A to allow all the changes.
Check for the latest Windows updates by typing the following into PowerShell:
Get-WindowsUpdate
Once you’ve confirmed that there are updates to install, type the following command. You may further be asked if you want to perform this action, to which you must type A to finalize.
Install-WindowsUpdate
Wait for the broken Windows updates to heal themselves. They will automatically execute in the PowerShell window.
Tip: how does PowerShell differ from Command Prompt? Read on to find out.
Install Optional Updates
If you access the Windows update screen by going to Settings -> Windows Update -> Advanced Options -> Additional Options, you will find the Optional Updates menu.
These updates are designed specifically to address features, quality, and driver issues for recent Windows updates. They become “proper” updates a few weeks later, once they’ve been thoroughly tested.
These updates are still pretty stable, though, and may be worth a shot if a recent update has broken something in Windows.
Uninstall Windows Updates
You can uninstall smaller Windows updates (to roll back builds, see the next section) if needed.
In Windows 10, go to Control Panel -> Programs -> Programs and Features -> Installed updates.
Scroll down in the main pane to the Microsoft Windows heading, and you’ll see all of the KB and security updates for Windows 10, along with the install dates. Right-click the one you want to uninstall, and reboot your PC.
Windows 11 also has the option to uninstall recent updates. Visit Settings -> Windows Update -> Update History -> Uninstall updates, and click the Uninstall button next to the update you want to eliminate. In this example, we are uninstalling an update for the month of May 2024.
How to Roll Back Windows Builds
After every major update, Windows gives you a 10-day window to roll back to a previous version. It’s a useful feature and should give you enough time to judge whether you have a problematic update on your hands. Of course, this won’t recover your files if Windows deletes them, but at least you’ll be on a more stable version of the OS.
Go to Settings -> Update & security -> Recovery in Windows 10 or Settings -> System -> Recovery in Windows 11.
Below Reset this PC is the option to Go back to the previous version of Windows.
Click Get started, then follow the steps to roll back Windows. Again, this option is only available for 10 days after a Windows build update.
Check Your Windows Build
Before looking into rolling back and fixing broken Windows updates, check the build of Windows you’re currently using to confirm which issues are affecting you.
Go to Settings -> Windows Update -> Update history (in Windows 11) or Settings -> Update & Security -> Windows Update -> View Update history (in Windows 10).
In the new window, click the arrow next to Feature Updates to see the version of Windows you’re currently using, and click Quality Updates to see all of the smaller KB updates you have installed.
You will also find Definition Updates, which are security intelligence updates related to Microsoft Defender.
At the bottom of the list, you may find Other Updates concerning programs such as the Windows Malicious Software Removal tool, Intelligence updates, and security patches.
Pause Windows Updates
To avoid getting the above update problems and more, take over control when Windows updates. This way, you can hold off getting updates the moment Microsoft rolls them out, monitor the news for a bit to see if any significant errors crop up, then manually do the update yourself.
If you’re running Windows 11, go to Settings -> Windows Update -> More options -> Pause updates, and choose the number of weeks you wish to defer updates in the future (from the default of one week to up to five weeks).
In Windows 10 Home, Pro, Enterprise, Education, or S, postpone updates by checking the same option under Settings -> Update & Security -> Windows Update. On some Windows 10 versions, it may be referred to as Defer instead of Pause and under a different heading.
Tip: did you know that Windows comes with a Super Administrator account? Learn how to activate it.
Completely Block Windows Updates
If you want to completely block Windows updates indefinitely, disable the main Windows Update service through the Registry Editor.
Click Start, type regedit, open the Registry Editor, and navigate to the following path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSMedicSvc
Right-click on Start to modify it, then change its Value data to 4.
Reboot your PC, then go to the Services window by using the Search function in Windows. Disable the Windows Update service in the same window by setting its startup type as Disabled.
Few things on PC are more frustrating than an update – ostensibly to improve performance – borking your system. Unfortunately, Microsoft still has work to do in this respect. Other issues with Windows include the Microsoft Store not working and a malfunctioning microphone. We can help with these, too!