#uefi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #uefi, aggregated by home.social.
-
Well that UEFI CA rollover is already causing the first problems in my family's Windows systems! Here we have HP firmware duking it out with Windows Update. I love the cheery tone about "no further action required" — this laptop won't boot and needs a firmware update as well as a BitLocker recovery key. #secureboot #uefi #microsoft #hp
-
Well that UEFI CA rollover is already causing the first problems in my family's Windows systems! Here we have HP firmware duking it out with Windows Update. I love the cheery tone about "no further action required" — this laptop won't boot and needs a firmware update as well as a BitLocker recovery key. #secureboot #uefi #microsoft #hp
-
Well that UEFI CA rollover is already causing the first problems in my family's Windows systems! Here we have HP firmware duking it out with Windows Update. I love the cheery tone about "no further action required" — this laptop won't boot and needs a firmware update as well as a BitLocker recovery key. #secureboot #uefi #microsoft #hp
-
Problema: Secure Boot Violation. Invalid signature detected.
Vía: @acaele
#Divulgación #Hardware #Tecnología #Cómputo #BIOS #SecureBoot #KeyManamegent #Clonación #Particiones #Acaele #AntonioKhouri #UEFI
-
Problema: Secure Boot Violation. Invalid signature detected.
Vía: @acaele
#Divulgación #Hardware #Tecnología #Cómputo #BIOS #SecureBoot #KeyManamegent #Clonación #Particiones #Acaele #AntonioKhouri #UEFI
-
Problema: Secure Boot Violation. Invalid signature detected.
Vía: @acaele
#Divulgación #Hardware #Tecnología #Cómputo #BIOS #SecureBoot #KeyManamegent #Clonación #Particiones #Acaele #AntonioKhouri #UEFI
-
Problema: Secure Boot Violation. Invalid signature detected.
Vía: @acaele
#Divulgación #Hardware #Tecnología #Cómputo #BIOS #SecureBoot #KeyManamegent #Clonación #Particiones #Acaele #AntonioKhouri #UEFI
-
Problema: Secure Boot Violation. Invalid signature detected.
Vía: @acaele
#Divulgación #Hardware #Tecnología #Cómputo #BIOS #SecureBoot #KeyManamegent #Clonación #Particiones #Acaele #AntonioKhouri #UEFI
-
Mood : https://www.youtube.com/shorts/o56qL2t4swA
Doing network booting (#DHCP, #TFTP, #iPXE, #UEFI, #SecureBoot)
I haven't reached the “Oh, that's why” so far. But very annoyedhttps://ipxe.org/secboot
“The Secure Boot shim (e.g. ipxe-shim.efi or snponly-shim.efi) will automatically load the iPXE binary with the corresponding name (e.g. ipxe.efi or snponly.efi).”
Definitely not what's happening…
So It kept loading the wrong iPXE firmware (not the snmponly) and I kept wondering why my keyboard wasn't working :< -
Mood : https://www.youtube.com/shorts/o56qL2t4swA
Doing network booting (#DHCP, #TFTP, #iPXE, #UEFI, #SecureBoot)
I haven't reached the “Oh, that's why” so far. But very annoyedhttps://ipxe.org/secboot
“The Secure Boot shim (e.g. ipxe-shim.efi or snponly-shim.efi) will automatically load the iPXE binary with the corresponding name (e.g. ipxe.efi or snponly.efi).”
Definitely not what's happening…
So It kept loading the wrong iPXE firmware (not the snmponly) and I kept wondering why my keyboard wasn't working :< -
Mood : https://www.youtube.com/shorts/o56qL2t4swA
Doing network booting (#DHCP, #TFTP, #iPXE, #UEFI, #SecureBoot)
I haven't reached the “Oh, that's why” so far. But very annoyedhttps://ipxe.org/secboot
“The Secure Boot shim (e.g. ipxe-shim.efi or snponly-shim.efi) will automatically load the iPXE binary with the corresponding name (e.g. ipxe.efi or snponly.efi).”
Definitely not what's happening…
So It kept loading the wrong iPXE firmware (not the snmponly) and I kept wondering why my keyboard wasn't working :< -
Mood : https://www.youtube.com/shorts/o56qL2t4swA
Doing network booting (#DHCP, #TFTP, #iPXE, #UEFI, #SecureBoot)
I haven't reached the “Oh, that's why” so far. But very annoyedhttps://ipxe.org/secboot
“The Secure Boot shim (e.g. ipxe-shim.efi or snponly-shim.efi) will automatically load the iPXE binary with the corresponding name (e.g. ipxe.efi or snponly.efi).”
Definitely not what's happening…
So It kept loading the wrong iPXE firmware (not the snmponly) and I kept wondering why my keyboard wasn't working :< -
Now it is a great time to ensure you've updated your #UEFI #Windows #SecureBoot Certificate Authority to 2023 versions. The old keys from 2011 are set to expire in June 2026.
Quoting microsoft:
"Devices that haven’t received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot level vulnerabilities.
Over time, this limits the device’s protection against emerging threats and may affect scenarios that rely on Secure Boot trust, such as BitLocker hardening or third-party bootloaders. Most Windows devices will receive the updated certificates automatically, and many OEMs provide firmware updates when needed. Keeping your device current with these updates helps ensures it can continue receiving the full set of security protections that Secure Boot is designed to provide."
-
Now it is a great time to ensure you've updated your #UEFI #Windows #SecureBoot Certificate Authority to 2023 versions. The old keys from 2011 are set to expire in June 2026.
Quoting microsoft:
"Devices that haven’t received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot level vulnerabilities.
Over time, this limits the device’s protection against emerging threats and may affect scenarios that rely on Secure Boot trust, such as BitLocker hardening or third-party bootloaders. Most Windows devices will receive the updated certificates automatically, and many OEMs provide firmware updates when needed. Keeping your device current with these updates helps ensures it can continue receiving the full set of security protections that Secure Boot is designed to provide."
-
Now it is a great time to ensure you've updated your #UEFI #Windows #SecureBoot Certificate Authority to 2023 versions. The old keys from 2011 are set to expire in June 2026.
Quoting microsoft:
"Devices that haven’t received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot level vulnerabilities.
Over time, this limits the device’s protection against emerging threats and may affect scenarios that rely on Secure Boot trust, such as BitLocker hardening or third-party bootloaders. Most Windows devices will receive the updated certificates automatically, and many OEMs provide firmware updates when needed. Keeping your device current with these updates helps ensures it can continue receiving the full set of security protections that Secure Boot is designed to provide."
-
Now it is a great time to ensure you've updated your #UEFI #Windows #SecureBoot Certificate Authority to 2023 versions. The old keys from 2011 are set to expire in June 2026.
Quoting microsoft:
"Devices that haven’t received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot level vulnerabilities.
Over time, this limits the device’s protection against emerging threats and may affect scenarios that rely on Secure Boot trust, such as BitLocker hardening or third-party bootloaders. Most Windows devices will receive the updated certificates automatically, and many OEMs provide firmware updates when needed. Keeping your device current with these updates helps ensures it can continue receiving the full set of security protections that Secure Boot is designed to provide."
-
Now it is a great time to ensure you've updated your #UEFI #Windows #SecureBoot Certificate Authority to 2023 versions. The old keys from 2011 are set to expire in June 2026.
Quoting microsoft:
"Devices that haven’t received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot level vulnerabilities.
Over time, this limits the device’s protection against emerging threats and may affect scenarios that rely on Secure Boot trust, such as BitLocker hardening or third-party bootloaders. Most Windows devices will receive the updated certificates automatically, and many OEMs provide firmware updates when needed. Keeping your device current with these updates helps ensures it can continue receiving the full set of security protections that Secure Boot is designed to provide."
-
heise+ | Ein Blick auf den Inhalt der EFI System Partition
Der UEFI-Bootloader für Windows liegt in einer gut versteckten Partition. Ein c’t-Skript zeigt, welche Dateien dort liegen. Wir erklären, wozu sie da sind.
-
heise+ | Ein Blick auf den Inhalt der EFI System Partition
Der UEFI-Bootloader für Windows liegt in einer gut versteckten Partition. Ein c’t-Skript zeigt, welche Dateien dort liegen. Wir erklären, wozu sie da sind.
-
heise+ | Ein Blick auf den Inhalt der EFI System Partition
Der UEFI-Bootloader für Windows liegt in einer gut versteckten Partition. Ein c’t-Skript zeigt, welche Dateien dort liegen. Wir erklären, wozu sie da sind.
-
heise+ | Ein Blick auf den Inhalt der EFI System Partition
Der UEFI-Bootloader für Windows liegt in einer gut versteckten Partition. Ein c’t-Skript zeigt, welche Dateien dort liegen. Wir erklären, wozu sie da sind.
-
heise+ | Ein Blick auf den Inhalt der EFI System Partition
Der UEFI-Bootloader für Windows liegt in einer gut versteckten Partition. Ein c’t-Skript zeigt, welche Dateien dort liegen. Wir erklären, wozu sie da sind.
-
Ce week-end j'ai un peu trifouillé le matériel de mon PC (installation d'un CPU qui a grillé à cause d'une mauvaise manip de ma part, puis réinstallation de l'ancien CPU), et depuis j'ai ce message qui apparaît au démarrage.
J'ai vérifié la pile, elle semble toujours bonne, l'UEFI garde bien la date et l'heure. J'ai tenté de réinitialiser la config #UEFI, sans succès.Quelqu'un a une idée de comment se débarrasser de cet écran ?
-
Ce week-end j'ai un peu trifouillé le matériel de mon PC (installation d'un CPU qui a grillé à cause d'une mauvaise manip de ma part, puis réinstallation de l'ancien CPU), et depuis j'ai ce message qui apparaît au démarrage.
J'ai vérifié la pile, elle semble toujours bonne, l'UEFI garde bien la date et l'heure. J'ai tenté de réinitialiser la config #UEFI, sans succès.Quelqu'un a une idée de comment se débarrasser de cet écran ?
-
Ce week-end j'ai un peu trifouillé le matériel de mon PC (installation d'un CPU qui a grillé à cause d'une mauvaise manip de ma part, puis réinstallation de l'ancien CPU), et depuis j'ai ce message qui apparaît au démarrage.
J'ai vérifié la pile, elle semble toujours bonne, l'UEFI garde bien la date et l'heure. J'ai tenté de réinitialiser la config #UEFI, sans succès.Quelqu'un a une idée de comment se débarrasser de cet écran ?
-
Ce week-end j'ai un peu trifouillé le matériel de mon PC (installation d'un CPU qui a grillé à cause d'une mauvaise manip de ma part, puis réinstallation de l'ancien CPU), et depuis j'ai ce message qui apparaît au démarrage.
J'ai vérifié la pile, elle semble toujours bonne, l'UEFI garde bien la date et l'heure. J'ai tenté de réinitialiser la config #UEFI, sans succès.Quelqu'un a une idée de comment se débarrasser de cet écran ?
-
Ce week-end j'ai un peu trifouillé le matériel de mon PC (installation d'un CPU qui a grillé à cause d'une mauvaise manip de ma part, puis réinstallation de l'ancien CPU), et depuis j'ai ce message qui apparaît au démarrage.
J'ai vérifié la pile, elle semble toujours bonne, l'UEFI garde bien la date et l'heure. J'ai tenté de réinitialiser la config #UEFI, sans succès.Quelqu'un a une idée de comment se débarrasser de cet écran ?
-
My experience upgrading the BIOS of a Windows 11 mini PC (with BitLocker) in 2026
-
heise+ | FAQ: So bootet Windows per UEFI
Was steckt hinter UEFI-Boot, BCDedit und dem BCD-Store? Diese FAQ vertieft einzelne Themen.
-
heise+ | FAQ: So bootet Windows per UEFI
Was steckt hinter UEFI-Boot, BCDedit und dem BCD-Store? Diese FAQ vertieft einzelne Themen.
-
heise+ | FAQ: So bootet Windows per UEFI
Was steckt hinter UEFI-Boot, BCDedit und dem BCD-Store? Diese FAQ vertieft einzelne Themen.
-
heise+ | FAQ: So bootet Windows per UEFI
Was steckt hinter UEFI-Boot, BCDedit und dem BCD-Store? Diese FAQ vertieft einzelne Themen.
-
heise+ | FAQ: So bootet Windows per UEFI
Was steckt hinter UEFI-Boot, BCDedit und dem BCD-Store? Diese FAQ vertieft einzelne Themen.
-
Erst #Phoenix, jetzt #AMI: ein weiterer #UEFI- bzw. #BIOS-Hersteller wird verkauft - für 1,65 Milliarden Dollar an einen Halbleiterhersteller #Lattice #AmericanMegatrends https://winfuture.de/news,158508.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Erst #Phoenix, jetzt #AMI: ein weiterer #UEFI- bzw. #BIOS-Hersteller wird verkauft - für 1,65 Milliarden Dollar an einen Halbleiterhersteller #Lattice #AmericanMegatrends https://winfuture.de/news,158508.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Erst #Phoenix, jetzt #AMI: ein weiterer #UEFI- bzw. #BIOS-Hersteller wird verkauft - für 1,65 Milliarden Dollar an einen Halbleiterhersteller #Lattice #AmericanMegatrends https://winfuture.de/news,158508.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Erst #Phoenix, jetzt #AMI: ein weiterer #UEFI- bzw. #BIOS-Hersteller wird verkauft - für 1,65 Milliarden Dollar an einen Halbleiterhersteller #Lattice #AmericanMegatrends https://winfuture.de/news,158508.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
