How to fix Windows update error 0x8024a22d?

Error 0x8024a22d means Windows Update could not install an update, most often a cumulative update or a new Windows 11 version such as 22H2 or 25H2. Microsoft does not document this exact code, and it often appears next to a second code that names the real problem. Restart the PC and select Retry first.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What Windows update error 0x8024a22d means

Codes that start with 0x8024 come from the Windows Update Agent, the part of Windows that finds, downloads and installs updates. Microsoft's error list groups them by component. The 0x8024A range is headed Automatic Update Errors, with documented codes such as 0x8024A000 (WU_E_AU_NOSERVICE, "Automatic Updates was unable to service incoming requests") and 0x8024AFFF (WU_E_AU_UNEXPECTED).

0x8024A22D is not on that list, and we could not find a Microsoft page that names it. In the reports we read, it is the code Windows Update shows when the install step fails, and a second code often appears beside it. That second code is the useful one: in one case DISM showed The configuration registry database is corrupt., in another the update failed with 0x8007054F as well.

Why Windows update error 0x8024a22d appears

Because Microsoft does not document the code, the order below comes from the cases where it shows up, not from a Microsoft statement. Each cause has its own fix, so you do not need to run all of them.

How to fix Windows update error 0x8024a22d

Fix 1 to Fix 3 are tied to what failed and solve the error for most readers. Fix 4 to Fix 8 repair Windows Update and Windows itself for the case where every update fails. Fix 9 reinstalls Windows over itself and keeps your apps and files.

Fix 1. Restart the PC, retry and note the second code

5 to 20 minutesNo riskThe update failed once or twice, or you do not know yet which update it is.

The code only says that the install step did not finish. A pending restart or an interrupted download stops it once and not again. Before you retry, note every code in the list, because a second code often names the real cause.

1. Open Settings > Windows Update > Update history (Windows 10: Settings > Update & Security > Windows Update > View update history).
2. Note the name of each failed item and its code: a KB number, Windows 11, version 25H2, or a .NET Framework update.
3. Save your work and select Start > Power > Restart. Use Restart, not Shut down.
4. Plug a laptop in and set it not to sleep while the update runs.
5. Open Settings > Windows Update and select Retry or Check for updates.
6. Leave the PC alone until it asks to restart, then restart it.

Fix 2. Install the Windows 11 version with the Installation Assistant or the ISO

1 to 2 hoursLow riskThe failed item is a feature update such as Windows 11, version 25H2 or 22H2, or the upgrade from Windows 10.

The Installation Assistant and setup.exe from the ISO install the new version without the Windows Update step that fails. In an October 2025 Sysnative case, the 25H2 update kept failing with 0x8024a22d and rolled back after the restart; the Installation Assistant then completed it.

1. Open Microsoft's Download Windows 11 page.
2. Under Windows 11 Installation Assistant, select Download Now and run the file. Or download the ISO further down the page.
3. For the ISO: right-click it, select Mount and double-click setup.exe on the new drive.
4. Choose to keep personal files and apps, and let Setup run. Keep a laptop plugged in.
5. If Setup stops, note the code it shows. A different code names the real problem.

Fix 3. Install the failed update by hand from the Microsoft Update Catalog

15 to 30 minutesLow riskA cumulative, security or .NET Framework update with a KB number fails at every retry.

The Catalog file is a complete, fresh copy of the update, so a broken Windows Update download is out of the way. A Microsoft Q&A volunteer gave this route for a Windows 11 22H2 cumulative update that failed with 0x8024a22d. If it fails too, the installer shows its own code, which is easier to look up.

1. Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
2. Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
3. Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
4. Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
5. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
6. Install several files with DISM. If there are several files, open an elevated Terminal or Command Prompt and run DISM with the newest file. DISM finds the other files in the same folder and installs them in the right order.

   DISM /Online /Add-Package /PackagePath:C:\packages\<newest-file>.msu

7. Restart. Restart the PC when the installation finishes, then run winver again: the OS build should have changed.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

Fix 4. Reset the Windows Update components

