Display Signal not detected until Windows 11 Login Screen

[jnb_72]

Was hoping to some advice as can't seem get into the bios for my desktop - current version is B560 Aorus Pro AX F7.

I need to make some changes but am unable to do so with the current monitor HP M24F. At present, the display signal is only detected when the windows 11 logon screen is live and hence I miss the opportunity to enter the bios. If I force a full restart then I am left with a black screen and have to hold down the power button and start again.

I have tried different cables and also using both the hdmi and displayport outputs from the motherboard but it makes no difference. I have also turned off the auto-detect from the monitor menu to force it to use hdmi but that doesn work either.

If I move the pc and plug the same cables into a TV then I do get the bios screen so it definitely seems to be related to the monitor. Whilst I could just enter the bios from here this is not a long term solution. Any ideas how I can resolve this?

[Hazel_Eyes]

Hey, I had a similar issue with a different HP monitor. It sounds like your HP M24f isn’t waking up fast enough to catch the BIOS screen. Some monitors take a couple of seconds to display a signal, and by that time, the BIOS window has already passed.

Since it works fine on a TV, it’s definitely the monitor’s response time or handshake issue. You could try these:

• Use a DisplayPort cable instead of HDMI if you haven’t already (some say it's quicker to detect).

• Try connecting through the graphics card output (if you have one) rather than the motherboard port.

• Disable Fast Boot in Windows (under Power Options > System Settings), as that sometimes helps bring back full POST.

• If you can access BIOS through the TV, look for settings like “Full Screen Logo” or “Fast Boot” and turn them off – this may give the monitor more time to wake up during startup.

[jnb_72]

Hi,

I have tried the first 3 options but that didn't help. I will try the last one later and post how it turned out 

Thank you for the suggestions 

[jnb_72]

Tried the last step and unfortunately this doesn't fix it