- Regular support for Windows 10 version 22H2 ended on 14 October 2025. Devices outside Extended Security Updates (ESU) no longer receive security updates; enrolled devices still receive critical and important security updates for a limited period
- Commercial ESU list prices are US$61 per device for Year 1, US$122 for Year 2 and US$244 for Year 3. ESU is cumulative, requires Windows 10 22H2 and only works once the ESU key is activated on each device
- Windows 11 needs a supported processor, UEFI firmware with Secure Boot capability, TPM 2.0 and other minimums. Enabling a disabled TPM clears one blocker, not all of them
- Enterprise LTSC, IoT Enterprise and other editions follow their own lifecycles. Confirm edition and version before you classify a device
- Cyber Essentials, UK GDPR, ISO 27001 A.8.8 and NIS rules expect managed vulnerabilities and documented decisions. None of them says every Windows 10 device must be replaced immediately
What end of support means in practice
End of support does not stop Windows 10 working. For Windows 10 version 22H2, Microsoft ended regular support on 14 October 2025: no more technical support, feature updates or quality updates, which include security fixes. A device that is not enrolled in ESU therefore no longer receives regular security updates. A device that is enrolled, with an activated ESU licence, continues to receive critical and important security updates for the years it is covered.
The dates here refer mainly to Windows 10 version 22H2 (Home, Pro, Enterprise and Education). Windows 10 Enterprise LTSC, IoT Enterprise and other editions have different lifecycles, and Microsoft states that LTSC releases are not covered by the Windows 10 ESU programme. Confirm the edition and version of each device before you classify it as supported or unsupported.
Not every vulnerability disclosed since October 2025 affects every Windows 10 device. Whether a new CVE matters depends on the vulnerability itself, whether the affected component is installed and enabled, how the device is configured, how exposed it is to the internet and to users, and which compensating controls are in place, such as endpoint detection, application control and network segmentation. What changes without ESU is that a fix for a relevant Windows flaw will not arrive through Windows Update, so exposure has to be managed by other means and tends to grow over time.
Third-party support does not end on a single date either. Timelines vary by product and vendor. Check the support matrices and contracts for your critical applications, security agents, browsers and VPN clients, and record which still support Windows 10 and until when.
How widespread Windows 10 still is
Statcounter data for September 2026 puts Windows 10 at about 15% of Windows desktop versions in the UK and about 21% in the Netherlands. These figures measure observed web usage by Windows version. They do not describe the make-up of any company's estate, and they do not show which devices are covered by ESU. Your own inventory is the only reliable measure for your organisation.
Organisations that bought most of their hardware before Windows 11 launched in 2021 are more likely to hold devices that fail the hardware check. Some only noticed when a Cyber Essentials assessment, an ISO 27001 audit or customer due diligence raised the question.
Your three options
Option 1: Upgrade eligible devices (free)
If a device meets the Windows 11 requirements, the upgrade is free through Windows Update, the Windows 11 Installation Assistant or management tools such as Microsoft Intune. How long it takes depends on the hardware, network and installed software, so time it on your own pilot devices rather than relying on a general estimate.
Before a wide rollout, run a pilot with a representative group of users, check that critical applications work, validate backups with a test restore, and agree a rollback or recovery procedure for devices where the upgrade fails. That is what keeps an in-place upgrade low-risk.
A failed compatibility check has several possible causes. TPM 2.0 may be present but disabled in firmware, the processor may not be on Microsoft's supported list, or the device may be running in legacy BIOS mode without Secure Boot. Enabling a disabled TPM can resolve one blocker but does not guarantee eligibility. After any firmware change, rerun PC Health Check or your management tool's readiness report before deciding.
Option 2: Replace hardware
Devices that still fail after firmware checks, typically because of an unsupported processor or TPM 1.2, are candidates for replacement. A laptop on a four to five year refresh cycle may be due for replacement in this period anyway, so the Windows 10 deadline often brings forward a refresh that was already planned.
If replacing, standardise on a hardware specification. Consistent hardware reduces support complexity and makes imaging, deployment and troubleshooting faster. Document the minimum specification for new purchases so procurement decisions do not recreate the same problem in a few years.
Option 3: Extended Security Updates (ESU)
For organisations, Microsoft sells ESU per device through volume licensing and Cloud Solution Provider partners. The list price is US$61 per device for Year 1 and doubles each year: US$122 for Year 2 and US$244 for Year 3, for a maximum of three years. ESU is cumulative, so if you join in Year 2 you also pay for Year 1. These are US dollar list prices; what you pay in pounds depends on exchange rates, VAT, your licensing programme and your reseller. Education customers have separate pricing. Windows 10 devices that connect to Windows 365 Cloud PCs, and Windows 10 virtual machines in Azure Virtual Desktop and certain other Azure services, receive ESU at no additional cost.
Buying ESU is not enough on its own. Each device must run Windows 10 version 22H2 with the prerequisite updates, the ESU key must be installed and activated for the correct year, and you need to verify that ESU updates are actually installing. Check activation status per device and confirm it in your patch compliance reporting.
For home users, Microsoft launched consumer ESU as a single year of cover. Its consumer ESU page now states that enrolled devices receive updates until 12 October 2027. If staff use personal Windows 10 laptops for work, ownership alone tells you little. Assess those devices by your endpoint management model: are they enrolled in Intune or another management tool, and do they meet your policies on supported software, encryption and endpoint protection? Use conditional access, device compliance policies or app protection to limit what they can reach, and restrict access to company data where adequate security cannot be demonstrated.
ESU provides critical and important security updates only. It does not add features, non-security fixes or general technical support, and it does not change other vendors' support decisions. Treat it as a time-limited bridge and set the migration deadline before your ESU cover ends.
IASME guidance states that Windows 10 devices used after 14 October 2025 must be enrolled in Microsoft's ESU programme to remain compliant, which also means running version 22H2. In-scope devices that are neither upgraded nor enrolled count as unsupported software. Confirm the current requirements with your certification body before your assessment.
Auditing your estate
Before planning any migration, you need an accurate inventory. In Microsoft Intune, filter device inventory by OS version and use the Windows 11 readiness reporting. With another RMM platform, generate an OS inventory report from the management console. Where you have no remote management tooling, run Microsoft PC Health Check locally on each device. For every Windows 10 device, record at least these four fields:
- OS edition and build. For example Windows 10 Pro 22H2 (build 19045), Enterprise LTSC or IoT Enterprise. This determines which lifecycle applies.
- ESU status. Not enrolled, licence purchased, or key activated with updates verified.
- Windows 11 compatibility result. Pass or fail, including the specific blocker.
- Business and application owner. Who approves downtime and who is responsible for the applications on the device.
Prioritise devices used for privileged administration first, then devices that access finance systems, sensitive data or remote access services.
Decision matrix by device condition
Turn the result into a migration plan that covers application testing, backups and restore tests, recovery and rollback, change windows, endpoint management (enrolment, policies and configuration baselines) and security validation after migration, such as confirming that endpoint protection, encryption and updates are working.
Windows 11 hardware requirements
Compliance implications
Cyber Essentials requires in-scope software to be licensed and supported, with critical and high-risk security updates applied within 14 days. Under IASME guidance, Windows 10 devices enrolled in ESU and receiving updates can remain in scope; devices without ESU need upgrading, replacing or removing from scope.
UK GDPR, Article 32 requires technical and organisational measures appropriate to the risk. It does not name operating systems, but if personal data is compromised on an unsupported device, the ICO may consider that when judging whether your measures were appropriate.
ISO 27001:2022, Annex A.8.8 (management of technical vulnerabilities) requires you to obtain information about vulnerabilities, evaluate your exposure and take appropriate measures. NIS2 Article 21 and the UK NIS Regulations require in-scope entities to manage risk, including vulnerability handling.
None of these frameworks universally requires every Windows 10 device to be replaced immediately. They expect you to assess the relevant vulnerabilities, the support available, your compensating controls and your migration plan, and to keep evidence of the decisions you take. ESU can be part of a documented risk treatment strategy. A migration plan with owners and dates is strongly recommended, and whether an assessor or auditor accepts your approach depends on the applicable requirements and the evidence you can show.
Windows 10 did not stop working on 14 October 2025. Outside ESU, it stopped receiving regular fixes.
Windows Server follows a separate lifecycle from the Windows desktop editions. If your estate also runs Windows Server 2016, read our guide to Windows Server 2016 end of support, which covers the server deadline and options.
Organisations concerned about the broader pattern of dependency on the Microsoft platform should review architectural approaches to reducing single-vendor exposure. Our guide to Microsoft dependency risks covers identity decoupling, infrastructure diversification, and migration sequencing.