How to fix Windows update error 0x80188309?

Windows update error 0x80188309 is the servicing code E_REGISTRY_COLLISION: two update packages want to write the same registry value, so Windows stops the install, usually close to 100 %. Restart and retry once, then install the update by hand. If it still fails, repair Windows in place: your files and apps stay.

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

What Windows update error 0x80188309 means

0x80188309 comes from the part of Windows that installs updates into the component store (Component Based Servicing, or CBS). On Microsoft Q&A, a volunteer moderator gives its name as E_REGISTRY_COLLISION and its meaning as "Two or more packages have registry settings that conflict". We could not find the code on a Microsoft documentation page, so this name comes from that answer.

In plain words: every update package carries registry values it will write. Before it writes them, Windows checks that no other installed package already owns the same value in a different way. When it finds such a clash, it refuses to go on rather than leave Windows half updated. The download is fine. The problem is in what is already on your PC.

What causes Windows update error 0x80188309

The code names one thing, a registry clash between packages, but there are a few ways your PC gets there. Microsoft publishes no ranking, so the order below follows what the code means and what users report.

In a Sysnative forum thread from 2024, a user on Windows 11 23H2 saw the update download, then fail near 100 % with 0x80188309 on KB5039212 and later on KB5041585. SFC and the troubleshooter did not help. The CBS log held the line about critical registry value collisions, and the helpers asked for the COMPONENTS registry hive to find the clashing value.

How to fix Windows update error 0x80188309

Fixes 1 to 4 take minutes and clear a pending restart or a damaged staged update. If the collision sits in the component store itself, they will not be enough, and Fix 5 or Fix 6 repairs Windows while keeping your files, apps and settings.

Fix 1. Restart the PC and retry the update once

5 to 15 minutesNo riskAlways first, most of all when another update says Restart required.

A pending restart means the component store is still in the middle of an earlier change. A real restart lets Windows finish that work, so the registry check starts from a settled state.

1. Save your work and plug a laptop into power.
2. Open Start, select the power button and choose Restart. Do not use Shut down for this step.
3. Wait two or three minutes after Windows starts.
4. Open Settings > Windows Update and select Retry next to the failed update, or Check for updates.
5. Leave the PC on until the update finishes or asks for a restart.

Fix 2. Install the failed update as an .msu file from the Microsoft Update Catalog

10 to 20 minutesLow riskOne update keeps failing and you can see its KB number in Update history.

On Microsoft Q&A this is the first advice given for 0x80188309. The offline installer brings its own complete package, so a damaged staged copy of the update is no longer in the way.

1. Open Settings > Windows Update > Update history and note the KB number next to the failure, for example KB5039212.
2. Open Settings > System > About and note your version (for example 24H2 or 25H2) and System type (x64 or ARM64).
3. Go to the Microsoft Update Catalog and search for the KB number.
4. Download the line that matches your version and system type.
5. Double-click the .msu file and confirm the install.
6. Restart when asked.

Full steps with screenshots: Install an update from the Microsoft Update Catalog

Fix 3. Reset the Windows Update components and cache

15 minutesLow riskOne update failed both through Windows Update and as an .msu, or you want to rule out a damaged staged copy.

The reset removes the download and the staging data of the failed update by renaming SoftwareDistribution and catroot2. Windows then stages the update again from zero, so leftovers of the failed attempt are gone.

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 4. Repair the component store with DISM, then run SFC

20 to 30 minutesLow riskThe same code comes back after Fixes 1 to 3, or other updates fail too.

The colliding registry data lives in the component store. DISM /RestoreHealth checks that store and replaces damaged parts. SFC alone checks only the system files and did not help the user in the forum report.

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 5. Reinstall the current version of Windows 11 through Windows Update

45 to 90 minutesRead the warningWindows 11, and Fixes 1 to 4 did not help, or Windows Update itself offers Reinstall now.

Microsoft offers this repair for updates that fail because of problems with system files or components. It reinstalls the same Windows version with a clean component store, so the clashing registry data is replaced.

1. Open Start > Settings > System > Recovery.
2. Under Fix problems using Windows Update, select Reinstall now.
3. Choose whether the PC may restart by itself 15 minutes after the install.
4. Select OK. Windows Update downloads a repair version of the last update that installed well and installs it.
5. Restart when it is done, then open Settings > Windows Update and select Check for updates.

Fix 6. Repair install with Windows Setup and keep files and apps

