Event-ID 1801 at Windows Servers

[SRU]

Hello,
this morning i see that on all our Windows Servers in both clusters:

Protokollname: System
Quelle:        Microsoft-Windows-TPM-WMI
Datum:         16.11.2025 21:00:46
Ereignis-ID:   1801
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:
Benutzer:      SYSTEM
Computer:      mailstore.wo.local
Beschreibung:
Die Zertifizierungsstelle/Schlüssel für den sicheren Start müssen aktualisiert werden. Diese Gerätesignaturinformationen sind hier enthalten.
DeviceAttributes: BaseBoardManufacturer:;FirmwareManufacturer:SeaBIOS;FirmwareVersion:rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org;OEMModelNumber:Standard PC (i440FX + PIIX, 1996);OEMModelBaseBoard:;OEMModelSystemFamily:;OEMManufacturerName:QEMU;OEMModelSKU:;OSArchitecture:amd64;
BucketId: c10890fb71aa7cdfb886e34f83c5f2893060b0edc4660221f2a01f8ccf67328b
BucketConfidenceLevel:
UpdateType: 0
HResult: Unzulässige Funktion.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TPM-WMI" Guid="{7d5387b0-cbe0-11da-a94d-0800200c9a66}" />
    <EventID>1801</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-11-16T20:00:46.792656900Z" />
    <EventRecordID>2222645</EventRecordID>
    <Correlation />
    <Execution ProcessID="2832" ThreadID="3304" />
    <Channel>System</Channel>
    <Computer>mailstore.wo.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DeviceAttributes">BaseBoardManufacturer:;FirmwareManufacturer:SeaBIOS;FirmwareVersion:rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org;OEMModelNumber:Standard PC (i440FX + PIIX, 1996);OEMModelBaseBoard:;OEMModelSystemFamily:;OEMManufacturerName:QEMU;OEMModelSKU:;OSArchitecture:amd64;</Data>
    <Data Name="BucketId">c10890fb71aa7cdfb886e34f83c5f2893060b0edc4660221f2a01f8ccf67328b</Data>
    <Data Name="BucketConfidenceLevel">
    </Data>
    <Data Name="UpdateType">0</Data>
    <Data Name="HResult">-2147024895</Data>
  </EventData>
</Event>

Does that mean Proxmox must provide a bios update?



---
proxmox-ve: 8.4.0 (running kernel: 6.8.12-15-pve)
pve-manager: 8.4.14 (running version: 8.4.14/b502d23c55afcba1)
proxmox-kernel-helper: 8.1.4
pve-kernel-5.15: 7.4-15
proxmox-kernel-6.8: 6.8.12-15
proxmox-kernel-6.8.12-15-pve-signed: 6.8.12-15
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
pve-kernel-6.2.11-2-pve: 6.2.11-2
pve-kernel-5.15.158-2-pve: 5.15.158-2
amd64-microcode: 3.20250311.1~deb12u1
ceph: 18.2.7-pve1
ceph-fuse: 18.2.7-pve1
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20250512.1~deb12u1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.6-1
proxmox-backup-file-restore: 3.4.6-1
proxmox-backup-restore-image: 0.7.0
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.1.2
pve-container: 5.3.3
pve-docs: 8.4.1
pve-edk2-firmware: not correctly installed
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.3
smartmontools: 7.3-pve1
spiceterm: 3.3.1
swtpm: 0.8.0+pve1
vncterm: 1.8.1