A few days ago, I had to scan and also print a few document pages. For no apparent reason, I couldn't print from Win 11. The print job seemed to be never arriving at the printer. Neither LAN nor USB cable did the trick. USB has always worked before.
I hate the ASUS' Armoury Crate.
That could probably never happen because of the driver situation. Too many drivers out there that were only tested with whatever the latest build of Windows was at the time they were written. Even in the Win10 days there were already drivers marked as "Compatible with anything back to 2015 LTSB" but really "Compatible with whatever version has all the APIs I used, good luck bro".
Worst case scenario is that there is a gap where devices made from 2024-2028 are poorly supported while everything before or after works fine, but really if Microsoft is forced to admit that Windows 11 is a disaster and they will be rolling back to 10 then device makers will have to support it.
I honestly hate that you need their proprietary apps to update the bios, or in the case of asus, to fix their faulty firmware they coded it specifically that way so you have to install their bullshit apps.
I'll respond to myself, because when I wrote that post I completely forgot the part about asus laptops with hdr displays that come with display edids that purposefully don't advertise the hdr capability to the OS unless you install the asus software, basically if you don't want to install their software or use linux, no hdr for you.
P/E-core support is Win 11 only. That's illustrative of the problem, not the only problem. Win 10 was built for architectures of the mid-2010s. It was as forward-looking as they could make it, but still, so much changed that they ended up having to rip-and-replace big pieces of it, particularly on the security sphere (which, I know, half of you think is a conspiracy to stop you from using Linux Mint).
There will be no rollbacks, they will stick with 11 and
It could easily take that long to fix it. One of the problems with AI coding is large amounts of unreadable, unknowable code gets slopped into your code base, and AI-driven fixing may just rip-and-replace enormous amounts of code in one go and still not fix it.
Has anyone thought to tell the AI to not fuck up and when it does, hit it? It worked when my dad did that to me as a kid. You can Venmo me my consulting fee, Micro$oft.
it's spaghetti code on spaghetti code, right when Windows 10 was making progress in removing the old spaghetti code with will written stuff. I expect Microsoft to have two choices: either they abandon everything and start from scratch or fork an open source project, or they roll back to the last good version of Windows and update it. I give it 50/50 odds and a potential future is that they fix the NT kernel and fork KDE Plasma or Cinnamon.
How can you be sure about the first scenario when chances are that they would shove thier AI-powered Jeet code right into that codebase just to hack together some of the good Windows 11 changes into 10, given how proud they are about AI vibecoding the current Windows codebase as is?
They will likely try that first, until they are forced to accept that they simpley cannot vibecode an OS.
Literally all they need to do is give the absolute core and let everyone else do the hard work, then fork or buy the most successful projects
