Has anyone noticed M$ turning on secure boot

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

    /Steve.

Duckpaddle

Well-known member
Oct 1, 2020
64
24
I was doing my full image backup with Clonezilla today and found the secure boot option had been enabled on an Intel NUC. Good idea which I will carry forward but suprised me as it is a BIOS option.
 

PHolder

Well-known member
Sep 16, 2020
969
2
402
Ontario, Canada
secure boot option had been enabled
Do you ever update your BIOS (or do you have a utility from Intel that will do so?) Recent BIOSes from ASUS and Gigabyte (the only brands I have around that have received updates) have made changes specific to Windows 11 to default enable the necessary support (so Secure Boot and TPM support.)
 

Duckpaddle

Well-known member
Oct 1, 2020
64
24
No I have not updated this BIOS. Good Idea, but that wasn't the cause of the settings flip.
 

systemz

New member
Sep 2, 2022
2
0
No I have not updated this BIOS. Good Idea, but that wasn't the cause of the settings flip.
In my over 15 years I've never seen M$ randomly enable secure boot, maybe you accidentally did one of the above or enabled it.

Were any other settings changed?
 

Duckpaddle

Well-known member
Oct 1, 2020
64
24
In my over 15 years I've never seen M$ randomly enable secure boot, maybe you accidentally did one of the above or enabled it.

Were any other settings changed?
Nope, this is a machine I maintain. The operator wouldn't have the motivation to navigate in the BIOS to this settings. I would have been called if this popped up. As this is an Intel NUC it could have been an update pushed through M$ to the device.
 

SeanBZA

Well-known member
Oct 1, 2020
74
14
Could have been part of a firmware upgrade that MS did to microcode that had the flag set, so update did it to all the NUC's in a region under the update server.