Fix 0X8000000C Error: GUID Conflict in Windows Update & Activation

Why You See Error 0X8000000C

This error code 0X8000000C pops up when Windows can't match its internal GUID (globally unique identifier) for activation or updates. I've seen it most often after a failed Windows Update, a system restore that went sideways, or — this one's nasty — after a malware cleanup tool deleted license files it shouldn't have.

Had a client last month whose print queue died because of a botched update. When we tried to fix it, 0X8000000C blocked everything. Here's the playbook I used to get them back online.

Cause #1: Corrupted Windows License File (Software Protection Service)

The most common culprit: the Software Protection service's licensing file (tokens.dat) got corrupted. This file stores your activation GUID. If it's damaged, Windows throws 0X8000000C.

Fix It with slmgr — The Command That Works

Skip the registry edits for this one. Use the built-in Windows activation tool slmgr.vbs. Here's the step-by-step:

1. Open Command Prompt as Administrator. Hit Win + X, select 'Command Prompt (Admin)' or 'Terminal (Admin)'.
2. Run this command to re-arm the license and clear the corrupted GUID:

slmgr /rearm

You'll get a popup saying 'Command completed successfully'. Reboot. That alone fixes it maybe 60% of the time.

If that doesn't work, go nuclear:

1. Run slmgr /cpky to clear the product key from the registry.
2. Then run slmgr /rilc to re-install the license files.
3. Finally, slmgr /rearm again.

Reboot, then check activation: Settings > Update & Security > Activation. If it's still busted, move to Cause #2.

Cause #2: System File Corruption from a Bad Update

If the slmgr trick didn't stick, the problem runs deeper. System files related to Windows Update or activation services got corrupted. This usually happens when an update failed mid-install, or a hard shutdown corrupted the component store.

Run SFC and DISM in Order

Don't skip DISM. SFC alone won't fix corruption in the servicing stack. Do them in this exact sequence:

1. Open Command Prompt as Admin.
2. Run DISM /Online /Cleanup-Image /RestoreHealth. This fixes the component store itself. Takes 10-20 minutes. Let it finish.
3. After DISM completes, run sfc /scannow. SFC now has a clean base to work from.

I've had DISM fail with 'source not found' — that means the corruption is bad. Use a Windows installation media as the source: DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess (adjust drive letter to your DVD or USB).

After both finish, reboot and try Windows Update or activation again. This resolves about 80% of remaining cases.

Cause #3: Malware That Nuked Your Activation Files

Third cause: a malware infection — especially adware or a fake antivirus — that deleted or corrupted tokens.dat and related files. I've seen this after someone ran a sketchy 'PC cleaner' that thought license files were junk.

Restore Missing Files from Backup or Upgrade

If you have a backup of C:\ProgramData\Microsoft\Windows\Activation, restore it. Most people don't. So here's your next move:

1. First, run a full Malwarebytes scan to ensure the machine is clean. Don't skip this.
2. Then, run the Windows Update Troubleshooter: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it.
3. If that fails, do a repair upgrade — basically reinstall Windows while keeping your files. Download the Media Creation Tool from Microsoft, run it, select 'Upgrade this PC now'. Keep files and apps.

A repair upgrade nukes any corrupted license files and rebuilds them from scratch. It's nuclear, but it's the sure fix. Had a client whose activation was so toast that even a clean install didn't work — the repair upgrade did.

After the upgrade, run slmgr /ato to force activation. You'll either activate immediately or get a different error (usually 0x8007232B indicating a product key mismatch — that's fixable too).

Quick-Reference Summary Table

Start with slmgr /rearm. It's quick and free. If that fails, DISM/SFC. Save the repair upgrade for last — it's heavy but it works. You'll beat 0X8000000C.