Using Windows 10 past EOL (via LTSC supported to 2032)
1–10 of 25 posts
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#2My PC doesn't have TPM. It's old, but still perfectly fine to run for my needs. I use Unreal 5, play games, watch videos. Could run quicker but it's no landfill device. I don't think it'll suddenly fall to pieces come October so I wasn't looking to scrap it by then.
Looks like the IoT LTSC version will work. I'm still hoping that Microsoft relent on this move. Last I checked Windows 10 is still a very popular OS and I find it unlikely that people are going to update if they haven't already. If some kind of WannaCry attack happens due to a security hole it's going to look bad on them.
Also, as a kinda dark humor moment. October 14th is the retirement day of Windows 10, which is also international e-waste day. Unless I missed the memo, I thought it was an effort to prevent creating e-waste not one of planned obsolescence to try and make more.
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#310LTSC + 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
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#4Bookmarked this for some weekend fiddling.
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#510LTSC + 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.
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#610LTSC + 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.
Massgrave ISOs actually download from Microsoft. It's just a small wrapper app that links you to the correct version. Microsoft also provides hashes, so it's pretty easy to validate that you're getting a legitimate ISO.
No comment on the other scripts. Although the source is available...
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#7What's the best strategy for a full backup and recovery if updating to LTSC goes wrong?
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#8My PC doesn't have TPM. It's old, but still perfectly fine to run for my needs. I use Unreal 5, play games, watch videos. Could run quicker but it's no landfill device. I don't think it'll suddenly fall to pieces come October so I wasn't looking to scrap it by then. Looks like the IoT LTSC version will work. I'm still hoping that Microsoft relent on this move. Last I checked Windows 10 is still a very popular OS and…
I've put IoT LTSC on a couple 10 year old laptops we use for misc things and it runs great.
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#9What's the best strategy for a full backup and recovery if updating to LTSC goes wrong?
Maybe create a full disk system image? But also upgrade adds a way to restore itself
Re: Using Windows 10 past EOL (via LTSC supported to 2032)
#1010LTSC + 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
Win7 + Office 2003 for me (pre-ribbon, thanks)