Modern Warfare 4 beta "BIOS Firmware: Update Required"? Here's what to do
By TourneyTime ·
The short version
“BIOS Firmware: Update Required” is not a broken motherboard and it is not a ban — it is RICOCHET’s hardware attestation check failing to confirm your PC’s security firmware. For the Modern Warfare 4 beta the consequence is harsher than anywhere else in Call of Duty: Activision’s own requirements page says both TPM 2.0 and Secure Boot are required, and that players who do not meet them cannot access any online game mode. In Black Ops 7 and Warzone the same failure only restricts you from “certain game modes (including Ranked Play)” and drops you into a separate matchmaking pool (Activision Support).
If you have not enabled anything yet, start with our full TPM 2.0 and Secure Boot walkthrough — that covers the straightforward case. This page is for the harder one: both settings are already on, you have already flashed a BIOS, and the game still says update required.
| What you are seeing | What it usually means | First move |
|---|---|---|
| ”BIOS Firmware: Update Required” with TPM and Secure Boot off | The check never ran properly | Enable Intel PTT or AMD fTPM plus Secure Boot |
| Same message, both already enabled | Your fTPM version is one Call of Duty rejects | Check the version in tpm.msc before reflashing |
| Passes the wizard, still blocked in game | Nothing you can toggle | See when it is not your PC |
What the beta actually requires
Straight from Activision’s requirements page, so these are the numbers to work from rather than anything you read in a thread:
| Requirement | What it needs |
|---|---|
| Windows | Windows 10 version 22H2 or later |
| Intel | 8th Gen or newer with Intel PTT |
| AMD | Ryzen 2000 series or newer with AMD CPU fTPM |
| Secure Boot | BIOS Boot Mode set to UEFI (not Legacy) |
| Disk | Partition style GPT (not MBR) |
All five are from Activision Support. The GPT line is the one that quietly catches people: if Windows was installed in Legacy/MBR mode, Secure Boot will be greyed out no matter how new the BIOS is.
Check your fTPM version before you flash anything again
This is the trap, and it is the reason “I already updated my BIOS” is not the end of the story. Activision rejects AMD fTPM software versions in the 3.*.0.* format — its own worked example is that 3.92.0.5 needs a firmware update, while 3.92.5.5 is accepted (Activision Support). Dexerto’s Modern Warfare 4 page reports the same rule: “Certain AMD systems with 3.x.0.x versions of TPM software aren’t compatible with CoD’s validation process, so you’ll need to update your BIOS” (Dexerto, 18 August 2026).
Check what yours is actually reporting:
- Win + R, type
tpm.msc, press Enter. - Look under TPM Manufacturer Information → Manufacturer Version.
- If it reads 3.x.0.x, you need newer board firmware. If it reads 3.x.5.x or higher, the version is not your problem and another BIOS flash will not help.
The bit worth knowing: a BIOS update only fixes this if that particular release actually bumps the fTPM version. Plenty of players have flashed to the newest firmware their board offers, checked tpm.msc, and found the same 3.x.0.x string staring back. Check the number, not the BIOS date.
Run the Secure Attestation Wizard
Before changing anything, use Activision’s own tool. The Call of Duty Secure Attestation Wizard scans your BIOS and either reports the system as compliant or tells you the specific component that is failing — TPM not enabled, Secure Boot disabled, and so on (Activision Support). Dexerto recommends the same order of operations: run the check first, then go into BIOS (Dexerto).
It is a five-minute step that stops you reflashing a board over a Secure Boot toggle.
What players are trying when the BIOS is already current
Everything in this section is community-reported and none of it appears on any official Activision page. We are including it because it is what the threads are full of, but treat it as “worth a try”, not as documented procedure — and do not touch BIOS settings you do not recognise.
enrollaik.exe— an executable in the Call of Duty install folder that players run manually to re-register the TPM’s attestation key. Reported both as a fix and, in the longest-running thread on Activision’s own Steam discussion board, as something that changed nothing.- The Call of Duty Broker Service — players report finding it disabled in
services.mscand getting through the check after setting it to start and launching the game again. - Clear TPM, then reflash — clearing the TPM in Windows TPM Management, then re-enabling fTPM and updating firmware, in that order.
- The error code doing the rounds is
0x80070490, which is what several r/CODWarzone reports quoted alongside the BIOS firmware message. It is not documented anywhere official we can find, so do not read a specific cause into it.
One player who tested BIOS updates, fTPM enable/disable cycles, TPM resets, Secure Boot checks, a manual enrollaik.exe run, a full game reinstall and Windows service checks reported that none of them worked (Steam Community). That is the honest state of play.
Sometimes it is not your PC
This is the part most fix lists leave out. In that same thread, the player says Activision support — after confirming the system was configured correctly — replied that “Our studio teams are actively investigating this issue. We do not have an exact time frame” (Steam Community). We cannot independently verify a support reply posted by a player, so weigh it accordingly, but it matches what the r/CODWarzone threads describe: correctly configured machines failing anyway.
And there is a group with no route out at all. If your board or laptop has no newer firmware available, there is nothing you can toggle to change the reported version — some manufacturers stop issuing BIOS updates within a year or two of release. If that is your situation, stop reflashing and wait for a game-side fix.
Why this is blowing up now
Timing. Preloading for the open beta opened on Wednesday 26 August at 9AM PT, and the open beta itself runs from Friday 28 August at 10AM PT to Tuesday 1 September at 10AM PT — no pre-order or beta code needed, on every platform (Dot Esports). Weekend One was pre-order only; Weekend Two is everyone. That means a far larger group of PC players is about to install the beta and meet the attestation wall for the first time.
If you are on AMD, check tpm.msc today rather than at 6PM on Friday. A BIOS flash is not something to rush.
Sources & how we keep this current
We anchor the hard requirements to Activision’s own page and label anything community-reported as exactly that. Last checked 26 August 2026 (MW4 beta, ahead of the Weekend Two open beta).
- Activision Support — TPM 2.0 and Secure Boot for Call of Duty (the requirement, the MW4 beta lockout, the AMD fTPM version rule, the Secure Attestation Wizard): support.activision.com
- Dexerto — How to enable Secure Boot & TPM 2.0 to play Modern Warfare 4 (18 August 2026): dexerto.com
- Dot Esports — Modern Warfare 4 open beta dates: dotesports.com
- Steam Community — official Call of Duty discussions, attestation megathread (player testing and the support reply): steamcommunity.com
- r/CODWarzone — the current wave of reports: reddit.com
Still locked out? Our full TPM 2.0 and Secure Boot guide covers the from-scratch setup, and if you are getting a PC ready for Weekend Two, the best MW4 beta PC settings are worth ten minutes. Drop into our Warzone Discord if you want a second pair of eyes on a BIOS screen.
