How to Fix SYSTEM_LICENSE_VIOLATION (0x0000009A) Blue Screen Error in Windows

Quick Answer

SYSTEM_LICENSE_VIOLATION (0x0000009A) is a Windows bug check associated with a violation of the operating system's software licensing rules. The exact condition depends on the bug check parameters and the operation that was being performed when Windows crashed.

Record the complete stop code and any displayed parameters. If Windows cannot start, use the Windows Recovery Environment to try an appropriate recovery option, such as System Restore or Startup Repair. Avoid modifying licensing-related registry values or attempting to bypass evaluation restrictions. These general recovery procedures may help with startup problems, but they are not guaranteed fixes for every 0x0000009A violation.

What Is SYSTEM_LICENSE_VIOLATION?

SYSTEM_LICENSE_VIOLATION is a Windows stop error with the hexadecimal bug check value 0x0000009A. Windows displays a blue screen when it encounters a serious condition that prevents it from continuing safely.

Microsoft documents this bug check in its Windows debugger reference. The first bug check parameter identifies the violation category, and the meanings of the remaining parameters depend on that value.

The documented categories include attempts to change product-type or evaluation-period information in an offline Windows installation and failures involving certain setup or licensing-related operations. The stop code alone does not establish the precise cause of a particular crash.

Official reference: Microsoft Learn: Bug Check 0x9A — SYSTEM_LICENSE_VIOLATION.

Common Causes

The following are documented categories or circumstances worth investigating. They should not be treated as confirmed causes without supporting diagnostic evidence.

• Offline product-type changes: An attempt to modify the product type of an offline Windows installation.
• Evaluation-period changes: An attempt to alter the recorded evaluation period of an evaluation installation.
• Setup information failures: Problems opening or reading information required by a system operation.
• Licensing-related data failures: Errors involving product options or license information for software suites.
• Unsupported system modifications: Changes to protected system or licensing information that correspond to the documented violation parameters.

Other circumstances may be relevant to an individual crash. Use the actual bug check parameters, system history, and available crash evidence rather than assuming that an ordinary Windows activation warning caused the stop error.

Symptoms

A system affected by this bug check may exhibit the following symptoms:

• A blue screen displaying SYSTEM_LICENSE_VIOLATION.
• The stop code 0x0000009A in the crash details.
• An unexpected restart when Windows encounters the violation.
• Repeated crashes during startup or system initialization.
• Inability to reach the Windows sign-in screen when the crash occurs during boot.

These symptoms help identify the problem but do not determine its root cause.

Before You Begin

• Record the exact stop code and all available bug check parameters.
• Note recent Windows servicing, deployment, configuration, or licensing-related changes.
• Back up important files if Windows is still accessible.
• If device encryption or BitLocker is enabled, locate the recovery key before entering recovery tools.
• For a business-managed computer or Windows Server, consult the responsible administrator before changing system configuration.

How to Troubleshoot SYSTEM_LICENSE_VIOLATION

1. Record and Interpret the Bug Check Parameters

If the blue screen or diagnostic report contains additional parameters, record them exactly. The first parameter is particularly important because it identifies the violation category in Microsoft's reference.

Microsoft documents parameter values 0x00 and 0x01 for violations involving attempted offline changes to product-type and evaluation-period information, respectively. Other values describe different violation conditions.

Do not interpret the remaining parameters without consulting the documentation for the applicable first parameter. Their meanings are not necessarily the same across violation categories.

See the official SYSTEM_LICENSE_VIOLATION parameter reference.

2. Review Recent System Changes

Determine what happened immediately before the first crash.

1. Check whether an administrator recently changed the Windows product type or performed offline servicing.
2. Determine whether the installation is an evaluation edition and whether its configuration was modified.
3. Review relevant deployment scripts, system-management tools, or configuration changes.
4. Ask the system administrator to review recent changes if the device is managed by an organization.

Do not repeat a potentially problematic operation simply to reproduce the crash. The purpose of this step is to establish context and identify evidence that matches the documented bug check parameters.

3. Open the Windows Recovery Environment

If Windows cannot start normally, use the Windows Recovery Environment (WinRE) to access recovery tools.

1. Restart the computer and check whether Windows automatically enters its recovery environment after repeated startup failures.
2. If automatic recovery is unavailable, boot from compatible Windows installation media.
3. Select the option to repair the computer rather than proceeding with Windows installation.
4. Open Troubleshoot and then Advanced options.

The available menus depend on the Windows version and device configuration. BitLocker-protected installations may require the recovery key.

