How to Fix Windows Update Error (Windows 10 and 11)

You click “Check for updates” and it fails. You try again, and it fails again. Maybe you see a code like 0x80070002. Maybe the bar sits at 0% for an hour. Maybe the PC says “We couldn’t complete the updates, undoing changes” and then loops. It is stressful, because updates carry security fixes, and you have work to finish. Many guides make it worse. They tell you to rename system folders or reset the whole PC, and they say little about the risk.

This guide shows how to fix windows update error problems in a safe order. I compared the top guides on this topic and read Microsoft’s own repair notes and a June 2026 report on a new update bug. Then I put the fixes in order from easy and safe to hard and risky. You also get a code lookup table, a symptom table, and a backup checklist. I checked the commands and key claims against Microsoft Learn, Petri, and BleepingComputer on November 4, 2026. I have not run them on a test PC, so I mark where you should be careful.

Quick answer: To fix a Windows update error, first restart your PC and make sure you have free disk space and a working internet link. Then run the Windows Update troubleshooter. If that fails, reset the update components, run DISM and SFC, and install the update by hand from the Microsoft Update Catalog. Use System Restore, an in-place upgrade, or Reset this PC only as a last resort.

Why Does Windows Update Fail?

Before you fix anything, it helps to know why updates fail. The cause tells you which fix to try first. The top guides name a handful of causes, and they overlap a lot.

Most Common Causes

• Corrupt or missing update files. Action1 lists corrupt update files as a top cause. Microsoft Learn describes damage to the component store, the area Windows uses to hold update parts.
• Not enough free disk space. Update files need room to download and unpack. Petri and Action1 both list low space.
• A stopped or stuck update service. EaseUS lists a stopped update service, and Action1 notes an overloaded update queue.
• Old or clashing drivers and devices. Action1 and Petri both mention hardware and driver conflicts.
• Security software in the way. EaseUS lists third-party antivirus, and Petri notes that security tools can block updates.
• A weak or broken internet link. AVG notes that a slow connection can stop a download.
• Temporary files left over from an earlier try. EaseUS lists leftover temporary update files.

Why It Matters Which One You Have

Each cause has a different fix. Low space needs cleanup, not a reset. A stopped service needs a restart, not a reinstall. Corrupt files need DISM and SFC. If you try the big fixes first, you can lose time or even data. So we start with the safe, quick checks and move up only when needed.

Why You Should Not Ignore Update Errors

Petri says Windows Update is critical for your device, and Action1 asks why you should install critical updates. Updates carry security fixes and bug fixes. A PC that keeps failing to update falls behind. That raises the risk of problems later. So it is worth a calm, step-by-step fix, not a quick workaround.

The good news is that most update errors have a fix. You do not need to reinstall Windows in most cases. The ladder below is built to avoid that.

Before You Start: A Safe Checklist

Spend five minutes on this list. It can save you hours. Action1 offers a pre-update checklist, and EaseUS puts data safety first. Our version adds more safety steps than either one.

Back Up What You Cannot Lose

Most fixes below do not touch your files. But the last-resort fixes can. Copy your key files to an external drive or a cloud folder. This includes documents, photos, and anything you cannot replace. If Windows will not boot, you can still pull files later, but a backup is far easier.

Quick Pre Fix Checklist

• Plug in your laptop. A dead battery during an update can cause trouble.
• Check your free space. As a rule of thumb, keep 20 GB or more free before a big update. This number is my suggestion, not Microsoft’s rule.
• Use a wired or strong connection. A weak signal can break a download.
• Unplug extra USB devices. AVG and Action1 both suggest this to rule out hardware clashes.
• Use an admin account. Many fixes need admin rights. Action1 lists “access denied” as a known error.
• Check the date and time. A wrong clock can block secure connections.
• Write down the error code. You will need it in the next section.
• Find your BitLocker recovery key if you use BitLocker. Big repairs can ask for it. This tip is my suggestion.

Safe Fixes vs Risky Fixes

Not every fix has the same risk. We label each fix in this guide so you can see the trade-off at a glance.

Risk level	What it means	Examples in this guide
Safe	Changes nothing that you would miss	Restart, troubleshooter, freeing space
Low	Changes update settings or system files in a repairable way	Resetting update components, DISM, SFC
Medium	Removes or replaces an update or a system state	Uninstalling an update, System Restore
High	Can remove apps or settings	In-place upgrade, Reset this PC, clean install