60 to 90 minutesRead the warningWindows 10, a managed PC, or Reinstall now was missing or failed.

Setup run from inside Windows replaces the whole component store with a clean one, without going through Windows Update. That removes any registry collision left by old packages.

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.
4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
5. Choose Keep my files. Select Keep my files. Do not select Remove everything.
6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
7. Reset. Review the summary and select Reset. The PC restarts several times.

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 0x80188309 is still there

The real cause is written in the CBS log, C:\Windows\Logs\CBS\CBS.log. Open it in Notepad as administrator, press Ctrl + F and search for collision. The failure line looks like the one a user posted: Error: 1 critical registry value collisions detected, failing. The lines just above it name the registry key and the packages that clash.

Send these to Microsoft Support or a Windows Update forum. If the PC also freezes or shows disk errors, check the drive first, because damage to the hive can come from the disk: Check a disk for errors (chkdsk). Windows 10 reached the end of support on 14 October 2025, so without Extended Security Updates a Windows 10 PC no longer gets monthly updates at all.

How to keep error 0x80188309 from coming back

For a different update code with a similar set of fixes, see Windows update error 0x80004002.

Frequently asked questions

What is error 0x80188309?

It is a Windows servicing code named E_REGISTRY_COLLISION, which means two or more update packages have registry settings that conflict. Windows finds the clash while it installs an update into the component store and stops rather than write conflicting values. The download itself is fine. Restart and retry once, install the update as an .msu file, and if it still fails, repair Windows with Reinstall now or Setup while keeping your files.

Why does the update fail with 0x80188309 near 100 %?

Because the registry check happens while the update is installed, not while it downloads. Users report the progress bar reaching the end, then the error. At that point Windows compares the registry values of the new package with what other installed packages already own. When it finds a clash, it rolls the install back and shows 0x80188309. Retrying repeats the same check, which is why the error comes back each time until the store is repaired.

Which updates fail with 0x80188309?

It is not tied to one update. Reports on Microsoft Q&A, Sysnative and Reddit name Windows 11 22H2 and 23H2 cumulative and preview updates, such as KB5028254, KB5039212 and KB5041585, and a February 2024 cumulative update. Once a PC has the collision, the next monthly update often fails with the same code, because the clashing data is still in the store. That is why the repair in Fix 5 or Fix 6 is often needed.

Will the Windows Update troubleshooter fix 0x80188309?

Usually not. The troubleshooter resets update services and settings, but the clash sits in the component store, which it does not repair. In the forum report, the troubleshooter found something to fix and the update still failed with the same code. You can run it, since it is quick and safe, but expect to need Fix 4 and then Fix 5 or Fix 6. Step by step: Run the Windows Update troubleshooter

Does Reinstall now delete my files or apps?

No. Microsoft says Fix problems using Windows Update reinstalls the same Windows version and keeps your apps, files and settings. It downloads a repair version of the last update that installed well and installs it. Keep the PC on power and connected to the internet the whole time. A power cut can still leave Windows unable to start, so a backup before you begin is a good idea.

Why is Fix problems using Windows Update not shown on my PC?

Microsoft names three reasons. Your PC runs a version older than Windows 11 22H2. It lacks the February 2024 optional update or a later one. Or its updates are managed by work or school, for example with a WSUS server or update deferral policies. Windows 10 does not have this option at all. In each case use Windows Setup with Keep personal files and apps, as in Fix 6.

Can I find and delete the colliding registry value myself?

Only with expert help. The clashing values sit in the COMPONENTS hive, a separate registry file in C:\Windows\System32\config that Windows loads only for servicing. Forum helpers find the exact value from the CBS log and a copy of that hive, then give a fix for that one PC. Guessing and deleting values there can break every later update. For most readers a repair install is faster and safer.

Should I turn off my antivirus to fix 0x80188309?

No. The error is a clash between packages already on your PC, so antivirus is not part of the cause, and Microsoft Defender never needs to be off for updates. If you use a third-party security suite and nothing else worked, you may pause it for one install attempt and turn it back on right after. Step by step: Turn off Microsoft Defender protection for a moment

I see 0x80188309 on Windows 10. What should I do?

The same fixes apply, except Fix 5, which Windows 10 does not have. Use the Media Creation Tool or Windows 10 Setup with Keep personal files and apps, as in Fix 6. Keep in mind that Windows 10 left support on 14 October 2025. Without Extended Security Updates, the PC gets no more monthly updates, so a long-term fix is moving to Windows 11 if your hardware allows it.