XPost: alt.comp.os.windows-10   
   From: nospam@needed.invalid   
      
   On Fri, 3/6/2026 6:18 AM, Carlos E.R. wrote:   
   > On 2026-03-06 02:07, VanguardLH wrote:   
   >> Jack  wrote:   
   >>   
   >>> Windows Secure Boot is EXPIRING: Do This Before June 2026!   
   >>> Windows Secure Boot certificates are reaching their "End of Life"   
   >>> starting June 2026. If you haven't updated your UEFI CA certificates,   
   >>> your PC's boot-level security is about to expire and you may have   
   >>> serious problems booting up your machine.   
   >>>   
   >>> This only applies to UEFI boot. ...   
   >>   
   >> Only if you have Secure Boot enabled in the BIOS.  I don't.   
   >   
   > A friend has a W10 machine that I will have to update in the summer, so I   
   will probably hit this. And to make it more interesting, the external backup   
   disk boots Linux.   
   >   
      
   It's not that hard to make a W10/W11 boot disk of your own.   
   The license does not gate operation, and you can move the   
   disk drive from machine to machine (this is unlike previous   
   Windows versions, where between the license and the driver issue,   
   it takes a fair bit of planning to do a disk drive move like that).   
      
   You can also boot the Windows Installer DVD, select Troubleshooting   
   and use the Command Prompt there. For example, you could   
   do a CHKDSK /f  on the customer C: drive, to tip it upright.   
   But plenty of other convenience features will be out of reach   
   if using the Installer DVD.   
      
   You can also take a Macrium Rescue CD with you, and the   
   item in there of usage is the "Boot Repair" option. It is   
   convenient for simple problems (ones the Microsoft repair   
   does not seem able to manage). There are Microsoft utilities   
   that can perform all sorts of miracles, but for reasons   
   of not damaging things, they are not typically automated   
   to "move quickly and break things".   
      
   For example, if D: was the EFI system partition (FAT32) and   
   C: was the thing that no longer booted, a sample command is:   
      
      bcdboot C:\Windows /s D:           # The "slash s" specifies the "system"   
   partition   
      
   And on Windows-multiboots, if C: is working but your   
   second OS on H: is not working, you can do this to remove   
   all the old H: related materials, so you can issue commands   
   to rebuild the details about H: .   
      
      bcdboot /bcdclean full   
      bcdboot H:\Windows                 # Since we replaced the boot files in D:   
   with   
                                         # the command above, and are actually   
   running off C:   
                                         # at the moment, adding H: back requires   
   no specification   
                                         # of where the system partition is   
   located.   
      
   There are differences between online and offline repair,   
   and also in the availability of some features (bcdclean),   
   so there is more to this than the simple commands demonstrate.   
   But what you see above, is some of the more powerful stuff   
   in the kit.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)