The End of Windows 10: a toolkit for community repair groups
4 comments
·July 14, 2025ivraatiems
garbagepatch
What is unsupported hardware in this context? Machines without TPM 2.0?
userbinator
It's already been a decade(!), yet I still remember the introduction of this amazingly spyware-filled OS like it was yesterday, and the large public backlash it caused. Unfortunately its successor is even worse, which may be why it still has a fanbase today.
Meanwhile, I know there are plenty who are still using Win7 and below, and there's even a nontrivial community writing drivers for newer hardware and such.
concinds
Frankly, “we’ll switch up everything you’re familiar with, but you see, you really should, because security” just feels like a terrible idea. I’m not defending Microsoft, this is a very premature abandonment. But your browser is still receiving updates. You don’t need to panic or scare people needlessly. They’ll be fine.
Switching your family members to Linux works because they’re your family members. You know how they use computers, their comfort level, their needs. They can call you for help. A repair cafe, helping people they’ll likely never see again? Installing Linux, or heck, things as complex as dual-booting (which they suggest)? You’re kidding! Just leave people alone with their fine, basically-secure computers.
I disagree with the framing of running Windows 11 on unsupported hardware as an undesirable option compared to desktop Linux, for several reasons. For context, I have several years' experience in the recycled and refurbished computer market and I regularly sell machines with Linux, ChromeOS Flex, Windows 11 on supported hardware, and Windows 11 on unsupported hardware.
The reality is that for the vast majority of people, even the simplest desktop Linux distributions are simply too high a learning curve to be useful outside the very basics. The problem is not that they're not usable when things are working right. The problem is that when things go wrong, problems rapidly begin to require levels of knowledge far outside what a layperson can reasonably acquire. A missing driver, updates that need to be installed, configuration problems - these all run rampant on Linux to degrees far beyond what one experiences with a machine designed for Windows. ChromeOS Flex is a partial solution, as many people are familiar with it, but it is useless on a lot of hardware due to lack of drivers and is not a good fit for more powerful machines.
On the other hand, if you install Windows 11 on a machine that doesn't support it, you get all security updates for the next year, and all the drivers you need are typically present in Windows Update. In situations where there is a need for legacy drivers, they usually work after a simple install. I have installed Windows 11 on systems from 2011 and 2012 and had it work flawlessly, and fast enough for basic use. Windows 11 itself isn't perfect, but moving from 10 to 11 is nowhere near the complexity of moving from 10 to Linux.
Of course, the big issue is that after that year of security updates, one has to manually download the next "feature update" and install it to get another year of updates. This isn't hard to do per se, but it's approaching the kind of complexity that the average person isn't going to navigate smoothly. I don't have a great solution for this yet, though I am thinking about one. For now, I just include disclaimers and documentation about what to do to make things easier. Even so, compared to something like a Linux major version upgrade, this is quite straightforward.
There is no legal or ethical reason not to just run Windows 11 on technically unsupported hardware to keep it alive. I think that's the best way to go.