One Rule: Rename, Do Not Delete

Several guides tell you to clear the SoftwareDistribution folder. Petri and Action1 do it by renaming the folder, and Technobezz uses a delete command. Renaming keeps the old copy, so you can go back. Deleting is permanent. So in this guide, we rename. It is the safer habit.

Find Your Windows Update Error First

Most guides tell you to try fixes at random. A better way is to read the clue first. The clue is either a symptom or an error code. Spend two minutes here, and you will pick the right fix faster.

Where to Find the Error Code

Open Settings, go to Windows Update, and open Update history. Failed updates are listed there, and many show an error code. Write it down exactly, including the “0x” at the start. The menu names can differ by Windows build, so look for the update history link if you do not see it right away.

If there is no code, note the message instead. Phrases like “Something went wrong” or “We couldn’t complete the updates” are also useful clues.

IT staff can go deeper. Microsoft Learn points to the setup event log and to the CBS.log file, which sits in the Windows Logs folder. Most home users will not need those.

Match Your Symptom to a Fix

Use this table to jump to the best starting point.

What you see	Likely cause	Start with
Update fails with a code	Corrupt files, a service, or a clash	The code table, then the fix ladder
Download stuck at 0%	Update service or cache problem	Easy fixes, then reset components
Install stuck at a percent for a long time	A hang during install	Wait, then restart; see the stuck updates section
“Something went wrong”	A general failure	Troubleshooter, then reset components
“We couldn’t complete the updates, undoing changes”	A failed install rolled back	See the undoing changes section
Fails again and again	Corrupt system files	DISM and SFC
Works on a friend’s PC but not yours	Local files, drivers, or security software	Easy fixes, then system repair
Fails right after a big Windows upgrade	A known 2026 issue	See the 2026 upgrade-path section

A Note on Waiting

An update that looks stuck may just be slow. Petri notes that you may need to wait on slow updates. If your drive light is still blinking and your PC is warm, give it time. If nothing changes after a long wait, move on to the fixes.

Windows Update Error Codes and What They Mean

An error code is a short label for what went wrong. You do not need to learn them. You only need to match yours to a cause, then pick a fix. The meanings below come from Action1, Microsoft Learn, Technobezz, and BleepingComputer. I list only meanings that one of those pages gives.

Update Error Code Lookup Table

Code	What it points to	Start with
0x80070002	File not found (missing or corrupt file, or an incomplete update)	Reset components, then DISM and SFC
0x80070003	Path not found	Reset components, then DISM and SFC
0x80070005	Access denied, often low admin rights	Sign in as an admin; check security software
0x80073712	Component store is corrupt or inconsistent	DISM, then SFC
0x800736CC	File hash mismatch	DISM, then SFC
0x800f0831	Component store corrupted	DISM, then SFC
0x800f081f	Repair source is missing	DISM with a good source, or manual install
0x800f0906	Download failed for a repair or feature file	Check internet; try DISM again
0x8024402F	Update service not running	Restart the update services
0x80244022	Internet connection problem	Check the connection; retry
0x8024002E	Windows Update service is disabled	Turn the service back on
0x80080005	Server execution failure	Restart the update services; check security software
0x80070643	Recovery partition too small (tied to one recovery update, per Technobezz)	See the note below
0x800f0993	A 2026 upgrade-path issue (per BleepingComputer)	See the 2026 upgrade-path section

The “Start with” column is my suggestion. The meanings come from the sources above.

Codes I Could Not Verify

You may also see 0x800f0922, 0x80248007, 0x8024a105, 0x8024d001, or 0x800704c7. Many sites write about these codes, but I could not confirm their meanings from the pages I read. For these, use the full fix ladder below, in order. Do not trust any page that gives a one-click fix for a code without explaining the cause.

A Note on 0x80070643

Technobezz says this code can tie to a Windows Recovery Environment update when the recovery partition is too small, and that you need at least 250 MB free there. Its other free-space figures may be out of date, so check Microsoft’s current guidance before you act. Treat resizing a recovery partition as an advanced job, and back up first.

