home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.os.windows-10      Steaming pile of horseshit Windows 10      197,671 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 197,657 of 197,671   
   Paul to Alan K.   
   Re: Windows Secure Boot Certificate   
   05 Mar 26 19:01:15   
   
   XPost: alt.comp.os.windows-11   
   From: nospam@needed.invalid   
      
   On Thu, 3/5/2026 6:24 PM, Alan K. wrote:   
   > On 3/5/26 6:30 PM, 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. On Windows 10 this was not necessary but   
   >> for Windows 11 this is now mandatory. Whether Microsoft updates this   
   >> before they expire remains to be seen but you can manually upgrade it by   
   >> using these PowerShell/Terminal commands as Administrator:   
   >>   
   >> Check if it needs updating:   
   >>   
   >> [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes)   
   >> -match 'Windows UEFI CA 2023'   
   >>   
   >> If it shows false then you need to change the registry:   
   >>   
   >> reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot   
   >> /v AvailableUpdates /t REG_DWORD /d 0x5944 /f   
   >>   
   >> Then run this in Terminal/PowerShell:   
   >>   
   >> Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"   
   >>   
   >> Article:   
   >>   
   >>    
   >>   
   >>   
   >>   
   >>   
   > This is so old it's pathetic.  2023.  I would sure hope that some standard   
   MS patch came down the line.   It would be a pity if millions of windows 11   
   users got hung out to dry.   
   >   
      
   My recommendation, is to check in the BIOS to see if you can   
   connect a USB stick and back up the four files with the   
   certificates in it. Keeping those four files, gives   
   you the ability to reset the certificate state if there   
   are problems anywhere along the line.   
      
   As for the proposition, Microsoft is concern-trolling us again,   
   just like the WinRE problem they would not fix for themselves.   
   I am "less excited" this time, at the prospect of messing   
   around with my stuff.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca