F5F Stay Refreshed Hardware Desktop How to enable secure boot on Gigabyte b450m ds3h and Ryzen 5 3600?

How to enable secure boot on Gigabyte b450m ds3h and Ryzen 5 3600?

How to enable secure boot on Gigabyte b450m ds3h and Ryzen 5 3600?

W
58
11-22-2019, 08:28 AM
#1
I've encountered the same problem in several games I wanted to play. The anti-cheat system fails to install due to the secure boot being disabled. I've tried adjusting it before, three years ago, which ended up damaging my motherboard. (I managed to fix it a year ago by reseating the RAM while the PC was running, but I don't know exactly how it worked). Now I'm more cautious about handling this. I'm determined to resolve the issue, and I've learned that disabling CSM is necessary to enable secure boot. I also know my drive must be GPT-formatted, which it is. However, most discussions online mention booting difficulties. My motherboard uses UEFI and is running firmware version f52. -BIOS version: f52 -BIOS mode: UEFI -FTPM is active -SSD is GPT I've attached some photos of my BIOS. Could you assist me? Thank you in advance!
W
wizarddrago123
11-22-2019, 08:28 AM #1

I've encountered the same problem in several games I wanted to play. The anti-cheat system fails to install due to the secure boot being disabled. I've tried adjusting it before, three years ago, which ended up damaging my motherboard. (I managed to fix it a year ago by reseating the RAM while the PC was running, but I don't know exactly how it worked). Now I'm more cautious about handling this. I'm determined to resolve the issue, and I've learned that disabling CSM is necessary to enable secure boot. I also know my drive must be GPT-formatted, which it is. However, most discussions online mention booting difficulties. My motherboard uses UEFI and is running firmware version f52. -BIOS version: f52 -BIOS mode: UEFI -FTPM is active -SSD is GPT I've attached some photos of my BIOS. Could you assist me? Thank you in advance!

D
DerNeueDoktor
Member
156
11-22-2019, 11:17 AM
#2
Secure boot should have been turned on by default, right? To check available settings, turn off CSM Support. Once that's done, Secure Boot will appear at the bottom. Watch this video for guidance: the OS might fail to start entirely. If that happens, you may need to reinstall Windows so Secure Boot works without CSM support (CSM isn't required unless you're using Windows XP or similar). This is completely normal and not a problem. However, if you disable CSM support and later enable Secure Boot, the system could stop functioning because it was built with that configuration. If you find yourself in this scenario, return to the BIOS, turn off Secure Boot, then enable CSM. Before doing so, back up your data. Afterward, reinstall Windows.
D
DerNeueDoktor
11-22-2019, 11:17 AM #2

Secure boot should have been turned on by default, right? To check available settings, turn off CSM Support. Once that's done, Secure Boot will appear at the bottom. Watch this video for guidance: the OS might fail to start entirely. If that happens, you may need to reinstall Windows so Secure Boot works without CSM support (CSM isn't required unless you're using Windows XP or similar). This is completely normal and not a problem. However, if you disable CSM support and later enable Secure Boot, the system could stop functioning because it was built with that configuration. If you find yourself in this scenario, return to the BIOS, turn off Secure Boot, then enable CSM. Before doing so, back up your data. Afterward, reinstall Windows.

A
ApeBarrel
Member
214
11-22-2019, 12:32 PM
#3
There’s no necessity to reinstall Windows to activate secure boot.
A
ApeBarrel
11-22-2019, 12:32 PM #3

There’s no necessity to reinstall Windows to activate secure boot.

A
Athenos
Junior Member
6
11-22-2019, 01:10 PM
#4
You could test it out without any risk. The changes won't damage anything. If issues arise, you can revert the bios settings and windows should start up normally afterward. Generally, toggling secureboot shouldn't impact Windows much, though the CSM support might be the issue. It's possible Microsoft addressed it, or it could still be a problem. I haven't tried it myself.
A
Athenos
11-22-2019, 01:10 PM #4

You could test it out without any risk. The changes won't damage anything. If issues arise, you can revert the bios settings and windows should start up normally afterward. Generally, toggling secureboot shouldn't impact Windows much, though the CSM support might be the issue. It's possible Microsoft addressed it, or it could still be a problem. I haven't tried it myself.

M
Major_Limitz
Member
96
11-22-2019, 04:56 PM
#5
Yes, you can prevent this by turning on secureboot and disabling the CSM before installing Windows.
M
Major_Limitz
11-22-2019, 04:56 PM #5

Yes, you can prevent this by turning on secureboot and disabling the CSM before installing Windows.

X
xPumma
Member
186
11-28-2019, 09:07 AM
#6
When setting up a new system, CSM should remain off by default while Secureboot stays active. This means you won’t need to make any changes yourself. You can verify the settings anytime. Typically, the only adjustments required in the BIOS today involve optimizing RAM timing and voltage to ensure performance. You might also consider enabling virtualization for a virtual machine or rearranging boot drives, but those are usually minor tweaks.
X
xPumma
11-28-2019, 09:07 AM #6

When setting up a new system, CSM should remain off by default while Secureboot stays active. This means you won’t need to make any changes yourself. You can verify the settings anytime. Typically, the only adjustments required in the BIOS today involve optimizing RAM timing and voltage to ensure performance. You might also consider enabling virtualization for a virtual machine or rearranging boot drives, but those are usually minor tweaks.

Y
yasnial
Junior Member
36
11-30-2019, 02:45 AM
#7
Just checking if Windows functions properly after you turned on Secure Boot. I’m guessing you’re facing the same issue as me.
Y
yasnial
11-30-2019, 02:45 AM #7

Just checking if Windows functions properly after you turned on Secure Boot. I’m guessing you’re facing the same issue as me.