What If Your Code Is Not Here?

Search for the exact code with the word “Windows Update”. Then run the safe fixes first. Most codes point to one of four causes: a damaged file, a stopped service, a connection problem, or a permission problem. The same ladder covers all four.

Easy Fixes to Try First (Safe)

Start here. These fixes are safe, and they solve more cases than you might expect. Petri even opens with “Seriously – restart your Windows PC.” Try each one, and test Windows Update after each.

Fix 1: Restart Your PC

Restart, do not just shut down. Restart clears the memory and ends stuck processes. Petri says a restart can clear temporary glitches, and Action1 lists it as the first step. After the PC is back, go to Settings, open Windows Update, and select Check for updates.

Risk: safe. Time: two minutes.

Fix 2: Free Up Disk Space

Low space is a common cause. Open Settings, go to System, and open Storage. Remove files you do not need. You can also run Disk Cleanup, or use Storage Sense if you see it. Empty the Recycle Bin when you are done.

Avoid heavy “PC cleaner” tools. AVG itself warns that cleaners may remove cookies and history, so you may need to sign back in to sites.

Risk: safe. Time: five to fifteen minutes.

Fix 3: Check Your Connection and Devices

Move closer to your router, or plug in a cable. Unplug USB drives, printers, and other extras that you do not need. AVG and Action1 both suggest this. Then try the update again.

Risk: safe. Time: three minutes.

Fix 4: Run the Windows Update Troubleshooter

Windows has a built-in tool that checks the update service and tries to fix common problems. In Windows 11, open Settings, go to System, then Troubleshoot, then Other troubleshooters, and run the Windows Update one. In Windows 10, look under Update & Security, then Troubleshoot. Petri uses the Windows 11 path in its steps and the Windows 10 path in its FAQ. Menu names can change, so if you do not see the option, search Settings for “troubleshoot”.

Let it finish and apply any fix it finds. Then restart and check for updates again.

Risk: safe. Time: five minutes.

Fix 5: Check Drivers and Security Software

Old drivers can clash with updates. Action1 and AVG both mention this. Look in Windows Update for optional driver updates. If you use third-party antivirus, EaseUS lists it as a possible cause. Petri suggests turning it off for a short time. If you do this, turn it back on right after the test. Do not leave your PC unprotected.

Risk: low. Time: ten minutes.

When to Move On

If the update still fails after these five fixes, it is time to look deeper. Move on to resetting the update components.

Fix 6: Reset Windows Update Components (Low Risk)

This is the fix that solves many stubborn errors. It stops the update services, renames two folders that hold update data, and starts the services again. Windows then builds fresh copies. Petri, Action1, and AVG all cover this method. It is also what people mean when they search “reset windows update components.”

What the Two Folders Do

• SoftwareDistribution holds downloaded update files.
• catroot2 holds signature data that Windows uses to check updates.

If these folders hold bad data, updates keep failing. A rename makes Windows create new ones. Because you rename and do not delete, the old copies stay on your drive as .old folders.

Steps

1. Open the Start menu, type cmd, right-click Command Prompt, and choose Run as administrator.
2. Stop the four services by typing each line and pressing Enter:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

3. Rename the two folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

4. Start the four services again:

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. Restart your PC. Then open Windows Update and check for updates.

These commands match the ones in Petri’s and Action1’s guides. Copy them exactly, and make sure the window says “Administrator.”

What to Expect

The next update check may take longer than usual. Windows has to rebuild its update records. Your update history may also look blank for a while. This is normal. Give it time before you decide it failed.

If a Command Gives an Error

An “access denied” message usually means the window is not running as admin. Close it and reopen it with admin rights. A message that a service is not running just means it was already off. Move on to the next line. If the rename fails because files are in use, restart in Safe Mode and try again. Action1 uses Safe Mode for this step.

Why Not Delete the Folders?

A few guides use a delete command. That is permanent. If something goes wrong, you cannot go back. Renaming costs nothing, and it keeps your options open. You can delete the .old folders later, once updates work and you are sure you do not need them.

A Note on Registry Fixes

EaseUS suggests resetting Windows Update registry keys with a downloaded file. I do not recommend this. Downloading a registry file from a web page and running it is risky, and you cannot easily undo it. The steps above reach the same goal without the risk.

