Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #32274
| From | Paul <nospam@needed.invalid> |
|---|---|
| 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-12 00:42 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <110g2o7$1ukik$1@dont-email.me> (permalink) |
| References | (11 earlier) <10ukfe3$1a8v$1@dont-email.me> <10ukiut$23i9$1@dont-email.me> <110crm6$13c1h$1@dont-email.me> <110ctms$13qj8$1@dont-email.me> <110fqas$1sgr3$1@dont-email.me> |
Cross-posted to 2 groups.
On Thu, 6/11/2026 10:19 PM, ....winston wrote:
> On 06/10/2026 7:58 PM, Paul wrote:
>> On Wed, 6/10/2026 7:23 PM, sticks wrote:
>>> On 5/20/2026 10:11 AM, ....winston wrote:
>>>> On 05/20/2026 10:11 AM, sticks wrote:
>>>>> On 5/20/2026 8:50 AM, Frank Slootweg wrote:
>>>>>> sticks <wolverine01@charter.net> wrote:
>>>>>>> On 5/19/2026 5:00 PM, sticks wrote:
>>>>>> [...]
>>>>>>>> Well I'll be damned. I then did a SFC /scannow and it did find some
>>>>>>>> errors and fixed them. Rebooted. Went into the event viewer and
>>>>>>>> instead of the FPM-WMI error it had 4 entries. A pre-attestation check,
>>>>>>>> a confirmation it is expected to pass attestation, TBS device identifier
>>>>>>>> has been generated, and finally "The TPM was successfully provisioned
>>>>>>>> and is now ready for use."
>>>>>>>>
>>>>>>>> We'll see if it error faults again.
>>>>>>>
>>>>>>> All for naught. Back again this morning. Disappointing
>>>>>>>
>>>>>>>
>>>>>>> Log Name: System
>>>>>>> Source: Microsoft-Windows-TPM-WMI
>>>>>>> Date: 5/20/2026 6:53:06 AM
>>>>>>> Event ID: 1796
>>>>>>> Description: The Secure Boot update failed to update SBAT with error
>>>>>>> Unknown HResult Error code: 0x800700c1.
>>>>>>
>>>>>> If it's any consolation, I also get this error, twice a day, since at
>>>>>> least 15/01/2026.
>>>>>>
>>>>>> The error comes with a "For more information, please see..." link [1],
>>>>>> but that only mentions Event ID 1795, not 1796. However the 'Change log'
>>>>>> of the document implies that 1796 *is* documented. Microsoft moves in
>>>>>> mysterious ways! :-(
>>>>>>
>>>>>> I think that this 'Error' is nothing to worry about.
>>>>>> IMO, if we got a dollar for every 'Error' in our Event Viewer logs, we
>>>>>> would make Elon look like a pauper! :-)
>>>>>>
>>>>>> [1] 'Secure Boot DB and DBX variable update events'
>>>>>> <https://support.microsoft.com/en-gb/topic/secure-boot-db-and-dbx- variable-update-events-37e47cf8-608b-4a87-8175-bdead630eb69>
>>>>>
>>>>> I know I can't do much more myself, and am not too worried about it. However, it does annoy me that the secure boot process is evidently missing some of the available data because of the update failure. I find it difficult to believe HP cannot figure out a way to fix this error.
>>>>>
>>>>>
>>>> Run this a Powershell admin window
>>>>
>>>> ([System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023')
>>>>
>>>> - If the above command returns “true,” then your PC is using the new certificate
>>>>
>>>>
>>>> If it returns true or false, the EventViewer error is normal.
>>>> a. can't update(thus fails) if already present or not installed
>>>
>>> Thought I'd follow up on this. Both HP desktops have finally gotten an
>>> available bios update. After install, both return true to winston's powershell
>>> command, and both still have the same TPM-WMI error in the event log. still
>>> seems a weird way to do things...
>>
>> Agree on the weird part.
>>
>> Tried to use a Linux today, on the Secure Boot machine, and I didn't know
>> there was a new scheme for running a video card. There is some trick to
>> load a firmware into a video card, to act as the driver. This is Not Supported
>> on my video card, so that explains why the HD monitor was running at 1024x768.
>> I had to remove around 20 packages from the package manager, ones
>> that use the "new method", reboot, then use the Driver Manager, and it
>> selected some legacy driver that does not use that method. and then
>> the HD screen was running at 1920x1080 again.
>>
>> It seems some video card company <cough>, is angling for us to have to
>> buy some of those "cheep $400 video cards" :-) Just to have continued driver support.
>> I would certainly want a rich man to be able to afford another
>> leather jacket for presentations. The problem with schemes along
>> these lines, is it is going to make some laptop owners "very angry".
>>
>> Thank goodness for innovation. "Where-ever it strikes".
>>
>> Paul
>>
>>
>>
>
> Doesn't sound like a Secure Boot issue.
>
> How old is that Secure Boot machine that 'tried to use' Linux?
> How old is its video card.
>
> Back on topic.
> @Paul and @sticks
> There are other powershell commands in admin mode that can be run for additional information on installation/updating 2023 certs.
>
> get-securebootuefi -decoded -name DB | Where-Object {$_.Subject -match "2023"} | Select subject
>
> get-securebootuefi -decoded -name KEK | Where-Object {$_.Subject -match "2023"} | Select subject
>
>
> For this Secure Boot enabled device(Win10 Pro ESU) with a 4th Gen i7-4770 chip(yes, quite old) on a Asus Z87 Sabertooth mobo, last UEFI/Bios March 2017) the results for the above commands are:
>
> 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
>
>
> 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
>
>
> Fyi...for those interested in an explanation of DB and KEK certs
> "DB (Allowed Signature Database): The list of certificates and trusted software the PC is allowed to run. The new 2023 DB certificates are used to sign modern Windows boot components."
> "KEK (Key Exchange Key): Often called the "master authority." The KEK gives Microsoft (and your hardware manufacturer) the permission to update your DB and DBX (revocation) lists without requiring a full manual BIOS flash".
>
[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.
The top two are unlikely to ever see a working SBAT response.
Even though the middle one got a BIOS update relatively recently.
The middle machine occasionally runs an AI, using a 58GB downloaded model.
The answers are just a dodgy as the one you get that is
data center powered on your own machine. There is no apparent
benefit from running it locally.
[Picture] Run-Queries-With-Network-Cable-Disconnected.gif
https://postimg.cc/k20gzLYy
https://imgur.com/a/It9jbsL
Paul
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