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.
Perhaps the AI boom will encourage / subsidize(?) native development in a way? If it can be made more approachable, then maybe it would become more prevalent...
Very few users care about how much RAM their media player uses. The practical difference between 370MB and 100MB is basically nil for any normal workload. It affects nothing but how many unlikely-to-be-used files fit in the page cache.
A problem in isolation this is not, however. Large portions of Windows now have this same bloat in terms of executable filesize, runtime needed for basic functions, and RAM usage. Windows Media Player by itself might not be an issue, but it's part of a trend that now affects Explorer, Desktop Window Manager, and a bunch of other core components to the operating system.
Do you have telemetry about how often systems are overcommitted due to Windows Media Player memory usage? I'll bet Microsoft does.
Considering the way Microsoft's product line is these days, I have a hard time believing its terabytes of "telemetry" go anywhere but the Windows equivalent of /dev/null.
If all apps are developed with the same mindset, all of them would consume much more memory. Does the average user have a 3x buffer just in case? I doubt the median-ish 8GB is enough these days.
There's a special case argument to be made in favor of ignoring media player resource consumption, given the maximum number of ears and eyes per human.
I expect there's someone out there who tiles 10 instances of simultaneously playing audio/visual media, but that's not most of us.
Computers can execute multiple different programs at the same time, so users are able to run a media player while their main focus is on a different window, tile, monitor or whatever else.
Given that 8GB machines are still widely in use (and will get even more common over the next years), 250MB of extra RAM use is a pretty huge portion of user's available RAM pool, so this is quite a big change.
I normally don't have notepad.exe or the windows media player open, so it's irrelevant. Chrome, clangd, rustc, etc. are all that matter. Optimizing anything else fails the pareto principle. I definitely do not want Microsoft paying its engineers to optimize windows media player memory usage.
I don’t want a trillion dollar investment in ram reduction, but the fist 80% of optimisation will be trivially achieved. Microsoft have a conflict of interest given they also sell surface devices where pushing people to the more expensive models is beneficial, while also probably benefiting when other hardware manufacturers benefit too.
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.
Last year I paid money to upgrade my laptop's RAM from 16 to 32 GB. I didn't pay it so apps could just be more bloated without offering any significant benefit.
Developers should respect and be efficient using hardware resources. There are no excuses for that.
From CS101 it’s called virtual memory. Things get swapped in and out of memory when they need to. An extra 200MB of memory when Chrome takes gigabytes of memory is a petty thing to complain about.
How much do you want to bet you don’t even use windows media player? It’s fake outrage and if you care that much use VLC.
I really only enjoyed Windows Media Player for its visualizations. I found that VLC could get close, but not quite an exact match (most likely due to licensing); there's something quite entrancing about them, and how they'd move in time and change with the music.
It's come and gone, and I'm still not fully sure what Groove Music was; was it something to do with the Zune?
Chrome does it, so it must be good? Is a extra 200mb going to cause the computer to choke? probably not, but that doesn't mean people cant complain about the fact that a lot of modern software has gone this route and it all does add up.
VLC on my Mac uses about 130 MB of RAM (as reported by Activity Monitor) to play a FLAC file, and about 300 MB to play a high-bitrate 1080p MP4 file. The audio file memory consumption frankly seems high, but it’s fine, and apparently 1/3 that of WMP.
More directly, do you not find it odd and embarrassing for a tech giant to be unable to beat a bunch of volunteers? I mean, ffmpeg famously hand-writes a lot of assembly, but it turns out Microsoft could absolutely do that as well if they really wanted to. They could produce performant, native apps; they just choose not to.
> VLC on my Mac uses about 130 MB of RAM (as reported by Activity Monitor) to play a FLAC file, and about 300 MB to play a high-bitrate 1080p MP4 file. The audio file memory consumption frankly seems high, but it’s fine, and apparently 1/3 that of WMP.
Not without reason VLC is considered to be a memory hog.
There are 100s of processes running on my Windows without starting anything explicitly. They are using more than 10 gb of RAM. I am already feeling the consequences of this sloppiness. Especially that my IDE/compiler/emulator easily use 20+ GB. My 32 GB of memory is not enough somehow…
I just remember buying 16MB from a wholesaler operating out of a nondescript warehouse. I'm pretty sure they had a runner delivering your order from elsewhere in the building.
The PCB layout program wasn't cutting it with Win 3.1 and 8MB. The bloat has me always circling back to that.
Apple when faced with the issue of C++ obsolescence started working on Swift. Google developed go. In theory Microsoft has C# but can't seem to settle on GUI toolkit. So now they've decided to use webshitten for applications. I think it's possible that is going to sink Microsoft.
Because no matter what a lot of people say here: you still need to be lucky to have a fully functioning system on Linux without continuous roadblocks everywhere. And I’m saying this after using Linux for more than a quarter of a century, occasionally as my main OS. I switched from it back just a few months ago, after I gave up to figure out how to have more uptime on battery for half a year, how to make my monitors with widely different DPIs work properly (literally without crashing the whole system), how to simply play a video reliably, and these just after solving a bunch of different issues already. And my lifestyle really doesn’t allow that battery drain issue at all.
It’s funny, because I don’t expect more features from Windows than Windows XP, or let’s pretend that I need more security (I don’t, but I know a lot of folks need them), then Windows 7. But even those could have been reduced greatly. I remember that I could disable at least half of the services in XP without losing anything. Maybe the only features since back then which I use are proper DPI scaling, individual app sound level settings, and maybe the favorite folders in Explorer, but I’m not sure whether this later one didn’t exist back then.
If they would provide that (with security patches of course), then they wouldn’t need “quick startup” and other bullshits to make things “quicker”.
It does not matter how well or poorly Chrome mismanages memory, 400MB is still 400MB. If that 400MB is 10% of the free RAM after the share the OS takes, then that is a hefty toll. And the regular updates Windows 11 users are getting are famously not providing value, but taking value away. Case in point right here is the new media player.
Windows Server 2022 comes up just fine in 4-8GB RAM disposable qubes. I can easily load Adobe MCCS6 applications in that. I can run Mathematica in that. I can load Siemens NX 10-12 in that and do basic modeling!
A single Chrome tab does not use gigabytes. In fact, this app IS a Chrome tab! It's web based, so it's using Edge, which is just Chrome in a trenchcoat.
Maybe a sales tax scaling with code size, memory use, and processor time for commercial software - a scale based on a 'model' computer that costs 3% of the median American's income - would disincentivise the shift to web languages, which has been happening because investors want to squeeze developers down to burger flipper pay levels.
Software made in 2005-2015 is no less capable than that today, except the lack of cloud cancer and AI gimmickry. "Downgrading" to those is actually a real upgrade today!
That would actually be like taxing or regulating the code itself, which could be pretty straightforward in proportion to its size and resource wastage.
I just think taxes have proven to be highly nonideal unless they are levied against some added-value being realized, but you're giving me ideas.
You could perhaps partially tax based on value too, but it could start to get confusing and unfair again.
Either way, taxes would probably turn out to be more of a parasite in terms of how it can overwhelm the value added if levies rise far beyond relative insignificance. Regardless of what good might come of it on the surface looking at the code.
The code itself is already regulated anyway, I would rather see a minor adjustment to the regulation where only code in an open-standard low-level language can be copyrighted.
You wouldn't even need to add enough taxes for negative incentive if the higher-level stuff was set free, that would unleash incredible resources.
That might be one of the most effective ways to reverse the exponential increase in resource-hogging, with greatest urgency.
Couldn't do it overnight, probably have to roll it back against a timeline, one layer at a time. Simulate the reversal of the metastization as logically as can be done from this point.
There's just no way we should have ever needed more than 100mb of C: drive space as long as you wanted to run your office with no further features than Windows 95 with Office 97. To be generous another 100mb for multimedia and another 100 for internet, plus the OS and Microsoft apps are supposed to get more efficient from there since they were rushed to market in the '90's themselves.
Gigabytes were supposed to be for storage and media files, and there was never supposed to be any latency of any kind as soon as processors got up to 1GHz and you got off dial-up. Mice with balls were all that was necessary too, and that was with IDE HDDs.
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?
Microsoft has written more application development frameworks than you can shake a stick at. They've also failed to gain traction with virtually all of them, even internally.
As an operating system vendor, it should be a dismissable offence to refuse to use the OS standard APIs. Your products need to be the standard that other try to imitate.
> 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?
> The advantages are more on the development side of those apps, i.e. you can hire JS UI devs way more easily
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!
> The advantages are more on the development side of those apps
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.
HEVC is provided by the official, licensed h265 standard. The open source ~HEVC-compliant codec library is x265 created by VideoLAN but was apparently not an option for Microsoft.
It's not about the code. The open source implementations are also subject to patent laws, they just ignore them and put the responsibility on the user. And users don't know/care about it so in the end they get playback for free.
That is why some distributions (RHEL derivatives, for example) do not ship support for many codecs out of the box and they make you jump to (admittedly simple) hoops to get it working.
x265 is an encoder, not a decoder. Also, being open source doesn't matter here: an open source library, even with a patent grant, doesn't give you a license to someone else's patents.
Windows 11 is not free software. Apple macOS, iOS, ipadOS all support HEVC and Dolby because Apple pays licensing costs, likewise Microsoft should do the same for Windows users, it is not free OS.
It’s been a few years since I tried but I think the codec support was pretty bad last time I checked. Sure it can play MOV files, but every time I tried to throw some pirated video at it it would choke.
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.
it's a reasonable-sounding inference (if your only context is that there's a "new" Media Player and it's taking more memory) that doesn't apply in this particular case.
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.
1. It does not use HTML/JS. It is a fully "native" app (at least if C# counts as native) written with C# and UWP/WinUI2 XAML. Actually, Xbox Music in Windows 8.x had a web tech based UI; when it was rebranded as Groove Music in Windows 10, its UI layer was rewritten. Xbox Music itself in turn was a reskin/rewrite of the UI layer of Zune (which was C++) so it's already been through full cycle of native->web->native. (The "new" Media Player still identifies as "ZuneMusic" in packaging metadata!)
2. it's not "after"; Groove Music was largely written in 2014-2017 in the early Windows 10 days, and even its rebrand as Media Player in Windows 11 happened in 2022, and it's barely been touched since then.
There isn't even really a barrier. It's not actually hard to do UIs in WinForms, nor WPF, and I assume not in WinUI either. The problem is that a lot of people are just too lazy to even try to step out of the HTML/JS comfort zone, not that it's hard to do.
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 loved the K-Lite Codec Pack and CCCP (Combined Community Codec Pack) back in the XP days, especially while exploring MKVs and anime, but I virtually never run into a media file that VLC or MPC-HC can't play by default these days. Just drop it in and it plays.
If I understand correctly, most of what K-Lite / CCCP did was wrapping libavcodec/libavformat for the Windows APIs, so native players could use them. VLC just ships with libavcodec included, so it supports all these formats. Not sure about MPC-HC nowadays (it used to use Windows APIs, but you’d usually get it with your codec pack installer anyway).
K-lite originally was a giant mess of stuff that gradually got pruned down as the libav-based things got better and covered more of what was needed. These days it's just mpc-hc plus lavfilters and a few incidental tools.
I still use K-Lite since they ship MPC-HC (a fork of Media Player Classic) that comes with really good HDR support and default configuration out of the box. If you don't like to have the desktop in HDR you can even configure it to automatically toggle on/off HDR whenever an HDR movies is played.
The HDR support in VLC has been really lackluster. Maybe it is better nowadays, I don't know.
> 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.
Idk, it is a media player. I’m not mad about it keeping a ton of cover images and audio stubs in memory for immediate playback. Plus probably metadata of the entire library, with various indices. Makes sense to me.
We might expect newer players to cache less because SSDs are fast, but perhaps this is offset by the increasing use of network storage, whether it’s internet-based or a local HDD NAS.
Windows media player always sort of sucked. I remember when I discovered mplayer. What a breath of fresh air by comparison. ostensibly worse, with it's barely there user interface. But... all it did was play video, it would play anything, no more faffing about with installing codecs or different programs for different formats. No annoying ui that tried too hard to look like a piece of hi-fi gear.
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
The article mentions W11 24H2 but that might have been the only update the article had if it was first published much earlier. Might have even been an advance warning about AC-3 even before 24H2 was released.
Otherwise looks a bit deceptively like new findings just because the date at the top of the page says June 18, 2026 :\
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.
WinUI, WinAppSDK are built on top of WinRT, which is C++ for the most part.
That is the whole joke about it, Windows division tried to kill .NET with their updated COM based on Vista victory over Longhorn, and the whole AddRef/Release makes it slower than WPF applications.
It's nice to see that someone revived MPC-HC (again). For a while MPC-BE[1] was the alternative. I don't know how they compare today, but the latter is still great.
Ugh... for the life of me I still can't understand why you can't click to play pause in VLC. Probably once upon a time it was about dvd, but the number of played dvds compared to pirated mk4 is probably one to a billion.
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 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.
feel like windows media player is only there to check a box that windows has a media player
This is probably not far from the truth. Although, I think it's still an important box to check, even if only 2.5 boomers are going to use an out-of-the-box media player.
The Media Player the article about is a fully "native" app though (at least if you count C# as native). The Windows8.x version (Xbox Music) was web tech based; it in turn was a reskin/UI-layer-rewrite of Zune (which was C++), so they've already gone through a whole cycle of native->web->native with this. (The "new" Media Player still identifies as "ZuneMusic" in packaging metadata!)
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.
The rebrand of Groove Music to Media Player was a Windows 11 thing, so it sort of did ship a "new" media player. It also still ships the old one though (as "Windows Media Player Legacy")
I wonder how the memory footprint would compare between vanilla Windows 11 (latest) and Windows 11 with all user apps substituted for memory efficient native apps. I know there are several third party “de-bloat” flavours but I believe they focus more on disabling redundant services.
Qubes OS is nice for that. Set up a plain vanilla Windows TemplateVM (Windows Firewall whitelisting in/outbound connections), clone the vanilla template for each subset of applications, then make a bunch of AppVMs which point to those cloned templates.
Can't wait for said professional software to eventually decide that Electron's the way to go as well, and make shittier new versions, but cross-platform.
(I don't know if this can be sarcasm anymore.)
What is Windows's moat among the business crowd? Is it the "can't get fired if they buy Windows" mantra?
Being Electron doesn't mean that the developer will release builds for all platforms that Electron supports. Discord took 3 years, for example.
> What is Windows's moat among the business crowd?
The moat is that it just works[1] will all of their software developed over the past 30 years, and support contracts/staff[2] is incredibly easy to obtain.
1. Contrarians will say that wine has better backwards compatibility than windows, but that's just cope and limited to a handful of games (and even then it's only because people made elaborate compatibility profiles for those specific games, those won't exist for internal apps).
2. Linux sysadmins are easy to obtain, but dedicated staff to support a desktop linux fleet is still fairly niche. There is some overlap in skillset and sysadmins can learn, of course.
The "power user" group which was traditionally completely Windows users is seeing some shifts to Linux. Linus Tech Tips' recent Linux switch tests went really well for Linux:
I think Media Player is there just to have a built in option. Can’t say I’ve ever seen anyone use it, even non-techies install some other player in my experience.
The lack of codecs takes us back 20 years when everyone was installing codec packs. Both the Dolby and HEVC extensions now come from alternative codec packs. Not a real problem but does signal a degradation of the experience to the level that was usually considered the “downside” for Linux.
Always a good idea to run alternatives to every software that might pull the rug from under you. Always be ready to switch when the experience starts to stink.
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...
reply