How to Enable Secure Boot and TPM 2.0 for Highguard on Windows PCs

If Highguard refuses to launch on your PC, Secure Boot or TPM 2.0 is usually disabled in your system firmware. Highguard relies on kernel-level anti-cheat protection, which only works when these security features are active.

How to Enable Secure Boot and TPM 2.0 for Highguard on Windows PCs
How to Enable Secure Boot and TPM 2.0 for Highguard on Windows PCs

This guide walks you through checking your current status and enabling Secure Boot and TPM 2.0 safely on Windows.

Step 1: Check If Secure Boot Is Already Enabled

Before changing anything in BIOS, confirm whether Secure Boot is already active.

Do this:

  • Press Windows + R to open Run.
  • Type msinfo32 and press Enter.
  • In System Summary, locate Secure Boot State.
  • If it shows On, Secure Boot is already enabled.
  • If it shows Off, you must enable it in BIOS.

This quick check avoids unnecessary BIOS changes.

Step 2: Check If TPM 2.0 Is Enabled

TPM 2.0 must also be active for Highguard to run correctly.

Do this:

  1. Press Windows + R.
  2. Type tpm.msc and press Enter.
  3. In the TPM Management window, check Status.
  4. If it says “The TPM is ready to use”, TPM is enabled.
  5. If it shows not ready or not found, you must enable TPM in BIOS.

Step 3: Enter Your BIOS / UEFI Settings

You enable Secure Boot and TPM inside your motherboard firmware.

How to enter BIOS:

  1. Restart your PC.
  2. As soon as the manufacturer logo appears, repeatedly press Delete, F2, or F12 (varies by brand).
  3. The BIOS or UEFI setup screen opens.

If Windows loads instead, restart and try again.

Step 4: Enable TPM in BIOS

TPM settings appear under Advanced, Security, or Trusted Computing menus depending on your motherboard.

Look for one of these options:

  • TPM
  • fTPM (AMD)
  • PTT (Intel Platform Trust Technology)
  • Trusted Platform Module
  • Firmware TPM

Set the option to Enabled.

Save changes if your BIOS requires a restart.

Step 5: Set BIOS Mode to UEFI (Disable Legacy / CSM)

Secure Boot only works in UEFI mode.

Do this inside BIOS:

  1. Open Boot Settings.
  2. Find Boot Mode, CSM, or Legacy Support.
  3. Select UEFI.
  4. Disable CSM / Legacy Mode if enabled.

If your Windows drive uses MBR instead of GPT, Secure Boot will not activate. Back up your data before converting disk formats.

Step 6: Enable Secure Boot

After switching to UEFI:

  1. Go to Boot or Security section.
  2. Locate Secure Boot.
  3. Set it to Enabled.
  4. If prompted, select Standard Mode or Install Default Keys.
  5. Save settings and exit BIOS.

Your PC will reboot automatically.

Step 7: Verify Secure Boot and TPM Again

After reboot:

  • Open msinfo32 → Confirm Secure Boot State = On.
  • Open tpm.msc → Confirm TPM status shows Ready to use.

Once both are active, Highguard should launch normally.

Common Fix If Secure Boot Won’t Enable

If BIOS displays a message like:

Secure Boot can be enabled only after enrolling platform keys.

Fix it:

  1. Enter BIOS → Secure Boot section.
  2. Change Secure Boot Mode to Custom.
  3. Select Enroll Default Keys.
  4. Save and reboot.
  5. Return to BIOS → Switch mode back to Standard.
  6. Enable Secure Boot.

Why Highguard Requires Secure Boot and TPM 2.0

Secure Boot prevents unauthorized drivers or cheats from loading during startup.

TPM 2.0 provides hardware-based protection and validates system integrity.

Together, they allow Highguard’s anti-cheat system to operate securely and block kernel-level tampering.

Can You Play Highguard Without Secure Boot?

No. Highguard will not launch without Secure Boot enabled. The anti-cheat system blocks gameplay if system security requirements are not met.

If you follow the steps above carefully, you should enable Secure Boot and TPM 2.0 without affecting your system stability. Once both features are active, restart your PC and launch Highguard normally.

If you encounter BIOS-specific menus or disk format warnings, proceed carefully and always back up important data before making structural changes.

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply