Quick answer

Open msinfo32 and read BIOS Mode and Secure Boot State, then check the Windows disk’s partition style. On means enabled state only. Off or Unsupported does not prove one universal fix. Before any firmware, TPM, key, or conversion change, save the recovery key and follow the exact game, disk, motherboard, and certificate branch below.

Contents

At a glance

Class
Gaming

Provenance

  • Oct 2, 2026Published
  • Oct 23, 2026Last substantive update

Call of Duty’s RICOCHET, EA Javelin, Riot Vanguard and FACEIT can stop a game over Secure Boot, TPM or attestation policy. Start with evidence instead of a reset: open msinfo32, record BIOS Mode and Secure Boot State, then read the Windows disk’s Partition style. Secure Boot State On confirms enabled state. It does not prove that 2023 certificates were serviced, TPM attestation passed or a game will accept the PC.

The game rules are specific. Modern Warfare 4 requires TPM 2.0 and Secure Boot for all online modes; Activision describes restricted modes or separate matchmaking for Black Ops 7 and Warzone. FACEIT’s Windows 10 22H2, ESU and current-update policy took effect October 14, 2026. The October 23 additions below are documentary research, separate from the exact October 2 owner observation retained in the TPM section.

Find your error message

Each row preserves the publisher’s message and scopes its published explanation. Where a message does not prove one cause or remedy, the table says so. The last column opens the matching branch below.

Game or anti-cheatWhat you seeWhat the publisher says it meansFix
Call of Duty (BO7, Warzone, MW4)Secure Attestation Wizard: “Secure Boot: Not Enabled”MW4 requires the security checks for all online modes; Activision names specified BO7/Warzone modes or playlists and possible separate matchmakingRead msinfo32
Call of Duty“BIOS Boot mode not set to UEFI” or “Boot Partition not set to GPT”Secure Boot cannot run until the PC boots UEFI from a GPT diskLegacy or MBR
Call of Duty“TPM 2.0: Not Enabled”, or tpm.msc shows “Compatible TPM cannot be found”Activision routes this to TPM enablement and support checks; the message alone does not separate themThe TPM half
Call of DutyThe enrollaik.exe prompt keeps coming back after you click YesActivision identifies one AMD firmware-version pattern; recurrence alone does not prove that cause on this PCThe TPM half
Call of Duty“TCG Event Log Failed”Windows is not up to dateCall of Duty
Call of Duty“Failed Attestation Status”Activision’s general article names restricted modes and possible separate matchmaking; its narrower wording does not settle MW4’s all-online ruleCall of Duty
EA Javelin games, Battlefield 6 included“The application encountered an unrecoverable error.”EA says expired or unsigned drivers can cause it; that cause and EA’s suggested remedy remain conditional for this PCBattlefield 6
Valorant, League (Vanguard)VAN 9003Secure Boot is not enabledRead msinfo32
Valorant, League (Vanguard)VAN 9001Vanguard does not detect TPM 2.0 as enabledThe TPM half
Valorant, League (Vanguard)VAN: STATUS_SB_POLICY, “The secure boot policy on this device could not be verified”Riot reports a policy-verification problem; the code does not prove that a generic key reset is safe or sufficientEnabled but not active
FACEIT“Please set Secure Boot preset to ‘Maximum Security’ in your BIOS”Some MSI boards’ default settingsEnabled but not active
FACEIT“TPM attestation failed”Possibilities include a discrete TPM, old GRUB, a self-signed loader, a revoked loader present in DBX or an internet-cafe tool; none is diagnosed from the message aloneThe TPM half
Easy Anti-Cheat games“Boot validation failed: Measured bootlog not found”, “Boot validation failed: PCR mismatch”, or “Unable to verify Secure Boot. Event missing from measured bootlog”Distinct missing-log, PCR-mismatch and missing-event branches, where that game’s developer uses EAC boot validationThe EAC guide
Any PC, at power-on“Secure Boot Violation” or “Invalid Signature Detected”A signature failure with several possible trust, firmware and boot-file causes; the screen alone does not identify oneIt will not boot

