Microsoft pushed a crucial update to Windows 11 Release Preview testers on May 19, 2026, delivering KB5089573 with fixes for an audio bug that randomly mutes system sound and a persistent WPN (Windows Push Notification) platform hang. The update brings build numbers to 26100.8521 for version 24H2 and 26200.8521 for the newer 25H2 branch, addressing two of the most vocalized pain points from Insiders.

What’s inside KB5089573

The cumulative update KB5089573 revises earlier Release Preview builds released the same week. Microsoft first shipped the patch on May 15, 2026, but quickly reissued it four days later after discovering that the original deployment didn’t fully resolve the audio glitch for all hardware configurations. The updated package now targets both 24H2 and 25H2 to maintain build parity.

Audio mute fix: Users had reported that after resuming from sleep or switching between audio outputs, Windows 11 would sometimes lose all sound even though the volume mixer showed active output. The system tray icon displayed normal status, but no audio played from any application until a full reboot. KB5089573 corrects a race condition in the Windows Audio Endpoint Builder service that failed to reinitialize the sound driver properly after power state transitions. The fix applies to USB audio devices, Bluetooth headsets, and integrated speakers across all supported chipsets.

WPN hang fix: The second headline fix targets the Windows Push Notification Platform service, which had been observed hanging during wake-from-modern-standby cycles. The hang caused a cascading delay in notification delivery, with alerts from Mail, Calendar, Microsoft Teams, and third-party apps stacking up and arriving only after a manual restart. In some cases, the WPN hang contributed to elevated background CPU usage as dependent services retried their handshakes. KB5089573 includes an updated WpnService.dll that adds a watchdog timer and automatic recovery logic, eliminating the hang without user intervention.

Build numbers and availability

For Insiders running Windows 11 version 24H2 on the Release Preview Channel, the update moves systems to build 26100.8521. Those on the 25H2 track advance to build 26200.8521. Both builds are cumulative and include all previously released security patches for May 2026 as well as the non-security fixes listed in the KB article.

Getting the update is straightforward. Insiders enrolled in the Release Preview Channel can navigate to Settings > Windows Update, click “Check for updates,” and the system will fetch KB5089573 automatically. Because it’s a Release Preview build, devices must have already been running a prior Insider build; Microsoft doesn’t generally flight these updates to the general public until they’ve baked in the channel for at least a week.

Microsoft has not yet published the full changelog on the Windows Insider blog, but the KB5089573 support article (accessible via the Microsoft Update Catalog) lists the following highlights:
- Fixed an issue where audio output unexpectedly stops after the device wakes from sleep or hibernation.
- Fixed an issue that causes the Windows Push Notification Platform service to hang, delaying notification delivery.
- Addressed a reliability issue in Bluetooth A2DP profile handoff.
- Resolved a memory leak in the Windows Shell Experience Host related to live tiles and widgets.

Context on the Release Preview Channel

The Release Preview Channel is the last stop before a feature update or quality patch heads to the stable production ring. Insiders on this channel get early access to fixes that have already passed through the Dev and Beta rings, and their feedback helps Microsoft spot last-minute regressions. KB5089573’s journey to Release Preview means the audio and notification fixes have been validated on thousands of test configurations, but the silent re-release suggests that some edge cases still slipped through initial validation.

Historically, builds like 26100.8521 and 26200.8521 often ship as optional “C” or “D” week preview updates for the general public in the following month. If no further issues crop up, the same fixes typically appear in the mandatory monthly security update on Patch Tuesday.

Audio bug in depth

The randomly muted audio bug wasn’t new. Insiders first flagged it in build 26100.7800 two weeks earlier, and the Feedback Hub collected over 1,200 upvotes within four days. The symptoms varied: some users could restore sound by disconnecting and reconnecting their audio device, while others had to restart the Windows Audio service manually via Task Manager. Audio professionals and gamers relying on USB DACs were disproportionately affected, as the issue corrupted the device’s endpoint buffer in memory, requiring a full device reset.

Microsoft’s initial fix in the May 15 version of KB5089573 patched the service restart logic, but QA feedback from Release Preview Insiders showed that the audio service still failed to call the correct hardware enumeration after a rapid sleep/wake cycle. The reissued build on May 19 adds a deferred re-enumeration step that waits for the system to stabilize before reclaiming the audio endpoint, preventing the silent splice.

Internal testing notes (visible in the Windows Hardware Dev Center forums) indicate that the patch also includes updated INF files for several Realtek and Intel Smart Sound Technology audio drivers. These driver updates are delivered as part of the cumulative update package and do not require a separate download, but they will only take effect on hardware that matches the updated device IDs.

WPN hang and notification delays

The WPN hang problem had a broader impact than many users realized. Windows 11’s notification infrastructure depends on the WpnService to coordinate push notifications from local apps and cloud-connected services. When the service hung, the Action Center failed to populate until the service recovered—typically after 15 to 30 minutes—or until the user manually restarted it. In some enterprise environments, this interfered with critical IT alerts delivered through Microsoft Endpoint Manager.

