Earlier quoted context omitted.
The thing is that with the LTSC branch, you never get full-version upgrades. That is why it exists.
The full-version upgrade here is LTSC
Ah, OK, I see what you mean. All right then, my mistake.
Using Windows 10 past EOL (via LTSC supported to 2032)
21–25 of 25 posts
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#22What's the experience with Windows 11? I haven't upgraded because Microsoft doesn't have a great track record of not screwing things, and I would hate their upgrade process to destroy the data in my harddrives. Which means I'll have to buy a NAS and do a full backup of everything before upgrading, and then pray that that software I bought years ago and that since then have transitioned to cough-money-monthly (like Zb…
It's very comparable to the difference between 10 and 7. Microsoft glued on an extra layer of fugly UI over the existing workable UI and just left it to rot.
If you right click something to bring up the context menu, you get a gross liquid ass style menu and then you have to click through to open the classic context menu to get the option you want. Why. Literally what is the point of this?!
Everything is worse, more annoying, and uglier in various quantities. They actually even managed to make Bluetooth even worse than in W10, which is frankly an astonishing achievement
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#23What's the experience with Windows 11? I haven't upgraded because Microsoft doesn't have a great track record of not screwing things, and I would hate their upgrade process to destroy the data in my harddrives. Which means I'll have to buy a NAS and do a full backup of everything before upgrading, and then pray that that software I bought years ago and that since then have transitioned to cough-money-monthly (like Zb…
It's very comparable to the difference between 10 and 7. Microsoft glued on an extra layer of fugly UI over the existing workable UI and just left it to rot. If you right click something to bring up the context menu, you get a gross liquid ass style menu and then you have to click through to open the classic context menu to get the option you want. Why. Literally what is the point of this?! Everything is worse, more…
Yeah, it's so bad. Change for the sake of change.. Absolutely zero benefit for people who use this OS
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#24I just looked up stats on the install base. I don't know how trustworthy statcounter is, but they state that this data is from may
Desktop Windows Versions Percentage Market Share
Win10 53.19%
Win11 43.22%
Win7 2.48%
WinXP 0.54%
Win8.1 0.29%
Win8 0.22%
Desktop Windows Version Market Share Worldwide - May 2025Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#2510LTSC + Office 2016 + open shell is the peak windows experience. 2016 was the last year you could autosave documents locally, then fucking OneDrive. Grab an ISO from Massgrave, write using Rufus and two scripts later your fully tweaked. irm https://get.activated.win | iex iwr -useb https://christitus.com/win | iex
using a disk image and some scripts from the web seem like a bad practice to get something 'secure' up and running. Note: never used massgrave. Just doesn't sound trustworthy from the name. If you can, download from msdn directly.
> using a disk image and some scripts from the web seem like a bad practice to get something 'secure' up and running.
> If you can, download from msdn directly.
Using anything from Microsoft "seem like a bad practice to get something 'secure' up and running. "