VAN 1067 is missing on purpose. Riot says it usually means an unexpected Vanguard startup or check-in problem, not a specific Secure Boot diagnosis. The rest of Riot’s codes are in the Vanguard error code table. Riot also published a September 22 notice about incorrect error-code display, but that notice is explicitly for VALORANT; it does not name the affected codes or an end date and should not be transferred to League or every Vanguard title.

Before you touch the BIOS

The firmware, TPM and disk-conversion branches can lock you out of Windows if they go in the wrong order. Do these first.

  1. Get your BitLocker recovery key. From another device, open aka.ms/myrecoverykey and sign in with the Microsoft account you use on this PC. If a key is listed for it, write it down. Microsoft’s list of events that send a PC to the BitLocker recovery screen includes a BIOS or UEFI firmware upgrade, clearing or disabling the TPM, changes to the boot manager and changes to the partition table. The change branches below can touch one or more of those.
  2. Suspend BitLocker for the BIOS work. In an administrator PowerShell, run Suspend-BitLocker -MountPoint "C:" -RebootCount 0. The 0 matters. Without it, protection resumes after the next restart, and BIOS work takes several. If your Windows disk is MBR, the conversion section asks for encryption to be off rather than suspended, so read it before you choose. Either way, the last section turns protection back on.
  3. Back up anything you would miss. GIGABYTE puts this in its own preparation list, and Riot says the disk conversion “cannot be reversed”.

Read msinfo32 first

Press Windows+R, type msinfo32 and press Enter. On the System Summary page, find BIOS Mode and Secure Boot State. Riot’s, EA’s and FACEIT’s Secure Boot guides start here, and so do MSI’s and GIGABYTE’s.

BIOS ModeSecure Boot StateWhat it meansGo to
UEFIOnSecure Boot is enabled in the running Windows state; certificate servicing, TPM attestation and game acceptance remain separateContinue with the exact message
UEFIOffSecure Boot is off; this does not establish GPT readiness, the correct firmware key state or a one-switch fixCheck the disk, then UEFI/Off
LegacyOff or UnsupportedWindows is using the legacy boot path; record the partition style before changing firmwareLegacy or MBR
UEFIUnsupportedThe observation needs exact-model, firmware and command context; it does not prove the board must be replacedState Unsupported

Microsoft documents that Confirm-SecureBootUEFI returns True when Secure Boot is on and False when it is off. Its unsupported-platform result is not False, and its access-denied result means the observation was not obtained with the required privilege. Neither error establishes the board’s future support, its certificate state or game acceptance.

Also check the disk. Open Disk Management, right-click the disk that holds Windows, choose Properties and open the Volumes tab. Partition style reads GPT or MBR. MBR changes the plan.

Legacy or MBR: convert the disk first

This is the step that stops Windows from booting when it goes wrong. Read it twice. If you switch the BIOS to UEFI, or turn CSM off, while the Windows disk is still MBR, Windows will not boot. MSI and GIGABYTE say so, and so does Riot. Riot’s version: “You must convert MBR > GPT before changing anything in BIOS.”

Microsoft’s MBR2GPT tool converts the system disk in place without deleting data. It refuses to run unless the disk passes its checks, including at most three primary partitions, no extended or logical partition, and room for the GPT tables. Riot and Activision add their own conditions: Windows 10 version 1703 or later, 64-bit Windows, no dual boot, firmware that supports UEFI, and Secure Boot off.

Encryption needs a decision first. Microsoft says MBR2GPT converts a BitLocker volume as long as protection is suspended, but to resume BitLocker afterwards the existing protectors have to be deleted and recreated. Activision’s and Riot’s checklists say BitLocker or any other encryption must be turned off, and Microsoft’s return code 6 is a conversion that failed because a volume on the disk is encrypted. I would follow Activision and Riot. In an administrator PowerShell, Disable-BitLocker -MountPoint "C:" removes all key protectors and starts decrypting the drive. Let it finish before you run the conversion.

Decrypting leaves the drive unprotected until you encrypt it again. Use the protection step as soon as the applicable conversion or firmware work is finished and Windows boots. Do not wait for Secure Boot, certificate servicing or a game to turn green.

Then, in an administrator Command Prompt:

mbr2gpt /validate /allowFullOS
mbr2gpt /convert /allowFullOS

Run the validate line alone first. It changes nothing. It only reports whether the disk can be converted. Without /disk:, both lines act on the system disk. Microsoft lists return code 0 as “Conversion completed successfully”; anything else is a failure with its own meaning in Microsoft’s table.

