Microsoft pushed out an emergency out-of-band update on July 13, 2025, to fix a widespread bug that left Windows 11 24H2 users staring at frozen Start Menus and unresponsive Taskbars following the July 8 cumulative update. KB5064489 lifts OS build 26100.4656 onto affected PCs and arrives just five days after the botched KB5062553 patch, which unleashed a cascade of interface lock-ups, System Restore failures, and app compatibility crashes.

The unscheduled release underscores how a routine Patch Tuesday update can cripple core Windows shell components when quality assurance misses the mark. Across forums and social media, frustrated users reported that after installing KB5062553, clicking the Start button or right-clicking the Taskbar yielded nothing—no response, no error, just a dead UI element. For many, the only workaround was a hard reboot or rolling back the update, leaving systems vulnerable to other security fixes included in the July 8 bundle.

What KB5064489 brings to the table

Microsoft’s support document for KB5064489 lists three targeted repairs, all directly addressing regressions introduced by the earlier cumulative update. The primary fix restores full interactivity to the Start Menu and Taskbar, the most visible pain point. The company acknowledges that users experienced unresponsive behavior, though it does not detail the root cause. Based on community reports, the glitch appeared to affect both click and keyboard invocation of the Start Menu, and in some cases, the Taskbar would freeze entirely, preventing switching between open applications.

Second, the update resolves a bug that caused System Restore to fail. After KB5062553, attempts to roll back to a prior restore point would error out, leaving no safety net for users who encountered other software conflicts. This left early adopters in a precarious position: either live with the broken shell or perform a clean recovery, a time-consuming proposition for business users.

Third, Microsoft says KB5064489 “enhances compatibility with third-party applications.” While the support note is vague, user feedback suggests that several popular tools—including system utilities that hook into the Taskbar or modify the Start Menu—were crashing on launch or causing explorer.exe to restart repeatedly. One community thread mentioned that applications like StartAllBack and ExplorerPatcher became unusable, and even some antivirus software triggered infinite reload loops of the Windows shell.

A closer look at the broken KB5062553

To understand the urgency, it helps to rewind to July 8, 2025. That day, Microsoft rolled out KB5062553 as a regular cumulative update for Windows 11 24H2. It carried the usual assortment of security patches, reliability improvements, and a handful of minor feature tweaks. Within hours, reports flooded in: the Start Menu was dead, the Taskbar was frozen, and System Restore wasn’t working. On Microsoft’s own Feedback Hub and Reddit’s r/Windows11, hundreds of users described identical symptoms, ruling out random hardware or driver issues.

One user wrote: “After the update, my Taskbar is completely unresponsive. I can’t click any pinned icons, can’t open the system tray, can’t even right-click to access Task Manager. Had to Ctrl+Alt+Del just to reboot.” Another added: “System Restore fails with error 0x80070005 every time I try. I’m stuck.”

Microsoft did not immediately acknowledge the problem publicly, but over the next few days it appears internal telemetry confirmed a spike in shell failures. The quick turnaround on an out-of-band fix—released on a Sunday, no less—suggests the issue was severe enough to bypass the normal weekly release cadence. In fact, this is the second OOB update for Windows 11 24H2 in as many months. In June 2025, Microsoft shipped KB5063060 to resolve an incompatibility with Easy Anti-Cheat that was triggering unexpected restarts when launching games like Fortnite and Apex Legends.

Installing KB5064489: What you need to know

KB5064489 is available through Windows Update as an optional update. If you check for updates manually, you’ll see it listed under “Optional updates available.” Microsoft recommends installing it only if you are experiencing the specific issues mentioned; otherwise, the fixes will be rolled into the next scheduled Patch Tuesday update.

But there’s a twist: the update package is not a single .msu file. The support page reveals that KB5064489 consists of two or more MSU files that must be installed in a specific order. This is unusual for a consumer-facing update and likely signals dependencies on a prerequisite servicing stack update. For most users letting Windows Update handle installation, the process is automatic. However, if you download the standalone packages from the Microsoft Update Catalog, you need to be careful.

Microsoft provides two methods for manual installation:

  • Method 1: Place all MSU files in the same folder and use DISM with the /Add-Package command pointing to the main KB5064489 file. DISM will automatically discover and install prerequisites.
  • Method 2: Install each MSU file individually, in this exact order:
    1. windows11.0-kb5043080-x64_... (a prerequisite update)
    2. windows11.0-kb5064489-x64_... (the main fix)

