UEFI Archives

Winsage

June 1, 2025

We installed SteamOS on our ROG Ally and Legion Go Windows handhelds and we don’t want to go back

SteamOS has been released for non-Steam Deck gaming handhelds, including the ASUS ROG Ally and Lenovo Legion Go. To install SteamOS, users need a USB-C stick and the SteamOS recovery image, which can be downloaded from Steam's website. The installation process involves creating a bootable USB drive using the Rufus utility, adjusting BIOS settings to disable Secure Boot, and following specific steps to wipe the device and install SteamOS. After installation, users can set up their Steam account and check for updates. The transition to SteamOS enhances performance and visual fidelity for these devices.

Winsage

May 29, 2025

Forced E-Waste PCs And The Case Of Windows 11’s Trusted Platform

The process of upgrading Windows operating systems was straightforward until Windows 11, which introduced a new requirement for a Trusted Platform Module (TPM), potentially rendering many capable PCs obsolete. The TPM is used for boot validation and storing biometric data, but it complicates data recovery and may lock out legitimate users. Users have found ways to bypass Windows 11's TPM and CPU restrictions, allowing installation on unsupported hardware. Microsoft’s enforcement of these requirements remains uncertain, raising concerns about system reliability and user access to updates. Many users are opting to stay on Windows 10 while advocating for continued support from developers.

Winsage

May 28, 2025

Did Microsoft Change Windows 11 Requirements? – Here’s the Truth

Microsoft has not changed the official requirements for Windows 11 since its launch. Users need a compatible 64-bit processor (1GHz or faster with at least two cores), a minimum of 4GB of RAM, and 64GB of storage. Essential features include UEFI firmware that supports Secure Boot and TPM version 2.0, DirectX 12 compatible graphics with a WDDM 2.0 driver, and displays of at least 9 inches with a resolution of 720p. Microsoft allows experienced users to manually install Windows 11 on unsupported devices at their own risk, but this is not advisable due to potential issues. The strict requirements are intended to enhance security and performance. Users can check compatibility with the PC Health Check Tool. Microsoft will support Windows 10 until October 14, 2025, after which there will be no official support. For those whose systems do not meet the specifications, upgrading hardware or purchasing a new PC may be necessary.

Tech Optimizer

May 27, 2025

BIOS and Bootloaders in the Crosshairs: Growing Firmware Threats

Hackers are increasingly targeting the startup sequence of systems, focusing on BIOS, UEFI, and bootloaders, which allows them to bypass traditional operating system defenses. Firmware threats often evade conventional security measures, providing attackers with a persistent foothold. Notable bootkits like BlackLotus, BootHole, and EFILock exploit vulnerabilities in boot components, even those protected by Secure Boot. Attackers can embed malicious code in firmware or replace legitimate bootloaders, maintaining control through OS reinstalls and hardware replacements. Common attack vectors include compromised storage, network connections, or console inputs during boot. Malicious code can execute before security software activates, and attackers may exploit misconfigured or outdated signature databases, as well as downgrade attacks on older firmware versions. To mitigate these threats, organizations should enforce Secure Boot policies, regularly update signature databases, and monitor boot behavior for anomalies.

Winsage

May 26, 2025

Deadline approaching: It’s time to say goodbye to Windows 10

Microsoft will officially discontinue support for Windows 10 on October 14, 2025. Users are encouraged to upgrade to Windows 11, which has specific hardware requirements including a modern processor, a minimum of 4 GB of RAM, and a TPM 2.0 security chip. To check compatibility, users can use the PC Health Check app. If a device does not meet the requirements, hardware upgrades or firmware adjustments may be necessary. If the BIOS mode is set to Legacy, users must convert the hard drive from MBR to GPT using the command mbr2gpt /convert /allowfullOS. It is recommended to back up data before upgrading. Microsoft is also offering an Extended Security Updates (ESU) option for approximately €27, extending support for an additional year.