Riot’s next instruction is to go straight into the BIOS rather than booting Windows. Change Boot Mode from Legacy or CSM to UEFI, disable CSM if that option exists and save. Then confirm Windows starts. Only then turn on Secure Boot, which is the next section.

UEFI with Secure Boot off: switch it on

To get into the firmware from Windows 11, open Settings > System > Recovery and select Restart now beside Advanced startup. Then pick Troubleshoot > Advanced options > UEFI Firmware Settings. The CPU temperature guide walks the same route. Activision lists Del, F2 or F10 at power-on as the other way in.

The switch has a different name on every board. These paths come from each vendor’s own page:

  • ASUS desktop boards. Press Delete, open Advanced Mode, then Boot, Secure Boot, and set OS Type to Windows UEFI mode. ASUS’s own table says Other OS means Secure Boot state is off. The Secure Boot State line is grey and cannot be set by hand.
  • MSI (MAG B550 TOMAHAWK as MSI’s example). Open Settings, Advanced, Windows OS Configuration and switch BIOS CSM/UEFI Mode to UEFI. MSI says the Secure Boot option only appears after that. Enable it, press F10 and reboot.
  • GIGABYTE (AM4 and sTRX4). Open Advanced Mode, Boot, and set CSM Support to Disabled, which makes the Secure Boot menu appear. Enable Secure Boot, then verify the running result in Windows. If keys are missing, use the procedure for the exact board and current certificate state rather than assuming that factory defaults contain every required 2023 trust entry.

For an ASRock or Biostar board, or a Dell, HP or Lenovo PC, use the manual. Activision’s and EA’s articles both link each manufacturer’s own Secure Boot page.

Save with F10, boot into Windows and run msinfo32 again. Secure Boot State should now read On.

Enabled in the BIOS but not active

This case confuses people because the BIOS says Enabled, msinfo32 says Off, and the game keeps refusing to start even after a cold boot and a second look at every menu. The switch is on. The thing it switches is not running. Work these in order:

  1. CSM is still on. Secure Boot cannot run in a Legacy or CSM boot, and on GIGABYTE and MSI boards the Secure Boot menu is hidden until CSM is off. msinfo32 showing BIOS Mode Legacy confirms it. Go back to Legacy or MBR before you change it.
  2. The trust keys need a model-specific route. Do not treat Reset to Setup Mode as another name for Restore or Install Default Keys: setup mode deletes the key databases, while restoration enrolls keys. Microsoft’s troubleshooting guide says a defaults reset after a PC has moved to the 2023-signed Windows boot manager can remove required trust when the firmware defaults are older. Updated OEM defaults that explicitly contain the required 2023 trust are a conditional exception. Microsoft’s different firmware-overwrite case, while the older 2011 boot manager remains, permits an attempted reset followed by the applicable OEM correction. These are two different states, not a universal reset rule or a universal ban.
  3. The ASUS setting is Other OS. On ASUS desktop boards, the Secure Boot toggle is OS Type, and ASUS says Other OS means Secure Boot state is off.
  4. Vanguard says STATUS_SB_POLICY. Riot’s STATUS_SB_POLICY route discusses key reset, but the code alone does not establish that a generic reset is safe or sufficient. Reconcile the Riot route with the exact motherboard procedure and the current Windows certificate state in step 2.
  5. FACEIT asks for “Maximum Security”. FACEIT’s MSI procedure says some boards have a known issue where Secure Boot does not work properly with default settings, even when it shows Enabled in the BIOS and Windows. On a recent MSI BIOS, open Settings, Security, Secure Boot, set Secure Boot Mode to Custom and Secure Boot Preset to Maximum Security. On an older BIOS without that preset, FACEIT’s path is Image Execution Policy, with Removable Media and Fixed Media set to Deny Execute. FACEIT says to update the BIOS if neither option exists.
  6. The measured-boot evidence is missing. Easy Anti-Cheat’s “Unable to verify Secure Boot. Event missing from measured bootlog” message says the expected event was not found. Check current firmware and the exact developer branch. The message does not prove the installed firmware is old, and a BIOS update is not a guaranteed fix. Easy Anti-Cheat’s current support articles and the focused EAC guide keep “Boot validation failed: Measured bootlog not found”, “Boot validation failed: PCR mismatch” and the missing-Secure-Boot-event message separate.

