rollback Archives

Winsage

June 1, 2026

Microsoft fixes KB5089549 Windows security update install issues

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

June 1, 2026

Microsoft confirms Windows 11 update is failing on some PCs, explains if you need a workaround

Microsoft has identified the root cause of installation issues related to the May 2026 update for Windows operating system and is rolling out a solution through an optional update, KB5089573. The May 12, 2026, Patch Tuesday update (KB5089549) introduced enhancements but many users faced installation failures due to error code “0x800f0922,” indicating insufficient space on the EFI System Partition (ESP). The ESP is critical for boot files and typically occupies around 256MB. Users can check ESP storage using a specific command. Low ESP space can lead to update failures, particularly when it drops below 10MB. Microsoft has rolled back problematic code and provided a fix in the optional update KB5089573, which resolves ESP space issues and ensures future updates will proceed smoothly. Users are encouraged to install this update or wait for the next scheduled Patch Tuesday update on June 9, 2026.

Winsage

May 31, 2026

Microsoft to add automatic driver rollback to Windows 11

Microsoft is set to introduce a feature for Windows 11 called Cloud-Initiated Driver Recovery (CIDR), which will automatically revert problematic driver updates to stable versions via Windows Update. This feature aims to improve user experience by eliminating the need for manual uninstallation of faulty drivers. CIDR will monitor drivers and, if a driver is found to be problematic, it can initiate a remote rollback to restore a stable version. The process will not require additional software installations or changes to existing workflows for hardware manufacturers. The automated rollback will specifically target only the affected hardware components, ensuring other drivers and system functions remain unaffected. Initial testing for CIDR is scheduled between May and August 2026, with a broader rollout expected in September 2026.

Winsage

May 28, 2026

Windows Server 2016 Update: Disastrous Bug Breaks AD

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.

Winsage

May 21, 2026

A Windows 11 bug blocks all updates since February. Here’s what to do

A segment of Windows 11 users has been unable to receive updates since February due to issues stemming from the January Preview Update, which caused download timeouts. This has resulted in missed security patches and critical updates related to Secure Boot certificates. Users may experience crashes during the update process, indicated by the error code 0x80010002. To check if affected, users can view their update history in Settings; if no updates have been installed since January and updates have not been paused, they are likely impacted. Microsoft is working on a fix linked to download timeout changes and firewall settings. A Known-Issue Rollback (KIR) can be executed to revert to a previous state before the problematic update, restoring normal functionality. This rollback is available for specific Windows 11 versions and Windows Server 2025.

Winsage

May 20, 2026

Microsoft confirms Windows 11’s May 2026 update is failing to install with error 0x800f0922 and outlines a mitigation for affected PCs

Microsoft has acknowledged installation issues with the May 2026 Security Update for Windows 11, specifically error code 0x800f0922, affecting devices on versions 24H2 and 25H2 after installing update (KB5089549) released on May 12. The failures occur during the reboot phase, often around 35 percent, primarily on devices with 10MB or less free space in the EFI System Partition (ESP). For consumer and unmanaged business devices, Microsoft has implemented a Known Issue Rollback (KIR), and restarting the computer may resolve the issue. For managed devices, network administrators must manually deploy a Group Policy workaround. Microsoft suggests modifying a Registry value to decrease reserved padding in the EFI partition as a potential fix, along with restarting the computer and checking for updates. A permanent solution is planned for a future Windows update.

Winsage

May 19, 2026

Microsoft confirms patching issues in restricted Windows networks

Microsoft has issued a service alert indicating that customers in restricted network environments may encounter Windows Update failures, specifically error code 0x80010002, after installing the January 2026 optional non-security preview updates. Affected devices might download the February monthly Windows security update but could struggle with updates released in March and beyond due to changes in download timeout requirements. Microsoft is working on a resolution, and IT administrators can use Known Issue Rollback (KIR) as a workaround by configuring the appropriate Group Policy for their Windows version. A device restart is required to apply these settings. Historical issues include a bug fixed in April 2025 affecting WSUS installations and another issue resolved in August 2025 related to the Windows 11 24H2 cumulative update. Additionally, a KIR fix was provided for a known issue causing the May 2026 Windows 11 security update to fail with error code 0x800f0922.

Winsage

May 19, 2026

Microsoft admits faulty drivers were killing Windows 11 battery life for years

Microsoft has acknowledged that faulty third-party drivers have caused significant battery drain and performance issues in Windows 11 and earlier versions. This issue, referred to as a "blind spot," has affected users through high latency, audio glitches, graphics errors, and micro-stuttering. To address this, Microsoft is implementing a more rigorous driver evaluation process that assesses the impact of drivers on power consumption and performance. Changes include improved battery management during standby mode, enhanced scrutiny of driver performance, early collaboration with developers, a stricter approval process for third-party drivers, and an automatic rollback feature via Windows Update to revert to older, compliant drivers.

Tech Optimizer

May 18, 2026

Google Pushes AI for PostgreSQL Development

Google is integrating artificial intelligence into PostgreSQL engineering while ensuring engineers remain responsible for their code contributions. This initiative aims to improve productivity and streamline processes, particularly in version upgrades, replication behavior, and production recovery. Sailesh Krishnamurthy, Google Cloud's VP of Databases, emphasized the importance of human oversight in this AI-driven approach. Between July and December 2025, Google's PostgreSQL engineering focused on logical replication, improvements to pg_upgrade, and upstream bug fixes. Logical replication allows selective database change transfers, which is beneficial for migrations and upgrades. The roadmap includes Automatic Conflict Detection and logical replication of sequences to minimize manual synchronization issues. Enterprise teams are particularly interested in these developments due to the challenges posed by write collisions and misaligned sequence values. The demand for PostgreSQL services at Google is increasing due to migration needs from Oracle and SQL Server. Recent data shows PostgreSQL's rising popularity, ranking fourth in the DB-Engines ranking and gaining 8.37 points year over year, while its competitors experienced declines.

Winsage

May 18, 2026

Windows boot partition runs out of space for Microsoft’s May security update

Microsoft has acknowledged a potential issue with its May 2026 security update, which may fail to install properly due to insufficient space in the EFI System Partition (ESP). If the available space in the ESP drops below 10 MB, users may encounter a 0x800f0922 error code, leading to installation failures during the reboot phase. This issue affects Windows 11 versions 25H2 and 24H2. Microsoft has proposed two solutions: a registry edit or a Known Issue Rollback (KIR), which has already propagated to consumer and non-managed business devices. The update addresses several critical Microsoft CVEs, although there have been no reports of active exploitation.