Practical Options After Windows 10 End of Support — A Decision Table for ESU, LTSC, and Replacement

“The PC connected to the inspection equipment on the factory floor is still running Windows 10.” “The shared PC in the office is showing a ‘Windows 10 support has ended’ notification, but we can’t commit because there’s no guarantee the business application will run on Windows 11.” “There’s apparently a life-extension option called ESU, but we don’t have time to research the pricing or the paperwork.” — It has been just over nine months since Windows 10 support ended on 14 October 2025. Visiting customer sites, we still run into this kind of “Windows 10 left as homework” all the time.

The awkward part is that there is no single right answer that covers everything. The options available for an office PC differ from those for an equipment control PC, the ESU terms for organisations are completely different from those for individuals, and on top of that, June 2026 brought a change in the terms themselves in the form of an extension to consumer ESU. Judging on the basis of outdated information leads either to unnecessary spending or, conversely, to leaving machines defenceless.

This article is aimed at IT staff and managers at small and medium-sized companies with Windows 10 PCs still in the office or on the factory floor, and at the developers responsible for the business applications running on them. It organises four options — (1) migrating to Windows 11, (2) extending life with ESU, (3) switching to a long-term support release such as IoT Enterprise LTSC, and (4) network isolation — into a decision table, based on primary sources as of July 2026. As a company that builds bespoke business applications, we also devote a section to the verification and remediation work required on the application side.

1. The Bottom Line First

• Support for Windows 10 (the standard editions) ended on 14 October 2025. The final version was 22H2, and since then all quality updates including security updates, feature updates, and technical support have stopped. The PCs keep running, but vulnerabilities do not get fixed.¹²
• The default answer is migrating to Windows 11. If a PC meets the hardware requirements (TPM 2.0, UEFI + Secure Boot, a supported CPU), the OS itself can be upgraded free of charge. What it costs you is mainly the effort of verification and swap-over.³
• Commercial ESU is “planned time-buying until migration is complete”. From USD 61 per device (year one), doubling every year, for a maximum of three years to October 2028. If you enrol later, a cumulative purchase rule requires you to buy the earlier years retroactively. If you manage devices with Intune or Windows Autopatch there is a discounted USD 45 for year one, and there are conditions under which it is free in cloud environments such as Windows 365.²⁴
• Consumer ESU was extended by one year in June 2026 and now runs to 12 October 2027. There are three routes — PC settings sync (free), 1,000 Microsoft Rewards points, or USD 30 — and the extension is applied automatically to existing enrollees.⁵
• ESU is security updates only. New features, non-security fixes, and ordinary technical support are not included. It is easy to misread it as “life extension” when it is not “keeping things as they are”.²
• In practice, switching to a long-term support release means Windows 10 IoT Enterprise LTSC 2021 and nothing else. It is supported until 13 January 2032. Ordinary Enterprise LTSC 2021, by contrast, runs only to 12 January 2027 — under six months away — so there is almost no point switching to it now.⁶⁷
• Microsoft 365 Apps continue to receive security updates on Windows 10 until 10 October 2028. Feature updates, however, stop at version 2608, and support enquiries come with restrictions. “Office gets updates until 2028” and “the Windows platform itself is defenceless” are two separate matters.⁸
• On the application side, the bottleneck is the periphery, not the core. The .NET Framework is defined as part of the OS and remains supported on Windows 11,⁹ but 64-bit signed driver support for equipment, COM/OCX registration, and Internet Explorer-dependent features are what decide whether migration is feasible.

2. Where Things Stand as of July 2026 — What Can Be Used and Until When

Start by getting the timeline right. The deadlines that underpin every decision are as follows.

As of the time of writing, any Windows 10 machine not enrolled in ESU has gone nine months without security fixes. Many of the vulnerabilities fixed in the monthly updates are common to both Windows 10 and 11, so the situation is one where “the fix is published every month, but it just never reaches my PC”. Whether that state of affairs is acceptable is the starting point for every decision that follows.

