Known Issue Rollback Archives

Winsage

April 16, 2026

Microsoft April Update Forces BitLocker Recovery on Servers

A recent Microsoft security update, April 2026 KB5082063, has caused issues for administrators of Windows Server 2025 and Windows 11 systems, with many devices entering BitLocker recovery mode after reboot, requiring a 48-digit recovery key. This issue primarily affects enterprise-managed systems with specific TPM Group Policy settings involving PCR7 validation. Similar problems have been reported with updates KB5083769 and KB5082052 on Windows 11. The issue arises from five conditions: BitLocker must be enabled on the OS drive, the Group Policy must include PCR7, the msinfo32.exe tool must show Secure Boot State PCR7 Binding as “Not Possible,” the Windows UEFI CA 2023 certificate must be in the Secure Boot Signature Database, and the device must not be using the 2023-signed Windows Boot Manager. Microsoft suggests two workarounds: removing the TPM validation Group Policy before the update and re-enabling BitLocker, or applying a Known Issue Rollback (KIR) before installation. Skipping the April updates is not advisable due to the addressing of 167 vulnerabilities, including two zero-days. BitLocker recovery issues following updates have been recurring since 2022, with similar incidents reported in August 2022, August 2024, and May 2025, indicating ongoing challenges with Secure Boot certificates and TPM validation bindings in enterprise environments.

Winsage

April 16, 2026

Microsoft: April updates trigger BitLocker key prompts on some servers

Microsoft announced that certain Windows Server 2025 devices may experience a BitLocker recovery prompt after installing the April 2026 KB5082063 Windows security update. The recovery mode will be triggered under specific conditions: BitLocker must be enabled on the operating system drive, the Group Policy for TPM validation must be configured with PCR7, the Secure Boot State PCR7 Binding must indicate "Not Possible," the Windows UEFI CA 2023 certificate must be in the Secure Boot Signature Database, and the device must not be using the 2023-signed Windows Boot Manager. Microsoft stated that this issue is unlikely to affect personal devices, as the configurations are mainly found in enterprise-managed systems. They are working on a resolution and recommend administrators remove the Group Policy configuration before deploying the update. If removal is not possible, applying a Known Issue Rollback (KIR) is advised to prevent triggering the recovery prompt. Microsoft has previously addressed similar BitLocker recovery prompt issues in May 2025, August 2024, and August 2022.

Winsage

February 22, 2026

Opinion: Windows 11 isn’t the disaster some claim – and it’s time to say so

Windows 11 has faced challenges, including a comprehensive list of top issues identified in 2025, but it is not uniquely unstable compared to earlier versions like Windows 95, 98, XP, 7, and 10. Recent headlines have highlighted various problems such as printer malfunctions and performance issues, but these are often exaggerated due to increased visibility. Historically, Windows has experienced similar cycles of instability, and the perception of widespread failure today is amplified by rapid documentation of minor issues. User trust in Windows has eroded, with skepticism about performance stemming from cumulative updates and the personal impact of issues on over a billion users. The focus should shift to improving predictability and transparency regarding updates rather than solely counting bugs. Windows 11's frequency of out-of-band updates is comparable to that of Windows 7 and 10, with improved mechanisms for addressing problems quickly. Gamers continue to adopt Windows 11 due to enhanced CPU scheduling, improved GPU performance, and features like Auto HDR and DirectStorage. Microsoft is committed to further improving the gaming experience. The scale of Windows operations, with over a billion users and multiple concurrent releases, contributes to occasional anomalies. Despite criticisms, most Windows 11 systems operate without significant issues, performing adequately for daily tasks and gaming. Microsoft has announced plans for enhancements, including bug fixes, performance improvements, and security upgrades, indicating that Windows 11 remains a solid choice for users.

Winsage

January 19, 2026

Windows 11 PCs Fail To Shut Down After Update

Some users of Windows 11 have experienced a problem where their PCs reboot instead of shutting down after the Patch Tuesday security update KB5073455. This issue primarily affects devices with Secure Launch on Windows 11 version 23H2. Microsoft has confirmed this behavior, which disrupts the usual power-off sequence and can drain battery life for laptops and complicate remote management processes. An out-of-band update, KB5077797, has been released to restore normal shutdown and hibernation functionalities for affected systems. Users can check for this update in Windows Update or download it from the Microsoft Update Catalog. To determine if they are affected, users should look for immediate restarts when selecting Shut Down or Hibernate and check if Secure Launch is enabled in System Information.

Winsage

January 18, 2026

Windows 11 KB5074109 issues: black screen, freezes Outlook POP, breaks Azure Virtual Desktop, LocalizedResourceName (desktop.ini)