For the certificate-specific ASUS route, ASUS prefers Windows Update. Its manual alternative puts an applicable BIOS update before its documented key operations; later Windows boot-manager servicing is still a separate step. Microsoft documents that a missing required OEM PK-signed KEK can block servicing without a supported manual workaround. The one-certificate recovery utility below does not restore that authorization.

Secure Boot State Unsupported

Read the BIOS Mode line beside it. Legacy with Unsupported is the Legacy case, and Riot’s guide sends both “Off” and “Unsupported” there.

UEFI with Unsupported needs exact-model evidence. EA says to check the motherboard specification sheet or manual. A missing setting or absent update can reflect the processor, firmware, OEM interface or support status, but it does not prove the board is unusable or that a purchase is required. Record what the exact model documentation and current firmware actually show; unknown remains unknown.

The TPM half

Start with tpm.msc: record Status and Specification Version before changing anything. Press Windows+R, type tpm.msc and press Enter. Activision and FACEIT both want Status to read “The TPM is ready for use”, and FACEIT adds that Specification Version should be 2.0. Those readiness fields do not establish TPM attestation, firmware compatibility or game acceptance. FACEIT separately checks Windows Security, Device security, Security processor details, where Attestation and Storage should both read Ready.

Activision says “Compatible TPM cannot be found” may mean TPM is disabled in the BIOS or the system does not support TPM 2.0. The message does not distinguish those possibilities, so check exact-model support before treating it as a setting to enable. The firmware TPM has a vendor name. Intel calls it PTT, AMD calls it fTPM, and Activision’s floor is Intel 8th gen with PTT or Ryzen 2000 with fTPM. The vendor paths:

  • GIGABYTE AM4. Advanced Mode, Settings, AMD CPU fTPM, set to Enabled.
  • MSI (B550 TOMAHAWK example). Settings, Security, Trusted Computing, then enable Security Device Support.
  • Others. FACEIT says the option usually sits under “Security” or “Trusted Computing”.

Then check the firmware version. In tpm.msc, read Manufacturer Version under TPM Manufacturer Information. Activision says AMD versions matching 3.*.0.* are not compatible with its games and need a firmware update: 3.92.0.5 fails, 3.92.5.5 is fine. Activision associates that pattern with a repeating enrollaik.exe prompt, but the prompt alone does not identify the reader’s firmware. For Intel, Activision flags INTC 302.12.*.* and INTC 303.12.*.* as possibly needing a firmware update. In MSI’s B550 TOMAHAWK example, the BIOS update moves AMD fTPM to 3.94.2.5. On Windows 11 25H2 build 26200.9457, read 2026-10-02, tpmtool getdeviceinformation runs without administrator rights and prints a line labelled TPM Manufacturer Version.

FACEIT’s current attestation guidance lists several possibilities, not a diagnosis:

  • A discrete TPM module on the board. FACEIT lists this as a possible cause and recommends switching from dTPM to fTPM. Apply that model-specific recommendation only after the recovery-key and protection preparation above.
  • An old GRUB in a dual boot. Boot Windows from the firmware boot menu instead, and update GRUB if that clears it.
  • A self-signed boot loader. Pick Windows Boot Manager from the boot menu.
  • A revoked boot loader present in DBX. Keep this separate from old GRUB; it is a boot-chain possibility that needs its own evidence, not proof that the BIOS is old.
  • CCU Cloud Update in an internet cafe. FACEIT sends that one to CCU’s support.
  • For other cases, FACEIT recommends checking current firmware. That does not guarantee a BIOS update will resolve a particular attestation failure.

Call of Duty and Modern Warfare 4

Activision’s current TPM and Secure Boot article requires both checks for every MW4 online mode. It names specified modes or playlists and possible separate matchmaking for Black Ops 7 and Warzone. The same article’s generic Failed Attestation wording is narrower, so retain the exact game and message instead of transferring a Ranked-only assurance to MW4.

