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...
Otherwise looks a bit deceptively like new findings just because the date at the top of the page says June 18, 2026 :\
I am not sure exactly what happened to it, it's maintainer moved on to other projects I imagine, it's current equivalent is probably mpv
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...
Ah yes, we don't want Microsoft to run out of JavaScript developers to keep improving their desktop operating system in this manner. More webdevs, that's what's going to fix what ails Windows!
Dropping AC3 does seem unnecessary.
I understand that project might have started way before the public statement but it really doesn't look good from a PR standpoint.
Using 400 MB of RAM vs 100 MB of RAM is close to unnoticeable in a world of a GB+ for a single Chrome tab... And if "easier for our developers" means the end user is getting more regular updates with fewer critical issues, then it's not an uncomplicated tradeoff at all, parts of it are actually synergistic.
I mean, I agree, but Microsoft of all companies really should be invested in building Windows native applications. If they can't be fucked to build Windows-native applications, why would anyone else?
Microsoft should be setting the example, and the high bar of what Windows-native quality software should be. It's frankly embarrassing for them that they can't or won't do it.
megamike•2h ago
functionmouse•2h ago
magicalhippo•1h ago
[1]: https://github.com/clsid2/mpc-hc/
applfanboysbgon•1h ago
Mindless2112•1h ago
AlienRobot•50m ago