How to fix Windows update error 0x800705b9?

Install error 0x800705b9 means Windows could not read an XML file while it installed an update. The code is Win32 error 1465, ERROR_XML_PARSE_ERROR, and in the solved cases the damaged file sat in the component store. Restart and retry once, then repair the store with DISM and SFC.

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

What install error 0x800705b9 means

0x800705b9 is an ordinary Windows system error in the eight-digit form that Windows Update prints. The first half, 0x8007, marks a Win32 error wrapped for the update components. The second half, 05B9, is 1465 in decimal. Microsoft's list of system error codes names 1465 ERROR_XML_PARSE_ERROR, with the text "Windows was unable to parse the requested XML data."

An update is not one file. Windows reads a set of package manifests (files ending in .mum in C:\Windows\Servicing\Packages) and component manifests, which are XML files, to know what to replace. If one of them is cut short, empty or overwritten with garbage, the parser stops and the update rolls back with this code.

Which Windows updates fail with 0x800705b9

The code is not tied to one update. People search it together with many KB numbers, from 2024 updates for Windows 11 23H2 to the 2026 security updates for 25H2. The cases below are the ones we read in full. They are user reports, not statements by Microsoft.

• 2026 updates searched with this code include the 2026-08 Security Update (KB5121003) (26200.9168) and the 2026-09 Security Update (KB5129195) (26200.9457), both for Windows 11 25H2. We did not read a case for each, so we do not claim a cause for them.
• Windows 11 23H2 and 24H2 Home and Pro no longer get monthly updates. On such a PC the lasting fix is a move to 25H2 or 26H2, which Fix 6 does in one step.
• Windows 10 left support on 14 October 2025. Without Extended Security Updates, a Windows 10 22H2 PC gets no new monthly updates to fail on.

Why Windows update error 0x800705b9 happens, from most to least likely

Microsoft has not published a cause for this code in Windows Update. The ranking below follows what the code says, an XML file could not be read, and how the cases we read were solved. Each cause points to the fix that matches it.

How to fix install error 0x800705b9 in Windows Update

Fix 1 takes ten minutes and changes nothing. Fix 2 repairs the store, which is where the cases we read were solved. Fix 3 is for a PC where DISM itself fails. Fixes 4 and 5 rule out the download. Fix 6 is the repair install, which rebuilds Windows and keeps your files and apps.

Fix 1. Restart, check your build and retry the newest update

10 minutesNo riskAlways first, and above all when the failing update is a preview or a month or more old.

A pending restart or an interrupted install can leave a manifest half written until the next start. A restart lets Windows finish that work. The build number shows whether a newer update has already replaced the failed one.

1. Restart the PC once with Start > Power > Restart. Do not use Shut down, which can skip pending work.
2. Press Win + R, type winver and press Enter. Note the version (23H2, 24H2, 25H2 or 26H2) and the OS Build.
3. Open Settings > Windows Update > Update history and note the full name and KB number of the failed update.
4. If the name contains Preview, you can skip it: its changes arrive in the next regular update.
5. If it is a regular update, search its KB number on Microsoft Support. The page title gives the OS build it installs.
6. If your build in winver is the same or higher, the update is in place. If it is lower, select Check for updates and install what is offered now.

Fix 2. Repair the component store with DISM, then system files with SFC

30 minutesLow riskThe same update fails again after a restart. This is the fix for most readers.

Windows Update reads its manifests from the component store. DISM RestoreHealth compares the store with clean copies and replaces damaged files, and SFC then repairs the system files that come from the store. In the solved Sysnative case the update installed right after a store repair and a DISM run.

Run DISM RestoreHealth first and System File Checker second, then restart and try the update. Step by step:

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 3. When DISM fails: find the damaged file in CBS.log

15 minutes, plus waiting for helpNo riskDISM itself stops with an error, or SFC keeps finding damage it cannot repair.

When the repair tool cannot start, the damage sits in the files DISM needs to run. CBS.log names the package or path it tripped on. In the solved case that led the helper straight to one .mum manifest in C:\Windows\Servicing\Packages.

