
Microsoft ended standard support for Windows 10 on October 14, 2025, but many businesses still depend on devices running the operating system. As of November 2026, the challenge for IT departments and managed service providers (MSPs) has shifted from preparing for end of support to managing Windows 10 endpoints through their second year of Extended Security Updates (ESU).
Commercial ESU Year 2 began on October 14, 2026, introducing another round of licensing costs and activation requirements. Meanwhile, organizations must address aging hardware, legacy application dependencies, and the operational risks of maintaining systems that cannot immediately migrate to Windows 11.
Microsoft's ESU program provides additional security coverage, but it does not restore full Windows 10 support or eliminate the risks associated with aging infrastructure.
This guide explains how Windows 10 ESU works in 2026, what organizations need to verify for Year 2, how much continued coverage costs, and how IT teams can maintain legacy endpoints while planning their migration.
What Is Windows 10 Extended Security Updates (ESU)?
Windows 10 Extended Security Updates is a Microsoft program that allows eligible devices to continue receiving Critical and Important operating system security updates after standard support ends.
For commercial organizations, Microsoft offers up to three years of extended coverage beyond the October 14, 2025, end-of-support date.
The program provides organizations with additional time to replace incompatible hardware, resolve application dependencies, and transition to Windows 11.
According to Microsoft's official ESU documentation, coverage is limited to qualifying security updates and does not extend the operating system's normal support lifecycle.
What Windows 10 ESU includes
Eligible, properly enrolled devices can receive security fixes for vulnerabilities Microsoft classifies as Critical or Important.
These updates help reduce exposure to newly discovered Windows vulnerabilities while organizations complete their migrations.
What Windows 10 ESU does not include
ESU does not restore the full range of services available during standard Windows support.
It excludes:
- New Windows features and functionality.
- Customer-requested nonsecurity updates.
- General performance improvements and design changes.
- Standard technical support for unrelated Windows problems.
- Guaranteed compatibility with future applications, drivers, or hardware.
Microsoft limits ESU-related support to licensing, installation, and possible regressions associated with the updates themselves, subject to applicable support arrangements.
ESU provides temporary security coverage, not a fully supported operating system.
An endpoint can receive eligible Windows security updates while remaining exposed to vulnerabilities in unsupported applications, firmware, or third-party components.
Windows 10 ESU Timeline: Key Dates for 2026 and Beyond
The standard commercial Windows 10 ESU program consists of three annual coverage periods.
Milestone | Date | Significance |
Standard Windows 10 support ended | October 14, 2025 | Regular security updates and general support ended |
Commercial ESU Year 1 ended | October 13, 2026 | First extended coverage period concluded |
Commercial ESU Year 2 began | October 14, 2026 | Second-year licensing and activation became relevant |
Commercial ESU Year 2 ends | October 12, 2027 | Second extended coverage period concludes |
Commercial ESU Year 3 ends | October 10, 2028 | Final scheduled commercial coverage period concludes |
These dates follow Microsoft's published product lifecycle schedule.
What changed for Windows 10 ESU in October 2026?
The transition to ESU Year 2 introduces an immediate responsibility for organizations that continue operating Windows 10.
Administrators must verify that retained endpoints have the appropriate second-year entitlement, that the entitlement is activated, and that applicable security updates are being installed successfully.
Successful Year 1 activation does not, by itself, establish that a device is correctly licensed and activated for Year 2.
For MSPs, this creates an additional compliance and reporting requirement across customer environments.
What IT teams should verify for ESU Year 2
Organizations retaining Windows 10 endpoints should complete the following checks:
- Confirm the installed Windows edition and version. Standard commercial ESU requirements apply to eligible version 22H2 devices. Long-term servicing editions have separate arrangements.
- Review the current ESU license. Confirm that the organization has purchased the appropriate Year 2 entitlement or qualifies for a separate cloud-based entitlement.
- Verify the required preparation packages. Ensure the device satisfies Microsoft's commercial activation prerequisites, taking account of newer superseding packages.
- Confirm Year 2 activation. For MAK-activated devices, verify that the correct annual ESU program reports a Licensed status. Cloud-entitled devices require their applicable eligibility and configuration checks.
- Check security update installation. Confirm that the latest applicable updates have installed successfully.
- Review the migration schedule. Identify devices that can be upgraded or retired before the next licensing period.
These checks help distinguish properly covered devices from systems that remain operational but lack necessary licensing or updates.
How Much Does Windows 10 ESU Cost in 2026?
Microsoft lists standard commercial Windows 10 ESU pricing at $61 per device for the first year, with the price doubling for each consecutive year.
At the published pricing model, the costs are:
Commercial ESU period | Price per device |
Year 1, 2025 to 2026 | $61 |
Year 2, 2026 to 2027 | $122 |
Year 3, 2027 to 2028 | $244 |
Total for three years | $427 |
The Year 2 and Year 3 figures follow Microsoft's published annual doubling policy. Actual charges can vary depending on purchasing arrangements, applicable discounts, and licensing terms.
The licensing rules and annual pricing model are described in Microsoft's Windows 10 ESU program documentation.
Why delayed enrollment does not eliminate earlier costs
Commercial ESU coverage is purchased in annual periods. Microsoft does not offer partial-year commercial ESU licenses.
The program is also cumulative.
An organization first enrolling during Year 2 must purchase the preceding year's coverage as well.
At published list prices, a device first enrolled in Year 2 would therefore require $183 in cumulative Year 1 and Year 2 licensing.
Waiting until a later year does not remove the requirement to purchase previous coverage periods.
When Windows 10 ESU may be available at no additional charge
The standard commercial per-device pricing does not apply to every deployment.
Microsoft provides ESU coverage at no additional ESU licensing charge for certain qualifying cloud environments.
These include:
- Azure Virtual Desktop: Eligible Windows 10 single-session and multi-session virtual machines receive ESU coverage without purchasing separate ESU licenses or performing the standard commercial MAK activation process.
- Windows 365 Cloud PCs: Existing eligible Windows 10 version 22H2 Cloud PCs can receive ESU coverage at no additional ESU charge.
- Windows 365-connected physical endpoints: Certain eligible physical Windows 10 devices used to access licensed Windows 365 Cloud PCs can also receive ESU entitlement under Microsoft's licensing and configuration requirements.
- Qualifying Azure virtual machines: Eligible Windows 10 virtual machines running in specified Azure-hosted scenarios can receive extended security coverage under Microsoft's cloud entitlement arrangements.
These benefits are conditional. Organizations must verify the applicable Microsoft service, operating system edition, user or device eligibility, and activation or policy requirements.
For Windows 365-connected physical endpoints, entitlement can depend on the assigned Cloud PC, Microsoft Entra account sign-in, explicit ESU policy configuration, and recurring eligibility validation.
Microsoft states that an administrative tool for identifying which physical endpoints have claimed ESU entitlement through Windows 365 is no longer available. Administrators must therefore maintain their own eligibility and configuration records rather than treating license assignment as conclusive proof of active device entitlement.
Microsoft explains these requirements in its Windows 365 ESU deployment guidance.
Organizations already using Microsoft cloud services should review their existing ESU eligibility before purchasing additional per-device licenses.
How phased migration can reduce ESU licensing costs
Consider an illustrative business with 50 Windows 10 endpoints requiring standard paid commercial ESU licenses.
The organization compares two approaches: retaining all 50 devices for three years or gradually reducing the fleet to 30 devices in Year 2 and 10 devices in Year 3.
Coverage period | Price per device | Retain all 50 devices | Phased migration |
Year 1 | $61 | $3,050 (50 devices) | $3,050 (50 devices) |
Year 2 | $122 | $6,100 (50 devices) | $3,660 (30 devices) |
Year 3 | $244 | $12,200 (50 devices) | $2,440 (10 devices) |
Three-year total | $21,350 | $9,150 |
Under these assumptions, phased migration reduces three-year ESU licensing expenditures by $12,200, approximately 57%.
The comparison assumes every remaining endpoint requires paid commercial coverage at Microsoft's published list prices, with the necessary preceding-year licenses included.
It excludes cloud entitlement exceptions, discounts, taxes, hardware purchases, migration labor, application upgrades, and other operating expenses.
This represents avoided future ESU licensing expenditure, not total migration savings. Hardware replacement and transition costs must be evaluated separately.
Other costs of maintaining Windows 10
ESU licensing is only part of the expense.
Organizations must also account for technician time, software compatibility issues, hardware maintenance, security monitoring, backup requirements, and possible downtime.
The financial decision should compare the remaining cost of operating Windows 10 against the full cost of upgrading or replacing affected devices.
Which Windows 10 Devices Are Eligible for ESU?
Microsoft's standard commercial ESU program applies to eligible Windows 10 version 22H2 devices that meet its licensing and update prerequisites.
For physical commercial endpoints, Microsoft's activation documentation identifies these requirements:
- Windows 10 version 22H2.
- KB5066791 or a later qualifying update.
- An applicable ESU Licensing Preparation Package installed after the required Windows security update.
- Administrative privileges.
- A valid commercial ESU entitlement and activation method.
Microsoft's commercial activation instructions reference preparation package KB5072653. However, Microsoft subsequently published KB5126256 on September 8, 2026, which supersedes earlier ESU licensing preparation packages.
What changed with KB5126256 in September 2026?
Microsoft identifies KB5126256 as an updated licensing preparation package for Windows 10 version 22H2.
It updates components used for ESU enrollment and supersedes previously released licensing preparation packages.
Microsoft recommends installing the latest applicable package so that devices are prepared for enrollment.
Importantly, KB5126256 is not exclusively a consumer update. Microsoft makes it available through several servicing channels, including:
- Windows Update.
- Windows Update for Business.
- Microsoft Update Catalog.
- Windows Server Update Services (WSUS).
The package applies to devices not yet enrolled in ESU. It does not itself enroll a device, activate a license, or install monthly ESU security updates.
Microsoft specifies that a qualifying security update released on or after October 14, 2025, such as KB5066791, must be installed before the preparation package.
Administrators should distinguish the older package referenced in commercial activation instructions from Microsoft's newer superseding package.
For devices that are already enrolled, installing a newer preparation package should not be treated as an automatic annual entitlement renewal.
The installation sequence, servicing channels, and supersedence are documented in Microsoft's September 2026 KB5126256 article.
Commercial and consumer ESU use different enrollment processes
Microsoft provides separate ESU arrangements for commercial organizations and personal-use devices.
Commercial organizations generally use volume licensing and the corresponding Multiple Activation Key (MAK) process.
The consumer ESU program uses a separate enrollment process and provides coverage through October 12, 2027.
The consumer enrollment options include Windows settings synchronization, Microsoft Rewards points, or a one-time purchase, subject to Microsoft's regional eligibility requirements.
Although the programs differ in licensing and enrollment, the underlying preparation packages should not automatically be categorized as exclusively consumer or commercial.
Administrators must follow the applicable program's activation instructions and verify the currently relevant servicing prerequisites.
Microsoft provides further details on its consumer ESU page.
Windows 10 LTSB and LTSC editions have different support timelines
Not every Windows 10 device follows the standard version 22H2 lifecycle.
Long-Term Servicing Branch (LTSB) and Long-Term Servicing Channel (LTSC) editions have separate release schedules and support policies.
This distinction is particularly important for manufacturing systems, embedded devices, specialized workstations, and equipment controlled by dedicated software.
Windows 10 edition | Lifecycle or ESU status |
Enterprise LTSB 2016 | Standard extended support ended October 13, 2026; separate ESU available |
IoT Enterprise LTSB 2016 | Standard extended support ended October 13, 2026; separate ESU available |
Enterprise LTSC 2019 | Supported through January 9, 2029 |
IoT Enterprise LTSC 2019 | Supported through January 9, 2029 |
Enterprise LTSC 2021 | Support ends January 12, 2027; separate ESU program available |
IoT Enterprise LTSC 2021 | Supported through January 13, 2032 under its own lifecycle |
Microsoft's Enterprise LTSC 2021 ESU offer does not apply to Windows 10 IoT Enterprise LTSC 2021.
The 2019 LTSC releases remain within their existing support lifecycle in 2026 and should not be treated as requiring the standard Windows 10 version 22H2 ESU program.
Organizations should verify the exact installed edition and release before selecting a licensing or migration strategy.
Microsoft documents these distinctions in its Windows client lifecycle information and separate LTSB/LTSC ESU activation guidance.
How to Activate and Verify Windows 10 ESU Year 2
For standard commercial Windows 10 version 22H2 ESU, Microsoft uses Multiple Activation Keys obtained through volume licensing.
Administrators with the appropriate permissions can locate their keys in the Microsoft 365 admin center.
The following procedure applies to the standard commercial MAK-based enrollment process. Cloud-entitled devices and certain LTSB/LTSC editions follow different requirements.
Step 1: Confirm the applicable ESU license
Verify that the device requires paid commercial ESU Year 2 coverage and that the organization has the appropriate entitlement.
The Microsoft Entra account used to retrieve the MAK must have the relevant volume-licensing permissions, such as Product Key Reader or VL Administrator.
Step 2: Verify prerequisites
Confirm the installed Windows edition and version, update history, and applicable ESU licensing preparation package.
Use Microsoft's current documentation to determine the appropriate package, including the newer KB5126256 for devices that have not yet enrolled.
The correct preparation sequence matters because the device must satisfy the required Windows security update prerequisites before installing the licensing preparation package.
Step 3: Install and activate the ESU key
Microsoft documents the use of slmgr.vbs to manage commercial ESU licensing.
Administrators can install the appropriate MAK using an elevated Command Prompt:
slmgr.vbs /ipk <ESU-MAK>
After installing the key, activate the corresponding ESU entitlement:
slmgr.vbs /ato <Activation-ID>
For the standard Windows 10 version 22H2 commercial ESU Year 2 program, Microsoft specifies this activation ID:
1043add5-23b1-4afb-9a0f-64343c8f3f8d
The activation command must use the correct ID and an appropriately licensed key.
Step 4: Confirm the Year 2 license status
Run the following command from an elevated Command Prompt:
slmgr.vbs /dlv
Review the output and verify that it identifies the relevant Win10 ESU Year2 program with a License Status of Licensed.
Do not rely solely on a successful Windows operating system activation or an existing Year 1 ESU entitlement.
Microsoft also provides alternative activation procedures for systems unable to contact its activation servers directly.
Step 5: Verify actual security update installation
Successful ESU activation does not establish that every applicable security update has been installed.
Administrators should separately review Windows Update history, identify missing applicable updates, and investigate installation failures.
License entitlement, successful activation, and patch compliance are separate checks.
The complete MAK-based process and activation identifiers are documented in Microsoft's commercial ESU activation instructions.
Why Managing Aging Windows 10 Endpoints Is Increasingly Difficult
ESU allows qualifying Windows vulnerabilities to continue receiving security fixes, but maintaining legacy endpoints involves challenges beyond operating system licensing.
Security coverage remains limited
ESU does not automatically protect unsupported third-party applications, drivers, firmware, or other components.
A device can be fully updated under ESU while still running an outdated application with known vulnerabilities.
Organizations therefore need a security process that includes application maintenance, vulnerability management, and appropriate protective controls.
Legacy applications can block migration
Businesses may retain Windows 10 because important applications have not been validated for Windows 11.
Examples include specialized manufacturing software, custom applications, older peripheral drivers, and programs dependent on obsolete components.
An operating system upgrade without compatibility testing can disrupt business operations.
IT teams should identify these dependencies and work with application vendors to establish supported migration paths.
Aging hardware introduces additional operational risks
Older devices may experience storage failures, thermal problems, deteriorating batteries, or performance limitations.
Some otherwise functional systems also lack hardware features required by Windows 11.
These limitations create different migration requirements. A device may need only an operating system upgrade, while another may require complete hardware replacement.
Patch failures require more investigation
Missing Windows 10 updates can result from licensing problems, failed activation, missing prerequisites, installation errors, or update applicability rules.
IT teams should avoid classifying devices as compliant based only on successful enrollment.
How IT Teams Can Manage Windows 10 Endpoints During ESU
A practical ESU management process should connect device inventory, license verification, patch deployment, security controls, and migration planning.
1. Maintain a reliable Windows 10 inventory
Identify every Windows 10 endpoint that remains in operation.
A useful inventory includes the installed edition and version, hardware specifications, applications, assigned user or business function, and last successful device check-in.
Categorize devices according to their migration requirements:
- Ready for Windows 11.
- Requires replacement hardware.
- Blocked by application compatibility.
- Dependent on specialized equipment.
- Scheduled for retirement.
This helps determine which systems need continued ESU coverage and which can be migrated before the next renewal period.
2. Track ESU compliance separately from general device health
A compliance record should contain enough information to assess each retained endpoint's coverage and update status.
Field | What to record |
Device identification | Hostname, asset ID, and assigned owner |
Windows edition and version | Installed release and servicing channel |
ESU coverage basis | Paid annual license or applicable cloud-based eligibility |
Commercial activation status | Year-specific MAK activation, where applicable |
Cloud eligibility and configuration | Applicable license assignment, device eligibility, policy configuration, and last known validation |
Latest applicable security update | Expected KB or applicable update level |
Last successful installation | Date and update result |
Migration blocker | Hardware, application, or operational dependency |
Target retirement date | Planned upgrade or replacement date |
For MAK-activated devices, administrators can verify the appropriate annual ESU program's activation status.
For Windows 365-connected physical endpoints, verification is different. Microsoft does not provide a current administrative tool that enumerates every endpoint that has claimed an ESU entitlement through Windows 365.
IT teams should therefore maintain supporting records of qualifying license assignments, device and user eligibility, ESU policy configuration, and relevant sign-in or revalidation activity.
Documented cloud eligibility should not be reported as definitive proof of an active claimed entitlement unless that status can be independently established.
Successful installation of applicable ESU security updates provides additional operational evidence that a device is receiving updates, although it does not replace the need to maintain appropriate licensing records.
3. Establish controlled patch deployment
ESU-covered devices still require systematic patch management.
A reliable workflow should:
- Identify newly released Microsoft security updates.
- Confirm their applicability to the installed Windows edition.
- Test updates on representative legacy systems.
- Deploy approved updates through scheduled maintenance windows.
- Monitor deployment results and required restarts.
- Investigate failed or incomplete installations.
Staged deployment is especially useful for devices that depend on older applications or specialized peripherals.
Microsoft's Windows 10 release information provides a reference for published updates and their corresponding builds.
4. Apply additional security controls
Organizations should evaluate risks that ESU does not directly address.
Appropriate measures can include:
- Maintaining supported endpoint protection.
- Restricting unnecessary administrative privileges.
- Using multifactor authentication where supported.
- Limiting exposed services and remote access.
- Segmenting higher-risk legacy systems.
- Maintaining tested backups and recovery procedures.
- Monitoring suspicious activity and unexpected configuration changes.
These controls help reduce exposure, but they do not replace missing operating system security patches.
5. Assign a migration owner and deadline
Every retained Windows 10 device should have a documented reason for remaining in service.
Assign responsibility for resolving the relevant dependency and establish a target migration or retirement date.
Review these dates periodically, particularly before ESU renewal periods.
A device that cannot migrate because of an unsupported application requires a different approach from a workstation that simply needs replacement hardware.
Windows 10 ESU vs. Windows 11 Migration: Which Is More Practical?
The decision to retain Windows 10 should account for both technical requirements and financial consequences.
When ESU provides practical value
ESU is particularly useful when an organization requires additional time to complete a migration.
A critical application may require validation, replacement hardware may not yet be available, or specialized equipment may depend on a Windows 10 configuration.
In these situations, ESU can provide temporary security coverage while the organization resolves the underlying dependency.
When migration should take priority
Devices that meet Windows 11 hardware requirements and run compatible applications are generally stronger candidates for an earlier migration.
Continuing to purchase ESU for these devices may provide limited operational value when a supported configuration is already available.
Devices that cannot meet Windows 11 requirements should be assessed for replacement or another supported computing arrangement.
Evaluate the complete cost
ESU licensing costs increase annually, but replacement decisions should not be based on licensing alone.
Organizations should evaluate the remaining cost of maintenance, technician workload, application compatibility, security exposure, and potential downtime.
A complete comparison includes migration expenses, new hardware, software licensing, and the costs of operating existing systems.
The appropriate decision depends on the actual requirements and remaining useful life of each endpoint.
What About Microsoft 365 Apps on Windows 10?
Microsoft 365 Apps have a separate support arrangement from the Windows 10 operating system.
Microsoft states that security updates for Microsoft 365 Apps running on Windows 10 will continue through October 10, 2028.
However, Microsoft 365 Apps on Windows 10 remain subject to limitations after Windows 10 reaches end of support.
Under Microsoft's announced arrangement, Windows 10 devices remain on Microsoft 365 Apps version 2608 and receive security-only updates through the extended period.
Microsoft also states that the OneDrive desktop application on Windows 10 version 22H2 will continue receiving updates through October 10, 2028.
These application-level updates do not extend Windows 10 operating system support.
An endpoint may continue receiving Microsoft 365 Apps security updates while requiring separate ESU coverage to receive qualifying Windows operating system security fixes.
Microsoft explains the arrangement in its Microsoft 365 Apps support guidance for Windows 10.
How MSPs Can Manage Windows 10 ESU Across Multiple Clients
For MSPs, the challenge is not limited to maintaining individual endpoints.
Each customer may have different licensing arrangements, legacy applications, hardware replacement schedules, and compliance requirements.
Standardize reporting across clients
MSPs should establish a consistent reporting process for retained Windows 10 endpoints.
Useful measures include:
- Total Windows 10 devices by customer.
- Devices with verified current commercial ESU activation.
- Devices with documented cloud ESU eligibility and configuration.
- Devices missing applicable security updates.
- Devices with unresolved licensing, activation, or entitlement issues.
- Endpoints blocked by hardware or application dependencies.
- Devices scheduled for migration or retirement.
This provides technicians with an operational view and helps account managers communicate the remaining work to customers.
Cloud entitlement reporting should distinguish verified prerequisites from entitlement states that Microsoft does not expose through its administrative tools.
Identify devices that require exceptions
Not every Windows 10 endpoint can follow the same patch or migration schedule.
Specialized systems may need extended testing, vendor approval, or restricted network access.
Document the reason for each exception, its compensating security controls, its owner, and its planned resolution.
This prevents temporary accommodations from becoming unmanaged long-term risks.
Review migration costs with customers
ESU licensing provides an opportunity to revisit customer endpoint replacement plans.
Rather than automatically renewing every remaining Windows 10 device, MSPs can use inventory and cost information to identify which systems should be upgraded or replaced first.
A phased approach can help customers distribute migration work over time while reducing future ESU licensing requirements.
MSPs should also evaluate whether customers already qualify for Microsoft cloud-based ESU entitlements before recommending additional licenses.
How Level Helps IT Teams Manage Aging Windows Endpoints
Maintaining Windows 10 systems during the ESU period requires accurate device information, reliable patch deployment, and the ability to troubleshoot systems without unnecessary disruption.
Level provides remote monitoring and management capabilities that can help IT teams maintain operational visibility while planning their transition away from Windows 10.
Identify Windows 10 devices through centralized inventory
Level's hardware and software inventory provides device information across managed Windows, macOS, and Linux endpoints.
Technicians can search and filter devices using operating system and other inventory information, organize endpoints with groups and tags, and export matching device information to CSV.
This can help teams establish the Windows 10 population requiring further review.
For example, technicians can use inventory data to identify Windows 10 endpoints, then maintain associated ESU licensing and migration records as part of their broader management process.
Manage applicable updates through patch automation
Level's patch management capabilities support operating system updates and third-party application maintenance.
Teams can build automated patch workflows, schedule maintenance, apply updates to selected device groups, and monitor failures.
Staged rollout controls also allow technicians to test updates before broader deployment.
For Windows 10 devices enrolled in ESU, Level can assist with the operational deployment and monitoring of applicable updates.
Level does not provide Microsoft ESU licensing or automatically establish that a device has the appropriate ESU entitlement. Administrators remain responsible for confirming Microsoft's licensing, eligibility, and activation requirements.
Troubleshoot legacy endpoints remotely
Level also provides monitoring and alerting, remote access, and scripting tools that help technicians investigate endpoint issues.
These capabilities are especially useful when older devices are distributed across offices, remote locations, or multiple customer environments.
Technicians can investigate operational problems and perform supported maintenance tasks without relying exclusively on on-site intervention.
Combined with centralized inventory and patch management, these capabilities can help organizations maintain oversight of aging Windows endpoints as they complete their migration plans.
Explore Level's RMM features to see how centralized endpoint management can support ongoing IT operations and Windows migration planning.
Final Thoughts
Windows 10 Extended Security Updates give organizations additional time to manage devices that cannot immediately move to Windows 11.
Entering commercial ESU Year 2 in October 2026 brings renewed licensing, activation, and security update verification responsibilities. Organizations should also account for different LTSC lifecycles, cloud-based entitlement exceptions, and increasing maintenance costs.
The practical priority is to identify which endpoints genuinely require continued coverage, verify their security update status, and maintain a realistic migration schedule.
For MSPs and internal IT departments, successful Windows 10 management means protecting necessary legacy systems while steadily reducing reliance on extended support.
Frequently Asked Questions
1. Can Windows 10 still receive security updates in 2026?
Yes. Eligible Windows 10 version 22H2 devices enrolled in Microsoft's Extended Security Updates program can continue receiving qualifying Critical and Important security updates. Commercial customers can obtain up to three years of extended coverage beyond October 14, 2025, subject to licensing and eligibility requirements. Certain LTSB and LTSC editions follow separate support arrangements.
2. How much does Windows 10 ESU cost for businesses in 2026?
Microsoft lists standard commercial ESU at $61 per device for Year 1, with prices doubling each consecutive year. The published pricing model therefore places Year 2 at $122 per device. Organizations first enrolling in Year 2 must also purchase the preceding coverage year. However, certain eligible Azure Virtual Desktop, Windows 365, and other qualifying cloud deployments can receive ESU coverage at no additional ESU licensing charge.
3. Can organizations continue using Windows 10 without ESU?
Yes. Windows 10 devices generally continue functioning after standard support ends. However, standard Windows 10 installations without qualifying ESU coverage no longer receive regular Windows security fixes. Antivirus software, network controls, and other protective measures can reduce exposure but cannot replace missing operating system security updates.
4. Does RMM software replace the need for Windows 10 ESU?
No. Remote monitoring and management software helps IT teams monitor devices, automate maintenance, deploy applicable updates, and troubleshoot endpoint problems. It does not provide Microsoft ESU entitlements or make unsupported Windows installations eligible for security fixes. Organizations must satisfy Microsoft's licensing, eligibility, and activation requirements separately.
