Known Issue Rollback Archives

Winsage

September 28, 2026

Windows 11 preview update causes black screen after sign-in; Microsoft publishes workaround

On September 24, Microsoft reported an issue affecting devices that installed the August 27 preview update for Windows 11, causing a black screen after sign-in and preventing the desktop from loading correctly. This issue primarily impacts Azure Virtual Desktop (AVD) hosts using FSLogix with existing user profiles. The affected OS versions are Windows 11 versions 26H1, 25H2, and 24H2, and the causal update is KB5120998. Microsoft has issued interim workarounds, including a manual desktop launch and a Known Issue Rollback (KIR), which will be automatically delivered to non-enterprise devices. Affected enterprise-managed devices require manual deployment of the KIR policy. The black screen issue is part of a series of update-related problems for Windows 11 in 2026, while Windows 10 has experienced fewer issues during the same timeframe.

Winsage

September 26, 2026

Microsoft: Recent Windows updates cause desktop loading issues

Microsoft has acknowledged that some users may experience desktop loading issues, specifically black screens, after installing the August 2026 preview updates and subsequent releases. This problem mainly affects Azure Virtual Desktop (AVD) hosts using FSLogix. Symptoms include a black screen post-sign-in and crashes related to Windows Explorer, which can be temporarily resolved by manually launching Windows Explorer through Task Manager. For enterprise customers, Microsoft has introduced a mitigation strategy via Known Issue Rollback (KIR), allowing IT administrators to reverse problematic updates by applying specific group policies. Additionally, Microsoft has addressed issues related to the loss of mouse and desktop settings on certain Windows 11 systems caused by the KB5120998 update.

Winsage

September 25, 2026

Windows 10 is more stable than Windows 11 in 2026, data shows

The September update for Windows 11 caused significant disruptions, including failures in USB audio functionality and the File History feature. This follows a trend of issues over the past months, with August experiencing printer and PDF problems, July affecting certain Dell PCs, and June reporting startup issues and BitLocker recovery failures. In total, eight out of nine months this year have had at least one major issue. A recurring BitLocker user lockout problem has also been noted. Despite these issues, Windows 11 has improved in overall stability, with fewer system crashes. Windows 10 has maintained stability by focusing solely on security updates since support ended in October 2025, avoiding new feature rollouts. Users satisfied with Windows 10's features may prefer to stay with it for stability. Windows 11 users facing instability can roll back updates or use the Known Issue Rollback feature to revert problematic non-security features.

Winsage

September 25, 2026

Windows update leaves some virtual desktops staring into the void

Microsoft has acknowledged an issue affecting some Windows 11 users utilizing virtual desktops, where a black screen appears after sign-in, requiring manual launch of Explorer to regain access. This glitch is linked to devices operating on the August 2026 non-security preview update or later. It has been predominantly observed on Azure Virtual Desktop (AVD) hosts using FSLogix, with crashes of Windows Explorer noted in the Application event log. A temporary workaround involves using Task Manager to initiate explorer.exe as a new task. Microsoft has implemented a Known Issue Rollback (KIR) via Group Policy to disable the problematic change until a permanent fix is released. Versions 26H1, 25H2, and 24H2 of Windows 11 are affected, while Windows 10 and Windows Server do not appear to be impacted.

Winsage

September 14, 2026

Latest Windows Server Updates Cause Remote Desktop Issues

Organizations that implemented Microsoft’s September 2026 security updates are experiencing challenges with Remote Desktop Services (RDS) on Windows Server systems, leading to instability and connection failures. Issues typically arise hours after the update, causing ongoing Remote Desktop sessions to freeze, difficulties in disconnecting, and failures in establishing new connections. Affected systems include Windows Server 2012 through Windows Server 2025 and select Windows client versions, with problems such as failed RDP connections, sign-in difficulties, unresponsive management tools, and servers stalling during Remote Desktop configuration. Microsoft advises administrators to uninstall the September 2026 updates, which would remove security enhancements, and is investigating the root cause while providing Known Issue Rollback policies. For inaccessible virtual machines, restarting the affected VM is recommended as a temporary measure.

Winsage

August 10, 2026

Which Windows 11 Update Is Causing Problems in 2026? – TheZeroNet

KB5094126, released in June 2026, is causing significant issues for Windows 11 users, including BSODs, boot failures, BitLocker lockouts, and problems launching Office applications. This update has particularly affected HP enterprise hardware, leading to BitLocker recovery loops and black screens. The issues stem from disk space limitations related to Secure Boot certificate handling and restricted EFI partition space. Affected users are advised to locate their BitLocker recovery keys and consider workarounds, such as launching Office applications directly. Windows 10 users are also experiencing similar problems due to the related update KB5094127. Microsoft is expected to release fixes in subsequent updates, including KB5101650 in July 2026.

Winsage

July 10, 2026

Microsoft goes all in on new AI-powered Windows security strategy – what it means for you