The other thing worth keeping in mind is that the terms move, as the June 2026 extension of consumer ESU demonstrates. The content of this article is likewise based on primary sources as of July 2026; before making a final decision, please check the current terms on the relevant Microsoft pages.

3. Option 1: Migrate to Windows 11 — The Default Answer

There is no way to dress it up: for ordinary office PCs used with an internet connection, migrating to Windows 11 is the default. Both ESU and isolation are simply ways of buying time at the price of cost or risk.

The decision starts with the hardware requirements. The minimum requirements for Windows 11 are a 64-bit CPU on the compatibility list (1 GHz or faster, two or more cores), 4 GB of memory, 64 GB of storage, UEFI + Secure Boot, and TPM 2.0.³ In practice, PCs shipped as business models from roughly 2018 onwards usually meet them, whereas for anything older, replacement is the realistic answer. A PC that meets the requirements can be upgraded free of charge directly from Windows 10 version 2004 or later.³

• PCs that meet the requirements: after completing application and driver verification (Section 7), upgrade in stages, for example department by department. There is no OS cost, so the real cost is the effort of verification and swap-over.
• PCs that do not meet the requirements: replace them. If you are considering a Snapdragon-based Arm version of Windows, there are compatibility caveats specific to business applications and drivers. Read “Do Business Apps Run on Windows on Arm? — The Reality of x64 Emulation (Prism) and Native DLLs/COM” first. Also, unless you have a documented procedure for retiring Windows 10 machines that goes as far as data erasure, they become a source of information leaks. “What to Do Before Disposing of a Windows PC — A Practical Checklist for Data Erasure, Account Unlinking, and Backups” collects this into a checklist.

If your reaction is “there are too many machines to do them all at once”, that is exactly where ESU comes in. ESU is not a reason to avoid migrating — the healthy way to use it is as insurance that lets you see a migration plan through to the end.

4. Option 2: Extend Life With ESU — Completely Different Terms for Organisations and Individuals

ESU (Extended Security Updates) is a paid programme that supplies security updates rated Critical and Important to Windows 10 22H2 after end of support. Only security updates are included — new features, non-security fixes, and ordinary technical support are not.²

The essentials of the commercial offering (volume licensing) are as follows.²

• The price is USD 61 per device in year one, and it doubles every year (USD 122 in year two, USD 244 in year three). It runs for a maximum of three years, extending life to October 2028.
• There is a cumulative purchase rule. If you enrol from year two, you still have to pay for year one, so “wait until it gets dangerous and it’ll be cheaper” does not work. The minimum purchase is one licence.
• Only Windows 10 version 22H2 is eligible. Updating to 22H2 is a prerequisite.
• There are discounted and free routes. Devices managed in the cloud through Microsoft Intune or Windows Autopatch are quoted a discounted USD 45 for year one.⁴ In addition, ESU is provided at no additional cost for Windows 10 on Windows 365, Azure Virtual Desktop, and Azure virtual machines, and Windows 10 endpoints connecting to a Windows 365 Cloud PC are also covered by ESU for up to three years while the subscription is active.²

The consumer offering is an entirely different beast.⁵

• It was originally planned to run for one year (to October 2026), but in June 2026 it was extended by a year, to 12 October 2027. The extension applies automatically to existing enrollees.
• There are three enrolment routes: free if you enable PC settings sync (Windows Backup), 1,000 Microsoft Rewards points, or a one-off USD 30 purchase. One licence covers up to ten devices, and all routes require enrolment with a Microsoft account.
• It is aimed at personally used PCs running Windows 10 22H2 Home/Pro and similar. For company PCs, use commercial ESU as a matter of policy.

The three-year total for commercial ESU is USD 427 per device (61 + 122 + 244), or USD 315 even with the cloud-management discount. With enough machines, there is always a line beyond which “you might as well buy new PCs with that budget”. ESU is not something to apply uniformly across every machine — the practical view is to buy it for exactly the number of machines that won’t make the deadline, times the number of years needed.

