Secure Boot Certificates

[Tunnelcat]

The manufacturer sent me this video. It's a similar process to what they gave me in my email and I see where I may have gone wrong. In the video, he also disables UEFI, which I gather allows it to boot into Legacy Mode. It's not all that apparent that's what it does and in the email instructions, they completely left out disabling UEFI in their instructions. But everyone's comments here have convinced me that UEFI and DOS won't work. I'm going to try that extra step since it seems in UEFI mode, there's no booting into DOS. The files I have to run are different too, not Step 1 or Step 2, but instead flash.nsh. So I'll recreate my Rufus USB with the newer BIOS files and give it whirl. Gads what a PITA.

[TigerRaptor]

Sorry if i"m going off topic again.

Isaac are you running BTRFS or EXT4 for your file system in Endeavour?

EXT4

I'm curious to see what others are running sometime. I'm currently using BTRFS with Cachy. With it being Arch-based, there's still a small fear of an update breaking something. If things continue to stay stable, I'll eventually switch over to F2FS.

[Jeff250]

EXT4. I'm fairly conservative when it comes to file systems.

[Tunnelcat]

Well, an update to the saga. The manufacturer offered to ship the laptop back to their facility to update the BIOS. Geez, even they had problems updating the older Clevo BIOS. It took them MONTHS. So in August, I get an email that it's repaired and ready to ship. So after receiving it, of course I had to reinstall their Windows image. Well, I'm not a happy camper. I couldn't set up a local account since they somehow disabled the USB boot option and I had to use their preloaded image, so Rufus was out. MS has blocked most of the other workarounds. But it gets worse. I went ahead and allowed the August update since I'd had no issues on my other systems. That was a mistake. Even though I didn't get the late August update, I got the first patch Tuesday Security updates and a .NET Framework update. This system is now worse off than when I sent it in! Now I get a black background upon boot and a screen that dims on the log-in screen and stays dim on the desktop until I adjust the brightness slider. Microslop's suggestion is to disable adaptive brightness, which I don't even have an option to do in settings. NADA. FU Microslop and your effing A.I. created updates. At this point, I hope a giant CME wipes out every data center on the planet.

But even if I reinstalled the OS AGAIN and blocked all updates to hopefully fix that hot mess, I STILL have a TON of TPM errors and failures, despite the fact that Sys Info claims Secure Boot is ON, certificates cannot be updated and it throws a failure error. I mean this was built in 2019 fer crying out loud! It's not ancient. There are a couple of other issues as well. Hotkeys has a file called vcore.exe that throws a .NET error and another related error, CONSTANTLY. I don't now how many CPU cycles all that is taking up. I assume the only way to get rid of those constant errors is to disable Hotkeys and rename that file. Then, Windows Security bitches that it can't turn on Core Isolation because of an old incompatible driver called zntport.sys in Windows/System32. The solution I finally found was to rename the damned file. I have no idea what program or Windows function it crippled yet however.

Dammit, the sledgehammer idea is starting to gain traction. I swear I'm going to remove the 2 now very expensive SSD drives, which are probably worth more than this brick of a laptop thanks to the system manufacturer and Microslop and their A.I. update BS and smash the rest of the POS! I'm never buying another laptop as long as I live. I'm still running my 2019 ASUS gaming rig, even though I still can't find a way to boot from a USB stick on that system either. Just like the laptop, the USB never shows in Boot Options. Same damned system builder too, whom I shall not name, even though it has an ASUS motherboard.