Risk: low. Time: ten to fifteen minutes.

Fix 7: Repair System Files With DISM and SFC (Low Risk)

If update files in the system are damaged, no reset will help. You need to repair them. Two built-in tools do this: DISM and SFC. Microsoft Learn, Petri, and EaseUS cover both. Action1 and AVG cover SFC. Microsoft’s own page names DISM as the main repair tool.

What Each Tool Does

• DISM repairs the Windows image and the component store. This is where update parts live.
• SFC (System File Checker) scans protected system files and replaces damaged ones.

Run DISM first, then SFC. That is the order Microsoft Learn uses.

Steps

1. Open Command Prompt as administrator, as before.
2. Run DISM to check and repair the image. Petri lists a scan and a restore command:

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

3. Wait for it to reach 100%. It can look stuck for a while. Do not close the window.
4. Run SFC:

sfc /scannow

5. Restart your PC and check for updates again.

What the Results Mean

SFC may say it found nothing wrong, or that it repaired files, or that it found problems it could not fix. If SFC could not fix something, run DISM again and then SFC again. Microsoft Learn says DISM repair works best when the PC can reach Windows Update, because that is where it gets good copies of files.

If DISM Fails

If DISM says a source is missing, it cannot find good copies. Microsoft Learn describes a repair source option for IT staff. It also notes that a repair source must match your Windows version. The error 0x800f081f in our code table means exactly this. For most home users, the next step is to install the update by hand, which is the next fix.

Where the Logs Are

Microsoft Learn says to check the CBS.log file for details when DISM does not succeed. It sits in the Windows Logs folder. This is an advanced step. You do not need it unless you work in IT or need to report the problem to support.

Why This Works When Other Fixes Do Not

Updates build on your existing system files. If those files are damaged, a new update cannot attach to them. Resetting folders will not help in that case. DISM and SFC repair the base, so the next update has a clean place to land.

Risk: low. Time: fifteen to forty-five minutes.

Fix 8: Install the Update by Hand (Low Risk)

If Windows Update keeps failing on one update, you can skip the update tool and install that update yourself. Petri and AVG both cover this method. It uses the Microsoft Update Catalog, which is Microsoft’s own download site for updates.

Why This Works

Windows Update has to find, download, check, and install an update in one go. Any broken piece in that chain can stop it. A manual install skips the finding and downloading part. You get the file, and you run it.

Steps

1. Note the KB number of the update that fails. You can see it in Update history. It looks like KB followed by digits.
2. Go to the Microsoft Update Catalog at catalog.update.microsoft.com.
3. Type the KB number in the search box and press Enter.
4. Pick the version that matches your PC. Check your Windows version and whether your PC is 64-bit or Arm. A wrong match will not install.
5. Click Download, then click the link that appears, and save the file. It will usually end in .msu.
6. Double-click the file and follow the prompts.
7. Restart when it asks.

How to Check Your Windows Version

Press the Windows key and R together, type winver, and press Enter. A small window shows your Windows version and build. Use it to pick the right file.

Safety Tips for Manual Installs

• Only use the official catalog. Do not download update files from other sites. Fake sites can carry malware.
• Check the KB number twice. A wrong update can waste time.
• Keep the PC plugged in during the install.
• Do not interrupt it. Even if it looks stuck, give it time.

When a Manual Install Also Fails

If the manual install fails, read the message. It may give a new error code, and that code can help you pick the next fix. A failed manual install often means damaged system files, so go back to DISM and SFC if you skipped them.

What About Feature Updates?

For a big version update, Action1 suggests downloading the latest feature update from Microsoft. The Media Creation Tool is Microsoft’s usual way to do this. A feature update is larger and takes longer than a monthly update, so keep your backup ready first.

Risk: low. Time: fifteen to thirty minutes.

Last Resorts If Nothing Else Works

If you reached this section, the safe and low-risk fixes did not work. Do not panic. You still have options. But these steps change more on your PC, so back up first. Petri groups them under “If all else fails,” and we use the same order, from least to most drastic.

Fix 9: Uninstall the Latest Update (Medium Risk)

Sometimes a recent update causes the trouble. EaseUS calls one of its fixes “System Restore,” but its steps actually uninstall the latest update. They are two different things, so we keep them apart here.

