SYSTEM_LICENSE_VIOLATION (stop code 0x9A) is an unusual blue screen: it’s the software licensing subsystem crashing Windows, not a driver or hardware fault in the usual sense. Something in the license validation path — corrupted licensing files, a tampered activation, or a hardware change the license can’t reconcile — went wrong badly enough to bugcheck.

There’s an elephant in the room with this stop code: it’s strongly associated with cracked activators and loaders (KMS hacks, HWID spoofs). If any such tool was ever run on this laptop, that’s very likely the cause. But genuine systems hit it too, from corrupted licensing stores and motherboard swaps. The fixes below handle both — honestly.

Why this happens

  • Cracked activators or loaders: KMS emulators and HWID spoofers patch licensing components; when Windows updates those components, the patches break and the system crashes.
  • Corrupted licensing store: Damage to the tokens.dat store or related files from disk errors or bad updates.
  • Major hardware change: Motherboard/CPU replacement invalidating the digital license’s hardware binding.
  • Tampered system files: Modified licensing DLLs failing integrity checks during validation.
  • Failed Windows update: An update that partially replaced licensing components.
  • Malware targeting activation: Some malware hooks licensing components, destabilizing them.

How to fix it

Work through these in order — remove tampering first, then repair.

Fix 1: Remove any activator, crack, or loader

Be honest with yourself here — this is the cause in most cases.

  1. Check Settings > Apps > Installed apps for anything with “KMS,” “activator,” “loader,” or “HWID” in the name. Uninstall it.
  2. Check scheduled tasks (Win + R > taskmgr > Startup apps, and taskschd.msc) for reactivation tasks that reapply cracks on boot — delete them.
  3. Check C:\Windows for suspicious folders from activator tools and remove them.
  4. Restart. If crashes stop, the crack was the cause. Purchase a legitimate license — grey-market keys from auction sites cause their own activation problems.
  5. Run a full Microsoft Defender Offline scan afterward — activators are a notorious malware vector.

Fix 2: Rebuild the licensing store

Corrupted licensing data crashes the validation path. Rebuild it cleanly.

  1. Open an elevated Command Prompt (Win + S, type cmd, right-click > Run as administrator).
  2. Stop the Software Protection service: net stop sppsvc.
  3. Rename the store: ren C:\Windows\System32\spp\store\2.0\tokens.dat tokens.dat.old. (The exact path varies; use dir to confirm.)
  4. Restart the service: net start sppsvc — Windows rebuilds the store automatically.
  5. Restart the laptop and check Settings > System > Activation for status.
  6. If activation shows an error, run the Troubleshoot link there — it resolves most post-rebuild issues.
  7. If the store won’t rebuild (service fails to start), boot into Safe Mode and repeat the rename — a third-party service may be locking the file. Also verify the disk isn’t failing with chkdsk C: /f, since recurring store corruption often traces back to bad sectors in the system partition.

Fix 3: Repair system files

Licensing components are system files — repair them.

  1. Elevated Command Prompt: run DISM /Online /Cleanup-Image /RestoreHealth first.
  2. Then sfc /scannow.
  3. These restore tampered or corrupted licensing DLLs to genuine Microsoft versions.
  4. Restart and verify in Settings > System > Activation.
  5. If SFC reports it repaired files, the corruption is fixed — but if a crack re-tampers them, crashes return. Make sure Fix 1 is complete.

Fix 4: Reactivate after hardware changes

Motherboard swaps need license transfer, not repair.

  1. Go to Settings > System > Activation > Troubleshoot.
  2. Select I changed hardware on this device recently and sign in with the Microsoft account linked to your digital license.
  3. Select the device from the list and activate.
  4. If the troubleshooter fails and you have a retail key, click Change product key and enter it.
  5. OEM licenses (preinstalled) generally don’t transfer to new motherboards — contact the laptop manufacturer if the board was replaced under warranty; they handle reactivation.
  6. Microsoft’s activation help is documented on the Windows support hub .

Fix 5: Check for malware in licensing components

Malware hooks the same components cracks do.

  1. Run a Microsoft Defender Offline scan (Windows Security > Virus & threat protection > Scan options).
  2. If you suspect deep infection, also run the Malicious Software Removal Tool: Win + R > mrt > full scan.
  3. Remove everything found, then redo Fix 2 (rebuild the store) — malware often leaves the store corrupted even after removal.
  4. Change your Microsoft account password afterward if malware had system-level access.

Fix 6: Uninstall the triggering Windows update

If crashes began right after an update on a genuine system, the update damaged licensing components.

  1. Settings > Windows Update > Update history > Uninstall updates — remove the most recent one.
  2. Or from recovery: Automatic Repair > Troubleshoot > Advanced options > Uninstall Updates.
  3. Pause updates for two weeks, then reinstall — Microsoft usually fixes licensing regressions quickly.
  4. Our blue screen after Windows 11 update guide covers the broader update-rollback workflow.

Fix 7: In-place upgrade as the final repair

If the licensing subsystem is damaged beyond SFC/DISM repair, refresh Windows.

  1. Download Windows 11 installation media and run setup from within Windows (if it boots) or from USB.
  2. Choose to keep files and apps — this reinstalls all system components including licensing, with genuine Microsoft files.
  3. After the upgrade, activate cleanly: link your Microsoft account or enter your legitimate product key.
  4. Related licensing-adjacent crashes: system license violation after Windows 11 update and the 24H2 variant .

Closing

SYSTEM_LICENSE_VIOLATION is Windows’ licensing subsystem failing catastrophically — and the fix starts with honesty about activators and cracks, which cause most cases. Remove them, rebuild the licensing store, repair system files, and reactivate properly after hardware changes. Genuine systems hit this too, and the same repair path fixes them — the licensing store rebuild alone resolves a large share of cases.

Frequently asked questions

What does SYSTEM_LICENSE_VIOLATION mean?
Windows’ software licensing components detected a violation severe enough to bugcheck (stop code 0x9A). Triggers include cracked activators, tampered licensing files, major hardware changes invalidating a digital license, or corrupted licensing store data.
Can a genuine Windows copy get this error?
Yes. Corrupted licensing store files, a failed update touching licensing components, or a motherboard replacement can trigger it on fully genuine systems. Genuine users should repair the licensing store, not reinstall.
Will fixing this deactivate my Windows?
The repair steps (SFC, DISM, rebuilding the licensing store) don’t deactivate genuine Windows. If your license was activated with a crack or loader, removing it will return Windows to unactivated — which is the correct and legal state.
I changed my motherboard and now get this BSOD. Why?
Digital licenses are tied to hardware. A motherboard swap invalidates the hardware ID, and the licensing subsystem can crash during revalidation. Use the Activation troubleshooter (Settings > System > Activation > Troubleshoot) to transfer the license.