F5F Stay Refreshed Hardware Desktop Problem with activating Secure Boot on Asus Strix X470 gaming device

Problem with activating Secure Boot on Asus Strix X470 gaming device

Problem with activating Secure Boot on Asus Strix X470 gaming device

M
mcbudder2004
Senior Member
687
01-17-2021, 05:52 PM
#1
I'm trying to set up Windows 11 on my modern machine, but the system is blocking it due to a health check. It claims Secure Boot isn't enabled and lists BIOS as legacy with Secure Boot marked unsupported. I've updated the BIOS but haven't found any settings that work. No one seems to know how to fix this or what the right options are. The system reports BIOS mode as legacy and Secure Boot as unsupported.
M
mcbudder2004
01-17-2021, 05:52 PM #1

I'm trying to set up Windows 11 on my modern machine, but the system is blocking it due to a health check. It claims Secure Boot isn't enabled and lists BIOS as legacy with Secure Boot marked unsupported. I've updated the BIOS but haven't found any settings that work. No one seems to know how to fix this or what the right options are. The system reports BIOS mode as legacy and Secure Boot as unsupported.

J
jamie2k
Member
51
01-18-2021, 12:04 AM
#2
View the video I discovered on YouTube. I think it should address your concerns.
J
jamie2k
01-18-2021, 12:04 AM #2

View the video I discovered on YouTube. I think it should address your concerns.

B
Bazza130202
Senior Member
386
01-18-2021, 12:34 AM
#3
It doesn't resolve the issue. The video shows more possibilities, indicating a Platform key is active. It seems the system displays "Enabled" even though there are problems. I've attempted to install and remove keys, but the health check continues to report issues.
B
Bazza130202
01-18-2021, 12:34 AM #3

It doesn't resolve the issue. The video shows more possibilities, indicating a Platform key is active. It seems the system displays "Enabled" even though there are problems. I've attempted to install and remove keys, but the health check continues to report issues.

B
Bifes_PT
Member
205
01-22-2021, 10:24 AM
#4
I resolved the issue. Initially, I had Windows 10 set up in Legacy BIOS, which differs from UEFI configuration. Even if your system runs in UEFI, the BIOS must match for proper startup. You can upgrade to UEFI without a full reinstall using the tool "Windows\System32\MBR2GPT.EXE". It changes a disk from MBR format to GUID Partition Table without altering or removing data. I executed the commands "mbr2gpt /validate /allowFullOS" and then "mbr2gpt /convert /allowFullOS", which successfully converted my drive. Now my PC is in BIOS mode with UEFI, secure boot is enabled, and the health check confirms it meets Windows 11 standards. Great!
B
Bifes_PT
01-22-2021, 10:24 AM #4

I resolved the issue. Initially, I had Windows 10 set up in Legacy BIOS, which differs from UEFI configuration. Even if your system runs in UEFI, the BIOS must match for proper startup. You can upgrade to UEFI without a full reinstall using the tool "Windows\System32\MBR2GPT.EXE". It changes a disk from MBR format to GUID Partition Table without altering or removing data. I executed the commands "mbr2gpt /validate /allowFullOS" and then "mbr2gpt /convert /allowFullOS", which successfully converted my drive. Now my PC is in BIOS mode with UEFI, secure boot is enabled, and the health check confirms it meets Windows 11 standards. Great!

C
CreeperBossZK
Junior Member
18
02-12-2021, 04:14 PM
#5
I attempted that but the system still reports invalid arguments.
C
CreeperBossZK
02-12-2021, 04:14 PM #5

I attempted that but the system still reports invalid arguments.

S
Stearogue
Junior Member
29
03-01-2021, 02:51 PM
#6
I interpret "Invalid arguments" as incorrect input.
The quotes around the commands should be removed.
The spaces before forward slashes must remain intact.
You should also run CMD with administrator privileges.
S
Stearogue
03-01-2021, 02:51 PM #6

I interpret "Invalid arguments" as incorrect input.
The quotes around the commands should be removed.
The spaces before forward slashes must remain intact.
You should also run CMD with administrator privileges.