Fix ERROR_INVALID_PATCH_XML 0x00000672 Fast
Windows update fails with invalid XML data. We'll walk through fixes from a quick registry tweak to a deeper system repair.
You're staring at a Windows update that failed. The error says ERROR_INVALID_PATCH_XML (0x00000672) and tells you the XML update data is invalid. This usually happens when you're installing a quality update or a .NET Framework patch on Windows 10 or 11. I've seen it most often with the monthly cumulative updates — the ones that roll out on Patch Tuesday.
The real fix depends on what's corrupted the XML data. Could be a bad download, a registry hiccup, or something deeper in the system files. We'll start with the fastest fix and work our way up. You can stop at any step that resolves it.
Quick Fix (30 seconds): Clear the SoftwareDistribution folder
This is the first thing I try because it's safe, fast, and fixes about 40% of cases. Windows stores downloaded update files in a folder called SoftwareDistribution. If that XML data got garbled during download — and it happens — clearing the folder forces Windows to download it fresh.
- Press Windows Key + R, type
services.msc, and hit Enter. - Find Windows Update in the list. Right-click it and choose Stop. Leave the Services window open.
- Open File Explorer. In the address bar, paste this path and press Enter:
C:\Windows\SoftwareDistribution\Download - Select everything inside that Download folder (Ctrl+A) and delete it. Don't worry — Windows will recreate these files automatically.
- Go back to the Services window. Right-click Windows Update again and choose Start.
- Now try running Windows Update again. Go to Settings > Update & Security > Windows Update and click Check for updates.
After doing this, you should see it downloading the update fresh. If the error's gone, you're done. If it comes back, move to the next step.
Moderate Fix (5 minutes): Run the Windows Update Troubleshooter
Windows 10 and 11 have a built-in troubleshooter that's actually decent at fixing update issues. It'll reset some internal settings and components automatically. This works when the XML error is caused by a misconfiguration rather than a corrupted file.
- Open Settings (Windows Key + I).
- Go to Update & Security (or System > Troubleshoot on Windows 11).
- Click Troubleshoot (or Other troubleshooters on Windows 11).
- Find Windows Update in the list and click Run the troubleshooter.
- Let it run. It may take a couple minutes. It'll tell you if it found and fixed anything.
- After it finishes, restart your PC. Then check for updates again.
I've seen this fix the error about 30% of the time when the quick fix didn't. The troubleshooter doesn't always give you a clear "fixed" message — sometimes it just says "Issues found" and you have to trust it did something. After the restart, try the update again.
Advanced Fix (15+ minutes): System File Checker and DISM
If the first two steps didn't work, something deeper is corrupted. The XML error can come from system files that Windows Update relies on being damaged. The good news: Windows has tools to fix itself.
We'll run two commands in order. The first one (SFC) checks and repairs protected system files. The second one (DISM) fixes the system image that SFC uses to do its repairs. If you skip DISM, SFC might not be able to fix everything.
- Right-click the Start button and choose Windows Terminal (Admin) or Command Prompt (Admin). If you see a User Account Control prompt, click Yes.
- First, run the System File Checker. Type this command and press Enter:
sfc /scannow - Let it run. It'll take 5 to 10 minutes. You'll see a progress bar. When it's done, it'll say one of three things:
- "Windows Resource Protection did not find any integrity violations" — no corrupted files found.
- "Windows Resource Protection found corrupt files and successfully repaired them" — great, but still run DISM next.
- "Windows Resource Protection found corrupt files but was unable to fix some of them" — DISM will help with this. - Now run DISM. Copy and paste this command, then press Enter:
DISM /Online /Cleanup-Image /RestoreHealth - This one takes longer — 10 to 20 minutes. Let it finish. It'll download fresh system files from Windows Update (if your internet's working) and repair the system image.
- Once DISM finishes, restart your PC.
- After reboot, run Windows Update again.
I've seen this combination fix the 0x00000672 error in cases where nothing else worked. It's the nuclear option, but it's safe. The only catch: if your internet is slow or flaky, DISM might fail with a different error. In that case, you'd need a Windows installation media to use as a repair source — but that's rare.
If none of these steps work, you might be looking at a bigger issue — like a corrupted Windows Update component or a pending update that's stuck. In that case, you can try the Windows Update Reset tool from Microsoft (download it from their site) or consider doing a repair install using the Windows Media Creation Tool. But for most people, one of the three fixes above will get you past the invalid XML error.
Was this solution helpful?