The MW4 PC requirements list a minimum AMD Ryzen 5 1400 or Intel Core i5-6600, while Activision’s TPM guidance names Ryzen 2000 with fTPM or Intel 8th gen with PTT. The security article supports Windows 10 22H2 or later and any Windows 11; MW4 separately lists the latest 64-bit Windows 10 update as minimum and the latest 64-bit Windows 11 update as recommended, with trial, beta or Insider versions possibly unsupported.

Activision’s published listing labels Secure Attestation Wizard version 1.3.0 as updated October 21, 2026. That is dated documentation, not an executable downloaded or verified for this article. The September launch announcement supplies historical dates; it is not evidence that a service or mode was observed available here.

The rest of the messages follow Activision’s current article:

  • “TCG Event Log Failed”: restart and install the latest Windows update.
  • “Authorization Key Failed”: the wizard’s Generate Key button triggers a UAC prompt for enrollaik.exe; select Yes.
  • A CODBrokerInstaller.exe UAC prompt on first launch needs an administrator username and password and Yes. Selecting No means you cannot play. If you get “CODBrokerInstaller.exe authorization declined” with no prompt at all, Activision’s fix is the User Account Control slider: set it to Always notify or the default level below it.
  • “Failed Attestation Status”: use the game-specific scope above. The generic article names some restricted modes and possible matchmaking with other players who do not meet the requirements; that does not narrow MW4’s all-online statement.

Battlefield 6 and EA Javelin

EA’s Battlefield 6 requirements list Windows 10 as the minimum OS and Windows 11 as recommended. They list TPM 2.0 and UEFI Secure Boot as enabled, while HVCI and VBS are capable. Those words describe different states; capability does not say that every listed Windows security feature must be enabled. EA’s MBR2GPT examples use /disk:0, and EA says the number must match the reader’s own Windows disk.

For “The application encountered an unrecoverable error.”, EA says expired or unsigned drivers can cause the launch failure. Restarting and then following EA’s Secure Boot route are publisher troubleshooting steps, not proof of that cause or a verified remedy on this PC. Javelin’s component guidance names Windows 10 build 19041; that component floor does not replace the full game’s own OS requirements or certify game eligibility.

Valorant and Riot Vanguard

Keep Riot’s complete message. VAN 9003 is its numbered Secure Boot route, VAN 9001 is its numbered TPM route and VAN: STATUS_SB_POLICY reports that the Secure Boot policy could not be verified. The STATUS message is not proof that a generic key reset is safe or sufficient; reconcile Riot’s attributed instructions with the motherboard’s exact key operation and the current 2023-certificate state.

A no-number VAN: RESTRICTION follows the requirement actually named in its message. Riot’s build 26100 branch is for Windows 11, not a universal Windows floor. Riot’s current VALORANT specification also conflicts with itself: its table says Windows 10 build 19041+, while prose on the same page says support from build 10904. Preserve that publisher discrepancy rather than silently choosing one or applying it to League.

When a displayed code conflicts with the state you actually recorded, Riot’s September 22 incorrect-code notice is relevant only to VALORANT. It lists no affected-code set or resolution date, so it qualifies the display without erasing every documented mapping. VBS and Memory Integrity remain a separate branch in Memory Integrity on or off; other codes are in the Vanguard error code table.

FACEIT on Windows 10

FACEIT’s Windows security FAQ says its October 14, 2026 Windows 10 policy is effective. A Windows 10 PC needs 22H2, applicable ESU enrollment or coverage, and applicable security updates actually installed. A build number or ESU label alone does not establish all three, and none proves current FACEIT access.

Check the requirements separately:

  1. Version and updates. Press Windows+R and run winver. FACEIT names Windows 10 22H2 (build 19045) and current applicable security updates. Its missing-updates message is evidence to check Windows Update, not proof that the build number is the only problem.
  2. ESU. Microsoft’s consumer ESU page describes that consumer route’s regional, account and device prerequisites. Already-enrolled consumer coverage continues through October 12, 2027 without another action. Do not assume a price, repeat purchase or that an Enroll now control must appear. Another applicable ESU route neither certifies nor prevents FACEIT access; record actual coverage and installed updates.
  3. Security features. FACEIT requires TPM and Secure Boot for players on Windows 10 and 11. It says Windows 11 becomes required in October 2027, with possible earlier exceptions for some devices. IOMMU enforcement waves remain a separate policy. FACEIT says VBS supports IOMMU; that does not merge IOMMU or VBS into the Secure Boot state.

