Skip to content
PCDecoder
0x00000145SECURE_BOOT_VIOLATIONStop codeWidely reported

SECURE_BOOT_VIOLATION (0x145): what it means and how to fix it

Updated Nov 8, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Bug check 0x00000145 indicates that Windows could not start Secure Boot policy enforcement due to an invalid policy or an incomplete required operation. This typically happens during system startup when boot policies, certificates, or firmware are mismatched. The first step is to run Windows Startup Repair to verify and restore system boot components.

What it means

What Windows is reporting

The SECURE_BOOT_VIOLATION bug check carries a value of 0x00000145. When this stop code appears, Windows has halted because Secure Boot policy enforcement could not be started. Secure Boot functions at the firmware level to ensure that the computer executes only validated, trusted boot files when starting up. If the enforcement mechanism cannot initialize, Windows stops the boot sequence immediately to prevent potentially untrusted code from running.

Why the policy enforcement fails

According to Windows technical documentation, error 0x00000145 occurs when the system encounters an invalid Secure Boot policy or when a required startup operation fails to complete. Secure Boot relies on policies and certificate authorities embedded in system firmware to evaluate boot binaries. If policy data in memory is malformed, has an invalid structure, or does not match expected integrity checks, the operating system aborts startup. Issues can arise after system updates, changes to UEFI firmware, or when boot binaries and certificate authorities—such as the Windows UEFI CA—are mismatched or outdated.

Debugging parameters

When a SECURE_BOOT_VIOLATION stop code is triggered, the system generates four specific parameters:

  • Parameter 1: The status code of the failure, identifying the exact reason the enforcement check was rejected.
  • Parameter 2: The memory address where the Secure Boot policy is located.
  • Parameter 3: The size of the Secure Boot policy in bytes.
  • Parameter 4: Reserved by Windows for system use.

These values provide low-level memory details about where the policy was loaded and why Windows deemed it invalid. For users, resolving the error requires restoring boot integrity through recovery tools or updating UEFI firmware to provide proper certificate support.

Common causes

  • An invalid or malformed Secure Boot policy loaded into memory during startup.
  • A required Secure Boot verification operation that failed to complete.
  • Outdated UEFI firmware lacking required Secure Boot Certificate Authority updates.
  • Corrupted Windows boot binaries following an update or system crash.

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 from Windows Recovery

    Use this when the system halts with stop code 0x145 during startup and cannot boot into the desktop.

    1. Power on your computer and hold down the physical power button for 10 seconds to force a shut down as soon as the Windows logo appears.
    2. Repeat this process twice until the system boots into the Automatic Repair environment.
    3. Select Troubleshoot on the Choose an option screen.
    4. Click Advanced options.
    5. Select Startup Repair.
    6. Choose your administrator account, enter your password if prompted, and allow Windows to automatically check and restore boot files.
    Did this fix it?

  2. Update your system UEFI firmware

    Use this when policy enforcement fails due to outdated firmware certificates or following system updates that require new certificate authority support.

    1. Go to the official support and driver download page of your computer or motherboard manufacturer using a secondary computer.
    2. Search for your exact computer model or motherboard model number.
    3. Download the latest UEFI/BIOS firmware update file.
    4. Copy the update files to a USB flash drive formatted to FAT32.
    5. Restart your computer, press the designated key (such as F2, F12, or Del) to enter UEFI setup, and open the built-in firmware flashing utility to install the update.
    Did this fix it?

  3. Rebuild boot files using the Command Prompt

    Use this if Startup Repair cannot automatically resolve boot binary mismatches.

    1. Boot into the Windows Recovery Environment using a recovery drive or Windows installation media.
    2. Select Troubleshoot, then select Advanced options.
    3. Click Command Prompt.
    4. Type `bcdboot C:\Windows` and press Enter to generate fresh boot files linked to your Windows installation.
    5. Type `exit` and press Enter once the confirmation message appears.
    6. Click Continue to restart your PC.
    Did this fix it?

  4. Run the Blue Screen troubleshooter

    Use this if Windows is still able to load the desktop intermittently between crashes.

    1. Open Settings by pressing Windows key + I.
    2. Select System from the left menu, then click Troubleshoot.
    3. Click Other troubleshooters.
    4. Locate the automated troubleshooting utility for Windows system errors and click Run.
    5. Follow the prompts to let Windows diagnose and repair the fault.
    Did this fix it?

Is it just you?

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

Checked Nov 5, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What is bug check 0x00000145 SECURE_BOOT_VIOLATION?

Bug check 0x00000145 indicates that Windows halted startup because Secure Boot policy enforcement could not be initiated due to an invalid policy or an incomplete verification step.

Will error 0x145 lock me out with BitLocker?

Firmware and boot integrity errors can trigger BitLocker recovery prompts. Keep your 48-digit BitLocker recovery key ready if your drive is encrypted.

What do the four parameters mean on a 0x145 blue screen?

Parameter 1 is the failure status code, Parameter 2 is the memory address of the Secure Boot policy, Parameter 3 is the policy size, and Parameter 4 is reserved for system use.

More stop codes decoded