Yesterday, October 13, 2026, marked another important milestone in Microsoft’s product lifecycle, but for many organizations, the conversation is far from over. While some businesses have successfully moved beyond aging systems, others are now facing a critical decision: renew Extended Security Updates (ESU), accelerate upgrades, or accept the risks of running unsupported technology.
The challenge is that end-of-support planning is rarely as simple as replacing every device at once. A frontline employee’s workstation may be ready for Windows 11, while a specialized system running a business-critical application could require additional time and protection. At the same time, cyber insurance requirements, compliance obligations, and security best practices continue to raise the stakes for organizations that fall behind on updates.
Before approving another year of coverage or assuming you’re fully protected, it’s worth taking a closer look at what’s actually reached end of support, what still qualifies for extended coverage, and what steps can help reduce business risk. The most successful organizations are approaching these decisions strategically, using ESU as a bridge to modernization rather than a permanent destination.
Key Takeaways
- Renew selectively: Windows 10 devices that still need ESU require Year Two coverage. Treat that purchase as time to finish a transition, not a reason to postpone one.
- Separate everyday devices from business exceptions: A standard office computer and a machine running an irreplaceable application may need different decisions.
- Check more than Windows 10: Windows Server 2012 and certain Windows 11 editions and releases also reached support deadlines on October 13, 2026.
- Match insurance answers to actual conditions: Confirm support and patch status before describing your security controls on an application.
- Inventory comes first: Record each system’s coverage, business purpose, and next step before approving another round of renewals.
Renew, Migrate, or Retire?
The most useful question is not “How old is this computer?” It is “What prevents us from moving it?” A device used for email, documents, and browser-based applications presents a different decision from one connected to specialized equipment or an older business application.
If the hardware supports Windows 11 and the applications are ready, migration may avoid another ESU purchase. If the hardware cannot make the move, compare replacement with the cost of keeping it another year. If the device no longer serves a necessary purpose, retirement may be the simplest answer.
What Another Year Actually Buys
Commercial ESU is purchased one year at a time, with the price doubling each year. Coverage is cumulative, so entering in a later year also requires paying for the preceding years.
| ESU Year | Coverage Ends | Per-Device Cost | Total Across Purchased Years |
|---|---|---|---|
| Year One | October 13, 2026 | $61 | $61 |
| Year Two | October 12, 2027 | $122 | $183 |
| Year Three, final | October 10, 2028 | $244 | $427 |
Across all three years, ESU costs $427 per device, a meaningful share of a new business desktop that would last about five years. Those fees buy continued security updates, not newer hardware or application compatibility. That can be money well spent when it prevents a rushed business disruption. It becomes harder to justify when nothing is blocking the move and no replacement date has been set.
Two Computers, Two Sensible Decisions
Consider a hypothetical business with two Windows 10 computers. One handles email and scheduling. It cannot run Windows 11, and no application requires keeping it. Replacing it avoids spending another year’s coverage on hardware that still needs to go.
The second runs a scheduling application connected to specialized equipment. Its replacement needs vendor testing before the business can switch. Renewing commercial ESU may be the better short-term choice, provided the business sets a testing milestone and a migration date.
The distinction is the reason for waiting. “We need time to test this application” supports a plan. “The computer still works” does not explain when the spending will stop.
Check Which ESU Program You Have
Microsoft’s consumer and commercial ESU programs are not interchangeable. Consumer ESU is not licensed for business use, and devices joined to a company directory or managed by a device management platform are excluded. For business devices, confirm that the coverage applies to the machines that need it. A device receiving updates is not, by itself, a complete record of its licensing and support status.
Already on Windows 11? Check the Release Too
Moving away from Windows 10 does not remove the need to track support. A computer can display “Windows 11 Pro” and still be running a release that no longer receives security updates.
Windows 11 24H2 Home and Pro reached that point on October 13, 2026. Enterprise and Education editions of the same release have a different support window. The inventory therefore needs the edition and release, not just the Windows name.
For these devices, the decision may be a release update rather than a hardware replacement. Check whether settings intended to delay disruptive updates have also delayed the move to a supported release.
Why Working Equipment Still Needs a Decision
Support ending does not stop a computer from booting or an application from opening. That is what makes the issue easy to defer: employees may notice nothing different.
What changes is the availability of security fixes. Keeping a system in service without them leaves the business carrying risk that routine patching can no longer address. The response should match the system’s importance and exposure, but continued operation is not evidence that the risk has stayed the same.
The Server Nobody Remembered to Replace
The systems most likely to complicate this plan may not be sitting on anyone’s desk. An older server can remain at a backup site, exist as a rarely used virtual machine, or sit inside vendor-managed equipment. An inventory entry such as “backup server” tells you its purpose, but not whether its operating system is supported.
Windows Server 2012 and 2012 R2 reached the end of their final ESU period on October 13, 2026. For these systems, another annual renewal is no longer the answer. The work is to identify what depends on them and plan retirement or migration.
This is why the inventory should include business purpose as well as technical details. Before switching something off, establish what would stop working with it.
The Next Decisions on the Calendar
| Deadline | Systems Affected | Business Decision |
|---|---|---|
| October 13, 2026, already passed | Windows 10 ESU Year One; Server 2012 and 2012 R2 ESU; Windows 11 24H2 Home and Pro | Confirm Year Two coverage where appropriate, migrate older servers, and update affected Windows 11 devices. |
| November 2026 | Windows 11 23H2 Enterprise and Education | Plan the move to a supported release. |
| January 12, 2027 | Windows Server 2016 extended support | Choose migration or confirm eligibility and cost for ESU. |
| October 12, 2027 | Windows 10 ESU Year Two | Complete the transition or budget for the final coverage year. |
Server 2016 deserves attention now because moving a server can involve application testing, vendor coordination, and planned downtime. A typical server migration takes three to six months from assessment to cutover, which means the window before January 12, 2027 is already tight. Before committing to a completion date, establish those dependencies. If migration cannot finish before support ends, confirm the available coverage rather than assuming an extension will fit.
Insurance: Check the Answers Before Renewal
An insurance application should describe the environment that exists, not the one planned for later in the quarter. Before answering questions about supported operating systems and regular patching, compare them with the inventory and current coverage records.
Unsupported systems can raise questions about exclusions, security-control commitments, and disclosure obligations. The effect depends on the policy and circumstances. If coverage has lapsed or a system must remain unsupported, discuss the actual situation with the broker rather than assuming either that coverage is unaffected or that a claim will automatically be denied.
The most important mistake to avoid: answering “yes” to a security question without confirming it. An inaccurate answer can put a future claim at risk, while an exception disclosed with a replacement plan is something a broker can work with.
Keep the supporting information together: affected systems, current coverage, temporary protections, and planned replacement dates. Insurance renewal is a checkpoint for that work, not a reason to leave a known gap unresolved until renewal season.
If You Handle Regulated Data
Older systems may also need attention in compliance reviews, particularly when they handle health information, payment data, or other regulated information. Include them in the applicable risk assessment and document the transition decision. Insurance review and compliance review are related tasks, but one does not replace the other.
When a System Cannot Move Yet
Some applications and equipment need more time. Start by distinguishing a system that still has an ESU option from one that has exhausted its support. Those are different situations, even if both require a replacement project.
For a system that must temporarily remain unsupported, the transition plan should address restricted access, separation from other systems, monitoring, and limits on what software can run. These measures reduce exposure; they do not restore vendor support or guarantee acceptance by an insurer or auditor.
Give the exception a named business owner, a documented reason, and a replacement date. Review progress against milestones so a temporary accommodation does not quietly become permanent.
Your Action Plan
Quick Wins: Establish What Needs Attention
- Confirm the inventory. Include devices, servers, backup locations, and vendor-managed equipment. Record operating system, edition, release, business purpose, and coverage status.
- Check Windows 10 renewals. Match Year Two coverage to the devices that actually need to remain on Windows 10.
- Identify immediate gaps. Look for Server 2012 systems and Windows 11 releases that have passed their support deadline.
- Review insurance answers. Compare the last application with current conditions and raise any discrepancies with the broker.
This Quarter: Turn the Inventory Into Decisions
Assign every affected system one outcome: renew, migrate, or retire. For renewals, record what the additional time will accomplish. For migrations, identify application dependencies and acceptable downtime. For retirement, confirm that no necessary service or data will be lost.
Prioritize systems without remaining support options and make the Server 2016 decision before its January deadline. Track the decisions and near-term milestones within the quarter, while setting realistic completion dates for work that depends on vendors or specialized equipment.
For South Florida businesses, a review of current coverage and replacement priorities can be a useful conversation whenever you’re ready.