The VBS decision is in Memory Integrity on or off. OS support, feature state, attestation and actual game access remain separate observations.

If the PC will not boot after the change

Do not reinstall Windows as the first response. Undo the actual last change that broke startup, using the exact model’s firmware procedure. If the disk is still MBR and UEFI was just forced, restore the prior boot path and return to the conversion prerequisites. If the disk conversion already completed and Windows had booted from GPT/UEFI, blindly enabling Legacy or CSM can reverse a required condition instead of undoing the later key or firmware change.

FACEIT says a UEFI/MBR mismatch is a common cause after enabling Secure Boot, but a “Secure Boot Violation” or “Invalid Signature Detected” screen has several possible trust, firmware and boot-file causes. The message alone does not prove that certificates are merely old or that one BIOS update will fix the PC.

For the bounded Microsoft recovery route, the helper PC must run an applicable Windows version with July 2024 or later security updates, and the procedure requires FAT32 media. Its x64 route copies SecureBootRecovery.efi to EFI\BOOT\bootx64.efi. Do not extend that filename into a promise for every architecture. The utility adds Windows UEFI CA 2023 to DB. It does not install every certificate, prove that servicing finished, repair a missing OEM PK-signed KEK or certify a game result.

Certificate expiry does not switch Secure Boot off by itself. Microsoft says an unserviced device can continue to start but will stop receiving newer early-boot protections, and advises against disabling Secure Boot merely to work around expiration.

If BitLocker asks for the recovery key on the first boot afterwards, that is the key from the first step. Enter it and let Windows start.

After the change: protect the drive again

Once the applicable conversion or firmware work and its intended restarts are finished and Windows boots, put encryption back the way you found it. Do not wait for Secure Boot On, certificate servicing or game acceptance. If an immediate recovery step has its own BitLocker instruction, follow that scoped instruction rather than leaving protection off indefinitely.

  • You suspended BitLocker. Run Resume-BitLocker -MountPoint "C:" in an administrator PowerShell. Microsoft says the cmdlet has no effect on a volume that is not suspended, so it does nothing for a drive you decrypted.
  • You turned BitLocker off for the conversion, on Windows Pro. Sign in as an administrator, type BitLocker in Start and select Manage BitLocker, then select Turn on BitLocker beside the drive. Microsoft’s steps then ask how the drive should open at startup, and for a backup of the recovery key. The key is new. Save it again.
  • You turned Device Encryption off, on Windows Home. Open Settings, Privacy & security, Device encryption, and use the toggle to turn it On. Microsoft notes that the entry is missing if the device does not support it or you are signed in with a standard account.

Secure Boot is On: record certificate servicing

Secure Boot On records enabled state. Windows certificate servicing, update eligibility, encryption protection and a game’s attestation are separate results. Finish the protection step above first; do not leave the drive unprotected while trying to make a servicing label change.

If you already have saved registry output, use that. Otherwise, these three reg query commands read named values. They were reviewed against Microsoft’s documentation on October 23, 2026 and were not run on this PC:

reg query "HKLM\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing" /v UEFICA2023Status
reg query "HKLM\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing" /v UEFICA2023Error
reg query "HKLM\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing" /v UEFICA2023ErrorEvent

For each line, save whether the read succeeded, the declared type, the exact data or query error, and the observation time with UTC offset. A command return code of 0 means the query succeeded; it is not the value stored in UEFICA2023Error. Missing, unreadable and malformed values remain unknown. Separate queries are not an atomic snapshot, so retain the individual readings if their device or capture context cannot be joined coherently.

Recorded registry valuesWhat that record supports
UEFICA2023Status is REG_SZ Updated and UEFICA2023Error is REG_DWORD 0 in one coherent observationRegistry reports completion. This does not require a retained Event 1808 or complete event history.
Updated with a successfully read nonzero ErrorThe fields conflict. Preserve both and investigate the error; do not silently declare it stale.
A successfully read nonzero Error while Status is missing, NotStarted, InProgress or unexpectedA nonzero error is recorded. Preserve the other status exactly; do not substitute success.
NotStarted or InProgress with successfully read Error 0Registry reports that named state. Missing Status is not a recorded NotStarted.
Updated with missing, unreadable, wrongly typed or malformed ErrorUpdated is recorded; Error is unknown. Unknown is not zero.
Mixed reads, an uncertain device, or unusable capture time/offsetKeep each valid field reading, but no coherent current-device result is established. A valid Error 21 remains Error 21.