1. Right-click Start and select Terminal (Admin). On Windows 10, search for cmd and select Run as administrator.
2. Copy the log to the desktop, so that you read a copy while Windows keeps writing the original.

   copy %windir%\Logs\CBS\CBS.log %USERPROFILE%\Desktop\CBS-copy.log

3. List the lines that carry the code. Note the time of the last hit.

   findstr /i /c:"800705b9" %USERPROFILE%\Desktop\CBS-copy.log

4. List the lines that name a manifest or a missing item.

   findstr /i /c:".mum" /c:"manifest" /c:"NOT_FOUND" %USERPROFILE%\Desktop\CBS-copy.log

5. Open CBS-copy.log in Notepad, go to the time of the last hit and read 20 to 40 lines above it. Note every package, manifest and file name.

The DISM message from the solved KB5036893 case, as the thread quotes it

Error: 193

An error occurred while attempting to start the servicing process for the image located at C:\.

For more information, review the log file.

With a file name in hand, a helper can check whether that one file is damaged. In the solved case the first question was the hash of the manifest, which you can read yourself. Replace the name with the one from your log:

Terminal (Admin): print the SHA256 hash of a package manifest

certutil -hashfile C:\Windows\Servicing\Packages\<name from your log>.mum sha256

Fix 4. Reset the Windows Update components and run the troubleshooter

15 minutesLow riskThe message says Download error - 0x800705b9, or SFC and DISM are clean.

A reset gives Windows Update an empty download cache and restarts its services, so a damaged download is fetched again. It does not repair files already in the component store, so in the solved case it would not have helped. That is why it comes after Fix 2.

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

Then run the built-in troubleshooter once: Run the Windows Update troubleshooter. If the system drive is nearly full, free space first, because an update needs room to stage its files: Free up disk space and delete temporary files

Fix 5. Install the update by hand from the Microsoft Update Catalog

20 to 40 minutesLow riskYou want to rule out Windows Update itself, or you install updates from the catalog anyway.

A manual install skips the Windows Update download and service chain. If it also fails, as it did in the solved case with "Installation Failed", you know the cause is in the files on the PC.

1. Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
2. Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
3. 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.
4. 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.
5. 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.
6. 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.
7. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
8. 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

9. 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

• More than one file. Windows 11 24H2 and later updates can list a checkpoint update first. Install the files in the order the catalog gives.
• A .NET Framework update. It has its own KB number and its own catalog entry, separate from the cumulative update for Windows.
• The same failure by hand. The download was never the problem. Go back to Fix 2 or Fix 3, or go to Fix 6.

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

1 to 2 hoursLow riskSFC and DISM are clean and the update still fails, DISM cannot run, or the PC runs Windows 11 23H2 or 24H2 Home or Pro.

A repair install writes a fresh copy of Windows with a new component store and new manifests, and keeps apps, files and settings. On Microsoft Q&A two users with 0x800705b9 wrote that this was what fixed it.

1. On Windows 11, open Settings > System > Recovery.
2. Next to Fix problems using Windows Update, select Reinstall now.
3. Confirm, keep the PC on and let it restart as often as it needs.
4. When Windows is back, run winver, then select Check for updates in Windows Update.

If Reinstall now is missing or fails, use installation media. Download the Windows 11 ISO from Microsoft's software download page, right-click it, select Mount and run setup.exe. On Ready to install, check that it says Keep personal files and apps before you select Install.

More reset options, including the ones that remove apps: Reinstall Windows without losing files

If 0x800705b9 is still there: the logs to read and what to send

When DISM cannot run and a repair install stops halfway, the next step is a person who reads CBS logs for a living. The Sysnative Windows Update forum and Microsoft Q&A both take such cases. Collect the logs right after a failed attempt.

PowerShell (administrator): pack the CBS logs into one file on the desktop

Compress-Archive C:\Windows\Logs\CBS -f (Join-Path ([Environment]::GetFolderPath('Desktop')) 'CBS.zip')