Microsoft is integrating artificial intelligence into its vulnerability management processes to enhance cybersecurity, particularly for its Windows operating system used by over 1.5 billion devices. The company is implementing an automated, AI-driven approach to identify vulnerabilities earlier in the development cycle, allowing for quicker fixes. Microsoft has developed a cloud-based scanning system called MDASH, which has identified 16 vulnerabilities since its introduction, four of which were critical and promptly patched. AI tools are being embedded earlier in the software development lifecycle, and Microsoft is updating its Secure Development Lifecycle best practices to address potential AI-enabled attack techniques. The shift towards an AI-enhanced system will lead to an increase in the volume of security updates, requiring enterprise administrators to adopt more agile approaches to testing and deploying updates. Microsoft has introduced a feature called Known Issue Rollback (KIR) to help admins revert problematic changes. The company emphasizes the importance of human oversight in evaluating AI findings and making informed decisions.

Winsage

July 9, 2026

Evolving Windows vulnerability management to meet the speed of AI-powered discovery

Microsoft is enhancing its security measures for Windows by integrating artificial intelligence (AI) to improve the discovery and analysis of vulnerabilities across its codebase. This includes the use of a multi-model agentic scanning harness (MDASH) that employs various AI models to identify and validate potential vulnerabilities efficiently. A dedicated cloud infrastructure supports this scanning process, which aims to minimize false positives and reduce the time from discovery to customer protection. The company collaborates across divisions to promote AI-powered tools and practices, refining its internal systems to integrate vulnerability discovery into development processes. This includes updating Secure Development Lifecycle (SDL) practices to address AI-enabled attack techniques. Customers can expect an increase in security updates as AI enhances vulnerability discovery capabilities. Windows updates undergo rigorous validation through programs like the Security Update Validation Program (SUVP) to ensure quality and compatibility. Microsoft also offers tools like Known Issue Rollback (KIR) for quick reversion of changes if issues arise during updates. Customers are encouraged to stay current with security updates and utilize resources like the Security Update Guide for prioritizing protections. To facilitate smoother update processes, Microsoft provides optional non-security preview releases for compatibility testing and employs modern management capabilities like Windows Autopatch to automate security updates. Azure Arc enables rebootless updates for Windows Servers, while Microsoft Defender and Intune help manage vulnerabilities and compliance across endpoints. Overall, Microsoft is committed to continuous improvement in its security practices to adapt to the evolving threat landscape and ensure customer protection through timely updates.

Winsage

June 12, 2026

Microsoft fixes Windows update failures linked to WUSA installer

Microsoft resolved an issue affecting the installation of Windows updates released since May 2025, which primarily impacted users using the Windows Update Standalone Installer (WUSA) from a network share, especially in enterprise environments. The problem was significant for devices running Windows 11 24H2/25H2 and Windows Server 2025, but did not occur when handling a single .msu file or when files were stored locally. In August 2025, Microsoft acknowledged that updates installed using WUSA might fail with error ERRORBADPATHNAME when multiple .msu files were involved. A Known Issue Rollback Group Policy was implemented in September 2025 to mitigate the impact on home and non-managed business devices. The issue was ultimately resolved with cumulative updates released in June 2026 for Windows 11 (KB5079391) and Windows Server 2025 (KB5094125). Microsoft provided a workaround for users experiencing difficulties with prior updates by suggesting they save .msu files locally for installation. Users were also advised to wait at least 15 minutes after installing an .msu file via WUSA before checking the Update History page. Additionally, Microsoft had previously addressed another issue in April 2025 that affected enterprise customers installing security updates via WSUS, which recurred in the August 2025 updates. Microsoft warned customers about potential issues with installing the latest monthly updates on devices upgraded to Windows 11 24H2 or 25H2.

Winsage

June 11, 2026

Microsoft fixes BitLocker recovery bug on Windows Server 2025

Microsoft has resolved an issue affecting certain Windows Server 2025 devices that were booting into BitLocker recovery mode after the April 2026 security update. This issue was linked to specific BitLocker Group Policy configurations and required users to input their BitLocker recovery key upon the first restart after the update. However, this key would only need to be entered once for subsequent restarts, provided the group policy configuration remained unchanged. The problem primarily affected enterprise systems rather than personal devices. The issue arose under specific conditions: BitLocker was enabled on the operating system drive, a particular Group Policy was set, the Secure Boot State PCR7 Binding was "Not Possible," the Windows UEFI CA 2023 certificate was present, and the device was not already using the 2023-signed Windows Boot Manager. Microsoft released fixes in the KB5094125 and KB5093998 updates to address this problem, preventing devices with incompatible group policy configurations from installing the 2023-signed Windows Boot Manager. Event ID 1032 in the System event log indicates the issue when Windows updates are installed. For IT administrators unable to deploy the latest updates, it is recommended to remove the Group Policy configuration before installing updates or to implement a Known Issue Rollback (KIR) on affected devices. Additionally, Microsoft had previously addressed similar BitLocker recovery issues in August 2024 and May 2025.