5. Option 3: Switch to LTSC — Not “Life Extension” but “Moving House”

The orthodox response to “we want to stay on the Windows 10 line for a long time” is switching to the Long-Term Servicing Channel (LTSC). As of July 2026, though, the choice has effectively narrowed to one.

• Windows 10 Enterprise LTSC 2021: supported until 12 January 2027. With under six months left, it is not something to switch to now.⁷
• Windows 10 IoT Enterprise LTSC 2021: supported until 13 January 2032. With roughly five and a half years of support left, this is the real candidate for long-term life extension.⁶

The fact that the same “LTSC 2021” has support end dates five years apart depending on whether it is the standard or the IoT variant is a point you will certainly get wrong if you do not know about it. Despite the “IoT” name, the product is an ordinary Windows desktop OS, and it suits PCs with a fixed purpose such as equipment control PCs and inspection terminals.

That said, switching to LTSC is less “life extension” than “moving house”. Factor in the following.

• A clean installation is the rule. It cannot be introduced by an edition switch from standard Windows 10 Pro, so the environment has to be rebuilt (reinstalling applications, migrating settings, setting up equipment drivers again).
• The licensing route is unusual. IoT Enterprise LTSC is fundamentally supplied through the OEM/embedded channel (via distributors); it is not something you can casually buy over the counter or through volume licensing.
• For a new equipment PC, its successor Windows 11 IoT Enterprise LTSC is also an option. The basic framing is: Windows 10 IoT Enterprise LTSC 2021 for extending the life of existing assets, Windows 11-generation LTSC for new deployments.

The differences between the LTSC editions, how to obtain licences, and practical configurations for equipment PCs are covered in detail in the sister article published the same day, “Which Windows Should You Put on an Industrial PC? — A Practical Guide to Windows IoT Enterprise / LTSC”. If equipment PCs are your concern, read that one alongside this.

6. Option 4: Isolate From the Network and Keep Using It

The final option is to give up on updates and isolate the machine. Frankly, this is not a countermeasure — it is buying time — but out in the field there really are PCs with no other option: “the equipment vendor has gone out of business and no Windows 11-compatible version exists”, “inspection equipment whose certified configuration cannot be changed”. These are exactly the PCs we encounter in our own equipment-integration work.

If you choose isolated operation, treat the following as a minimum set.

• Cut it off from the internet physically or by VLAN. “We just don’t normally use it, but it could get out if you connected it” is not isolation. Not using that PC for email or the web is a basic premise.
• Control what gets carried in. The classic infection routes for a PC on a closed network are USB memory sticks and maintenance laptops brought in from outside. Decide on rules for USB media (dedicated media, a staging PC for virus scanning) and countermeasures against lateral spread via shared folders (minimum necessary shares, separate network segments).
• Treat a hardware failure as the end of life, and prepare for it. The moment the hardware breaks, that Windows 10 environment cannot be procured again. Take disk image backups and, where possible, secure a spare machine.
• Put it on the asset register and set a deadline. Manage “which PC, why it is isolated, and by when that will be resolved” in your asset register. Isolation without a deadline turns into an unmanaged machine nobody knows about the moment the responsible person changes roles.

This option only becomes meaningful once you have decided what you will do with the time isolation buys you — whether that is an equipment replacement plan or re-platforming the application.

7. Verification and Remediation Needed on the Application Side — A Developer’s View

Whichever option you choose, the verification points are the same from the perspective of the party responsible for the business application. In our experience, it is rare for the application “core” to stop working in a Windows 10 → 11 migration; what trips you up is almost always the periphery.

