home bbs files messages ]

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

   alt.comp.os.windows-11      Steaming pile of horseshit Windows 11      4,969 messages   

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

   Message 4,969 of 4,969   
   =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==? to Jack   
   Re: Windows Secure Boot Certificate   
   06 Mar 26 19:03:04   
   
   XPost: alt.comp.os.windows-10   
   From: winstonmvp@gmail.com   
      
   On 3/5/2026 4: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:   
   >   
   >    
   >   
   >   
   >   
   >   
   No need to change the registry   
      
   [1] If your device is capable and supported for an updated UEFI/BIOS,   
   update the UEFI/BIOS before performing the following.   
      
   Force Secure Boot Update   
      
   Logon to Windows with an admin account then Open Powershell in admin console   
      
   Manual(Force Update)   
   Set-ItemProperty -Path   
   “HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot” -Name   
   “AvailableUpdates” -Value 0x40   
      
   Start-ScheduledTask -TaskName “\Microsoft\Windows\PI\Secure-Boot-Update”   
      
   After you separately run each of the above commands, it is necessary to   
   restart your PC twice for the update to take effect.   
     => in your admin logged-on Windows profile, click on the Start button,   
   click on the Power button(lower right), click Restart. Once Windows   
   restarts to the Lock screen, do not sign on. Click on the Power button,   
   and click Restart again.   
     Then, and only then log on to Windows in the same admin account.   
      
   Open Powershell in an admin prompt, then separately run each of these   
   two commands.   
      
   Secure Boot Certs   
   ([System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes)   
   -match 'Windows UEFI CA 2023')   
      
   ([System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI   
   dbdefault).bytes) -match 'Windows UEFI CA 2023')   
      
      
     - If the first command returns “true,” then your PC is using the new   
   certificate   
     - If this second command returns “true,” your system is running an   
   updated BIOS with the new Secure Boot certificates built in.   
     Note: Older PCs and systems without a BIOS update installed will   
   return “false” here.   
      
   One can always repeat the above Powershell process if a UEFI/BIOS update   
   is available in the future.   
      
      
      
      
      
   --   
   ...w¡ñ§±¤ñ   
      
   --- 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