10 minutesLow riskThe same update keeps failing after Fix 1 to Fix 3, or every update fails.

Windows Update reuses what is in its SoftwareDistribution and catroot2 folders at every retry. If that cache is broken, the update fails the same way each time. Renaming the folders and restarting the update services makes Windows start again from zero; this is the first step the Microsoft Q&A volunteer suggested for 0x8024a22d.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 5. Repair Windows files with DISM and SFC, and read their message

15 to 40 minutesNo riskEvery update fails, or the Catalog installer in Fix 3 also failed.

Updates are built on the component store, where Windows keeps its own files. If it is damaged, the update cannot finish. DISM downloads clean copies of damaged files and SFC then repairs the system files. Their messages also tell you whether the damage is deeper.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 6. Check Device Manager for a faulty driver

15 minutesLow riskDevice Manager keeps refreshing itself, or a device such as Bluetooth stopped working around the time updates began to fail.

One user on Microsoft Q&A reports that updates failed for months until he removed a broken Bluetooth driver that made Device Manager refresh every two seconds. After he installed the maker's current driver, Windows Update worked again. It is a rare cause, but quick to rule out.

1. Right-click Start and select Device Manager.
2. Watch it for half a minute. If the list keeps collapsing and redrawing, a device is failing.
3. Unplug USB devices one at a time and see if the refreshing stops.
4. Look for a device with a yellow warning mark, or a device that no longer works, such as Bluetooth.

Reinstall that device's driver from the PC or device maker: Update, roll back or reinstall a driver

Fix 7. Install the update in a clean boot

15 minutesLow riskUpdates fail and you have security, VPN or system tools from other makers installed.

A clean boot starts Windows with only Microsoft services. If the update installs then, a program you installed blocks it, and you can find it without turning off protection for good.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.
3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.
5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.
6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

Fix 8. Run the Windows Update troubleshooter

5 minutesNo riskYou prefer an automatic check before a reinstall.

The troubleshooter checks the update services, their settings and the pending update state, and repairs what it finds. It does not repair a damaged registry hive or a broken feature update, so it comes after the specific fixes.

1. Open Troubleshoot settings. Select Start > Settings > System > Troubleshoot.
2. Open the list of troubleshooters. Select Other troubleshooters.

   

3. Run the Windows Update troubleshooter. Under Most frequent, select Run next to Windows Update. The Get Help app opens and starts the checks.

   

4. Read the result. Wait until Get Help finishes. If it found and fixed a problem, it says so and asks whether this solved the problem. Answer the question so it can offer the next step.

   

5. Restart the PC. Restart when the troubleshooter finishes, even if it does not ask you to.
6. Check for updates again. Select Start > Settings > Windows Update > Check for updates, and install the updates it finds.

These steps were written for Windows 11 (screenshots: 26H2). The full page with the other versions and what each result means: Run the Windows Update troubleshooter

Fix 9. Reinstall Windows over itself and keep your apps and files

1 to 2 hoursLow riskDISM reports a corrupt registry database, or every update fails with 0x8024a22d after Fix 1 to Fix 8.

A repair reinstall replaces Windows Update, the component store and the system files with clean copies, while apps, files and settings stay. In the Sysnative case, a forum analyst repaired the damaged registry hive with his own tool before the upgrade worked; a repair reinstall is the route that needs no such tool.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

If error 0x8024a22d is still there

Since Microsoft does not explain 0x8024a22d, the useful information is everything around it: the second code, the DISM message and, for a feature update, the Setup logs. Collect them before you ask for help.

1. Note the exact name of every failed update and its code from Update history.
2. Note the message DISM and SFC showed in Fix 5.
3. For a feature update, copy the folders Panther and Rollback (if it exists) from C:\$WINDOWS.~BT\Sources to the desktop. Copy the folders themselves, not shortcuts.
4. Press Win + R, type winver and press Enter. Note the version and build.
5. Send all of this to Microsoft support, a Windows Update forum, or your administrator on a work PC.

