Removing HEVC support wasn't their choice but probably stems from the licensing pools increasing their prices [1].
Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today.
As for the RAM increase, well that's probably a consequence of the general trend of doing frontend engineering via JS/TS instead of using OS native frontend APIs. The advantages are more on the development side of those apps, i.e. you can hire JS UI devs way more easily, and probably LLMs know way better how to deal with a react app than an UML one.
If Google and Apple also decided to remove support for common video formats instead of just paying the slightly higher licensing fee, I might have some sympathy.
Microsoft thinks they have all the money in the world when it comes to wasting huge sums on mergers and acquisitions that go nowhere. Spend some on maintaining the user experience.
Also, with Dell and others releasing new Windows laptops with 8 Gigs of RAM, needless memory bloat is unacceptable.
I believe, at this point they could direct AI to vibe rewrite every UI code written after 2010 in Win32 and MFC and the result would still be vastly better than crap they push us nowadays.
>As for the RAM increase, well that's probably a consequence of the general trend of doing frontend engineering via JS/TS instead of using OS native frontend APIs
Can someone explain to me why these multi operating system app building tools don’t compile down to native code and leverage native APIs? Is there nothing like that available?
> As for the RAM increase, well that's probably a consequence of the general trend of doing frontend engineering via JS/TS instead of using OS native frontend APIs.
How do we live in a world where simultaneously "human coding is dead" and also "we need to trade performance for developer efficiency"? I thought code is free now?
Also--this is Microsoft! It's their OS!
Microsoft should just come out and say that the whole of Win32 is deprecated and kept around for legacy compatibility only, and all new software should be written in Electron. They're already acting that way, why not make it official?
I don't think I've ever voluntarily used their shitty media player since the classic version. MPC-BE (some folks use MPC-HC) is my goto with VLC as a backup if certain codecs don't play nice with it. I'm able to use nVidia super resolution with them as well.
I kinda have to hand it to Microsoft for dogfooding vibecoding with Copilot to such an extent. You can't say they encourage their customers to use a bad solution while doing something different in-house.
This app is a reskinned Groove Music, it was mostly written back in the early Windows 10 days (2014-2017) and long predates Copilot/etc. Even the Windows 11 rebrand as Media Player (2022?) predates that stuff, and it's barely been touched since then.
> The modern Media Player is said to use around 377MB of RAM when idle, compared to roughly 103MB for the old player—about 3.5x as much memory while doing absolutely nothing.
As a part of the user-mode half of the GPU driver, GPU vendors ship media foundation transform DLLs to use HEVC hardware codecs. Don’t AMD, Intel and nVidia already pay patent royalties? I expect them to include into price of the GPUs with hardware support i.e. all of them made in the last decade.
I think what I find fascinating about this is it's a native app with no web version... and they still decided to write it in html/js. This is after Microsoft's commitment to rebuild things in WinUI.
Don't get me wrong, I totally understand the barrier of friction that native presents compared to html/js, but that barrier has lowered so much with the advent of agentic development. It just feels like things weren't thought out.
I rarely use widows, but i feel like windows media player is only there to check a box that windows has a media player. Most people dont play local videos anyway, and those who do use something else like VLC.
Kind of a pity that we used up the phrase "a fractal of bad design" on php, it's so applicable to much of the stuff coming out of MS. I've been using PowerBi for a few weeks now and I'm sometimes impressed by the novel ways it finds to suck.
This article is likely AI slop, none of this is "news" and I'm pretty sure that this is just factually Not Accurate. Windows 11 is not shipping a new media player, it has the same one as it has since Win10. Codecs have like HEVC/H.265 always cost a very small amount of money, in order to pay patent owners. Again, it has done this for years now.
45 comments
[ 2.7 ms ] story [ 50.9 ms ] thread0. https://mpv.io
https://iina.io
EDIT: Also, what do they mean by "new" Media Player? It shipped in 2022 [1]. This article is garbage. The source article [2] is fine.
[0]: https://www.windowscentral.com/microsoft-now-charging-hevc-v...
[1]: https://en.wikipedia.org/wiki/Windows_Media_Player_(2022)
[2]: https://www.windowslatest.com/2026/06/16/microsoft-reveals-w...
https://www.majorgeeks.com/files/details/dolby_ac_3ac_4_inst...
and then you recieve the latest update from windows store.
Windows media player probably sees very little usage nowadays and probably even less for HEVC, when most content playback happens via streaming and browsers today.
As for the RAM increase, well that's probably a consequence of the general trend of doing frontend engineering via JS/TS instead of using OS native frontend APIs. The advantages are more on the development side of those apps, i.e. you can hire JS UI devs way more easily, and probably LLMs know way better how to deal with a react app than an UML one.
[1]: https://arstechnica.com/gadgets/2026/04/lawsuits-licensing-a...
Microsoft thinks they have all the money in the world when it comes to wasting huge sums on mergers and acquisitions that go nowhere. Spend some on maintaining the user experience.
Also, with Dell and others releasing new Windows laptops with 8 Gigs of RAM, needless memory bloat is unacceptable.
Can someone explain to me why these multi operating system app building tools don’t compile down to native code and leverage native APIs? Is there nothing like that available?
ms-windows-store://pdp?productId=9N4WGH0Z6VHQ
It's a wide know workaround, been there for years, obviously Microsoft pretends they don't know about it.
https://www.howtogeek.com/680690/how-to-install-free-hevc-co...
Is this just for a purely software implementation of it?
Xbox Music in Windows 8.x was actually web tech based, but was rewritten into C# and XAML when it was turned into Groove Music in Windows 10
How do we live in a world where simultaneously "human coding is dead" and also "we need to trade performance for developer efficiency"? I thought code is free now?
Also--this is Microsoft! It's their OS!
Microsoft should just come out and say that the whole of Win32 is deprecated and kept around for legacy compatibility only, and all new software should be written in Electron. They're already acting that way, why not make it official?
/clutches pearls
Won't somebody think of the trillion-dollar companies!
Dropping AC3 does seem unnecessary.
Mostly because everything is H.264, H.265, VP9, AV1, MP3 or AAC.
I understand that project might have started way before the public statement but it really doesn't look good from a PR standpoint.
Running MS Windows these days is like having a "kick me, hard" sign on your back. Or, you're treated like a money and data piñata.
even 103MB sound like a lot for doing nothing
As a part of the user-mode half of the GPU driver, GPU vendors ship media foundation transform DLLs to use HEVC hardware codecs. Don’t AMD, Intel and nVidia already pay patent royalties? I expect them to include into price of the GPUs with hardware support i.e. all of them made in the last decade.
Don't get me wrong, I totally understand the barrier of friction that native presents compared to html/js, but that barrier has lowered so much with the advent of agentic development. It just feels like things weren't thought out.
Last update seems to be from 2022 at mplayerhq.hu.
Used to be the go-to that played basically anything years ago.
Windows core apps used to be pure C++.
Cry long enough about "safe" languages and expect to take the RAM hit.