cumulative updates

Winsage
June 12, 2026
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 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.
Winsage
June 10, 2026
Microsoft has warned customers about potential installation complications with the latest monthly updates on certain Windows devices upgraded to Windows 11 versions 24H2 or 25H2. Users may encounter error codes 0x80073712 or 0x800f0993 when attempting to install cumulative updates for June 2026. Affected devices include a small fraction of those running Windows 10 versions 22H2 and 21H2, as well as Windows 11 version 23H2. Users may find that updates have failed, and the specified error codes will appear in the Windows Update log files. Microsoft plans to deploy a resolution for unmanaged enterprise devices and personal PCs after a system restart, with no new devices in these categories affected starting from May 19, 2026. For impacted devices, Microsoft has released specific updates as part of its June 2026 Patch Tuesday to prevent the issue. However, the problem will not be fixed for systems already upgraded to Windows 11 versions 24H2 or 25H2, and users are advised to remove the affected package using a command in an elevated Command Prompt. If this does not resolve the issue, users may need to perform a Windows 11 in-place upgrade. Microsoft has previously addressed similar challenges related to Windows update installations, including issues from the March 2026 non-security preview update and the January 2026 optional non-security preview updates.
Winsage
June 10, 2026
On June 9, 2026, Microsoft announced a vulnerability in Windows BitLocker, identified as CVE-2026-50507, which allows unauthorized attackers with physical access to bypass BitLocker Device Encryption. The flaw is categorized under CWE‑306, indicating a missing authentication check for a critical function, and has a CVSS v3.1 base score of 6.8. It affects various versions of Windows 10, Windows 11, and Windows Server from 2012 R2 to 2025. Microsoft released security updates to address the vulnerability, and it was classified as “Exploitation More Likely.” Although there is no evidence of active exploitation, proof-of-concept code exists. Organizations are advised to implement multi-factor configurations and reassess device handling and security protocols.
Winsage
May 28, 2026
A Secure Boot certificate refresh is being deployed across supported Windows devices via Windows Update. The Secure Boot certificates from 2011 will begin to expire in June 2026, prompting Microsoft to introduce new 2023-dated certificates to maintain security. Most users will require minimal action if their PCs are updated, but older devices may face challenges. The current certificates include: - Microsoft Corporation KEK CA 2011: expires June 24, 2026 - Microsoft UEFI CA 2011: expires June 27, 2026 - Microsoft Windows Production PCA 2011: expires October 19, 2026 The new certificates will remain valid until 2038, with plans for post-quantum cryptography around 2030. While PCs using the 2011 certificates will continue to function, they will lose access to new security protections, making them vulnerable to emerging threats. A notable example of such a threat is the BlackLotus bootkit, which exploited vulnerabilities to bypass Secure Boot. Microsoft's rollout strategy involves a staged update process that typically takes around 48 hours and may require restarts. Users are advised to keep Windows updated and check their Secure Boot status. Known issues may arise for older PCs, systems that bypassed Windows 11 requirements, Legacy BIOS systems, and custom firmware configurations. IT teams managing devices should inventory their systems, monitor specific event IDs, test updates, and document devices that cannot be updated.
Winsage
May 26, 2026
Removing Microsoft Edge from Windows can be complex due to its integration as a system component, especially in Windows 10 and standard Windows 11 installations. Edge may not have a straightforward Uninstall button in the Settings page, but methods exist for uninstallation, including using Edge's own installer or command-line approaches. In the EU, users may find an easier uninstall option in Settings due to the Digital Markets Act (DMA). To uninstall Edge, users should check their Windows version and region, install a replacement browser beforehand, and be aware that updates might reinstall Edge. Elevated permissions are typically required for uninstallation methods. Method A involves using Edge's setup.exe in uninstall mode from its Installer directory, which is widely compatible. Method B allows for a Settings-based uninstall in certain EU Windows 11 builds influenced by DMA. Method C uses PowerShell to remove Edge partially but may not be effective on newer builds. Method D suggests disabling Edge instead of fully uninstalling it for better system stability. Advanced techniques exist but carry risks, including potential system integrity issues. Users should consider application dependencies and the likelihood of Windows updates restoring Edge. For enterprise environments, policy-based control is preferred over complete removal. The EU DMA is driving changes toward a more modular Windows architecture, allowing for greater user choice regarding browser components.
Winsage
May 15, 2026
Microsoft's Patch Tuesday update for Windows 11, KB5089549, released on May 13, 2026, has caused installation issues for some users, who receive an error message indicating a rollback. Additionally, a smaller group has reported decreased internet performance after the update. Users facing installation failures may see the system revert to the previous version automatically and can attempt to reinstall the update or troubleshoot by clearing the SoftwareDistribution cache or using the Windows Update troubleshooter.
Winsage
May 15, 2026
Windows systems are threatened by a vulnerability in the Windows DNS Client, identified as CVE-2026-41096, which allows remote code execution without user intervention. It has a CVSS base score of 9.8, indicating high severity. The flaw is a heap-based buffer overflow in the dnsapi.dll component, enabling unauthenticated remote attackers to execute arbitrary code. Exploitation requires sending a specially crafted DNS response to a vulnerable system, potentially leading to complete control over the host. Affected systems include supported versions of Windows 11 and Windows Server 2022/2025. Microsoft released security updates on May 12, 2026, and administrators are advised to apply these patches and reboot systems. Despite the severity, Microsoft currently classifies exploitation as “Exploitation Unlikely,” with no known public exploits or in-the-wild attacks.
Search