I have an EQ6, but I haven’t messed with Secure Boot yet. My only experiments have been with Windows 11 as a Virtualbox Guest under a Windows Host. A long time ago, Linux hosts with Windows guests had to work with Virtualbos to get a way to work with the Secure Boot option. After about a year of waiting, the engineers at Oracle worked out the problem, and we Windows guest users were to told to finally update our working version of Virtualbox and be sure “Secure Boot” was NOT enabled. It is only to this message from the Microsoft community that I felt compelled to try enabling Secure Boot. Interestingly, on one Windows VM I was able to Enabloe Secure Boot without any perceived problem, but on another Windows VM when I changed to Secure Boot, I became unable to boot into the Windows VM. Fortunately, I was able to "play games with turnin g UEFI on and off, restarting the entire machine a couple of times then turning Secure Boot back on, I was able to reboot instead of recreating the Virtual Session from a backup.
I personally think that this will return to be a controversial subject with Windows users who got fed up with Windows 10 becoming unsupported and turning to Linux. Microsoft is fighting to keep their revenue stream.
So I don’t need a replacement BIOS at this time, because I haven’t tried to enable Secure Boot in my EQ6. I’ll fight the Linux problem this summer when I DO try to boot into the additional drive I installed in my EQ6 which supports a Linux distro. I decided to use the “chose the OS by selecting the drive via a Function key” rather than using a Windows Manager or Grub.
So, if you still want to direct me to a replacement BIOS, then point me to the EQ6 folder. Thanks.