See Microsoft's Windows Recovery Environment guidance.

4. Try System Restore

System Restore can return certain system files, registry settings, drivers, and installed applications to an earlier restore point. It may be useful if the issue began after a relevant system change, but it is not a confirmed universal fix for this bug check.

1. Open WinRE and select Troubleshoot > Advanced options > System Restore.
2. Select an available restore point created before the problem began.
3. Review the available information about affected programs and settings.
4. Follow the instructions to complete the restoration and restart the computer.

If no suitable restore point exists, use another appropriate recovery method. System Restore is not a replacement for a separate backup of important files.

See Microsoft Support: System Restore.

5. Run Startup Repair

Startup Repair attempts to diagnose and repair certain problems that prevent Windows from starting. It may be appropriate when the computer cannot reach the sign-in screen, but it does not specifically resolve every licensing-related bug check.

1. Open the Windows Recovery Environment.
2. Select Troubleshoot > Advanced options > Startup Repair.
3. Select the Windows installation if prompted.
4. Follow the instructions and restart the computer after the process finishes.

If Startup Repair does not resolve the issue, record the reported result and proceed with targeted diagnostics.

See Microsoft Support: Startup Repair.

6. Examine Available Crash Dumps

If the computer repeatedly crashes, an IT technician can examine available crash dumps to obtain the bug check code, parameter values, and other diagnostic information.

On systems configured to save small memory dumps, check this standard directory:

C:\Windows\Minidump

The directory may not exist or contain a dump if Windows was not configured to save one or the crash prevented successful dump creation.

Use an appropriate Windows debugging tool and Microsoft's bug check documentation to interpret the available information. A module named in a crash report is not automatically the root cause.

Crash dumps can contain sensitive system information. Share them only through trusted support channels and review privacy implications before providing them to third parties.

7. Restore a Supported System Configuration

If the evidence identifies an unsupported modification to Windows product-type or evaluation information, use the appropriate supported recovery or deployment procedure.

• For managed computers, involve the administrator responsible for Windows deployment and licensing.
• For evaluation installations, follow the applicable official product and licensing guidance.
• If a script or third-party management tool changed the configuration, review its documented rollback procedure before making further changes.
• If the cause remains unclear, preserve the crash evidence and obtain qualified technical assistance before modifying protected system information.

There is no single universal repair command established by the bug check code for every possible violation category.

How to Verify the Repair

1. Restart the computer and confirm that Windows starts normally.
2. Use the system and check whether the same stop code reappears.
3. Review available system logs and crash information if another failure occurs.
4. For managed systems, ask the responsible administrator to confirm that the intended supported configuration has been restored.
5. Back up important files and retain the diagnostic details if the issue returns.

A successful restart does not necessarily prove that the underlying cause has been identified. Recurring crashes require further investigation.

When to Seek Technical Assistance

Consult a qualified Windows technician or system administrator if:

• The computer continues to crash after appropriate recovery attempts.
• The bug check parameters identify a violation that you cannot interpret.
• The affected computer runs a production server or business-critical workload.
• Recovery could risk important files, encryption access, or organizational configuration.
• Kernel crash dump analysis is required.

Provide the Windows version and edition, exact stop code, all available parameters, recent changes, and relevant diagnostic results.

Frequently Asked Questions

Does SYSTEM_LICENSE_VIOLATION mean Windows is not activated?

Not necessarily. The bug check identifies a software licensing violation detected by Windows, but an ordinary activation warning alone does not establish the cause of bug check 0x0000009A.

Can System Restore fix error 0x0000009A?

It may help when a suitable restore point predates a relevant system change. However, System Restore is not guaranteed to resolve every licensing-related violation.

Should I edit the registry to fix this stop code?

No, not as a general troubleshooting step. The code alone does not identify a specific registry value that should be changed. Unsupported edits may make the installation unbootable.

What does parameter 1 indicate?

Parameter 1 identifies the violation category. The meanings of the other parameters depend on its value. Consult Microsoft's official bug check reference before interpreting them.

Should I reinstall Windows?

Reinstallation should not be the first response. Identify the likely violation, protect important data, and consider supported recovery methods first. Reinstallation may be appropriate only when less disruptive options are unsuitable or unsuccessful and a supported installation path is available.

Sources

• Microsoft Learn: Bug Check 0x9A — SYSTEM_LICENSE_VIOLATION
• Microsoft Learn: Bug Check Code Reference
• Microsoft Support: Windows Recovery Environment
• Microsoft Support: System Restore
• Microsoft Support: Startup Repair