A KB update breaks your PC: here's how to identify and revert it without losing files

When a Error installing a KB update in WindowsIt's easy to get overwhelmed: the system keeps insisting, the messages are unclear, and to top it all off, you might experience performance or security problems if you leave it uninstalled. Furthermore, with the end of support for Windows 10 and the arrival of Windows 11 24H2 and 25H2, each A new cumulative patch KB update can make all the difference. between having a protected PC or being an easy target.

In recent months Microsoft has published critical patches such as KB5072033, KB5070773 or KB5071546These patches are designed to correct very specific vulnerabilities and errors (including USB flaws in WinRE or zero-day exploits). Meanwhile, manufacturers like ASUS and Microsoft support itself have provided details. Official methods for troubleshooting KB update installation problemsThis guide covers all of this in both Windows 11 and Windows 10. It organizes all the information, explains it clearly, and expands on what's happening, how to install or repair each KB, and what to do if something goes wrong.

What are KB updates and why do they cause so many problems?

Windows updates identified as KB (Knowledge Base) These are packages that fix bugs, close vulnerabilities, add improvements, and, in some cases, prepare the system for new versions. Each cumulative patch (like KB5072033 for Windows 11 24H2/25H2 o KB5071546 for Windows 10 22H2This includes many internal changes that depend on system files, drivers, network components, or even the Windows Recovery Environment (WinRE).

When a KB update fails to install, it is usually due to corrupted files, unmet dependencies, driver conflicts or previous problems with Windows Update. Sometimes simply trying again is enough; other times, more advanced solutions such as DISM, SFC, manual installation from the Microsoft Update Catalog, or even restoring the system from a restore point are required.7

Recent key updates: KB5072033, KB5070773 and KB5071546

In the most recent patch cycle, Microsoft has distributed updates especially relevant for Windows 11 and Windows 10For example, it stands out KB5072033, a cumulative patch designed to Windows 11 24H2 and 25H2This update is available both via Windows Update and through the Microsoft Update Catalog. It can be downloaded as one or more MSU packages, and its correct installation is essential to keep your system up to date.

Along with this cumulative patch, Microsoft has also released a out-of-band update, KB5070773This update, aimed at Windows 11 builds 24H2 and 25H2, focuses on resolving a very specific but critical bug: USB devices (mice, keyboards, etc.) that stop working in the Windows Recovery Environment (WinRE)which is a problem if you ever need to repair the system and can't manage the recovery environment.

For users who are still in Windows 10 22H2 Under Extended Support Units (ESU), Microsoft offers another important piece: KB5071546, a cumulative patch that fixes multiple vulnerabilities and bugs in this version. Only devices with an active ESU can receive these updates.So if your Windows 10 is not under this program, it will miss out on these latest security patches.

Vulnerabilities and security flaws fixed

Microsoft's latest security bulletins have resolved 57 vulnerabilities in Windows 11all of them classified as “important”. Among them are several rulings of elevation of privilegeswhich allow an attacker to gain SYSTEM privileges, and vulnerabilities of remote code execution (RCE), considered among the most dangerous although, on this occasion, none have received a "critical" label.

Among these corrections, the following stand out: three zero-day failures which were already being actively exploited on the Internet. One of them, identified as CVE-2025-62221, is related to a Memory leak in Cloud Files that allows privileges to be elevated to SYSTEMgiving a local attacker complete control of the system. Another, CVE-2025-64671, is associated with a command injection in GitHub Copilot for JetBrainsThis opens the door to local code execution via malicious files or compromised MCP servers.

The third vulnerability, CVE-2025-54100, affects PowerShell when using Invoke-WebRequestallowing the execution of code embedded in web pages if malicious content is visited and the parameter is not included -UseBasicParsingThese vulnerabilities demonstrate why it is so important. Install KB updates as soon as possibleeven if you have a good antivirus.

How to obtain and prepare for installation of a KB update

Before you rush to install any KB update, it is recommended prepare the system and choose the appropriate installation methodIn the case of patches like KB5072033Microsoft offers standalone MSU packages through the Microsoft Update CatalogThese files may require a specific installation order (for example, first windows11.0-kb5043080-x64… and then windows11.0-kb5072033-x64…), so following official guidelines is crucial.

To get the package, simply access the website of the Microsoft Update CatalogSearch by KB number (such as KB5072033, KB5071546, KB5017271, KB5016688, etc.), and download the version that corresponds to the architecture and editing of your systemOnce all the necessary MSUs have been downloaded, it is recommended place them in the same folder (for example, C:/Packages) to facilitate manual installation using DISM or Windows PowerShell.

Method 1: Install all MSU files from a KB using DISM

When a KB update comes split into multiple MSU files, Microsoft suggests Install them together using DISM (Deployment Image Servicing and Management)The procedure involves downloading all the MSU packages from the corresponding KB (for example, KB5072033) and saving them in a folder such as C:\PackagesThen, the parameter is used /PackagePath DISM so that the tool automatically detects and installs the necessary files based on dependencies.

To apply the update to a PC running Windows, we need to open a Command prompt with administrator privileges and execute a command similar to this: DISM /Online /Add-Package /PackagePath:c:\packages\Windows11.0-KB5072033-x64.msuAlternatively, you can use Windows PowerShell with the command Add-WindowsPackage -Online -PackagePath «c:\packages\Windows11.0-KB5072033-x64.msu»There is also the option of resorting to Windows Update standalone installer to apply the MSU directly.

Method 2: Install each MSU file separately and in order

In other scenarios, Microsoft indicates that it is better Manually install each MSU file one by one and following a strict order.For KB5072033, for example, the package might be required first. windows11.0-kb5043080-x64_9534496720… and later windows11.0-kb5072033-x64_199ed7806a…This order ensures that the prerequisites are met and errors are avoided during installation.

Each of these MSUs can be installed with DISM as with the Windows Update standalone installerThe typical flow would be: download the first file from the Microsoft Update Catalog, run it (or add it with DISM /Online /Add-Package), restart if prompted, and then repeat the process with the next MSU in the list. Respect the indicated sequence The KB documentation is vital to prevent compatibility errors or pending packages from appearing.

Out-of-band update KB5070773: Fixing USB in WinRE

One of the most annoying problems recently seen in Windows 11 24H2 and 25H2 is the bug that causes Mice, keyboards, and other USB devices stop working within the Windows Recovery Environment (WinRE)To resolve this, Microsoft launched the aforementioned KB5070773 as an out-of-band updateThat is, a special patch outside the usual cycle of the second Tuesday of the month.

The experts' recommendation is Install KB5070773 as soon as possibleEven if your system seems to be working fine, you never know when you might need to boot into WinRE to repair Windows. This KB article ensures that... USB input devices function correctly in the recovery environment, avoiding getting "stuck" on a screen where you can't use a mouse or keyboard.

How to check the WinRE version with GetWinReVersion.ps1

To check if your WinRE is up to dateMicrosoft offers a small PowerShell script called GetWinReVersion.ps1This script is mentioned in the official update documentation. KB5050411 for the Windows Recovery Environment in Windows 10 21H2 and 22H2Specifically, in the section “Methods to verify the installed WinRE version”.

Even so, it is important to point out that The rest of the information in that article KB5050411 is directed exclusively to Windows 10 and it's not applicable to Windows 11. What you can use is the GetWinReVersion.ps1 script to check the exact version of WinRE you have installed and confirm whether the updates have been applied correctly or if you need to integrate an additional KB.

Using DISM and SFC to repair corrupted system files

When the problems with the KB seem more profound, it's possible that there are damaged or missing system files that prevent patches from being applied correctly. In these cases, Microsoft recommends using two built-in tools: DISM (Deployment Image Servicing and Management) y SFC (System File Checker).

To begin, open a Command Prompt as administrator (searching for “Command Prompt” and choosing “Run as administrator”) and run the command DISM.exe /Online /Cleanup-image /RestorehealthThis process may take some time, as it checks the integrity of the Windows image and repairs damaged components. When the command finishes with the message “The restore operation completed successfully,” enter sfc /scannow and wait until the verification reaches 100%.

Once the SFC scan is complete, close the command window and try again. Install the KB update that was failingIn many cases, this combination of DISM and SFC manages to resolve persistent Windows Update errors without the need for more drastic measures.

Restore the system or reset Windows if nothing else works

If errors with KB updates have started not long ago and you have a system restore point Before the problem occurred, a good idea is to try restoring your computer to its previous state. System Restore reverts changes to system files, drivers, and key settings, while keeping your personal documents intact.

However, if the problem persists despite trying the troubleshooters, DISM, SFC, and several attempts at manual installation, you might need to... reset the systemBefore doing so, it is essential back up your personal filesSince a factory reset can leave your computer like it just came from the factory, Windows offers options to keep or erase your data, but in any case, it's better to be safe than sorry.

Practical solution: delete the SoftwareDistribution folder

From Microsoft support, many agents recommend a fairly effective solution when Windows Update gets stuck with corrupted updatesClean the downloads folder of updates. That folder is C:\Windows\SoftwareDistribution, and it is where the files downloaded by Windows Update are stored before installation.

If the downloaded KB update is corrupted or incomplete, deleting the contents of C:\Windows\SoftwareDistribution forces Windows to redownload all the information from scratchYou can delete all the files within that folder; if the system won't let you, a trick is to rename it (for example, "SoftwareDistribution_old"). Doing so will cause Windows to create a new, clean folder, and on the next attempt, it will download the updates again.

Uninstall a KB update that is causing problems

Sometimes the problem isn't that the KB isn't installed, but that The system starts to fail right after installation.Screenshots, crashes, terrible performance… In those cases, the wisest course of action is temporarily uninstall the conflicting patch while you wait for Microsoft to release a fixed update.

To remove a KB update from the interface, go to Settings > Windows Update > Update History and select the “Uninstall updates” option. In the list, look for the problematic patch (for example, KB5072033Select it and click "Uninstall". If you prefer to do it via the command line, you can use PowerShell or Command Prompt. wusa.exe /uninstall /kb:5072033 /quiet, replacing the KB number with the one that corresponds to your case.

Compatible with ASUS hardware and MiniPC, desktop and laptop PCs

A large portion of the troubleshooting guides for a KB update have been written with equipment from manufacturers like ASUS with that in mind, including Laptops, desktops, All-in-Ones, portable consoles, motherboards, MiniPCs and NUCsAmong the models affected by these recommendations are listed products such as ELMGR7093DX4, GR70, multiple MiniPC PB50, PB60, PB61, PB62, the PN series (PN40, PN41, PN42, PN50, PN52, PN53, PN54, PN60, PN61, PN62, PN63, PN64, PN65, PN80, PN865, etc.), as well as other equipment from the PL and PA ranges.

In all these devices, ASUS emphasizes the importance of Keep your BIOS and drivers updated using their own tools (MyASUS, EZ Flash, Firmware Update) and the official website. Regularly updating BIOS, Windows, and drivers helps to Improve stability, performance, and compatibility With the new Microsoft KB articles, installation errors and problems arising from recent patches are being drastically reduced.

Considering all of the above, it is clear that a Windows KB updates are both a critical line of defense and a potential source of headaches.The key is knowing the relevant patches (KB5072033, KB5070773, KB5071546 and others), knowing how to install them manually or automatically, applying the built-in repair tools (DISM, SFC, troubleshooter, system restore), and not hesitating to uninstall a problematic patch if your computer notices it's causing problems. With these resources at hand, it's much easier to keep Windows 10 and Windows 11 updated, secure, and running smoothly.