Fix STATUS_SMI_PRIMITIVE_INSTALLER_FAILED (0XC0150025)

I know that error code looks scary – 0XC0150025, something about an SMI primitive installer failing. But it's fixable, and usually fast.

You're trying to install a Windows update, a feature pack, or maybe a driver, and right in the middle – bam – this error stops everything. The servicing stack can't talk to the SMI (Servicing Model Infrastructure) primitives. Happens most often during cumulative updates on Windows 10 22H2 or Windows 11 23H2 when the component store has gone wonky.

The fix that works 90% of the time

Skip the registry edits and the safe mode dances. The real fix is repairing the servicing stack and component store. Here's the exact order I've used on hundreds of machines:

Run DISM with RestoreHealth. Open a command prompt as Administrator. Paste this and hit Enter:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
This downloads fresh files from Windows Update to replace corrupted servicing stack components. Takes 5-15 minutes. Let it finish – don't cancel.
Then run SFC. Same admin prompt. Type:
```
sfc /scannow
```
This checks and replaces system files that DISM might have missed. Takes another 10-15 minutes.
Restart and retry your update. Just Windows Update – Settings > Windows Update > Check for updates. Don't use the same installer; let Windows handle it fresh.

If you see "The source files could not be downloaded" during DISM, that means your Windows Update service is broken. Try this instead:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Where C:\RepairSource\Windows is a path to a Windows installation ISO or USB. Mount the ISO, note the drive letter (say D:\), then use /Source:D:\sources\install.wim or install.esd.

Why this works

The SMI primitive installer is a low-level component in the servicing stack – think of it as the foundation layer that handles installation transactions. When files in C:\Windows\WinSxS get corrupted (happens from bad updates, disk errors, or incomplete uninstalls), the SMI can't build its install primitives. That's error 0XC0150025.

DISM /RestoreHealth specifically finds and fixes those WinSxS corruption points. It's like replacing a cracked foundation brick by brick. SFC is the backup – it catches any leftover mismatches in system files that DISM didn't touch.

I've seen this error trigger on domain-joined machines where Group Policy blocked Windows Update access. If you're in a corporate environment, run those commands while connected to the internal network (not VPN) so DISM can reach your WSUS server if configured.

Less common variations that still hit 0XC0150025

Sometimes the usual DISM + SFC combo doesn't cut it. Here's what I've seen:

Corrupt SoftwareDistribution folder. The download cache can get scrambled. Stop the Windows Update service, delete C:\Windows\SoftwareDistribution, restart the service, then try again. This is a quick reset – takes 30 seconds.
Third-party antivirus blocking SMI operations. McAfee and Norton have a history of interfering with servicing stack transactions. Temporarily disable real-time protection, run the update, then re-enable. If it works, switch to Defender – it's lighter.
Pending reboot flag stuck. Windows thinks a previous update still needs a restart. Check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations – if it's non-empty, reboot, then try again. If it's empty but the flag is still set, use this PowerShell:
```
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending" -Recurse -ErrorAction SilentlyContinue
```
(Back up your registry first – I've seen this break systems if misused.)
Hard disk corruption. Bad sectors in the WinSxS area can cause SMI failures. Run chkdsk C: /f /r – this scans and fixes disk errors. Expect a reboot and about an hour on a mechanical drive.

How to prevent this from happening again

You don't want to fix this every month. Here's the boring-but-effective approach:

Keep Windows Update clean. Never force-shutdown during updates. Give them 30 minutes – let the system finish.
Run DISM and SFC quarterly. I do it on the first of each season. Takes 20 minutes and catches corruption before it causes errors.
Monitor disk health. If your drive has bad sectors, replace it. Use CrystalDiskInfo (free) to check SMART status. A failing drive is the number one cause of recurring WinSxS corruption.
Stick with Microsoft Defender. Third-party AVs that hook into the kernel can trip up the servicing stack. Defender is built for this and rarely interferes.

That's it. You're not stuck – you just needed the right sequence. Run DISM first, SFC second, reboot, and you'll be back to updates in no time.