Open Settings, go to Windows Update, then Update history, and look for the Uninstall updates link. Pick the most recent update, and remove it. Then restart and try again. Use this when problems began right after one update.

Risk: medium. Time: ten minutes.

Fix 10: Use System Restore (Medium Risk)

System Restore takes your system files, programs, and settings back to an earlier restore point. Action1 notes that it does not affect personal files. It only helps if you or Windows made a restore point before the problem began. Search the Start menu for “Create a restore point” and open System Restore from there.

If you have no restore points, this fix is not available. Pick the date before the trouble started. Programs you installed after that date may be removed.

Risk: medium. Time: twenty to forty minutes.

Fix 11: Do an In-Place Upgrade (High Risk)

An in-place upgrade reinstalls Windows over itself. It keeps your files and apps when you choose that option. Petri puts it before a full reset, and a Microsoft notice reported by BleepingComputer on June 10, 2026 names it as a fix for one upgrade-path bug. Technobezz also lists it as the last repair step.

There are two ways to start it:

• Open Windows Update settings and look for a Reinstall now option, as Petri describes. Petri gives the path as Windows Update, Advanced options, Recovery, then Fix problems using Windows Update. Petri says your data, files, and apps stay.
• Download Windows installation media from Microsoft, run it from inside Windows, and choose to keep your files and apps.

This takes a long time, and your PC will restart several times. Do not shut it off. Make sure you have a backup and your BitLocker key if you use it.

Risk: high. Time: one to two hours.

Fix 12: Reset This PC (High Risk)

Reset this PC reinstalls Windows. You can choose to keep your personal files, but apps and settings are removed. Petri says most personal folders, such as Documents, Downloads, and Pictures, can be kept, but Windows and all apps are wiped. Back up first anyway.

Open Settings, go to System, then Recovery, and select Reset this PC. Follow the prompts.

Risk: high. Time: one to three hours.

Fix 13: Clean Install (Highest Risk)

A clean install erases the drive and installs Windows fresh. EaseUS lists it as the last step, and AVG says to allow several hours. Use this only if nothing else works or your PC is badly damaged. Have your product key ready if you need it, and back up everything first.

Is It Time to Check Your Hardware?

If updates fail even after a clean install, the problem may be hardware, such as a failing drive or memory. Action1 notes that hardware conflicts can cause trouble. At that point, see a technician.

The 2026 Upgrade-Path Error (0x80073712 and 0x800f0993)

This section covers a newer problem that most guides do not mention. BleepingComputer reported it on June 10, 2026, based on a Microsoft notice. If your updates began failing after a big Windows upgrade, read on.

What Is Happening

Some PCs that were upgraded to Windows 11 24H2 or 25H2 cannot install the monthly cumulative updates. The report says the problem hits PCs that started on Windows 10 21H2 or 22H2, or on Windows 11 23H2, and were later upgraded. Microsoft calls it “a small percentage” of devices.

The errors are 0x80073712 and 0x800f0993. The first one means the component store is corrupt. The second one is tied to missing rebase files, according to the report. The article does not name a root cause beyond those error names.

Which Update Started It?

Starting version	Update that started it	Update that fixed it
Windows 10 21H2 / 22H2	KB5082200	KB5094127
Windows 11 23H2	KB5082052	KB5093998
Windows 11 24H2 / 25H2	KB5079391	KB5094126

These numbers come from the BleepingComputer report. Check them against Microsoft’s own notice before you rely on them.

What Microsoft Says to Do

• Home PCs and unmanaged business PCs: Microsoft says a fix rolls out after a restart. The report says no new devices in these groups should be affected from May 19, 2026, 6:30 p.m. PT. A restart may apply the fix sooner.
• PCs already on 24H2 or 25H2: Microsoft does not fix these directly. The report says to remove the affected package from an elevated Command Prompt.
• If that fails: do a Windows 11 in-place upgrade, which we covered above.

The Removal Command

The report quotes this command. Run it only in an administrator Command Prompt, and only after you confirm the package name in Microsoft’s current note. Package names can change, and a wrong name can fail or remove the wrong item.

dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

Back up first. If the command fails, move to the in-place upgrade.

How to Tell If This Is Your Problem