• The .NET Framework outlives your application. .NET Framework 4.x is defined as a component of the OS and follows the lifecycle of the OS it is installed on.⁹ In other words, 4.8 on Windows 10 shares Windows 10’s fate, while 4.8.1 on Windows 11 continues to be supported alongside Windows 11. Apps targeting 4.x will generally run unchanged on Windows 11, but for apps targeting older 4.5-series versions, this is the moment to confirm they run on the 4.8-series runtime. An OS migration is also a good opportunity to take stock of your application assets — the “Pre-Migration Checklist for Moving from .NET Framework to .NET” is useful here.
• COM/OCX/ActiveX assets fall over at “registration”. 32-bit applications themselves run under WOW64 on Windows 11, but insufficient privileges during an installer’s COM registration step, mixing up the 64-bit and 32-bit registry views, and deployment mistakes that work on the dev machine but not in production are all still standard failure modes. In migration testing, always run the “install from the installer onto a clean Windows 11” test. For the details, see “Registration and Bitness Pitfalls in COM/OCX/ActiveX Development”. Runtime support for VB6 applications is set out in “How Long Will VB6 Apps Keep Running? — Runtime Support Status and a Practical Path to .NET Migration”.
• The real bottleneck is drivers. Hardware that comes with a kernel-mode driver — measurement boards, dongles, serial converters, printers — will not work on Windows 11 unless the vendor supplies a 64-bit signed driver. This is the watershed for whether migration is feasible at all, and PCs where “the application can migrate but there is no driver for the board” are precisely the ones to which you apply individual solutions such as IoT Enterprise LTSC or isolated operation.
• Flush out IE dependencies and 32-bit connectivity components. Dependence on the WebBrowser control (the IE engine), missing 32-bit ODBC/OLE DB drivers, version requirements of reporting tools — these only surface once you change the OS. Preparing a single Windows 11 test machine configured identically to production and going end to end (installation → a full pass through the business workflow → report printing → equipment connection) ends up being the cheapest approach.

8. The Decision Table — Which Option for Which PC

Here is everything so far, condensed onto a single page. The trick is to sort machine by machine according to its role.

Rather than picking one option for the whole company, the realistic answer is a combination — something like “office PCs move to Windows 11 within this financial year; the 20 that won’t make it get one year of commercial ESU; three equipment PCs are re-platformed onto IoT LTSC; and the one machine whose vendor has gone out of business is isolated with a spare secured”.

9. Summary

• Support for Windows 10 (22H2) ended on 14 October 2025, and PCs not enrolled in ESU have gone nine months without security fixes. Start by taking stock of every machine.
• For office PCs with an internet connection, the default is migration to Windows 11. Use ESU as insurance to see the migration plan through, for exactly the number of machines and years you need.
• Commercial ESU is USD 61 in year one, doubling annually, up to October 2028, with a cumulative purchase rule. It is worth checking the discount for devices managed by Intune or Windows Autopatch and the free conditions on Windows 365 and similar.
• Consumer ESU was extended in June 2026 and now runs to 12 October 2027. Free routes exist, but for company PCs use the commercial offering.
• The real candidate for long-term life extension is Windows 10 IoT Enterprise LTSC 2021 (to January 2032). Bear in mind, though, that it is a “house move” involving a clean installation and licence procurement, and take care not to confuse it with standard Enterprise LTSC 2021 (to January 2027).
• For PCs with no way out, isolated operation buys time — but unless you combine cut-off, media control, a spare machine, the asset register, and a resolution deadline, it is simply neglect.
• On the application side, the main event is drivers, COM/OCX registration, IE dependencies, and 32-bit connectivity components rather than .NET itself. Complete an end-to-end test on a Windows 11 machine equivalent to production before you migrate.

Related Articles

