Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #32359
| From | "Bill Bradshaw" <bradshaw@gci.net> |
|---|---|
| Newsgroups | alt.comp.os.windows-11, alt.comp.os.windows-10 |
| Subject | Re: Microsoft intends to kill your computer, no Secure Boot updates for you. |
| Date | 2026-06-15 09:22 -0800 |
| Message-ID | <n9aqlsF2hm7U1@mid.individual.net> (permalink) |
| References | (14 earlier) <110ctms$13qj8$1@dont-email.me> <110fqas$1sgr3$1@dont-email.me> <110g2o7$1ukik$1@dont-email.me> <110kvd6$3aegc$2@dont-email.me> <110oj3o$98so$1@dont-email.me> |
Cross-posted to 2 groups.
Paul wrote:
> On Sat, 6/13/2026 9:16 PM, ....winston wrote:
>> On 06/12/2026 12:42 AM, Paul wrote:
>>>> get-securebootuefi -decoded -name DB | Where-Object {$_.Subject
>>>> -match "2023"} | Select subject
>>>>
>>>> get-securebootuefi -decoded -name KEK | Where-Object {$_.Subject
>>>> -match "2023"} | Select subject
>>>>
>>>>
>>
>>>>
>>> [MSI] MPG B550 Gaming Plus (MS-7C56) \
>>> Infineon TPM 2.0 \
>>> Ryzen 7 5700G 8C 16T CPU \
>>> BIOS version 7/13/2024 AMI 1i0 \
>>> DDR4 RAM (four sticks) \
>>> \___ Both have been used for Secure Boot test.
>>> [ASUS] ROG STRIX B550-F Gaming Wifi II / Secure Boot is now turned
>>> off on both.
>>> fTPM (no header for a physical TPM 2.0) / They're PCA2023. One has
>>> failed a media Secure Boot
>>> Ryzen 9 5950X 16C 32T CPU / where the media was still signed with
>>> PCA2011 and
>>> BIOS version 1/4/2026 AMI 3636 / at a guess, that is revoked.
>>> DDR4 RAM (four sticks) /
>>>
>>> [Asus] P9X79 <=== used for testing non-Secure-Boot behaviors
>>> no TPM at all (UEFI/CSM BIOS)
>>> 4930K 6C 12T (HEDT, 42 PCIe lanes) This machine has W10 and W11 and
>>> can test what
>>> BIOS Version 12/24/2013 AMI 4608 miserable performance others might
>>> see. It has
>>> DDR3 RAM (eight sticks) a mixture of HDD and SSDs for test. Mouse
>>> click to response, takes 1 second.
>>
>>
>> Did you run the get-securebootuefi on any of these devices or other
>> devices(no virtual machines, but only devices with Windows 10 ESU or
>> Win11 25H2 as the installed to metal o/s)?
>>
>> If so, what were the results?
>>
>
> OK, so lets do that. First I have to turn Secure Boot back on.
> This will be on the 5950X. Then I can select the Win10 on the same
> machine, and see what is cooking over there.
>
> First Win11.
>
> msinfo32 (as administrator)
> BIOS Mode: UEFI
> Secure Boot State: ON
> PCR7 Configuration: Binding Possible
>
> Device Security
> Secure Boot - Looks like a power button circle, with the tick at
> the top, and green checkmark on the side. Text reads:
>
> "Secure Boot is on and all required certificate
> updates have been applied. No further certificate
> changes are needed." [SBAT status being ignored]
>
> Yes, this is an Administrator Terminal, but currently, either "value"
> can show
> up for the current working directory, for either terminal type.
>
> PS C:\Users\bullwinkle> get-securebootuefi -decoded -name DB |
> Where-Object {$_.Subject -match "2023"} | Select subject
>
> Subject
> -------
> CN=Windows UEFI CA 2023, O=Microsoft Corporation, C=US
> CN=Microsoft Option ROM UEFI CA 2023, O=Microsoft Corporation, C=US
> CN=Microsoft UEFI CA 2023, O=Microsoft Corporation, C=US
>
> PS C:\Users\bullwinkle> get-securebootuefi -decoded -name KEK |
> Where-Object {$_.Subject -match "2023"} | Select subject
>
> Subject
> -------
> CN=Microsoft Corporation KEK 2K CA 2023, O=Microsoft Corporation, C=US
>
> # Updates were stuck on the W11, due to (apparently) the recovery
> partition size. # I Resized it using a Macrium backup and
> restore/resize without breaking it.
>
> PS C:\Users\bullwinkle> reagentc /info
> Windows Recovery Environment (Windows RE) and system reset
> configuration
> Information:
>
> Windows RE status: Enabled
> Windows RE location:
> \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE Boot
> Configuration Data (BCD) identifier:
> 8f4fa731-3780-11ef-8ce3-b963a4dceb9a Recovery image location:
> Recovery image index: 0 Custom image location:
> Custom image index: 0
> Windows RE Version: 10.0.26100.8455
>
> DISKPART> list part
>
> Partition ### Type Size Offset
> ------------- ---------------- ------- -------
> Partition 1 System 100 MB 1024 KB
> Partition 2 Reserved 16 MB 101 MB
> Partition 3 Primary 108 GB 117 MB
> Partition 5 Recovery 2068 MB 108 GB <=== Win11 is
> using its Recovery Partition Partition 4 Primary 127
> GB 110 GB <=== Win10 is using C: for the purpose "Access is
> Denied"
>
> Winver on box reads as: 26200.8655
>
> Oh, and the box logs in without using a password (local account) :-)
> Don't
> ask me how that happened, I haven't a clue.
>
> *******
>
> Now, we'll hop over to the Win10 side, and see what it says. The
> Win10 does not
> have a Recovery partition. I hope it doesn't break anything. Doing a
> backup
> before heading over...
>
> msinfo32 (as administrator)
> BIOS Mode: UEFI
> Secure Boot State: ON
> PCR7 Configuration: Binding Possible
>
> Device Security
> Secure Boot - Looks like a power button circle, with the tick at
> the top, and green checkmark on the side. Text reads:
>
> "Secure boot is on, preventing malicious software
> from loading when your device starts up."
> "Your device meets the requirements for standard
> hardware security."
>
> Windows PowerShell
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> Try the new cross-platform PowerShell https://aka.ms/pscore6
>
> PS C:\Windows\system32> get-securebootuefi -decoded -name DB |
> Where-Object {$_.Subject -match "2023"} | Select subject
>
> Subject
> -------
> CN=Windows UEFI CA 2023, O=Microsoft Corporation, C=US
> CN=Microsoft Option ROM UEFI CA 2023, O=Microsoft Corporation, C=US
> CN=Microsoft UEFI CA 2023, O=Microsoft Corporation, C=US
> D
> PS C:\Windows\system32> get-securebootuefi -decoded -name KEK |
> Where-Object {$_.Subject -match "2023"} | Select subject
>
> Subject
> -------
> CN=Microsoft Corporation KEK 2K CA 2023, O=Microsoft Corporation, C=US
>
> PS C:\Windows\system32> reagentc /info
> Windows Recovery Environment (Windows RE) and system reset
> configuration
> Information:
>
> Windows RE status: Enabled
> Windows RE location:
> \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
> <=== this is the C: drive of W10 Boot Configuration Data (BCD)
> identifier: 8f4fa72c-3780-11ef-8ce3-b963a4dceb9a Recovery image
> location: Recovery image index: 0 Custom image location:
> Custom image index: 0
>
> REAGENTC.EXE: Operation Successful.
>
> Winver reads: 19045.7417 22H2 Windows 10 Home (my only ESU_
>
> Box login requires password.
>
> Paul
I am runnig Window 11 Pro and I am on 8457. I can not get updated and
downloaded the cumulative update to 8655 but it will not update. Checking
Device Security reports all is fine with certificates, etc.
diskpart shows:
Partition 4 Recovery 755MB 113GB
Partition 5 Recovery 800MB 114GB
Do I need to try and increase the size of the Recover Partitions?
I recognize this is not a lot of info.
<Bill>
Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Microsoft intends to kill your computer, no Secure Boot updates for you. anon <noreply@mixmin.net> - 2026-05-19 03:30 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Lynn McGuire <lynnmcguire5@gmail.com> - 2026-05-18 23:20 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-05-19 02:08 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Lynn McGuire <lynnmcguire5@gmail.com> - 2026-05-19 23:06 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-20 03:17 -0400
Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-19 13:48 +0800
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "s|b" <me@privacy.invalid> - 2026-05-19 15:02 +0200
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-19 22:48 +0800
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "s|b" <me@privacy.invalid> - 2026-05-19 16:53 +0200
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "....winston" <winstonmvp@gmail.com> - 2026-05-19 11:04 -0400
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog JJ <jj4public@gmail.com> - 2026-05-19 20:37 +0700
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-19 22:47 +0800
Re: Act now: Secure Boot certificates expire in June 2026 - Windows IT Pro Blog "....winston" <winstonmvp@gmail.com> - 2026-05-19 11:00 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Philip Herlihy <nothing@invalid.com> - 2026-05-19 11:44 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "s|b" <me@privacy.invalid> - 2026-05-19 14:40 +0200
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-05-19 10:31 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "s|b" <me@privacy.invalid> - 2026-05-19 16:55 +0200
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-05-19 18:48 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "s|b" <me@privacy.invalid> - 2026-05-20 15:34 +0200
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-19 12:02 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-19 11:30 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Frank Slootweg <this@ddress.is.invalid> - 2026-05-19 17:52 +0000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-19 16:29 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-19 16:07 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-19 16:43 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-19 17:00 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-19 20:13 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-20 07:42 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Frank Slootweg <this@ddress.is.invalid> - 2026-05-20 13:50 +0000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-20 09:11 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-05-20 11:11 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-20 11:46 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-20 20:18 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Andy Burns <usenet@andyburns.uk> - 2026-05-21 08:34 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-21 10:24 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. rbowman <bowman@montana.com> - 2026-05-21 18:15 +0000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Daniel70 <daniel47@nomail.afraid.org> - 2026-05-22 19:45 +1000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-05-22 20:52 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-22 17:50 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-05-23 00:43 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Daniel70 <daniel47@nomail.afraid.org> - 2026-05-23 19:33 +1000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-10 18:23 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-06-10 19:58 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Daniel70 <daniel47@nomail.afraid.org> - 2026-06-11 20:53 +1000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Daniel70 <daniel47@nomail.afraid.org> - 2026-06-11 23:09 +1000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-11 22:19 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-11 21:26 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-14 03:56 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-16 08:05 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-16 10:35 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-16 09:54 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-16 14:31 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-16 18:40 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-16 20:12 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-06-16 20:08 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-17 02:33 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-06-12 00:42 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-13 21:16 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-06-15 06:11 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-15 09:31 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-06-15 10:33 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "Bill Bradshaw" <bradshaw@gci.net> - 2026-06-15 09:22 -0800
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-15 20:48 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-06-16 08:38 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "Bill Bradshaw" <bradshaw@gci.net> - 2026-06-16 08:26 -0800
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-16 14:51 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "Bill Bradshaw" <bradshaw@gci.net> - 2026-06-17 08:25 -0800
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. "....winston" <winstonmvp@gmail.com> - 2026-06-18 02:21 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-20 18:05 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-20 18:31 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-20 20:12 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-20 20:16 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-22 11:15 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. sticks <wolverine01@charter.net> - 2026-05-22 11:15 -0500
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-22 17:27 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-19 21:00 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. John Smith <invalid@invalid.invalid> - 2026-05-19 19:00 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-19 16:34 -0400
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Frank Slootweg <this@ddress.is.invalid> - 2026-05-19 17:52 +0000
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Philip Herlihy <nothing@invalid.com> - 2026-05-21 11:22 +0100
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Stan Brown <someone@example.com> - 2026-05-19 17:46 -0700
Re: Microsoft intends to kill your computer, no Secure Boot updates for you. Paul <nospam@needed.invalid> - 2026-05-19 21:14 -0400
csiph-web