cumulative update

Winsage
July 1, 2026
Microsoft has restored GIF functionality in the Emoji Panel for Windows 11 users after the retirement of the Tenor GIF search engine's API, which caused disruptions starting June 30. The company has transitioned to GIPHY as the new GIF provider, implemented in the preview cumulative update KB5095093 released on June 23 for Windows 11 versions 24H2, 25H2, and 26H1. Users are advised to install the latest updates to restore GIF functionality. Microsoft is also working on a solution for users on Windows 11 23H2 and Windows Server 2025. The KB5095093 update includes the Point-in-Time Restore feature and addresses various bugs and known issues.
Winsage
June 29, 2026
Microsoft has extended the availability of Windows Server 2022 hotpatching until 2027, specifically for the Windows Server 2022 Datacenter: Azure Edition. Mainstream support for Windows Server 2022 will end on October 13, 2026, while extended support will last until October 14, 2031. Hotpatching allows administrators to apply security updates without server downtime, although quarterly cumulative updates requiring a reboot will still occur. This feature is exclusive to Azure Edition users, with no similar support for on-premises users of Windows Server 2022. Additionally, hotpatch updates are being introduced for Windows 11 24H2 Enterprise clients and are now the default for Windows Autopatch.
Winsage
June 28, 2026
Microsoft is rolling out an enhanced File Explorer for Windows 11 as part of the June 2026 optional update (KB5095093 / Build 26200.8737), which will also be included in the cumulative update scheduled for July 2026. This update improves File Explorer performance, particularly by streamlining the "Home" tab and enhancing the speed of launching File Explorer. Users will experience a more responsive interface, with improvements in the address bar and fixes for issues related to unresponsiveness when mounting disk images. Enhancements also include refinements in file and folder renaming, allowing for better text selection and case-only name changes. Users can navigate between folders using double backslashes and quotation marks in the address bar. Microsoft is also testing a faster, configurable right-click menu to improve usability. The preloading feature for File Explorer is still in development, with no guarantee it will match the speed of Windows 10.
Winsage
June 12, 2026
Microsoft released a cumulative update for Windows 10, designated as KB5094127, during the latest Patch Tuesday. Some users are experiencing issues where they are prompted to enter their BitLocker recovery key after installing the update. This problem is linked to systems with an "unrecommended" BitLocker Group Policy configuration and has occurred in previous updates. Specific conditions that can lead to this issue include having BitLocker enabled on the operating system drive, a certain Group Policy setting configured, the System Information tool reporting a specific Secure Boot State, the presence of a particular certificate in the Secure Boot Signature Database, and not using the 2023-signed Windows Boot Manager. Affected users may face difficulties accessing their BitLocker recovery key, potentially leading to lockouts. Microsoft suggests that personal devices are less likely to be affected, with the issue primarily impacting enterprise setups. The company is working on a resolution and advises IT administrators to consider removing the Group Policy configuration before installing the update. Update KB5094127 is available only to Windows 10 users in the Extended Security Updates program for versions 21H2 and 22H2, addressing various bugs and security vulnerabilities.
Winsage
June 8, 2026
Microsoft has rolled out new Defender patches for Windows 11 ISOs, aligning with its commitment to security updates. Updates for Microsoft Defender for Endpoint's endpoint detection and response (EDR) will no longer be included with monthly Windows security updates or Patch Tuesdays; they will now be delivered via Microsoft Update. This change aims to allow faster deployment of EDR enhancements independently of the operating system's update cycle. The rollout for Windows 10 began in late May 2026, with plans to extend support to Windows 11 and other versions by fall 2026. EDR updates will be delivered using KB5005292, contingent on prerequisite updates. Systems must run Sense version 10.8798.25857.1000 or later and have specific Windows updates installed to qualify for the new delivery method. Organizations should align their update policies with this new approach before the broader rollout. In case of significant issues, the EDR update can be reverted using a specific command. Further details are available in the Microsoft 365 Admin Center under message ID MC1381119.
Winsage
June 1, 2026
Microsoft resolved an issue causing installation failures and error code 0x800f0922 during the deployment of the May 2026 Windows 11 security update (KB5089549), which was linked to insufficient free space on the EFI System Partition (ESP). The problem mainly affected devices with 10 MB or less available space, leading to automatic rollbacks of the update. The resolution was provided through the release of the Windows 11 KB5089573 preview cumulative update on May 26, 2026. Users installing updates released on or after this date will not need a workaround, while those with earlier updates can use the Known Issue Rollback feature. Additionally, IT administrators in enterprise settings can manually address the issue through Group Policy configurations. The KB5089573 update introduced 30 changes to improve performance and reliability.
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 28, 2026
Microsoft released a mandatory patch (KB5087537) for Windows Server 2016 to enhance cryptographic layers and address critical vulnerabilities. This update is essential for organizations using legacy workloads, as mainstream support ended in January 2022, but extended support continues until January 12, 2027. The patch aims to prepare systems for the expiration of Windows Secure Boot certificates in June 2026, which, if not updated, could compromise security and expose systems to malware. The update uses a phased deployment model and includes a new SecureBoot folder to assist IT professionals in managing certificate status. It also addresses various quality-of-life issues, including bugs affecting Remote Desktop Connection and authentication errors with Microsoft services. However, a significant issue arises when the host server name is exactly 15 characters long, causing failures in the domain controller discovery process and obstructing critical operations. This bug is linked to the historical 15-character limit of NetBIOS, which affects the Active Directory lookup mechanism. Microsoft has acknowledged the issue but has not provided a timeline for a fix, leaving administrators to either rename servers or uninstall the update. As the Secure Boot deadline approaches, IT departments must carefully assess their environments to avoid disruptions while ensuring security compliance.
Search