• Which Windows Should You Put on an Industrial PC? — A Practical Guide to Windows IoT Enterprise / LTSC
• Pre-Migration Checklist for Moving from .NET Framework to .NET
• How Long Will VB6 Apps Keep Running? — Runtime Support Status and a Practical Path to .NET Migration
• Extending the Life of and Migrating VB6 / Access Business Apps — A Decision Table for Keep, Wrap, or Replace
• Do Business Apps Run on Windows on Arm? — The Reality of x64 Emulation (Prism) and Native DLLs/COM
• What to Do Before Disposing of a Windows PC — A Practical Checklist for Data Erasure, Account Unlinking, and Backups
• Registration and Bitness Pitfalls in COM/OCX/ActiveX Development

Related Consulting Areas

KomuraSoft LLC handles Windows 11 support for business applications and equipment-integration software currently running on Windows 10 (compatibility verification, remediation around installers and COM/OCX, isolating driver issues), as well as technical consulting on migration plans that include re-platforming onto LTSC. Starting from simply establishing “will this application run on Windows 11?” is perfectly fine.

• Migration and Reuse of Existing Assets
• Modernization and Maintenance of Windows Applications
• Technical Consulting & Design Review
• Contact Us

References

Related Articles

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

Related Topics

These topic pages place the article in a broader service and decision context.

Where This Topic Connects

This article connects naturally to the following service pages.

Frequently Asked Questions

Common questions about the topic of this article.

Is it immediately dangerous to keep using Windows 10 after end of support?

Your PC won't suddenly refuse to boot — Windows 10 keeps running after 14 October 2025. However, unless you are enrolled in ESU, no security updates are delivered at all. As of the time of writing (July 2026), that means nine months' worth of vulnerability fixes have not been applied. If the PC is used with an internet or email connection, we recommend deciding quickly on one of three directions: migrate to Windows 11, enrol in ESU, or isolate it.

How much does commercial ESU cost, and how long can it extend the life of a PC?

Through volume licensing it starts at USD 61 per device for year one, and the price doubles every year (USD 122 in year two, USD 244 in year three), for a maximum of three years — up to October 2028. If you enrol from year two, you must still purchase the year-one coverage retroactively (cumulative purchase). Devices managed in the cloud through Microsoft Intune or Windows Autopatch are quoted a discounted USD 45 for year one, and Windows 10 virtual machines running on Windows 365 or Azure Virtual Desktop are covered by ESU at no additional cost. Note that ESU delivers security updates only — new features and ordinary technical support are not included.

Wasn't consumer ESU only supposed to run until October 2026?

It was originally planned to last one year from the October 2025 end of support (to October 2026), but in June 2026 Microsoft announced a one-year extension, so it now runs to 12 October 2027. The extension is applied automatically to existing enrollees, with no additional steps required. There are three enrolment routes: enabling PC settings sync (Windows Backup) at no cost, 1,000 Microsoft Rewards points, or a one-off USD 30 purchase — all of which require a Microsoft account. For company PCs, use commercial ESU as a matter of policy.

Can I extend the life of my current PCs as they are by switching to LTSC?

You may be able to keep using the same hardware, but not "as they are". LTSC cannot be introduced by an edition switch from standard Windows 10; in principle it requires a clean installation and a rebuild of the environment, and you have to procure the licence separately. In addition, ordinary Enterprise LTSC 2021 is supported only until 12 January 2027, so there is almost no point switching to it now. The candidate for genuine long-term life extension is Windows 10 IoT Enterprise LTSC 2021, supported until 13 January 2032 — an option aimed at PCs with a fixed purpose, such as equipment control.

Will business applications run on Windows 11 without changes?

Desktop application compatibility is high, and most apps built on the .NET Framework or the VB6 runtime run unchanged. That isn't unconditional, though, and what trips you up in practice is mostly the periphery. Specifically: hardware such as measurement boards and dongles for which no 64-bit signed driver is supplied; COM/OCX registration steps in installers and bitness mismatches; Internet Explorer-dependent features such as the WebBrowser control; and missing 32-bit ODBC/OLE DB drivers. The reliable approach is to prepare a single Windows 11 test machine configured identically to production and walk through the whole cycle, from installation to report printing and equipment connection.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.