Winsage

May 20, 2025

Microsoft releases emergency hotfix for Windows 10’s May update issues

Microsoft released an out-of-band update, KB5061768, for Windows 10 users to address urgent security vulnerabilities. This update is available through the Microsoft Update Catalog for Windows 10 versions 1903 and later, including Windows 10 LTSB, and supports both x86 and x64 architectures. The download size ranges from 415 MB to 711 MB. The update is crucial for users experiencing BitLocker issues and blue screen crashes after the May Windows 10 patch, particularly on devices with Intel Trusted Execution Technology enabled on 10th-generation Intel vPro processors or newer. Users unable to install the update due to boot issues should disable Intel VT for Direct I/O and Intel Trusted Execution Technology in the BIOS/UEFI settings to allow normal startup and apply the update.

Winsage

May 20, 2025

Microsoft Confirms Emergency Update For Windows Users

Microsoft has released an emergency update for Windows 10 due to issues following May’s mandatory security update, which caused BitLocker Recovery screens and Blue Screens of Death for users. The problem primarily affects devices with Intel Trusted Execution Technology on 10th generation or later Intel vPro processors. Users who encounter these issues are advised to disable Intel VT for Direct I/O and Intel TXT in BIOS/UEFI settings, install update KB5061768, and then re-enable the settings. Microsoft has stated that its support team cannot retrieve lost BitLocker recovery keys. This issue mainly impacts enterprise users, as consumer devices generally do not use Intel vPro processors.

Winsage

May 18, 2025

Microsoft Confirms New Update Locks Windows 10 — Or Worse. Here’s What To Do

Windows 10 users are facing issues due to the mandatory KB5058379 update, which has caused some PCs to boot into Windows Recovery mode and prompted the need for a BitLocker key. Some users have also experienced a Blue Screen of Death (BSOD). The update primarily affects devices with Intel Trusted Execution Technology (TXT) using 10th generation or later Intel vPro processors, particularly on Windows 10 versions 22H2 and Windows 10 Enterprise LTSC 2021. Microsoft is working on a resolution and plans to release an Out-of-band update soon. Affected users are advised to disable Intel TXT in the BIOS to complete the update successfully and avoid further issues. Windows 11 is not impacted by this problem.

Winsage

May 16, 2025

Windows 10 PCs are locking and crashing after May’s security update

Microsoft's KB5058379 update has caused issues for Windows 10 users, prompting unexpected requests for the BitLocker recovery key during startup. This problem is affecting users in Germany and the United States, impacting both corporate and personal devices. Users without the recovery key find their systems locked, leading some to perform system recoveries. Additionally, some users experience blue screen crashes after booting into Windows 10. A potential workaround is to disable the “Intel Trusted Execution Technology (Intel TXT)” option in the BIOS/UEFI. The issue primarily affects devices from Dell, HP, and Lenovo running Windows 10 versions 22H2 or 21H2 Enterprise. Microsoft has not yet acknowledged these issues related to the update.

Winsage

May 14, 2025

Microsoft fixes Linux boot issues on dual-boot Windows systems

Microsoft addressed a boot issue affecting dual-boot systems running Linux alongside Windows after the August 2024 Windows security updates, which caused Linux systems to fail to boot due to a Secure Boot Advanced Targeting (SBAT) update. This issue impacted various Windows operating systems, including Windows 10, Windows 11, and Windows Server 2012 and later. The problem arose from a detection mechanism that failed to recognize some customized dual-boot setups, leading to error messages such as "Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation." Microsoft confirmed that the boot issues would be resolved with the May 2025 Patch Tuesday security updates and provided a temporary workaround in late August, advising users to delete the SBAT update. On September 19, Microsoft stopped the automatic application of the problematic SBAT update and recommended a command to prevent future SBAT updates. The issue was specific to the August 2024 security and preview updates, and subsequent updates starting with September 2024 did not contain the problematic settings.