Skip to content
PCDecoder
0x0000009ASYSTEM_LICENSE_VIOLATIONStop codeWidely reported

SYSTEM_LICENSE_VIOLATION (0x9A): what it means and how to fix it

Updated Oct 20, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Bug check 0x0000009A indicates that Windows detected a violation of its software licensing terms or failed to read critical licensing records. It most often happens when registry keys like ProductOptions or setup data become corrupted, missing, or damaged after a failed system restore. The first step is to run Startup Repair from the Windows Recovery Environment to fix broken startup data.

What it means

Windows enforces its licensing parameters through low-level registry keys and kernel checks during startup. These components track whether an installation is a client or server edition, verify evaluation time limits on trial versions, monitor the licensed processor count, and check system setup states. Stop code 0x0000009A appears when the operating system detects that these parameters have been violated or when the kernel worker threads cannot access the underlying records.

Why the check fails

Under the hood, Windows looks for specific registry paths and values, including the setup key, SystemPrefix, SetupType, SetupInProgress, and ProductOptions. If an unauthorized tool attempts to convert a client installation to a server edition offline, reset an evaluation time period, or alter the licensed processor limit, Windows deliberately halts the system with this bug check. The system also triggers 0x9A if the internal policy cache has been modified outside normal operating parameters.

Corruption vs. actual violations

Most home and office users who see this error have not attempted to manipulate their license. Instead, disk errors, power cuts during registry writes, failed Windows updates, or incomplete System Restore operations can corrupt the system hive. If the kernel attempts to read the ProductType value, query LicenseInfoSuites, or set up change notifications on ProductOptions and encounters a read failure, it treats the missing or unreadable license data as an integrity failure. Because the operating system cannot verify that it is running within its legitimate boundaries, it generates a blue screen to prevent further operations under an invalid license state.

Common causes

  • Corrupted or missing system registry keys such as ProductOptions, the setup key, or LicenseInfoSuites.
  • Interrupted or damaged registry state following a failed System Restore or Windows update.
  • Missing startup values such as SetupType, SetupInProgress, or SystemPrefix in the setup registry.
  • Offline modifications to the Windows trial period or operating system product type.
  • Unauthorized changes to the licensed processor count or system policy cache.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run Startup Repair

    Use this first when Windows crashes with 0x9A during startup and cannot reach the desktop.

    1. Power on your computer, and as soon as the Windows logo appears, hold down the power button until the computer turns off completely.
    2. Repeat this process two more times until Windows boots into Automatic Repair.
    3. Select Advanced options on the blue recovery screen.
    4. Navigate to Troubleshoot, then select Advanced options.
    5. Click Startup Repair and allow the tool to diagnose and repair damaged startup configuration files.
    Did this fix it?

  2. Revert to a previous System Restore point

    Use this if the crash began immediately after a recent update, software installation, or previous restore attempt.

    1. Boot into the Windows Recovery Environment using the power button interruption method or Windows installation media.
    2. Click Troubleshoot, then select Advanced options.
    3. Select System Restore.
    4. Choose a restore point created prior to the appearance of the 0x9A stop code.
    5. Follow the prompts to confirm your choice and let the restoration complete without powering off your PC.
    Did this fix it?

  3. Repair system files and disk errors via Command Prompt

    Use this when licensing registry entries or system components may be damaged by file system errors.

    1. From the Windows Recovery Environment, select Troubleshoot, then Advanced options, then Command Prompt.
    2. Type sfc /scannow and press Enter to scan and repair protected system files.
    3. Type chkdsk C: /f /r and press Enter to scan the primary partition for bad sectors and directory errors.
    4. Close Command Prompt once both tasks finish and restart your computer.
    Did this fix it?

  4. Reset Windows

    Use this as a last resort if system hives are permanently damaged and other recovery tools cannot repair the licensing configuration.

    1. Access the Windows Recovery Environment.
    2. Select Troubleshoot, then click Reset this PC.
    3. Choose Keep my files to preserve personal data, or select Remove everything for a completely clean reinstallation.
    4. Select Local reinstall to rebuild the operating system from existing local recovery files.
    5. Follow the remaining on-screen instructions to finish the reset process.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 14, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Does SYSTEM_LICENSE_VIOLATION mean my copy of Windows is pirated?

Not necessarily. Although it triggers if activation rules or product types are altered, it routinely happens on genuine systems when the registry keys containing licensing data become unreadable or corrupted.

Can a failed System Restore cause stop code 0x9A?

Yes. An interrupted System Restore can leave the registry in an inconsistent state where crucial values like ProductOptions or SetupInProgress are missing, prompting Windows to crash on boot.

How do I fix 0x9A if I cannot get past the blue screen?

Interrupt your computer's boot process three times in a row using the power button to open the Windows Recovery Environment, then run Startup Repair or use System Restore from the Advanced options menu.

More stop codes decoded