From: admin@127.0.0.1   
      
   On Thu, 12 Feb 2026 01:10:36 -0500   
   Paul  wrote:   
      
   > On Thu, 2/12/2026 12:08 AM, Axel wrote:   
   >   
   > > I had already started a fresh install before i saw your comprehensive post,   
   > > thank you. it seemed the best option to avoid a possibly corrupted system.   
   > > thankfully all is working well now. btw.. this laptop has the most   
   > > rudimentary BIOS I have ever seen. there are very few settings, and   
   > > most cannot be changed. It has UEFI with secure boot, but there's no way   
   to disable SB.   
   >   
   > This is the era I feared. We were promised what is basically "optionless"   
   > machines for the year 2026 or so, removing the ability to turn off Secure   
   Boot   
   > and the ability to do Legacy Boot.   
   >   
   > That's going to cause a lot of problems, and your example is just the   
   > beginning.   
   >   
   > The thing is, if the scheme was "perfect", I can see this transition   
   > making sense. But the scheme is far from perfect, holes galore to fall   
   > in, and why limit the escape hatches on a thing which is a mess ?   
   >   
   > There is one less reason to buy a new computer.   
   >   
   > Take my 11 year old computer. The kids can't break it. No MOK. No   
   > Secure Boot materials. Ability to boot from Legacy media and UEFI media.   
   > Will be able to run its copies of W10 and W11 past June 2026 (when   
   > one of the keys on the other machine expire). Right now, that's my most   
   > defensively designed computer in the room. 11 years old. If a boot   
   > breaks on a Linux there, I can fix it. Whereas a 3 year old machine   
   > that Ubuntu injected two certificates into, I can't get them out!   
   > Even in recovery mode for the materials.   
      
   Very worrying.   
      
   --   
   Bah, and indeed Humbug.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)