Windows 11 KB5074109 has caused several issues for users, particularly those with Nvidia GPUs, including black screens, Outlook freezing with POP accounts, and problems with File Explorer's desktop.ini settings. Users have reported random black screens and desktop freezes after installing the update, with some finding temporary relief by changing their monitor's DisplayPort mode. Outlook Classic has been problematic, remaining active in the background and freezing shortly after opening, prompting users to terminate the process in Task Manager or uninstall the update. Additionally, the update disrupts Azure Virtual Desktop functionality, leading to sign-in failures and connection issues. Microsoft has acknowledged these problems and is investigating solutions, including a Known Issue Rollback for AVD. The update also breaks the LocalizedResourceName directive in File Explorer, preventing folder name customization. Users can uninstall the update through Settings, but this may expose them to security vulnerabilities.

Winsage

January 17, 2026

How to fix Nvidia GPU FPS drop due to the Windows January 2026 update?

Users with Nvidia GPUs are experiencing decreased gaming performance after the January 2026 Windows update (KB5074109), which was intended to enhance security and address vulnerabilities. Reported issues include drops in frames per second (FPS), black screen freezes, display hangs, and driver crashes related to nvlddmkm errors. Nvidia has released a new GPU driver to address these problems. A temporary solution for affected users is to uninstall the KB5074109 update, although it is a security patch that may need to be reinstalled later. Users can also update their Nvidia drivers to the latest hotfix version and use Display Driver Uninstaller (DDU) in Safe Mode for better results. It is recommended to pause Windows updates until a fix is provided by Microsoft.

Winsage

January 16, 2026

For January, Patch Tuesday starts off with a bang

Users accessing Azure Virtual Desktop or Windows 365 Cloud PCs through the Windows App may experience authentication errors and credential prompt failures after installing updates KB5074109, KB5073455, or KB5073724. Microsoft is preparing an out-of-band fix and advises affected users to connect via the Remote Desktop client for Windows or the Windows App Web Client. A minor subset of users may also find the password icon missing on the Windows login screen, an issue since the August 2025 update, for which Microsoft has introduced a Known Issue Rollback for Pro and Home users, while enterprise deployments should implement an updated Group Policy. Microsoft has removed legacy Agere and Motorola soft modem drivers to address CVE-2023-31096, a security vulnerability, which will render hardware reliant on these drivers non-functional after the January updates. Additionally, certificates from 2011 used by many Windows devices will begin to expire in June and October, potentially causing boot issues or loss of access to Secure Boot security fixes for devices not updated with 2023 certificates. A new section for resolved issues has been introduced in the monthly updates, addressing challenges impacting enterprise environments.

Winsage

January 15, 2026

Windows App forgets how to log in with first security update of the year

Microsoft's January security update, released on January 13, 2026, has caused connection and authentication failures for users of Azure Virtual Desktop and Windows 365, particularly affecting those using the Windows App. The update has resulted in credential prompt failures during Remote Desktop connections across all supported Windows versions, from Enterprise LTSC 2016 to Windows 11 25H2, as well as Windows Servers from 2019 to 2025. Microsoft is investigating the issue and plans to release an out-of-band update soon. Users have been advised to either uninstall the update or use the Remote Desktop Client or the Windows App web client as workarounds. Reports indicate persistent issues, including an "Unable to Authenticate" error when attempting to connect via the Windows App. Microsoft has also made a Known Issue Rollback available to address these credential problems.

Winsage

November 7, 2025

Surprise! A Windows BitLocker bug has returned to ruin your reboot — here’s how to get around it

Windows 11 and Windows 10 users are experiencing a recurring bug related to BitLocker, which has reappeared after Microsoft's October security updates. Microsoft has acknowledged this issue within its Microsoft 365 Business and Windows 11 Enterprise channels, particularly affecting systems using Modern Standby. A fix is being deployed, and organizations impacted by the bug are advised to use the Known Issue Rollback tool as a temporary workaround. Users encountering the BitLocker recovery screen can retrieve their recovery key from their Microsoft account at aka.ms/myrecoverykey. Additionally, recent updates have introduced various bugs, including disruptions to the "Reset my PC" feature and issues with localhost connections and the Windows Recovery Environment. Microsoft is actively working to address these bugs.

Winsage

November 6, 2025

Latest Windows Updates Trigger BitLocker Recovery

Microsoft has warned that its October 2025 security update may cause a BitLocker recovery prompt on certain systems, particularly affecting devices running Windows 10 version 22H2 and Windows 11 versions 25H2 and 24H2. BitLocker, a security feature in Windows, encrypts drive contents to protect against unauthorized access. The issue arises when some devices inadvertently enter BitLocker recovery mode during startup. This is especially common with Intel-based devices that support Connected Standby. Affected users may need to enter a recovery key once, after which the device should boot normally. Microsoft has provided a fix that administrators must manually deploy, and users without their recovery key risk losing data. They are advised to try retrieving the key through their Microsoft account.