Fixing "BIOS Firmware Update Required" in Warzone

ATTESTATION: RESOLVABLE / PINK PARSNIP DIAGNOSTIC NOTES
Ricochet · Call of Duty · PC Hardware

Fixing "BIOS Firmware Update Required" in Warzone

Ricochet blocked your access to multiplayer with a "Failed Attestation" screen. Most of the time this is a Windows or BIOS setting, not a dead end — work through the checklist below before you go anywhere near a BIOS flash.

Secure Boot StateOn
TPM 2.0 DevicePresent
Virtualisation-based SecurityEnabled, not running
fTPM Firmware Version3.x — below minimum
01

Confirm what Windows currently sees

Before changing anything, check your baseline.

msinfo32

  1. Press Win + R, type msinfo32, hit Enter.
  2. Check Secure Boot State — should read On
  3. Check BIOS Mode — should read UEFI, not Legacy
  4. Check Virtualisation-based security — should read Running
02

Enable TPM 2.0 and Secure Boot in BIOS

Reboot, press Del or F2 at POST.

  1. Advanced → Trusted Computing — set Security Device Support to Enable, Device Selection to TPM 2.0
  2. Advanced → PTT Configuration (if present) — set Device Selection to PTT
  3. Boot → Secure Boot — set to Enabled, install default keys if prompted
  4. Confirm Windows is on GPT (not MBR) and BIOS is in UEFI mode — Secure Boot won't hold otherwise
03

Clear and reprovision the TPM

A TPM that "shows enabled" but was configured before Secure Boot was on can be stuck in a stale state.
  1. Win + Rtpm.msc
  2. Actions pane → Clear TPM… → confirm
  3. Restart — confirm any firmware prompt during POST, don't skip it
  4. Reopen tpm.msc, confirm it reads "The TPM is ready for use."
04

Get VBS actually running, not just enabled

This is the most common silent blocker — Ricochet checks that Memory Integrity is active, not just switched on.

In BIOS

  • SVM Mode (CPU Configuration) → Enabled
  • NX Mode / No-Execute Memory Protection → Enabled — frequently the actual fix when SVM alone isn't enough

In Windows

  1. Settings → Privacy & Security → Windows Security → Device Security → Core Isolation
  2. Toggle Memory Integrity off, then back on, restart
  3. Recheck msinfo32 — should now say Running
⚠ If Above 4G Decoding crashes your boot Some budget/generic boards don't handle this cleanly. If Windows hangs on the loading wheel after enabling it: force shutdown, go back into BIOS, and set Above 4G Decoding back to Disabled. It isn't required for VBS or attestation — NX Mode and SVM are the settings that matter here.
05

Relaunch the game

Fully close Battle.net and any Call of Duty processes in Task Manager — don't relaunch over a stuck process, Ricochet's driver can cache a stale session. Reboot the whole PC once, then try again.

06

Still failing? It's the fTPM firmware version

If TPM is active, Secure Boot is on, and VBS is confirmed Running — but you're still seeing "BIOS firmware: Update Required" — the actual firmware version inside your TPM module is the problem, not its presence.

On AMD platforms, Ricochet rejects fTPM firmware in the 3.x.x.x range and requires 6.32.5.6 or newer. That version only ships bundled inside a BIOS update carrying a newer AGESA release — there's no setting that fixes this.

Check yours: BIOS → Advanced → Trusted Computing → Firmware Version

07

Before hunting for a BIOS update

Your odds of a safe, working fix depend heavily on what board you actually have.
Best odds

Branded — recent chipset

MSI / ASRock / ASUS / Gigabyte on B450/B550/X470/X570. Most have shipped an AGESA update fixing this. Check the official support page for your exact model + revision.

Uncertain

Branded — older chipset

A320 / original X370 boards, even from major vendors. Support is inconsistent — some got the fTPM fix, many were simply never updated for it.

High risk

Unbranded / generic factory boards

JGINYUE, Machinist, Ninkear, T-Creator, or no name at all. Usually one shared ODM PCB resold under several labels, often with no dedicated official BIOS page. Flashing an unverified file here risks bricking the board.

Bottom line Always run through steps 01–05 fully before considering a flash. If your board is unbranded and no verified official BIOS exists for it, full Ricochet compliance may genuinely not be achievable on that hardware — a chipset/board upgrade is the safer recommendation over flashing an unverified file.

Contact us