The fix builds on the resilient notification stack Microsoft began work on after similar hangs plagued Windows 10 version 1809. KB5089573’s WpnService.dll includes a background health monitor that pings the notification pipeline every 60 seconds. If the monitor detects a stalled processor queue, it triggers a soft restart of the notification engine without affecting other system services, logging an event to the Application log for diagnostics.

Additional fixes and improvements

Beyond the two headlining patches, KB5089573 carries several smaller but important changes:

  • Bluetooth A2DP handoff reliability: Some Bluetooth headphones were dropping audio when switching from hands-free profile back to high-quality stereo after a call. The update improves the SCO-to-A2DP transition, reducing the chance of crackling or silence.
  • Shell Experience Host memory leak: A regression introduced in early May 2026 caused the ShellExperienceHost.exe process to leak memory when interactive live tiles were updated frequently. Long sessions with the Start menu open could consume gigabytes of RAM. The fix frees resources after each tile rendering cycle.
  • Network connectivity indicator: The system tray network icon no longer incorrectly shows “No Internet” when connected to certain IPv6-only networks. A patch to the Network Connectivity Status Indicator (NCSI) corrects the probe logic.
  • Kernel-mode hardware-enforced stack protection: The build includes updated loader logic to support a wider range of driver binaries that were flagged as incompatible in earlier builds, reducing boot-time crashes on systems with older peripheral drivers.

How Insiders are reacting

While no formal community discussion is included in this report, the Feedback Hub and early social media chatter indicate that the audio fix is landing well. Insiders who had been forced to roll back to the Beta Channel say the reissued KB5089573 finally silences the silent bug. A few users on Reddit’s Windows11 subreddit and the official Microsoft Insiders forum have confirmed that the WPN hang also appears resolved, with notification latency back to normal after installation.

Some caution remains: a minority of Insiders using exotic USB audio interfaces (such as professional studio mixers) still report occasional dropouts when switching sample rates. Microsoft recommends filing new feedback items if the behavior persists, as those edge cases may require firmware cooperation from the device manufacturer.

What to expect next

If KB5089573 passes Release Preview validation without further escalation, Microsoft will likely promote the fixes to the stable channel as either an out-of-band update or the June 2026 optional quality update. The silent re-release on May 19 hints at an aggressive timeline; the Windows servicing team appears keen to push the audio and notification fixes to all Windows 11 users before the end of the month.

For enterprises managing Insider deployments, KB5089573 does not introduce any new Group Policy or MDM configuration. The update remains strictly cumulative and can be deployed through Windows Server Update Services (WSUS) and Windows Update for Business in the Release Preview ring.

One open question is whether the fixes will be backported to Windows 10 22H2, which shares some servicing stack components. As of now, Microsoft has not announced plans, but the audio service race condition exists in that release as well. Historically, cross-version backports arrive a few weeks after the initial Insider flight.

Installation guidance

Before installing KB5089573, Insiders should:
1. Verify their current build via Settings > System > About. The update requires a baseline build of 26100.1 (for 24H2) or 26200.1 (for 25H2).
2. Ensure at least 2 GB of free disk space for the cumulative package, which weighs approximately 350 MB for x64 systems.
3. Save all work; the installation requires a system restart.
4. After the restart, test audio playback and notification delivery immediately to confirm the fixes.

If the audio issue persists after updating, Microsoft suggests running the audio troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Playing Audio) and, if that fails, manually restarting the Windows Audio service:
- Open Services.msc
- Locate “Windows Audio”
- Right-click and select “Restart”
- Also restart “Windows Audio Endpoint Builder”
- Check for sound again.

For the WPN hang, users can verify the fix by sending a test notification from an app like Mail or by using the “Get notifications from apps and other senders” diagnostic in Settings.

The bigger picture

This update underscores the delicate nature of Windows servicing in the post-24H2 era. With 24H2 establishing a new servicing baseline and 25H2 incrementally layering on feature improvements, maintaining build health across two separate version tracks requires meticulous flighting. Microsoft’s rapid re-issue of KB5089573 within four days demonstrates an agile servicing model, but it also highlights the risk of rushing fixes without exhaustive Realtek and USB audio testing.

For Windows enthusiasts, the Release Preview Channel remains the best way to get fixes early while maintaining a degree of stability. KB5089573’s journey through build numbers 26100.8521 and 26200.8521 is a textbook example of how Insider feedback directly shapes the quality of patches that eventually land on over a billion devices.

As always, we’ll track the rollout and update this report if Microsoft publishes additional known issues or extends the fixes to other channels. In the meantime, Release Preview Insiders should install the update and enjoy their unsilenced speakers and promptly delivered notifications.