Hi Sahil,
When Secure Boot shows as enabled in firmware but “not active” in Windows, it usually means the system is booting with a non‑signed or legacy bootloader. The most common cause is that the platform key (PK) and signature databases (KEK/DB) in UEFI are either missing or not properly provisioned, so Windows reports Secure Boot as off even though the toggle is on. Go into your UEFI setup and look under Secure Boot configuration; if you see “Custom” mode, switch it back to “Standard” and re‑install factory keys. On many boards this is done via an option like “Install Default Secure Boot Keys” or “Restore Factory Keys.”
Also confirm that your GPU driver and bootloader aren’t unsigned, since certain modified boot managers or legacy Option ROMs can silently disable Secure Boot. If you’ve cloned or migrated the OS, check that the EFI System Partition contains the Microsoft Boot Manager (\EFI\Microsoft\Boot\bootmgfw.efi) and that it’s signed. Once the keys are reset and the system boots through the signed Microsoft loader, Windows will report Secure Boot as active. That should satisfy the BF6 beta requirement.
Harry.