• You upgraded to 24H2 or 25H2 from an older version.
• Your monthly updates fail with 0x80073712 or 0x800f0993.
• Fixes like DISM and SFC did not help.

If only the first two apply, this section is a good place to start. If you are not sure, run the safe fixes first and look at your update history.

Risk: medium to high. Time: thirty minutes to two hours.

Windows Update Stuck? How to Fix Frozen Updates

Two of the most common complaints are an update that will not move and an update that rolls itself back. Both feel the same: you wait, and nothing works. Here is how to tell what is going on and what to do. Petri has a short section called “How to fix stuck Windows updates?”, and many results online focus on the “undoing changes” message. This section combines both.

Is It Really Stuck?

Give it time first. Big updates can take a long time, and the percentage may sit still for many minutes. Look for signs of life. Does your drive light blink? Does your PC feel warm? If so, it is likely still working.

As a rule of thumb, I would wait at least two hours before you decide an install is frozen. This number is my suggestion, not Microsoft’s.

Stuck at 0% While Downloading

This usually points to the update service or the cache. Try these steps in order:

1. Check your internet link and restart your router.
2. Restart your PC.
3. Run the Windows Update troubleshooter.
4. Reset the update components, using the steps above.
5. Try a manual install from the Microsoft Update Catalog.

Stuck During Install

If the screen has not changed for a very long time and you see no disk activity, a forced restart may be the only way out. Hold the power button until the PC turns off, then turn it on. Windows will often finish or roll back the update by itself. A forced shutdown carries some risk, so use it only after a long wait.

What Does “We Couldn’t Complete the Updates, Undoing Changes” Mean?

This message means that Windows started to install an update, ran into a problem, and is now rolling back. The rollback keeps your PC from being left in a half-updated state. It is a safety step, so let it finish. Do not turn the PC off during it.

After the rollback, your PC will start as usual. The update will show as failed in your update history. Then:

1. Write down the error code from Update history.
2. Free some disk space and unplug extra devices.
3. Run DISM and then SFC.
4. Reset the update components.
5. Install the update by hand.
6. If it still fails, try the steps in the last resorts section.

Petri’s FAQ also mentions starting in Safe Mode with Networking, and Action1 uses Safe Mode to clear the update cache. Safe Mode loads only the basic parts of Windows, so fewer things can get in the way.

Why the Loop Happens

The loop happens because the same update tries to install each time and fails in the same way. The fix is to remove the cause, not to retry. Damaged files, low space, driver conflicts, and security software are the usual causes. Fix one, and the update can finally finish.

Stuck on “Pending Restart” or “Pending Install”

If Windows Update says it is waiting for a restart, restart your PC. If it still shows the same status after a restart, reset the update components. This clears a stuck queue. Action1 notes that an overloaded update queue can be a cause.

Quick Rule

If nothing is happening, wait. If something is clearly broken, read the code. If you have no code, start at the easy fixes.

Windows 10 vs Windows 11 Update Errors (and Work PCs)

Most fixes work on both versions. But the menus differ, and some advice depends on your version. Competitors often mix the two. Petri, for example, uses the Windows 11 path in its steps and the Windows 10 path in its FAQ. This section keeps them straight.

What Is the Same

The commands are the same. Resetting the update components, DISM, SFC, and manual installs from the Update Catalog work on both Windows 10 and Windows 11. Microsoft Learn says its DISM section applies to Windows 11, Windows 10, and Windows Server 2016 and later. So you can use the command steps in this guide on either.

What Is Different

Task	Windows 11	Windows 10
Open update settings	Settings, then Windows Update	Settings, then Update & Security, then Windows Update
Run the troubleshooter	Settings, System, Troubleshoot, Other troubleshooters	Settings, Update & Security, Troubleshoot
Reset the PC	Settings, System, Recovery	Settings, Update & Security, Recovery
Version names you may see	24H2, 25H2, 26H2	21H2, 22H2

Menu names can change with new builds. If you do not see an option, use the search box in Settings.

A Note on Windows 10

Windows 10 is now past its standard support window. Windows Latest has reported on Windows 10 extended security updates, such as KB5120249 in August 2026. I did not read the full report, so check Microsoft’s current rules for your PC. If you use Windows 10, make sure you know which update program you are on, because that affects which updates you can get.

