08-22-2024, 11:27 AM
It's been brought up already. Yes, it's a secure boot issue. This happens on some PCs that have been updated, or newer PCs from the factory. There supposedly is a solution, but I can't seem to find out what it is, it looks like you have to snag an EFI file from some Linux distro and put it on the drive. I've not been able to follow along on it to find out exactly where.
Like you said, you can boot to it if you turn off secure boot. I do so , just for that session and then reenable it when done. I am sure I'll forget one sooner or later and leave it disabled 'in the wild' and get my a## chewed out for it.
Like you said, you can boot to it if you turn off secure boot. I do so , just for that session and then reenable it when done. I am sure I'll forget one sooner or later and leave it disabled 'in the wild' and get my a## chewed out for it.