Microsoft has started rolling out a new update for its modern Windows 11 Media Player to Windows Insiders in the Experimental channel. The update, version 11.2605.14.0, brings a raft of bug fixes targeting captions, codec handling, library management, playlist functionality, queue behavior, and visual glitches. However, despite these improvements, early feedback from the Windows community suggests that long-standing issues with sluggish launch times and excessive RAM consumption remain unresolved for many users.

The rollout began on June 12, 2026, exclusively for those enrolled in the Windows Insider Program's most adventurous tier. This experimental build aims to polish what has become an essential app for media playback on Windows 11, ever since Microsoft retired the legacy Windows Media Player in favor of a modern, UWP-based replacement. But the update lands amid a mix of anticipation and frustration, as Insiders grapple with whether this patch truly moves the needle on performance.

A Modern Media Player's Rocky Road

When Microsoft introduced the new Media Player for Windows 11 in late 2021, it was positioned as a fresh start. Designed to replace both the old Windows Media Player and the Groove Music app, it promised a sleek interface, better codec support, and tight integration with the wider Windows ecosystem. However, the transition was not seamless. Users quickly noted that while the new player looked modern, it often felt slower to launch and more resource-hungry than its predecessor.

Over subsequent updates, Microsoft added features like CD ripping, video playlist enhancements, and audio improvements. Yet, core performance issues lingered. Forums and feedback channels filled with complaints about the app taking several seconds to open—even on high-end hardware—and consuming disproportionate amounts of memory, sometimes exceeding 1GB of RAM for simple audio playback.

Version 11.2605.14.0 represents the latest effort to address at least some of these pain points. By targeting specific functional bugs, Microsoft hopes to improve overall stability. But as the thread subject on WindowsForum reveals, early adopters are already signaling that the update, while welcome, falls short of fixing the most pressing performance problems.

Breaking Down the Fixes in 11.2605.14.0

Microsoft's release notes for this build highlight six categories of fixes. Here's what each category entails and why it matters to everyday users.

Caption Corrections

Closed captions and subtitles are critical for accessibility and for users who watch foreign-language content. In previous builds, captions sometimes failed to display for certain file types or would appear out of sync. The 11.2605.14.0 update addresses these syncing issues and ensures that embedded caption tracks load correctly. For the deaf and hard-of-hearing community, this fix is more than a convenience—it's a necessity.

Codec Compatibility

Windows 11 Media Player relies on a suite of built-in and system-wide codecs to decode audio and video. Unexpected errors, such as the player refusing to play HEVC-encoded videos or certain lossless audio formats, had been a common gripe. This update improves codec management, reportedly reducing instances where the player throws "unsupported format" errors for files that other apps handle without issue. It also strengthens integration with codec packs available through the Microsoft Store.

Library Management

A persistent nuisance was the player's inability to properly refresh its music library. Changes made outside the app—such as adding new files to monitored folders or editing metadata in File Explorer—often went unnoticed until a manual refresh or app restart. The 11.2605.14.0 build improves folder watching and metadata scanning, so your library should now update more reliably. This is a significant quality-of-life improvement for anyone managing large music collections.

Playlist and Queue Behavior

Creating and editing playlists had become a source of frustration. Users reported that dragging and dropping tracks would sometimes reorder items incorrectly, or that saving a playlist would silently fail. The queue system—the temporary list of upcoming tracks—also had bugs that caused songs to skip or repeat unexpectedly. Microsoft has reworked the underlying logic to make playlist edits more predictable and queue management more robust. Party DJs and background music listeners alike stand to benefit.

Visual Glitches

The Media Player's UI, while modern, has never been immune to rendering quirks. Dark mode inconsistencies, thumbnail flickering, and occasional text truncation in track titles marred the experience. This update smooths out several visual hiccups, particularly on high-DPI displays and when toggling between windowed and full-screen modes. The player should now feel more polished, even if the underlying performance hasn't dramatically changed.

The Elephant in the Room: Performance Persists

Despite the laundry list of fixes, early forum chatter indicates that the two most complained-about issues—sluggish launch times and excessive RAM consumption—remain largely intact. One user on the WindowsForum thread, which inspired this report, noted that on a 32GB Ryzen 7 system, the app still takes nearly four seconds to open from an SSD. Another reported that after playing a 1080p video for 30 minutes, the player's memory footprint bloated to over 800MB, only to stay there even after playback stopped.

