Keeping Windows and macOS alive past their sell-by date You can switch to running mostly FOSS without switching to Linux. First, though, give your OS a bit of TLC. We'll come back to what to do next in part two. Most computers run the OS they came installed with until they're scrapped… because most non-specialists would prefer to just buy a whole new computer than deal with trying …
MacOS Tiger on Powerbook G4 12" :(
Was still ok until TenFourFox ceased development. OpenBSD installs and runs but the X11 stuff is pretty rough. :)
The original system 2½" IDE drive must be wearing a bit thin by now — I looked at replacing the drive about 15 years ago — the instructions for doing so make the steps required to move the Shuttle from the Smithsonian to Texas seem child's play.
I have two 2012 MBPs and they work better than when they were new. I had to repair a niece's slightly newer MBP and it was very easy to replace a bad SSD and install from scratch. Eventually I would need to replace the trusty MBPs - not really looking forward to that!
You do realise that your information can be misconstrued as aiding and abetting knowledgeable and effective computer use by educating the unknowing and preventing extended corporate cash flow? How long before you will get a cease and desist letter for preventing corporations from making necessary money by telling their customersvictims they don't need to buy into the shiny promises?
Oh, and, if you try this with your mobile, you will be caught and dealt with swiftly according to the new rules, making any non-sanctioned use a criminal offence.
I might guess that large corporations are already lobbying for even harsher laws.
One might also consider simply disabling the internet access to your elderly PC either via a firewall or by simply unplugging the network cable(s). Web access? Buy a used Chromebook. They're cheap and while far from perfect, the OS isn't awful. It's adequate for email, cat videos, and web surfing. Spending enough for a touch screen is strongly recommended as it is difficult and sometimes impossible to scroll some websites using just the (rather limited) keyboard and the touchpad. The drawbacks? Anything your PC needs networking for may have to be sneakernetted to/from the chromebook. And Google will no doubt spy on every action you take on the chromebook unless and until the world's governments get together and put an end to that nonsense.
I wasn't one of them, but maybe it was the fact that the proposed solution to an old but likely serviceable computer was to spend money on a newer computer they don't need, segment all their stuff into two different machines when they could avoid doing so, and the one part that was accurate was the long list at the end of reasons why this would be harmful. There can be more reasons to oppose something than alleging that it simply wouldn't work. Something that works but is negative on most or all the elements it's supposed to help with isn't a very good proposal.
Their old computer can likely run a browser for free, no Chromebook required. The things they want to do outside the browser will determine whether the best approach is to stick with the original operating system but harden it or replace it with something likely Linux-based, but neither would involve an extra expense. If they are going to spend money, depending on how much they want to do, they could likely get a better newer computer to run everything on rather than getting something cheap which will only last a little bit longer.
This doesn't work on machines running Windows 10 Home though, does it?
I've just had to reinstall Win 10 after an unexpected catastrophic HDD failure, where Win 10 Home couldn't be resurrected, hut thankfully Id already enrolled the machine in the extended updates for the next year.
Biggest problem I had was the truck load of updates for Office 2010.
What will I do next year? Nothing, unless the hardware fails. I'll keep Win 10 while third party browsers, firewalls and antivirus still support Windows 10.
I believe Enterprise LTSC is a separate license key to even Windows 10 Enterprise Non-LTSC.
In theory this would be possible to install on an machine already running Win 10 Home by doing a clean installer and forcing it to use Enterprise LTSC version. However, you would need to ensure you had the correct license key/agreement to use it.
Thanks, Liam, for the original article back in April 2025. I only have one Windows PC left (the rest are all running Linux now), but I still have a few programs (NOT apps!!!) that still require the Windows behemoth, hence the one rescued via your LTSC article (and the massgrave site).
Drivesnapshot works. I am using it for > decade now. But test restore: Boot from Windows 7/10/11/S2019/S2022/S2025 DVD/USB, start in "wanna fix PC, give me CMD" mode have the .exe and your backup ready, restore-test. I have the WindowsRE-version or Minitool Partition Wizard at hand too for the cases gparted fails. And I combined that on a 256 GB USB "Stick", with 2 GB as FAT32 UEFI-WinRE-Boot + rest as NTFS (encrypted if you want). Which is actually one of my older Samsung 8XX Pro SSDs in an USB case.
You "just" need to make that backup.
The full driver library it pulls down is ~40GB but definitely worth keeping on a spare USB stick.
It has support for some rather obscure bits, too - even managing to find Intel HD 2000 graphics drivers for Windows XP 64-bit.
I also found it could grab W7 compatible chipset and graphics drivers for a thin client running some obscure AMD embedded APU.
Even more useful when the OEM has removed the drivers from their website (thanks HP....)
I quit buying any new or used HP computers the moment they pulled the dick move of blocking access to their SoftPaq download site to everyone who does not have a current computer support agreement with them.
SoftPaqs include firmware for hard drive controller boards, BIOS updates, and such.
They probably have renamed SoftPaqs (name c.f. "Compaq") to something else by now, and may have removed those "obsolete" Compaq files.
"Most Macs will never run anything but their original copy of macOS."
This seems wrong, as there is a new macOS release every year and has been since 2011.
And most new Macs will get a minimum of 4 or 5 years worth of updates, meaning they'll be several copies in before dropping support.
Unless it was meant to imply that a "fresh/clean" install will never be done?
As with all corporate beasts, they tend to change things that are part of peoples' workflows just enough to claim they have 'added value' by the new system, but instead the changes inadvertently break things, slow things down, or just generally annoy foks who were used to the old esthetic. In my house, with five souls using all manner of devices and OS's, only 3 devices have the latest Apple OS on them. Some are too old, one isn't connected to anything and is only used to read books, and a number have had Linux put on them, because it's just easier than dealing with planned obsolescence.
Because new <> better, at least not always. See Windows 10 vs Windows 11, but also the latest OS from Apple (Tahoe) did IMHO add very little value other than leaning harder on the hardware to do exactly the same thing the previous version did. To me (in my opinion as a medium term user of MacOS), Tahoe has added so little that I felt the whole design 'spiel' was just to camouflage a lack of true innovation other than adding AI-alike things everywhere.
I don't care how may times he uses the word 'excited' in his talks (an emotion that never quite makes it to his facial expression and eyes), Tahoe proved once again that Tim Cook is a bookkeeper, not an innovator.
Apple has switched to a company that merely keeps the lights on. Yes, they're far enough ahead in tech that they can do this for a while, but that is not what got Apple to this position in the industry in the first place. It's a shame, but it appears that beyond a certain threshold revenue the need to actually innovate wears off and everything is but controlled by the numbers alone (which is weird because exactly that position should liberate enough funding to get creative again, but hey, I'm not in finance so I probably have this all wrong).
At least they're not switching to amping up the data theft from users as Microsoft appears to be doing, but that's no guaranteed for the future either. For the moment, protecting users is what makes Apple's gear sell, but given the 'innovations' so far I cannot rule out a change of heart if that data theft model proves to be more profitable. Numbers rule, not emotion.
I'm not sure what all the whining about Tahoe is about.
It's fine. Sure, you have to tweak a few things (System Settings > Accessibility > Display > turn on Reduce transparency, Show window title icons, Show toolbar button shapes are the big ones) then Appearance > Show scroll bars Always, Desktop & Dock > Click wallpaper to show desktop Only in Stage Manager, turn off all the stupid window tiling crap, then Trackpad and turn on Tap to click, turn off the idiotic "natural" (backwards) scrolling, and of course under Displays turn on Show all resolutions and select one resolution down to get rid of the idiotic notch on newer MacBooks.
But once you've gotten rid of the stupidity (most of which is actually older than Tahoe, the backwards scrolling goes way back) it's fine.
> Why would anybody refuse to upgrade to the latest supported macOS version?
Well, as an example, I kept Mojave as long as was feasible because nothing newer would run my very elderly version of Microsoft Word.
Apple tends to remove old features with about 50% of its new OS releases. This prevents the OS getting too bloated but sometimes it removes things people are still using.
Like, say, 32-bit app support, or a filesystem Linux can read and write, or certain networking abilities... What depends on the individual user.
My brother, for one. His iPhone automagically updated* and he's lost, so he is slamming on the brakes with 26.2. I'm in no hurry either, but, it's a mac, I'll find my way when I do upgrade.
I have automagic updates turned off! No reason to have them on IMHO, I like macs, but know better to wait for the releases to mature, let others cut themselves on the bleeding edge. I did AppleSeed testing15 years ago...
«However, if you are willing to change versions, we suggest switching to Windows 10 LTSC. As we explained back in August, the Windows 10 Enterprise LTSC 2021 edition will get updates until 2027, and if you don't mind using US English, it'll last until 2032.»
There are so many errors with this statement:
1.) Yes, LTSC 2021 will be supported until Jan 2027, but, contrary to what the article says, IoT 2021 is the one that will be supported until 2032, or, giving it its full name: Windows 10 Enterprise LTSC IoT 2021. Notmal LTSC and IoT LTSC are two very different beasts. Easy mistake to make for many, less excusable for an ElReg writer. (and LTSC 2019 will be suppoted until Jan 2029)
2.) LTSC and IoT Versions of Windows can not be had by normies, as the EULA forbids it. While readers at sites like El Reg may not care, those readers inform their friends who are lawyers/CPAs/MDs/SMB Owners. In these areas there are certifications/auditing/(cyber)Insurance requirements that are incompatible with violating EULAs. You can get blue in the face arguing that EULAs are not court enforceable, you may even win the case in actual court, but if all (cyber)Insurance companies, the PCI certification requirements and the GDPR say that you need to store customer data in up to date systems that comply with their respective EULAs, well, you better comply with the EULA.
3.) And speaking of Certification/Auditing/(cyber)Insurance requirements, Running Win11 on unsupported machines also does not cut mustard in those scenarios, as is an unsupported configuration. Also, the burden/onus of yearly seaching on the internet what is the "Method-du-jour" for applying the 2xH2 megapatch is on the user
4.) A better advice in those cases (and for the general population too) to keep an old machine running longer is to get Server 2019 with Desktop Experience (supported untl Jan 2030) or Server 2022 with Desktop Experience (supported untl Jan 2033). Fully legal to own, fully compliant with PCI, HIIPA, GDPR and such...
Hope this helps inform y'all, and that you inform your friends.
And this advice is for people who can't (or do not want to) switch to Linux or BSD
If creating a bootable USB installer seems daunting, there is also an alternative approach to download the latest compatible version of OS X/macOS for your system:
Reboot your Mac.
Immediately hold down the Option (⌥), Command (⌘), and R keys simultaneously.
This will initiate a recovery process that downloads and installs the latest compatible version of macOS for your system.
This method is most suitable for Intel-based Macs. It also works on Apple Silicon, albeit a little differently.
You'll need sufficient bandwidth and time for the download.
For more details: https://support.apple.com/en-us/102655
What definition are you using for "clean install", because most of us appear to be using the one that means that the thing you installed four years ago and forgot about gets wiped out. That can help when people have had a machine for twelve years and have a stack of third-party drivers, software that starts at login, license checkers, and settings they probably should update but don't know about. The more you're careful about what you install and change, the less benefit you get from that, but this article is clearly directed at those with less technical skill which, in my experience, often have a few things they forgot about which aren't helping their system's speed or stability.
Snappy Driver and Ventoy were unknown to me, never needed them, but good to know and have those tools at hand.
As for my usual 10th-bazillion times repeated hint: Server 2022 and 2025, keys which activate are cheap, or use your favourite graveyard tool. Does not need a hacked-installer to not-annoy you. And has some nice features. like dedup, or setting a quota in a directory, or limit the file type / sizes, disconnected RDP sessions don't stop like on workstation Windows, they just work on, SMB Bandwidth control (nice for LAN parties, 'cause your game play is more important than those copy jobs). Well, and that's it, the rest of the server features/capabilities/roles are too esoteric for a workstaton install, or are already the same on normal Windows, except mins the crap you get on normal Windows.
If you want to install something from the store (manually, without account, like the Windows-Camera) or need bluetooth audio (read, never tested self on S2022) you are better off with Server 2025.
And you get updates long enough.
How old are we talking here with "very old"? If it's anything like standard W11 I assume Server 2025 requires UEFI and won't work with a traditional BIOS. Given that UEFI has been in use since 2011 or so we're talking some rather elderly machines here.
From a performance standpoint some lower end computers from that era are going to struggle with anything as heavy as a newer Windows OS regardless of how stripped back they are.
Just tested: Server 2025 in a "Gen1 VM", which is no UEFI, no secure boot, "IDE Intel 82371 controller" etc. But well, it is Hyper-V Gen1, you can try with other hypervisors or PC-emulators and see how far you can get. I have no non-UEFI capable real hardware (nearby, I definetly won't resurrect some of the boxes in my basement for that test).
Core2Duo has a problem: It does not support newer CPU instruction requires since Windows 11 wants SSE4.2 and POPCNT as abdolute minimum (for now, they may require other minimum things as well with a future build). Be aware: Some linux districutions don't work there too for the same reason. Server 2022 MIGHT work, since Windows 11 21h2 did not yet enforce SSE4.2, but you have to test (you may fail for the drivers though). Server 2019 WILL work.
You will need at least NEHALEM for Server 2025, i.e. the very first i3 i5 and i7 CPUs.
For desktops I usually try and find the best processor for that generation of slot/socket and upgrade it as well (if they are cheap, some are not for some reason) once it gets old enough. That is part of the reason I've started moving to AMD on decent boards for my new builds; they make chips that fit for ages.
Its a good idea to replace your thermal paste regardless on older machines as it tends to dry out over time.
"If the machine has a spinning hard disk drive, get an SSD, and put the old disk into an external USB caddy as a backup drive."
I'd suggest that even if it's an SSD you do this. If the machine's that old a bigger SSD will cost less than the old one did and who doesn't need more storage? Also you start without whatever where the old one had accumulated.
> wear!
Aha! I _was_ wondering.
The only thing is this:
I tend to only use my external drives occasionally. Not often. Maybe not even every year.
SSDs stored without power for long time periods have a tendency to lose their data. Hard disks don't. So, for intermittent and backup use, in general, stick to HDDs.
Liam, I'll just summarise:
- massgrave.dev
- O&O Shutup 10
- gently, very very gently, begin broaching the subject to SWMBO that one day, for her daily use, she will be just *fine* using something that isn't Windows (don't yet mention the word "Linux")
- even more gently broach the subject that even though it is SWMBO, the O stops at letting anything Windows >=11 on to any machine within the premises.
OK, those last 2 may not come from your article, but were added by me.
«Ordinary users can sort things out when Windows goes wrong?»
Surprisingly, yes. Many things can be fixed via GUI. with colorufull guides with snapshots aplenty.
Sometimes, there will be a powershell alternative if the user does not want to go the GUI route. no chmod +w or dependencies involved. This is frowned upon on linux (with good reason), but is a hurdle for normies.
The most complicated thing would probably be "run regedit and change these esoteric values", but if it gets to that stage, the normie will just run the powershell thinguie.
I think even then you will have paid a Microsoft tax. Can't recall the devious mechanism they used to achieve that, but if I recall correctly it works on the principle that it has the *potential* to install Windows and should teherfore pay upfront to prevent piracy, or some othter BS argument that mnakes no sense but got lobbied and dined into existence anyway.
It's nothing like what you describe. Your version suggests it's mandatory or government-supported, when any tax or lack of tax is due to private agreements between Microsoft and computer manufacturers with no external legal backing and subject to anti-competition law if they go too far and regulators are looking (admittedly not often, but when they want to start looking, I think there are bigger problems in tech for them to start with).
The old version was that OEMs could license every machine with a discount or just the machines they wanted to at full price. As long as most customers wanted Windows and intended to get a license with their hardware, the first option was cheaper for the OEM. Things are likely different now but probably go along similar lines. You can dislike it, and you can even raise a regulatory complaint or, where supported by your local laws, file suit about this, but not until you know what's happening and what's not.
Dell (and I think Lenovo and HP too) sell laptops with Ubuntu pre-installed.
With the warm fuzzy feeling of everything pre-tested to just work, and customer support and warranty for a number of years. Also, will pass any HIIPA, PCI, or GDPR certification assesment, auit ot cyber insurance requirements.
A perfectly cromulent option for smart-non-computer-saavy people that want to go to linux, Like Lawyers/solicitors/barristers, MDs, CPAs, etc...
I've just turned an old 2014 Mac Mini into a nice media player. I bunged in a small SSD and installed LIbreELEC. It grabs media from various SMB shares on the network. I also installed a YouTube Addon.
I'm using an ancient iPad running Kodi Remote to control it.
I've got 4 more Mac Minis to do something with...
Less than a month ago I installed Win10 on an old Win8 laptop my brother had. He needed Win10 or newer for a particular program. I owed him a favor so I did it pro bono. This originally Win8 laptop was unsupported for Win11. I had a Win10 install DVD in my library. From what I knew it should go easy enough. No need for any data preservation or other software installation, just Win10. Win10 installed easy enough from the DVD. First hurdle no proper wifi adapter driver. A little searching, trial and error then a light at the end of that tunnel the mothership could be contacted. Windows Update started doing it's job right away as expected since the DVD was an older Win10 release. Then the failed update loops started. Not having recent experience with these things (I switched to Slackware from Mint since dropping Win7 at EOL), I did not recognize the scale of the loop mistaking it for code bloat taking a long time to download, unpack, lay the update foundation, stage the install files, check the status of the squirrel population, then install prior to requiring a reboot to do a smaller cycle missed on the previous iteration. No, it was downloading multiple gigs, proceeding to nearly but not quite 99.9999999999...% before flashing an error for a microsecond and undoing the update only to restart. I caught on in the third iteration since the first happened while this meatbag performed it's nocturnal ritual of sleep. The second happened whilst I was busy tending to some other life necessity like eating. On the third, I caught glimpse of the error, checked the status and determined I need another approach since my goal was to get that latest available of Win10. I settled on downloading the .iso image of the latest installer. Then I ran into another set of problems. 1) That .iso was a 5.8 gig-ish file and I only had 4.7 gig DVD blanks. B) The HP laptop was of the (U)EFI era, but no amount of coaxing could get it to boot from the bootable USB stick I put the image on. (yes, I turned it off then on again, I did not dd the image over my Linux swap partition, and I did apply the right touch percussive persuasion multiple times to both the sweet spots below the keyboard on either side of the trackpad.) III. Win10 was now complaining about activtion and I was not sure if that was impacting the progress. (BTW the favor was owed due to use of his garage and his time to help swap an engine into my car 1.5 days, this was now taking longer than that task 1.75 days and not complete) I remembered that Windows had gained the ability to mount an ISO file so I tried that and the install image was there in Windows Explorer. I decided the HP recovery/reinstall partition being large enough was no longer of any use. I changed it to a standard partition and replaced it's files with the latest Win10 install image files then ran setup.exe from there. Install happened and wifi driver was good this time and Windows update ran and did it's thing properly. Still not activated but not an issue. I did the local account thing, no password so it boots right to a desktop under an unprivileged account. The question is Will I be happier with the new engine than he with the new OS? I gotta remember to answer: I don't do Windows, gave it up for lent, new year's resolution, it's a work of the Devil, anything but Windows or systemd.
When you are updating ANY computer to a newer version of the OS, AND DOUBLY SO IN WINDOWS, always, and I mean ALWAYS update to the LATEST firmware* first. Then, get the LATEST installer available for the OS. Do not use an installer you have "Lying around".
It will save you a lot of grief.
This applies equaly to Windows, any Linux Distro, or xBSD.
* Updating to the latest firmware has a slight chance to brick the machine. If is not your machine, be EXTRA clear with the ownner, MULTIPLE times. If the owner says no to a firmware update, you perform no OS Upgrade.
PS: I recently experienced it first hand. I was setting up two IDENTICAL old Tosh laptops with linux to give away. One with the lattest firmware (I personaly did said update when I brought that machine from XP to 7 for my brother), one sans. Since Tosh exited the Laptop Market, said firmware can not be downloaded. One completed the LMDE-X32 install no problems, the other got stuck halfway due to a known linux bug/regression with the low power states on old processors (P4, Core & Core2).
I am curious where the source of this data point comes from.
MacOS is incredibly easy to update, as long as the current version supports the underlying hardware. Apple runs about a five-year deficit on supported hardware before cutting it off. And Mac OS is usually update annually.
Where is the author's data showing that a five year old Mac was never once updated to a new OS version?
> I am curious where the source of this data point comes from.
It is not a data point. I have no citation. It is my personal opinion based on 38 years of professionally supporting Macintosh hardware in production use.
No matter how many in-place upgrades a machine may get, that remains the original OS installation.
A reinstall means formatting or replacing the drive and starting afresh.
I am currently typing on a MacBook Pro 2011. Lately I have tried it with High Sierra (last supported), Sonoma (using Open Core) and Linux (Debian 13 / Lubuntu 25.10).
I am gravitating towards using Lubuntu (Debian is fine too). Sonoma works surprisingly well, but you have to disable things to make it reasonably fast and it still feels heavy. Getting Linux running properly requires some tinkering with WiFi-installation (WiFi still slower than on macOS) and accelerated video support (for YouTube). High Sierra is too outdated for my practical purposes.
I've had similar experiences with my own 2011 Macbook Pro - it's been running Ubuntu or variants of since September 2022 when I dug it out from under the bed.
Currently running latest Linux Mint Cinnamon, it seems to be responsive enough thanks to a retrofitted SSD although the early generation i5 in this is starting to struggle with the modern internet now, especially Youtube. Wi-Fi performance is adequate but can be a little flaky thanks to the somewhat crap broadcom-wl chipset driver.
I installed Sequoia using OCLP on a 2015 MacBook Pro 15-inch (2.5GHz i7), thinking that it would be well-capable of running the OS. Things did not go smoothly.
Fans were constantly running, it ate through my newly-installed battery and an Apple update completely borked the installation, preventing it from booting. This happened after a period of time on Sequoia, so it wasn’t an issue of the new OS indexing.
I therefore flattened the drive, took it back to a clean installation of Monterey and everything’s going swimmingly again.
Maybe when Monterey gets too past it, I’ll try again with OCLP but in the meantime, life’s too short.
Great article though, with lots of sensible, practical advice.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
