Microsoft’s modern replacement for the venerable Windows Media Player is gobbling up over three times the memory while doing absolutely nothing, according to fresh community measurements. On a clean Windows 11 installation, the new Media Player app chews through an average of 377 MB of RAM just sitting idle, whereas the legacy Windows Media Player sips a comparatively modest 103 MB. The revelation, surfacing in enthusiast circles on June 22, 2026, pulls back the curtain on a decade-long architectural tension that shows no sign of resolution. Users are now openly questioning whether the glossy interface, subtler animations, and cloud-connected features are worth the hidden system toll.
The chasm in idle memory use is only the most measurable symptom. Early adopters of the latest Insider builds report launch delays that fluctuate by as much as 400 milliseconds between the two apps, with the newer player consistently stumbling out of the gate. Factor in stubborn codec friction—specifically around HEVC video and AC‑3 audio—and you have a recipe for confusion among those who simply want to double‑click a file and watch it play. Microsoft’s decision to fork the player ecosystem has left power users and casual consumers alike navigating a maze of licensing pop‑ups, store download prompts, and silent playback failures.
How the memory numbers stack up
Testing conducted on a reference system running Windows 11 build 22631.2428 with 16 GB of RAM shows the modern Media Player consuming a baseline working set of 377 MB after a cold launch, with no media loaded. The legacy Windows Media Player, still accessible through the “Windows Tools” folder or the optional features menu, settles at about 103 MB under identical conditions. That 274 MB differential is larger than the entire footprint of some lightweight media players such as VLC or MPC‑BE when actually playing 1080p video. The modern app’s RAM appetite grows further when the mini‑player is pinned or when it begins scanning the local music library.
Technically, the ballooning memory stems from the underlying platform. The new Media Player is built on the Universal Windows Platform (UWP) and shares its rendering engine with the now‑deprecated Groove Music. It loads a full XAML UI stack, media pipeline, and several background services—including Windows‑index integration and cloud sync hooks for OneDrive—well before a single frame of video is decoded. Legacy Windows Media Player, by contrast, is a pure Win32 executable that relies on the slimmer DirectShow and Media Foundation frameworks, initializing only the components it needs at that moment.
Launch speed: milliseconds that add up to frustration
Community testers equipped with high‑speed cameras and USB‑based latency analyzers found that the modern Media Player takes, on average, 1.8 seconds to display its first frame after a double‑click on an .mp4 file, compared with 1.4 seconds for the legacy player. While a 400 ms delta may sound academic, it translates into a perceptible hitch when users are rapidly opening multiple files or jumping between folders. The delay is amplified on systems with traditional spinning hard drives, where the UWP app’s heavier disk I/O for configuration and metadata retrieval can push launch times past the three‑second mark.
Microsoft has improved cold‑start performance incrementally over successive Insider builds, yet the architectural overhead remains. The app pre‑fetches a host of UI elements and initializes audio endpoints even before it knows which codec will be required. Legacy Media Player, in contrast, uses a lazy‑loading model, deferring most setup until after the file header is parsed. That design allows it to begin playing a locally cached WMV file in under 800 ms on the same hardware, a snappiness the newer app cannot match.
The codec quagmire: HEVC, AC‑3, and the license labyrinth
No topic stirs more ire in Windows forums than codec support, and the split between the two players has turned a minor annoyance into a persistent friction. The modern Media Player leans heavily on the system’s Media Foundation codecs, while legacy Player can also tap into the older DirectShow framework and a wider assortment of third‑party filters. This divergence becomes painfully apparent the moment someone tries to play a video captured on a modern smartphone or a high‑end mirrorless camera.
HEVC (H.265) is the poster child. Windows 11 ships with a rudimentary HEVC decoder that is often insufficient for 10‑bit or HDR content. To unlock full acceleration, users must navigate to the Microsoft Store and purchase the official HEVC Video Extensions package—priced at $0.99 in the US—or track down the hidden free “HEVC Video Extensions from Device Manufacturer” listing, which doesn’t appear in search results directly. The modern Media Player respects only the system‑level Media Foundation decoders, so without that store package, HEVC files either throw an opaque error or play with only audio. The legacy player, through its DirectShow compatibility, can leverage community codec packs such as K‑Lite or LAV Filters, often sidestepping the paywall entirely.
AC‑3 (Dolby Digital) audio tells a similar story. Many MKV containers use AC‑3 tracks, and Windows 11 does not include a native Media Foundation AC‑3 decoder. The modern Media Player will fail to produce sound or may crash when encountering these streams. The legacy player, when combined with AC3Filter or similar DirectShow filters, handles them without a hiccup. Microsoft’s official response has been to guide users toward paid decoder packs like Dolby Access, creating the perception that a basic media playback feature is being nickel‑and‑dimed.
Insider builds: a moving target
Members of the Windows Insider program have watched the Media Player evolve rapidly since its debut, with each Dev and Beta channel build tweaking memory allocation, startup sequence, and codec negotiation. Build 25131, for example, introduced experimental fetching of online album art, which inadvertently spiked idle RAM to over 500 MB for users with large OneDrive music libraries. A subsequent patch in build 25140 reined it back to the 377 MB figure observed in current testing.
The Insider builds also serve as a testing ground for a new codec‑negotiation layer that attempts to bridge the gap between Media Foundation and the legacy DirectShow infrastructure. In early briefings, Microsoft engineers hinted at a universal adapter that would allow the modern player to fall back to DirectShow filters when a Media Foundation decoder is unavailable. Some builds briefly included a “media.legacydecoderfallback” flag in the registry, but the feature proved unstable and was removed before reaching the Release Preview channel. Insiders report that when the flag worked, it cut HEVC‑ and AC‑3‑related playback failures by nearly 90 percent, but also introduced random crashes in applications like Photos and Clipchamp.
Real‑world impact: what users actually experience
For the average consumer who sticks to streaming services and occasional MP4 files, the new Media Player’s memory and speed penalties are largely invisible. The machine has enough RAM to absorb the 377 MB hit, and the prettier interface feels modern. Trouble begins when users push into anything beyond the default codec comfort zone, or when they find themselves on a budget device with 4 GB or 8 GB of memory.
On a $400 laptop with 4 GB of RAM, the new Media Player alone can occupy nearly 10 percent of total system memory at idle. If the user also has Microsoft Edge open with a handful of tabs, the system quickly tips into swapping territory, making multitasking sluggish. The legacy player’s 103 MB footprint is much friendlier to such devices. In corporate environments where IT departments lock down the Microsoft Store, the inability to add HEVC or AC‑3 extensions means the modern player is effectively broken for any video captured on recent iPhones or on conference‑room recording equipment.
Community workarounds: downloading the good old days
Faced with these frictions, a growing number of Windows enthusiasts are simply opting out of the modern experience. A thread on a popular Windows forum with over 600 replies details methods to re‑enable Windows Media Player Legacy in Windows 11 build 22621 and newer. The most reliable approach involves opening Optional Features, adding the “Windows Media Player” component, and then manually pinning the wmplayer.exe shortcut to the taskbar. Others advocate for PowerShell scripts that import registry keys to set the legacy player as the default handler for all video and audio files.
There’s also a quiet resurgence of third‑party media players. VLC, MPC‑HC, and PotPlayer downloads spiked during the period when the HEVC installer controversy flared, and many of those users never went back. Unlike Microsoft’s modern offering, these players ship with built‑in codec libraries that require no store purchases and impose minimal idle memory overhead—VLC often idles under 50 MB.
Microsoft’s quiet balancing act
Why hasn’t Microsoft simply ported the legacy player’s efficiency into the modern app? The answer lies in strategic direction. The company has spent years trying to unify its media ecosystem around the UWP/WinUI model, which brings benefits like smooth scaling on high‑DPI displays, better touch and pen support, and tighter integration with the Windows security model. The legacy player’s reliance on DirectShow is also a security vector; the framework’s filter‑graph architecture allows third‑party codecs to run with minimal sandboxing, a risk Microsoft has been keen to eliminate.
Yet the compromise has left a gap. Windows 11 is now officially replacing the legacy Control Panel with Settings, but the Control Panel still exists because too many features are missing. Similarly, the modern Media Player has been available for over three years, but the legacy player continues to ship in the OS as an optional component. It’s an unspoken acknowledgment that the new app cannot fully replace what came before.
Forward outlook: convergence, or continued divergence?
Recent job postings from Microsoft’s Media Platform team hint at a renewed focus on codec acquisition. The listings mention work on “streamlined codec negotiation with user‑friendly resolution paths,” suggesting that the company is aware of the HEVC/AC‑3 embarrassment and is engineering a solution that doesn’t involve sending users to a hidden store link. A more radical possibility is the integration of a lightweight version of the open‑source FFmpeg library, which would instantly solve almost all codec compatibility issues. Nothing has been confirmed, but Insiders have spotted references to “ffmpeg‑host” in several debug symbols of recent builds.
On the memory front, the UWP framework itself is undergoing a diet. The May 2026 Windows SDK introduced APIs that allow media apps to suspend more aggressively, releasing memory back to the OS when the player is minimized or not actively rendering. Early results from SDK adopters show a 30–40 percent reduction in idle working sets. If the Media Player team adopts these APIs later this year, the idle footprint could drop into the 200–250 MB range—still double the legacy player, but at least competitive with streaming‑focused apps like Spotify or Apple Music.
For now, Windows users face a pragmatic choice. If they value a sleek, touch‑friendly interface and never stray from common file formats, the modern Media Player suffices. If they prefer raw speed, minimal resource consumption, and universal codec support, the legacy player—plus a community codec pack—remains the de facto champion. The tension is unlikely to disappear until Microsoft either unifies the two frameworks or concedes that one‑size‑fits‑all has never applied to media playback on the PC.