A saved REG_SZ Updated value still records Microsoft’s completed-servicing status, and a successfully read REG_DWORD Error value of 0 is its documented success value. Missing time or readings that cannot be joined limit a conclusion about one current device observation without erasing either field’s individual meaning. Do not invent a timestamp, offset or Event 1808.

These meanings come from Microsoft’s Secure Boot registry guide. UEFICA2023ErrorEvent is a REG_DWORD event ID, not an error code or timestamp. When Error was correctly read as 0, an absent optional ErrorEvent is not itself an error; a present zero ErrorEvent is not a success event. Preserve a populated ErrorEvent that conflicts with Error=0 for correlation, but do not promote the ID alone to a current error or failure. A wrongly typed, malformed or unreadable ErrorEvent remains unknown.

Event history is separate corroboration. Event 1808 reports a complete rollout at that event; Event 1799 reports only the 2023-signed boot-manager component. Record the provider, log, device, full operation, event time/offset and reviewed time range. An applicable later error or pending event remains a separate history conflict alongside a coherent Updated/0 registry report. Investigate its exact operation, provenance and timing; do not invent an offset or completion event. Missing or malformed provenance cannot be discarded as positively unrelated. See Microsoft’s Secure Boot event reference.

Optional fields do not replace that report. WindowsUEFICA2023Capable is reference-only, not general servicing status. AvailableUpdates is a work/behavior bitmask: absence or zero does not prove completion; Microsoft’s normal documented sequence may retain 0x4000, and its missing-KEK exception can leave 0x4004. Those values are context to record, never values to set here. A missing OEM PK-signed KEK can block work without a supported manual workaround.

Examples:

  • Updated/0 with no retained events: registry reports completion; history corroboration is unknown.
  • Typed Updated and Error=0 with no usable capture time: Updated still means completed servicing and Error=0 still means success, but these saved readings do not establish one current-device conclusion.
  • Updated recorded at 09:00 and Error=0 at 10:00, when the reads cannot be joined: preserve both field meanings and their metadata without combining them into current completion.
  • Updated/0 plus a later applicable error or pending event: keep both the affirmative registry report and the separate history conflict.
  • Updated/21: keep the field conflict, even if an earlier 1808 exists.
  • Valid Error 21 with missing offset or mixed reads: keep Error 21, but withhold a coherent current-device conclusion.
  • Updated/0 while a game still reports attestation or policy failure: keep both results separately. Neither Microsoft field meanings nor the game result overwrites the other.

This manual record does not collect anything automatically and does not contain a parser or status checker. Do not put recovery keys, credentials or account data in it. The plain-text worksheet has the same fields:

Secure Boot certificate
servicing record
Manual worksheet.
Do not include recovery keys,
credentials, or account data.

DEVICE AND CAPTURE
Device label
(local, non-secret):
Capture start date/time
and UTC offset:
Capture end date/time
and UTC offset:
Can these readings be joined
as one coherent observation?
yes / no / unknown:
Capture or clock limits:

SEPARATE ENABLED AND
UPDATE OBSERVATIONS
BIOS Mode:
  Exact result:
  Observation time:
Secure Boot State:
  Exact result:
  Observation time:
Windows edition/version/build:
Applicable update evidence:
  Or unknown:
Encryption protection
after the work:
  Or unknown:

REGISTRY READINGS
UEFICA2023Status
  Read result:
    present / missing /
    unreadable
  Declared type:
  Exact data or
  exact query error:
  Per-field device/time
  metadata, if recorded:

UEFICA2023Error
  Read result:
    present / missing /
    unreadable
  Declared type:
  Exact hex and/or
  decimal data or
  exact query error:
  Per-field device/time
  metadata, if recorded:

UEFICA2023ErrorEvent
  Read result:
    present / missing /
    unreadable
  Declared type:
  Exact data or
  exact query error:
  Per-field device/time
  metadata, if recorded:

