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.
[1]: https://arstechnica.com/gadgets/2026/04/lawsuits-licensing-a...
'It's worse for our users, but easier for our developers' is an unacceptable tradeoff, they deserve the backlash.
I mean... Yes, but there's nuance here.
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.
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…
IME, there is a negative correlation “justifies increased memory consumption by citing DX” and “ships code with fewer critical issues.”
How come I have never seen this tradeoff work in practice?
You see it all the time in Slack, Discord and so on.
Isn’t VS Code an Electron app? Or just its predecessor?
There is no nuance in 400%...
Of course there is. If it increased from 1MB to 4MB, that would definitely be insignificant
> 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.
> 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!
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.
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.
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.
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.
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.
Do people still use the K-Lite Codec Pack so their players have all the codecs installed? Or just use vlc?
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).
Is vlc still popular and widely used or is there a new 'kid' in town?
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.
mpv is really good but a little light on the GUI; I recommend VLC for most people
SMPplayer is a frontend for mpv which I use and like.
It also has MPC GUI mode for nostalgia :)
On macOS, IINA is my go-to mpv wrapper nowadays, and last time I tried, Haruna is pretty good on KDE.
For media using common codecs, you could just drop it into Firefox.
MPC is better if you're on Windows.
PotPlayer is the new kid, I guess? Personally I don't like VLC because of the UI, so I've always used MPC.
For everything except sabotage-ware rootkit based games, Linux is the better solution for basically everything.
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.
There is a lot of professional software that locks people in also.
So it started sucking almost a decade ago, checks out in my experience
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 :\
HEVC used to be a capped license per organization, so not providing it in the OS seems really harmful and expensive. Has the cap changed recently?
HEVC has been a paid add-on for as long as windows 10 has been around, iirc.
Dropping AC3 does seem unnecessary.
Didn't they just publicly make an apology for enshitting Windows over the last years, and committed to go back to building native app?
I understand that project might have started way before the public statement but it really doesn't look good from a PR standpoint.
M$ knows the laws will change in their favor requiring a gov ID to boot a computer. This is how they will get away with crap like this.