Windows 10 after the end: ESU, LTSC, or replace the machine

Verified 2026-10-294 min read

Windows 10 support ended on 2025-10-14. The three real routes for the machines still on it, what ESU does and does not include, and when the SSD matters more than the OS.

Tested onPro (26H2) / Server · Build 26300.9457 / 26100.33650 · x64

Build: 26300.9457 / 26100.33650
Edition: Pro (26H2) / Server
Architecture: x64
Support: Documentation (E1)
Evidence: E1Official documentation
Verified: 2026-10-29
Page type: Concept

The short answer

Windows 10 Home, Pro, Enterprise and Education reached end of support on 2025-10-14. Version 22H2 was the last release; there will be no 23H2.

That leaves three honest routes, and one that people take but should not:

Route	Runs until	Cost	Best for
ESU (Extended Security Updates)	consumer programme to 2027-10-12	free (MSA) / points / ~$30	machines that must keep working for another year
LTSC 2021 (clean install)	2027-01-12	licence + reinstall	fixed-purpose devices, not desktops
IoT Enterprise LTSC 2021	2032-01-13	OEM/volume channel only	kiosks, industrial, appliances
Upgrade to Windows 11 or replace	depends on hardware	licence / new hardware	anything that fails the TPM 2.0 + CPU floor
~~“bypass” install on unsupported hardware~~	unsupported	free	nobody — see below

What ESU actually buys you

ESU is security updates only, for critical and important vulnerabilities. It does not include:

new features,
non-security fixes,
general technical support,
driver updates.

On a consumer device, enrolment is tied to signing in with a Microsoft account (settings sync), or 1000 Microsoft Rewards points, or a one-off payment of about US$30 that covers up to 10 devices. Microsoft has extended the consumer programme to 2027-10-12 — it was originally one year, to 2026-10-13.

# what am I actually running, and is ESU enrolled?
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object ProductName,DisplayVersion

LTSC: legal, and usually the wrong tool

LTSC is not a “lighter Windows for gamers”. It is a long-life servicing channel for fixed-purpose devices — ATMs, industrial controllers, medical equipment. Microsoft says so explicitly, and the licensing runs through volume/OEM channels, not retail.

	Windows 10 Enterprise LTSC 2021	Windows 10 IoT Enterprise LTSC 2021
End of support	2027-01-12	2032-01-13
Licensing	volume	OEM / volume
Written for	fixed-purpose devices	fixed-purpose devices
Store / consumer apps	minimal by design	minimal by design
Edge	included	included

Two claims worth correcting, because they circulate widely:

“LTSC has no Edge / no browser.” It ships with Edge. What it lacks is the consumer app set and the feature churn.
“LTSC is zero telemetry.” It collects less than consumer editions, but security and diagnostic data still flow. “No tracking at all” is not a documented configuration.

The hardware is the real bottleneck

The uncomfortable part: on a machine with a spinning disk and 4GB of RAM, changing the OS does not change the experience. Windows 10 → LTSC saves background work; it does not make a 5400rpm drive seek faster.

Order of return on a 2015-era desktop:

SSD — largest single improvement, by a wide margin.
RAM to 8GB — stops the paging thrash.
Clean install of a supported OS — removes years of accumulated startup debt.
New machine — when the CPU has no modern instruction support and the platform has no TPM 2.0.

An SSD plus Windows 11 (where the hardware qualifies) beats LTSC on the same hardware for most people. See buying guide and when to replace the machine.

Why “bypass” installs are a bad trade

Registry edits and patched installers can put Windows 11 on unsupported CPUs. What you keep: a working desktop. What you lose:

update eligibility — Microsoft does not guarantee feature updates or security fixes on unsupported configurations;
support — no OEM or Microsoft support path;
stability — drivers for unsupported platforms are not validated against the newer kernel;
the honest upgrade story — the machine is one bad update away from an unbootable state with no vendor to call.

For a lab VM, a bypass is a fine experiment. For a machine someone depends on, it is a loan against future time.

A decision sequence that works

Run winver and note the build. Confirm you are on 22H2.
Run PC Health Check to see exactly which requirement fails (TPM 2.0, Secure Boot, CPU generation).
If only TPM is missing and the board has a header: a TPM 2.0 module is cheap and is the legitimate fix.
If the CPU is below the supported list: the decision is ESU (buy a year) or replace (buy a machine), not a bypass.
Whatever you choose: back up first, and export the BitLocker recovery key if the machine is encrypted.

# the two checks that decide everything
Get-Tpm | Select-Object TpmPresent,TpmReady,SpecVersion
Get-CimInstance Win32_Processor | Select-Object Name,NumberOfCores,MaxClockSpeed
Confirm-SecureBootUEFI -ErrorAction SilentlyContinue

Lab boundary

E1. All lifecycle dates on this page were checked against Microsoft’s lifecycle product pages on 2026-10-29. The ESU enrolment flow was not exercised in this lab: the lab VMs run Windows 11, not Windows 10.