IT admins deploying via WSUS or Configuration Manager will need to import the catalog files and sequence them correctly. Failure to follow the order can leave the system in an inconsistent state. This complexity has drawn criticism from some enterprise users who expected a single-click fix for such a critical bug.

The growing pains of Windows 11 24H2

The Start Menu and Taskbar debacle is the latest in a series of hiccups for Windows 11 24H2, which began rolling out in late 2024. The feature update brought under-the-hood changes to the shell, including deeper integration of the Copilot AI and a revamped notification system. Those architectural shifts appear to have introduced fragility that surface during cumulative updates.

Earlier in 2025, a different update caused File Explorer to crash on systems with specific folder customizations. And the Easy Anti-Cheat issue, while unrelated to the shell, highlighted how even minor changes can ripple into third-party ecosystems. The common thread is that Windows 11’s increasingly modular design—breaking the OS into smaller, independently updateable components—sometimes leads to compatibility gaps that only emerge when updates are combined in the wild.

Microsoft’s commitment to servicing agility, however, is evident. Out-of-band updates like KB5064489 bypass the rigid monthly schedule, allowing the company to push a fix within days instead of weeks. For users whose primary interface to the OS is frozen, that agility is not just a convenience—it’s a productivity saver.

Community reaction: Relief tempered by frustration

On the WindowsNews forums and elsewhere, the reception has been mixed. Many users expressed relief that a fix arrived before they had to roll back using a system image. “Installed it this morning, and my Taskbar is alive again,” one commenter wrote. “But why does this keep happening? Every other month, an update breaks something fundamental.”

Others pointed to the optional nature of the release. “It’s an optional update, so many people won’t even see it unless they hunt for it. My dad’s PC is still frozen because he doesn’t know to check for optional updates,” a user noted. Microsoft has not pushed the update automatically via Windows Update, meaning the millions of affected users who aren’t tech-savvy could remain stuck until the next mandatory Patch Tuesday.

There’s also frustration over the opaque release notes. “Enhanced compatibility with third-party applications” is hardly informative. Which applications? What changed? The lack of detail forces users and IT admins to guess whether their specific software will benefit, potentially leading to unnecessary installations or, conversely, missing a critical compatibility fix.

The bigger picture: Out-of-band updates and trust

Out-of-band updates are a double-edged sword. On one hand, they demonstrate responsiveness; on the other, they signal that routine quality control failed. Microsoft has released six OOB updates for Windows 11 in 2025 alone, a pace that some industry watchers find concerning. While many address niche security vulnerabilities, consumer-facing OOBs like KB5064489 and the Easy Anti-Cheat fix point to testing gaps.

Windows Insider testing should, in theory, catch shell-breaking bugs before they reach production. Yet the Start Menu freeze eluded detection for weeks in the Release Preview channel. This suggests either insufficient real-world stress testing or a last-minute change in the final cumulative package that bypassed insider validation.

For businesses, the fallout is more than annoyance. Help desks were flooded with tickets on July 9, with no immediate resolution. The only official workaround was to uninstall KB5062553, but that removes all other fixes, including security patches. Now, with KB5064489 available, IT teams face a choice: deploy immediately—risk further unknown issues—or wait for broader validation.

What should you do?

If you’re on Windows 11 24H2 and your Start Menu or Taskbar is unresponsive, go to Settings > Windows Update > Check for updates and look under Optional updates. Click Download & install next to KB5064489. A reboot will be required.

For those who haven’t yet installed the problematic KB5062553, you can safely pause updates for a few days to avoid the broken code path. Microsoft has not updated the KB5062553 package itself to include the fix; instead, the new KB5064489 layers on top. That means the original bug remains present in the July 8 update, and installing it followed immediately by the OOB fix is the intended path.

If you manage fleets, test the dual installation on a subset of machines first. The multi-file ordering adds a layer of complexity for automated deployment systems, so verify that your patch management tool chains the updates correctly.

Looking ahead

Microsoft has not stated whether it will integrate KB5064489’s fixes into the August 2025 Patch Tuesday release automatically, but historically, out-of-band fixes are rolled forward. The company is also likely reviewing its testing procedures to prevent a recurrence—though no official statement has been made.

The incident serves as a reminder that even mature software ecosystems are vulnerable to regressions when complexity scales. For Windows enthusiasts, staying informed through forums and community channels becomes essential for navigating these rough waters. KB5064489 is a swift bandage, but the deeper lesson is that Windows Update’s reliability is only as strong as the validation behind each cumulative package.

In the meantime, if your Start button works again, give it a click. You’ll feel a sense of relief—and perhaps a renewed appreciation for the code that normally does its job quietly.