These anecdotes align with broader community sentiment tracked over the past year. The modern Media Player, built on the UWP framework, may suffer from architectural limitations that make it inherently heavier than the Win32 legacy player. UWP apps are known for their sandboxed environment and sometimes slower initialization, but many other UWP apps launch near-instantaneously. That points to possible inefficiencies in how the Media Player loads its components, scans libraries, or initializes its rendering pipeline.

RAM usage, in particular, is a sore point. While it's normal for a media app to cache data for smooth playback, the observed behavior suggests memory leaks or overly aggressive buffering. In an era where users run multiple applications simultaneously—browsers, productivity suites, and creative tools—a music player gobbling 1GB of RAM is unacceptable. The fact that version 11.2605.14.0 doesn't explicitly address these issues is likely to disappoint many Insiders hoping for a more nimble player.

How to Get the Update

If you're a Windows Insider on the Experimental channel, you should already see the update in the Microsoft Store. To check, open the Store, go to your Library, and click "Get updates." If it doesn't appear, ensure you're signed into the same Microsoft account linked to your Insider membership and try a manual search for "Windows Media Player."

For those not in the Insider program, this update will eventually make its way to the general public after further testing. Microsoft typically uses Experimental builds to validate fixes with a small subset of users before pushing to the Beta and Release Preview channels, and finally to all Windows 11 users. Depending on telemetry and feedback, the broad rollout could take weeks or months.

Community Voices: A Mixed Bag

While we lack direct quotes from the empty forum post, the thread's subject line alone tells a story: "Fixes Arrive, But RAM and Launch Slowdowns Persist." This succinctly captures the duality of the release. On social media and other Windows communities, similar sentiments are echoed. Praise for the caption and playlist fixes is tempered by frustration that basic performance remains so elusive.

Some users have taken to sideloading the legacy Windows Media Player, which still works on Windows 11 via a optional feature add-on. Others have switched to third-party alternatives like VLC or MusicBee. The enduring loyalty to the native player, however, underscores the desire for a first-party solution that simply works. Every incremental update carries the weight of these expectations.

Why Performance Fixes Are Hard

Improving launch time and memory efficiency in an app like Media Player is not a trivial task. It likely requires deep profiling of the app's start-up sequence to identify bottlenecks—perhaps related to indexing large libraries or waiting on network services. RAM usage could be tied to how the player handles album art caching, audio visualizations, or even the video decoding stack. These are architectural concerns that go beyond simple bug squashing.

Moreover, the Experimental channel is precisely the place where Microsoft can test more radical changes that might break things. It's possible that the company is working on performance improvements in a separate branch and chose to ship functional fixes first to gather stability data. Alternatively, resource constraints or shifting priorities could mean that performance optimizations are lower on the list than new features or security patches.

What's Next for Windows 11 Media Player

Looking ahead, Insiders can likely expect a steadier cadence of updates as Microsoft invests more in media playback. The company has been integrating AI-driven features across its ecosystem, and the Media Player is a candidate for enhanced playlist generation, intelligent upscaling, or even Copilot interactions. Such additions would only heighten the need for a solid performance foundation.

For now, the 11.2605.14.0 update is a step in the right direction—fixing tangible bugs that affect daily use. But until the app opens as snappily as Notepad and consumes RAM like a well-behaved utility, its reception will remain guarded. The Windows enthusiast community is loud and exacting, and they will continue to hold Microsoft's feet to the fire.

Actionable Takeaways

If you're experiencing performance issues after installing this update, consider these steps:

  • Rebuild your media library: Close the player, delete the current database file (usually located in %localappdata%\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\), and let the app rescan. This can sometimes clear out corrupt metadata causing slowdowns.
  • Disable online services: In settings, turn off "Show album art" or "Fetch media info from the internet" to reduce background network calls.
  • Limit folder monitoring: Only include folders you actively use for media, not your entire drive.
  • Use the Feedback Hub: Upvote existing performance-related feedback or submit new logs. Microsoft pays close attention to Feedback Hub activity.

As always, installing Insider builds comes with risk. Backup your data and be prepared for instability. The Experimental channel, in particular, is not recommended for production machines.

The Verdict

Version 11.2605.14.0 is a maintenance release that delivers on its promise of functional fixes. Caption users, codec tinkerers, and library organizers have reason to celebrate. But the larger narrative of Media Player's performance woes remains unchanged. The Windows community will be watching closely to see if future builds can finally exorcise the demons of slow launches and memory bloat. Until then, the search for a truly snappy first-party media player continues.