• What to send: CBS.zip, C:\Windows\Logs\DISM\dism.log, the output of winver, the KB number, the dates from Update history and what you already tried.
• One test with the antivirus paused. If you use an antivirus other than Microsoft Defender, pause it for one attempt and turn it back on right after: Turn off Microsoft Defender protection for a moment
• A work or school PC. Updates may come from your organization's server. Send the logs to the administrator before a repair install.
• Is it hardware? Nothing in the cases we read pointed at hardware. If SFC finds new damage after every repair, check the drive: Check a disk for errors (chkdsk)

How to keep install error 0x800705b9 from coming back

Each point follows from what the code means. Error 1465 appears when a file Windows must read as XML is damaged. Anything that cuts a write short or removes servicing files leaves the next update with the same problem.

Frequently asked questions

What does install error 0x800705b9 mean?

It means Windows could not read an XML file while it installed an update. The code is Win32 error 1465 in the form Windows Update uses, and Microsoft names it ERROR_XML_PARSE_ERROR, "Windows was unable to parse the requested XML data". Update packages are described by XML manifests in the component store. In the case we read in full, the damaged file was one package manifest, and the update installed once it was replaced.

What is the difference between Download error and Install error 0x800705b9?

The code is the same, only the stage differs. Install error means the update downloaded and failed while Windows processed it, which points at the component store and Fix 2. Download error means the failure came while Windows prepared the download, so a reset of the update cache (Fix 4) is worth trying earlier. We did not find a solved Download error case, so if the reset does not help, continue with Fix 2.

The 2026-08 Security Update (KB5121003) (26200.9168) fails with 0x800705b9. What do I do?

Treat it like any other update with this code. 26200 is the build of Windows 11 25H2, so the update is a regular monthly security update. Restart and retry once, then check whether a newer update, such as the 2026-09 Security Update (KB5129195), is offered and installs. If the newest one fails with the same code, the cause is on your PC: run DISM and SFC as in Fix 2.

Is 0x800705b9 a known issue that Microsoft is fixing?

We could not find it as a known issue. Microsoft documents only the generic meaning of error 1465, and we found no statement that a later update fixes it. In the cases we read, the cause was on the individual PC: a damaged file in the component store. That is why the same PC can fail several updates in a row while other PCs install them without trouble.

I see "Installatiefout - 0x800705b9" or "Downloadfehler - 0x800705b9". Is it the same error?

Yes. Windows prints the same code in every language, and only the words in front of it change. "Installatiefout" is Dutch for install error, "Downloadfehler" is German for download error, "Erreur d'installation" is French and "Błąd instalacji" is Polish. The cause and every fix on this page are the same. Menu names in Settings are translated, but commands such as winver, DISM and sfc /scannow are typed the same way everywhere.

DISM fails with error 193 or error 2. What now?

Then the tool that should repair the store is damaged too. That was the situation in the solved KB5036893 case: DISM stopped with error 193, a repair install stopped at 59 %, and the PC only recovered after a helper replaced the damaged files with a fix made for that PC. Read CBS.log as in Fix 3, collect the logs and ask a Windows Update forum for help. Do not run a fix someone made for another PC.

SFC and DISM say everything is fine. Why does the update still fail?

Because SFC checks protected system files and DISM CheckHealth only reports flags already set, so a single damaged manifest can be missed. Run DISM with RestoreHealth, not only CheckHealth, and read CBS.log for the lines just above 800705b9. If nothing stands out, a repair install (Fix 6) writes a fresh component store, which is what fixed the error for two users on Microsoft Q&A.

Will a repair install delete my files or programs?

Not when you keep personal files and apps. Reinstall now in Settings > System > Recovery and setup.exe from Windows 11 media are both built to keep your files, apps and settings. With setup.exe, check the Ready to install screen: it must say Keep personal files and apps before you select Install. Back up your important files anyway, because a repair install is a large operation, and some apps may ask you to sign in again.

Should I turn off my antivirus to fix 0x800705b9?

Not for good. No case we read was solved by the antivirus, and the code points at a damaged XML file, not at a blocked download. If you use an antivirus other than Microsoft Defender, you can pause it for one attempt and turn it back on right after, whatever the result. If the update still fails, the antivirus is not the cause, so continue with Fix 2.