KB5083769: Overview with user sentiment and feedback

Overview

KB5083769 is the April 2026 cumulative security update for Windows 11 versions 25H2 and 24H2, released on April 14, 2026 with OS builds 26200.8246 and 26100.8246. This update consolidates security fixes and quality improvements from multiple previous releases spanning March 2026, including KB5079473, KB5085516, KB5079391, and KB5086672. The update addresses critical security vulnerabilities while introducing enhancements across multiple system components including Secure Boot certificate management, networking reliability, Remote Desktop security, and system reset functionality.

The update includes a significant security hardening initiative that adds known vulnerable kernel drivers to Microsoft's vulnerable driver blocklist, representing a proactive measure to protect systems from exploitation. Additionally, the patch includes updates to AI components for Windows Copilot+ devices and improvements to the Windows servicing stack (KB5088467). While the update delivers important security protections, it has been associated with multiple reported issues affecting core Windows services, particularly impacting backup operations and network-dependent functionality.

General Purpose

This cumulative update delivers comprehensive security enhancements and quality improvements across Windows 11. The primary focus includes strengthening Secure Boot certificate management with improved device targeting and phased rollout mechanisms to ensure secure boot functionality remains operational. The update enhances networking reliability by improving SMB compression over QUIC, reducing timeout occurrences and supporting more dependable network performance. Remote Desktop security receives significant attention with improved phishing protection through enhanced warning mechanisms and default-disabled connection settings. The patch also addresses a critical issue affecting the Reset this PC functionality that was causing failures when using the Keep my files or Remove everything options following previous March 2026 updates. A notable security hardening change introduces protections against known vulnerable kernel drivers by adding them to the Microsoft vulnerable driver blocklist, preventing exploitation through outdated driver components. The update includes servicing stack improvements to ensure robust update delivery mechanisms and updates to AI components for supported devices.

General Sentiment

Community sentiment regarding KB5083769 is decidedly mixed, with significant concerns emerging despite the patch's important security objectives. While the security improvements and Secure Boot enhancements are recognized as necessary, multiple users and IT professionals have reported severe disruptions following installation. The most prominent criticism centers on widespread BITS (Background Intelligent Transfer Service) failures that manifest as hangs, timeouts, and unresponsiveness, particularly affecting backup operations, Outlook synchronization, and network discovery functionality. Managed Service Providers managing multiple endpoints report clusters of failures across diverse hardware and network configurations, suggesting systemic issues rather than isolated incidents. Some users experienced cascading failures affecting multiple unrelated services simultaneously due to BITS dependency, indicating the scope of impact. However, counterbalancing perspectives note that subsequent May 2026 updates appear to have resolved many reported issues, with users confirming restoration of functionality after applying KB5089549. The vulnerable driver blocklist implementation, while security-conscious, has created compatibility issues with backup applications relying on older drivers, requiring vendor updates. IT professionals express frustration with the patch-test-fix cycle and the tension between rapid security patching requirements and system stability. Overall, while the update's security intentions are sound, execution issues and their impact on critical business functions have generated considerable skepticism about deployment timing and testing adequacy.

Known Issues

• BitLocker Recovery Key Requirement: Devices with specific unrecommended BitLocker Group Policy configurations (particularly those with PCR7 included in TPM validation profiles) may be required to enter their BitLocker recovery key on first restart after installation. This affects a limited number of enterprise-managed systems and requires Group Policy reconfiguration or temporary BitLocker suspension as workaround.
• Remote Desktop Warning Display Issues: Security warnings displayed when opening Remote Desktop (.rdp) files may not render correctly on systems using multiple monitors with different display scaling settings (e.g., 100% and 125%), resulting in overlapping text or hidden buttons that impair usability.
• BITS Service Hangs and Timeouts: Multiple reports indicate Background Intelligent Transfer Service becoming unresponsive after system idle periods, causing bitsadmin commands to freeze, download operations to timeout, and dependent services (Outlook OAB downloads, backup software, DISM, Windows Update) to fail. System reboot temporarily resolves the issue until idle time recurs. Uninstalling KB5083769 eliminates the problem.
• Backup Application Failures: Third-party backup applications relying on vulnerable kernel drivers (particularly psmounterex.sys) experience failures when attempting to mount or manage disk images, displaying errors such as "The backup has failed because Microsoft VSS has timed out during the snapshot creation" or VSS_E_BAD_STATE.
• Network Discovery Service Failures: Network Discovery service becoming unresponsive with timeout errors, breaking network browsing and discovery functionality.
• Outlook Email Delivery Disruption: Outlook Classic stopping email delivery to inbox across configured accounts without error messages, with temporary resolution through application restart but recurring issues.
• VSS and Volume Shadow Copy Service Issues: Volume Shadow Copy Service conflicts with backup software, particularly on first backup after restart, requiring VSS writer re-registration as temporary workaround.

Disclaimer: We take measures to ensure that AI-generated content is of the highest possible quality, but we cannot guarantee its accuracy and recommend that users do their own independent research. Generated on 2026-05-31 01:22 PM

Back to Knowledge Base Catalog