Registry report and limits:

OPTIONAL EVENT HISTORY
Reviewed device:
Reviewed log:
Reviewed provider:
Reviewed date range:
UTC offset:
Latest relevant Event 1808:
  Or none retained:
Later relevant error:
  Or pending event:
Unknown-provenance events:
Retention/access/reset/
clock/history limits:
History report and limits:

SEPARATE GAME RESULT
Game/client:
Exact message/code:
Observed date/time:
UTC offset:
Result still present after
registry report?
yes / no / not checked:
Notes and remaining unknowns:

Sources

Frequently asked questions

Why does it say Secure Boot is not enabled when it is enabled in the BIOS?
Enabled in firmware and the state Windows reports are separate observations. Read BIOS Mode, Secure Boot State and the disk partition style first. CSM, missing trust keys or a model-specific policy can keep the state Off. Do not apply a generic key reset: current 2023-certificate state and the exact motherboard procedure determine whether reset, update or enrollment is appropriate.
What does Secure Boot State Unsupported mean?
Unsupported is a routing clue, not proof that the board must be replaced. With BIOS Mode Legacy, investigate the disk and UEFI conversion branch. With UEFI, check the exact model manual and current firmware. Confirm-SecureBootUEFI reporting unsupported or access denied is different from a False result and does not establish certificate state, game eligibility or hardware failure.
Can turning on Secure Boot stop Windows from booting?
Yes. Switching a machine to UEFI while its Windows disk is still MBR can stop it booting. Validate and complete the supported disk conversion before changing the boot mode. If a later change breaks startup, undo that actual last change. After a completed GPT conversion, blindly enabling Legacy or CSM can contradict the required UEFI configuration.
Will changing Secure Boot or TPM settings trigger BitLocker recovery?
It can. Save the recovery key before firmware, TPM, boot-manager or partition changes. Suspension keeps encryption in place and must later be resumed; decryption removes protection and must later be enabled again. Resume-BitLocker cannot re-encrypt a decrypted drive. When encryption is enabled again, save the new recovery key and do not delay restoration for a pending game result.
Does Secure Boot or TPM 2.0 lower FPS?
FACEIT says TPM and Secure Boot do not affect performance. It separately says IOMMU and VBS can have a minor effect in some cases, particularly on older systems or systems with immature firmware. That publisher statement is not a benchmark from this page. Treat VBS and Memory Integrity as separate settings from Secure Boot.
Can I still play FACEIT on Windows 10?
FACEIT’s October 14, 2026 Windows 10 policy is effective: version 22H2, applicable ESU enrollment or coverage, and applicable installed security updates. A build number or ESU label alone does not prove access. Microsoft’s consumer route has account, region and device prerequisites; FACEIT says Windows 11 follows in October 2027, with possible earlier device exceptions.
Does the 2026 Secure Boot certificate expiry turn Secure Boot off?
No. Microsoft says an unserviced device can continue to start, but it stops receiving newer early-boot protections. Do not disable Secure Boot merely because a certificate expires. Microsoft’s recovery utility adds one Windows UEFI CA 2023 certificate to DB; it does not install every certificate, prove full servicing, repair a missing OEM-authorized KEK or certify a game result.
Is VAN 1067 a Secure Boot error?
Not specifically. Riot says VAN 1067 usually means Vanguard had an unexpected startup or check-in problem, not a specific Secure Boot diagnosis. Route numbered and no-number restrictions by their complete text. Riot’s incorrect-code notice applies only to VALORANT and does not erase all published mappings. Compare a conflicting code with the observed state instead of resetting keys blindly.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 51 cited sources, listed below, each checked against the original page on the date shown beside it. Every publisher page, motherboard vendor page and Microsoft document below was opened on 2026-10-02 and the error strings, menu labels, dates and commands on this page were copied from them. The GIGABYTE, MSI and Easy Anti-Cheat pages were read in a browser, because the first two refuse scripted requests and the third renders its answers client-side. ASRock’s FAQ did not load, so this page carries no ASRock menu path. The Windows facts in the TPM section (tpmtool running without administrator rights and printing a TPM Manufacturer Version line) were read on 2026-10-02 on Windows 11 Home 25H2, build 26200.9457, with read-only commands and no setting changed.
Sources
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.