How to Fix "Invalid Signature Detected: Check Secure Boot Policy in Setup" Error

The "Invalid Signature Detected: Check Secure Boot Policy in Setup" error typically occurs when Secure Boot is enabled in BIOS or UEFI, blocking the boot of unsigned software. Secure Boot is a feature that protects the system from unauthorized loaders, but it can sometimes interfere when installing new components or changing the operating system.

What Causes This Error?

Secure Boot checks for a digital signature on all booting components. If the OS or drivers you’re trying to load lack the required signature, the system will block them. This error commonly appears in situations like:

  • Installing an alternative operating system (such as Linux).
  • Using unsigned or outdated drivers.
  • Changing hardware components, like a graphics card or hard drive.

How to Resolve the "Invalid Signature Detected" Error

1. Disable Secure Boot in BIOS/UEFI

To disable Secure Boot, follow these steps:

  1. Restart your computer and enter BIOS/UEFI. This is usually done by pressing Del, F2, or Esc immediately after turning on the PC.
  2. Locate the Boot or Security section, depending on your system model.
  3. Find the Secure Boot option and switch it to Disabled.
  4. Save your changes and exit, then restart the system.

2. Install the Required Signed Drivers

In some cases, installing the latest, signed drivers from the manufacturer can resolve this issue. To do this:

  1. Visit the official website of your device’s manufacturer.
  2. Download and install the updated drivers that support Secure Boot.

3. Install Certificates for Secure Boot

If you wish to keep Secure Boot enabled but avoid the block, you can manually install certificates for the necessary applications. This is a more advanced process that requires careful handling.