PowerShell

Winsage
July 29, 2026
Microsoft reassured Windows 11 and Windows 10 users that their PCs will continue to boot normally and receive updates even if they have not yet received the new Secure Boot 2023 certificates. The rollout of these certificates is expected to continue over the upcoming months. The initial Secure Boot certificate expired on June 24, 2026, and Microsoft has been replacing older 2011 certificates since 2024. The latest update, KB5101650, transitioned Windows 11 to OS builds 26200.8875 and 26100.8875 for versions 25H2 and 24H2, respectively. The 2023 certificates replace older certificates with modern cryptographic standards, allowing Microsoft to deliver DBX revocation updates without interruption. Devices using the 2011 KEK can only receive DBX updates signed with that key, which is no longer valid after June 24. Microsoft has been rolling out the 2023 certificates for the past two years, and many devices remained in a yellow or red status by the June deadline. To check Secure Boot status, users can navigate to Windows Security > Device Security. A green checkmark indicates successful application of the certificates, while yellow and red alerts indicate compatibility issues or firmware incompatibility. PCs that are older or operating in Legacy BIOS mode will not receive the updates. Windows 10 also receives Secure Boot updates, but enrollment in Extended Security Updates (ESU) is required.
Winsage
July 29, 2026
Pressing F7 in the Command Prompt displays a pop-up with a numbered list of recently executed commands, allowing users to select and execute commands quickly without retyping. This feature, introduced in MS-DOS 5.0 through DOSKEY.exe, has been integrated into Windows since the early 1990s. Users can navigate the command list with the Up and Down arrow keys and execute a command by pressing Enter. The command history is session-specific and is lost when the window is closed. The F7 feature provides a visual overview of commands, enhancing efficiency compared to repeatedly pressing the Up Arrow key. However, it does not retain command history between sessions or offer advanced features found in modern shells like PowerShell.
Winsage
July 27, 2026
On July 22, Microsoft announced the KMS Hardware-Secured requirement, linking Windows volume activation servers to a TPM chip. This initiative is aimed at organizations using Key Management Service (KMS) servers to enhance security by ensuring that KMS hosts verify their identity and integrity through the TPM before activating Windows machines. The motivation behind this requirement is to prevent unauthorized activation methods that exploit fake KMS servers. Organizations are advised to ensure their KMS hosts are certified and that TPM is enabled. The KMS Hardware-Secured measures do not target individual users with pirated copies of Windows, as most current piracy methods do not involve KMS servers. Microsoft has not pursued legal action against minor piracy instances, focusing instead on maintaining user engagement through subscriptions and services.
Winsage
July 18, 2026
Microsoft held its OEM Secure Boot Office Hours event on July 15, where engineers collaborated with OEM representatives from companies like Acer, Asus, Cisco, Dell, and HP. IT administrators were able to ask live questions about the Secure Boot 2023 rollout. The discussion thread became a detailed technical record, especially following the expiration of the first certificates three weeks prior. Concerns raised by IT admins included BitLocker recovery loops, stuck confidence ratings, and unhelpful Intune error codes. Key facts include: - Devices offline for long periods will still receive the 2023 certificates upon reconnecting to Windows Update. - Devices with existing 2023 certificates in firmware will switch to the new boot manager after the latest Windows patches are installed. - A new script, Detect-SecureBootCertUpdateStatus.ps1, is available in Windows for checking certificate status. - BIOS updates may reset a device’s confidence rating to unrated, which is normal and does not indicate certificate failure. - Admins should edit the AvailableUpdates registry key, not the AvailableUpdatesPolicy, which is managed by Intune and Group Policy. - A licensing bug affecting AvailableUpdatesPolicy on devices upgraded from Pro to Enterprise was resolved by Microsoft in 2026. - BitLocker recovery is not typically linked to the certificate update process but may relate to firmware or PCR issues. - Dell and HP provided guidance on which BIOS versions include the 2023 certificates for their newer models. - Older HP EliteBook 840 G5 units require a manual update package for the new certificates. - Eligible devices can still receive the 2023 certificates in the future, and Surface devices released from 2024 onward come pre-equipped with them. - Microsoft confirmed that devices running 2011 certificates will not lose the ability to receive the 2023 chain. - The Microsoft Corporation KEK CA 2011 and Microsoft UEFI CA 2011 certificates have expired, with the Microsoft Windows Production PCA 2011 set to expire on October 19, 2026.
Search