Update Errors on Work or School PCs

If your PC belongs to your job or school, your IT team may control updates. Settings such as Group Policy or an update server called WSUS can block or delay them. Microsoft Learn points home users away from its IT-focused page. Action1, a company that sells update management tools, aims its guide at admins too.

For a managed PC, do this:

• Do not change policies or registry keys yourself.
• Check with your IT team before you rename folders or run repair commands.
• Send them the error code and the KB number.
• Keep your files backed up to the approved storage.

If you are the admin, Microsoft Learn’s DISM guide and CBS.log steps are the right place to dig deeper. For many PCs, a management tool can push updates and report failures in one place. That is a separate topic, and not needed for a home PC.

Home PC or Managed PC? A Quick Check

If you see the message “Some settings are managed by your organization” in Windows Update, your PC is managed. In that case, talk to your admin before you try the deeper fixes.

How to Stop Windows Update Errors From Coming Back

Once your PC updates again, a few habits can keep it that way. Action1 recommends automatic updates and installing at quiet times, and Petri says Windows Update is critical for your device. Here is a simple plan.

Keep Enough Free Space

Check your storage every month. Remove files you do not need. Move large photos and videos to an external drive or a cloud folder. Low space is one of the most common causes in the guides we compared.

Leave Automatic Updates On

Action1 suggests automatic updates and scheduling installs for off hours. Set your active hours in Windows Update settings, so the PC does not restart while you work. Do not turn updates off for long. A PC that falls far behind has more to install, and bigger updates can fail more easily. That last point is my view, not a figure from a source.

Restart Now and Then

A PC that has run for weeks can build up stuck processes. A weekly restart is a simple habit. It can also finish updates that are waiting for a reboot.

Keep Drivers and Security Software Current

Old drivers and clashing security tools came up in several of the guides. Update drivers through Windows Update, or from your PC maker. Keep one security product, and keep it updated.

Make a Restore Point Before Big Updates

Before a feature update, make a restore point and a file backup. If the update fails, you have a way back. This takes a few minutes, and it can save hours.

Do Not Interrupt Updates

Plug in your laptop. Do not force a shutdown during an install, unless you have waited a long time. Interrupting an update is a common way to damage files.

Can I Skip Windows Update?

Action1 asks this question, and the safe answer is that you should not skip updates for long. They carry security fixes. You can pause updates for a short time if a bug in a new update is hurting your PC. Windows has a pause option in Windows Update settings. Action1 gives separate steps for Windows 10 and Windows 11, so look for Pause updates on the Windows Update page. Then install updates again when the problem is fixed.

Watch for Known Issues

Big updates sometimes ship with bugs. The 2026 upgrade-path error is one example. If your updates fail right after a new release, look for a Microsoft notice or a news report about it before you try heavy fixes. Often the fix comes from Microsoft with a later update.

FAQs

Final Thoughts

After comparing the top guides and Microsoft’s own repair notes, my view is that most people fail at this for one reason. They jump to the big fixes too early. A restart, a free-space check, and the troubleshooter cost almost nothing, and they fix many cases. When they do not, resetting the update components and running DISM and SFC fix most of the rest. The risky steps, such as an in-place upgrade or a reset, belong at the end of the list, not the start. That is why this guide labels every fix with its risk and its time.

Two habits will save you the most grief. First, read your error code and symptom before you try anything, because the clue points to the right fix. Second, rename folders instead of deleting them, and back up before any step that changes more than update files. I checked the commands and key claims against Microsoft Learn, Petri, and BleepingComputer on November 4, 2026, but I have not run them on a test PC. So please test the steps on your own build, and check Microsoft’s current notice if your updates began to fail after a big Windows upgrade. If you are stuck, bookmark this page and work down the ladder one step at a time.

Sources

• Petri: How to Fix Windows Update Errors
• EaseUS: Windows Update Not Working
• Action1: Windows Update Failed, 7 Ways to Fix It
• Microsoft Learn: Fix Windows Update corruptions and installation failures
• AVG: How to Troubleshoot Windows Update Errors
• BleepingComputer: Some upgraded Windows PCs fail to install monthly updates
• Technobezz: Windows Update Error 0x80073712 or 0x80070002