0XC0150020

STATUS_ADVANCED_INSTALLER_FAILED 0XC0150020 Fix

Windows Errors Intermediate 👁 8 views 📅 Jul 3, 2026

Quick answer: run DISM + SFC, then re-register Windows Installer. This error means a system app or update failed during setup. I've seen it mostly after a bad Windows Update or a third-party installer crash.

Quick Answer for Advanced Users

Run these commands as Admin: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Reboot. Then msiexec /unregister and msiexec /regserver. If still broken, check the CBS log for the exact component.

What the Heck Is This Error?

You get 0XC0150020 and the message "STATUS_ADVANCED_INSTALLER_FAILED". It usually pops up during a Windows Update, installing a driver, or running a third-party installer like a game or a printer setup. I've seen it most often on Windows 10 version 22H2 and Windows 11 after a failed cumulative update. The error means the Windows servicing stack — the part that installs updates and apps — couldn't finish its job. It's not your hardware. It's a software mess.

Why This Happens

Here's the short version: Windows uses a thing called the "advanced installer" to handle big updates or app installs. When it crashes, it leaves behind a half-finished state. Common triggers:

  • A Windows Update that got interrupted (power loss, shutdown mid-install)
  • An older third-party installer (like Adobe or Norton) that isn't compatible with your current Windows build
  • Corrupted system files from a previous failed update
  • Missing or broken Windows Installer service

Fix Steps (Main Fix)

  1. Run DISM + SFC. Open Command Prompt as Admin. Type:
    DISM /Online /Cleanup-Image /RestoreHealth
    Wait for it to finish (could be 10-15 minutes). Then:
    sfc /scannow
    Reboot your PC.
  2. Re-register Windows Installer. In the same Admin Command Prompt, type:
    msiexec /unregister
    Then:
    msiexec /regserver
    Reboot again.
  3. Check for pending updates. Go to Settings > Windows Update and click "Check for updates". Let it complete. If it fails with the same error, skip to alternative fixes.

Alternative Fixes (If Main Fix Doesn't Work)

Fix 1: Reset Windows Update components

Sometimes the update service itself is stuck. Run these in Admin CMD:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Reboot and try the update again.

Fix 2: Use System Restore

If you have a restore point from before the error started, go to Control Panel > Recovery > Open System Restore. Pick a point dated before the first time you saw this error. I've had this work when nothing else did. It's a nuclear option but safe.

Fix 3: Manual install the update

If the error came from a specific Windows Update, go to Microsoft Update Catalog. Search for the KB number. Download the standalone installer (.msu) for your system (x64 or ARM). Run it. If it fails, try the .cab version with DISM: DISM /Online /Add-Package /PackagePath:C:\path\to\cab.

Fix 4: In-place upgrade

Last resort. Download the Windows Media Creation Tool. Run it and choose "Upgrade this PC now". Keep your files and apps. This reinstall Windows but keeps everything. I've used this for stubborn 0XC0150020 errors after a bad update. Takes about an hour.

Prevention Tip

Don't force shut down your PC during a Windows Update. I know updates are annoying, but pulling the plug mid-install is the #1 reason for this error. Also, keep your Windows Installer service set to Automatic. Check it in Services.msc. If it's disabled, set it to Automatic and start it.

"This tripped me up the first time too. The real fix is always DISM + re-register first. Skip the registry edits and third-party tools — they just waste time."

If after all this you're still stuck, check the CBS.log file at C:\Windows\Logs\CBS\CBS.log. Search for "0XC0150020" or "advanced installer" in that log. The exact line will tell you which component failed. Share that in a forum or with Microsoft support — it's the clue they need.

Was this solution helpful?