A520M Gaming - not booting to bios

The only suggestion I have is to repeat the clear CMOS steps I linked before. 10
mins should be enough, I stipulated longer in the guide because it's meant to be
a 100% foolproof option. If 10 mins doesn't work you can repeat for a longer period.

This is why I never update the BIOS on a working system. I only upgrade when I need
to for hardware support.

pads wrote: Turns out that the monitor has a dodgy DP input (I'm using my own 2nd monitor) HDMI is fine.

Always something you didn't expect isn't it....

pads wrote: ?�So got up windows. However - big however. 1) To update to win11, I need secure boot. I go through the process described by yourselves - https://www.asrock.com/support/faq.asp?id=531 2) But then the system just continually boots to BIOS. and the boot priority list has disappeared.

I'm afraid this is where my usefulness ends, I have absolutely 0 experience dealing
with Windows 11. All this TPM 2.0, secure boot and other "requirements" put me
right off. Windows 11 was the last push I needed to say goodbye to Microsoft.

If I had to take a stab at it though, I would guess that the secure boot
settings mess up your boot settings for windows 10 and cause the system to POST
loop into BIOS. Basically the system is behaving as it would if you had no hard
disk/SSD installed when you enable secure boot. My guess would be it's the CSM
"Disabled" setting. You installed windows 10 with it enabled in legacy mode so
it won't boot with CSM (compatibility support module) disabled now.

On the plus side, you are out of the woods hardware wise, now you have software
issues.... Google should help here: "Can't boot with CSM disabled"

FYI, I am just a moderator here, I don't work for ASRock tech support, just another
forum member

Sorry I couldn't be more help.




Edited by Xaltar - 2 hours 24 minutes ago at 10:47pm

This is a very common issue with people wanting to upgrade to windows 11 vs install
a fresh copy. Your current OS is installed in MBR mode (master boot record), secure
boot needs it to be EFI mode. There are several guides on how to convert to efi
mode out there. A quick google search popped this one up:
https://www.windowscentral.com/how-convert-mbr-disk-gpt-move-bios-uefi-windows-10

In cases like this our decades of experience actually bite us in the rear a little.
A lot has changed

Edited by Xaltar - 2 hours 3 minutes ago at 11:08pm

You could just try a boot medium and attempt a fresh install of windows 10 with
safe boot enabled. I am guessing you don't have any valuable data on the drive yet
so no harm in a fresh start.

Maybe the simple solution will do the trick?