How to keep error 0x8024a22d from coming back

If you met the error with a feature update and want to wait, you can stay on your current Windows 11 version while it is still supported. Check its end of support date before you postpone for long. For a neighbouring code in the same range, see our guide to error 0x8024a203.

Frequently asked questions

What is error 0x8024a22d?

It is a Windows Update error that appears when an update downloads but does not install. Microsoft's Windows Update error list does not include this exact code. It sits in the 0x8024A range, which Microsoft calls Automatic Update Errors, next to documented codes such as 0x8024A000 and 0x8024AFFF. In practice it behaves like a general install failure, so the name of the failed update and any second code matter more than the code itself.

How do I fix 0x8024a22d with the Windows 11 25H2 update?

First restart and select Retry. If 25H2 fails again, or installs and then undoes the changes at restart, run the update with the Windows 11 Installation Assistant or setup.exe from the Windows 11 ISO, as in Fix 2. In an October 2025 report the Assistant completed the 25H2 update after Windows Update failed with this code. If Setup rolls back too, run DISM and read its message (Fix 5).

0x8024a22d came with 0x800703f1 or 0x8007054f. What does that mean?

The second code is the better lead. 0x800703F1 is the code for The configuration registry database is corrupt, the message DISM shows when a registry hive is damaged; DISM and SFC cannot repair that, so use the repair reinstall in Fix 9. For 0x8007054F we could not confirm a cause specific to updates. Try Fix 3 and Fix 4 first, and look that code up on its own if the error stays.

Is 0x8024a22a or 0x8024a22 the same error?

0x8024a22 is the same code cut short; Windows always shows eight digits after 0x. 0x8024a22a is a neighbour in the same 0x8024A range of Automatic Updates errors. Like 0x8024a22d, it is not on Microsoft's public error list, so we could not confirm what it means. The same approach applies: read the name of the failed update, restart and retry, then use the Installation Assistant or the Update Catalog to install it outside Windows Update.

Is 0x8024a22d a Windows 10 or a Windows 11 error?

Both. The reader's question on this page came from Windows 10, while recent reports name Windows 11 22H2, 23H2 and 25H2 updates. The Windows Update Agent works the same way on both systems, so the fixes are the same; only some Settings paths differ, and the steps give both. Windows 10 left support on 14 October 2025, so on Windows 10 the best long-term fix is the move to Windows 11.

What will these fixes change on my PC?

Fix 1, Fix 5 and Fix 8 change nothing you would notice. Fix 4 renames the Windows Update cache folders, so the update history page may look empty, but installed updates stay. Fix 6 reinstalls one driver, and Fix 7 turns off other makers' services until you turn them back on. Fix 2 and Fix 9 reinstall Windows and keep your files, apps and settings, which is why you back up first. None of the fixes turns off security features.

Can I fix 0x8024a22d by turning off my antivirus?

Not as a fix. No source we read ties this code to security software, and turning protection off leaves the PC exposed. If you suspect another program interferes with updates, the clean boot in Fix 7 is the safer test. If you still want to rule out the antivirus, pause it for one try only and turn it on right after: Turn off Microsoft Defender protection for a moment. Start with Fix 1 to Fix 3, which cover the usual cases.

Will I lose my files if I reinstall Windows to fix this?

Not with the repair reinstall in Fix 9 or the Installation Assistant in Fix 2. Both keep your apps, files and settings. Reset this PC with Keep my files is different: it keeps your files but removes installed apps. Back up the files you cannot lose before any reinstall, and keep a laptop plugged in until it finishes, because a reinstall that stops halfway can leave Windows unable to start.

I searched in another language: non si installa, xử lý thế nào, как исправить. Is this page for me?

Yes, if you see 0x8024a22d. Non si installa is Italian for it does not install, lỗi này xử lý thế nào is Vietnamese for how do I deal with this error, and как исправить is Russian for how to fix it. The code is the same in every language of Windows. Menu names here are the English ones, so follow their position in Settings; the steps give the Windows 10 path in brackets where it differs.