Windows 10 22H2 and Office 2016/2019 End of Support: What to Do by Oct 14, 2025

Microsoft has set a hard deadline: on October 14, 2025, routine security updates and mainstream support end for Windows 10 (version 22H2) and for perpetual releases Office 2016 and Office 2019 — a coordinated sunset that forces consumers and organizations to choose between upgrading, buying limited extended protection, or running unsupported software that will steadily accumulate risk. (support.microsoft.com)

---

Background / Overview​

Microsoft’s lifecycle program establishes firm end‑of‑servicing dates so engineering effort can be focused on current platforms. For Windows 10 (final servicing release: 22H2) and a broad set of Office-era products, October 14, 2025 is the point when Microsoft stops shipping regular monthly security fixes, feature updates, and standard technical support. The company’s published lifecycle notices and support pages confirm the date and the consequences for both operating systems and Office suites. (learn.microsoft.com)
At the same time Microsoft published transition guidance: it is recommending upgrades to Windows 11 where hardware supports it, offering a limited Windows 10 Consumer ESU (Extended Security Updates) bridge for one year, and urging Office users to migrate to Microsoft 365 Apps or consider Office LTSC 2024 for scenarios where a perpetual, long‑term servicing channel is required. These are official vendor options; understanding each one’s scope, cost, and limits is essential before deciding. (blogs.windows.com)
The BornCity post that prompted this series likewise highlighted the dual deadline and the lack of an ESU program for Office perpetual releases — a detail confirmed by Microsoft and widely reported.

---

What exactly ends on October 14, 2025?​

• Security updates (OS-level and product-level) for Windows 10 (22H2) and for Office 2016/2019 stop being issued to non-enrolled devices.
• Technical support from Microsoft (phone/chat/official troubleshooting) ends for those specific versions.
• Feature and quality updates cease for Windows 10 mainstream SKUs; Office 2016/2019 receive no further security or bug fixes after the date.
• Some Microsoft‑managed product timelines are staggered — for example Microsoft 365 Apps receives special handling when tied to Windows platform support — but the Office 2016/2019 line has a fixed end date with no ESU bridge. (support.microsoft.com)

This means that while installed software will continue to run after the cut‑off, it will do so without vendor patches — a progressively worsening security posture as new vulnerabilities are discovered and weaponized.

---

Windows 10 Extended Security Updates — what Microsoft offers (and at what cost)​

Microsoft created a tailored ESU offering for Windows 10 to ease the transition for both consumers and commercial customers. The headline points are:

• Consumer ESU (one year): Available through three enrollment paths — free if you sync your Windows Backup settings to a Microsoft account, redeem 1,000 Microsoft Rewards points, or purchase ESU for $30 USD (or local equivalent). Coverage runs through October 13, 2026. Enrollment requires the device to be on Windows 10, version 22H2, and to sign in with a Microsoft account during enrollment. Microsoft’s rollout included an in‑OS enrollment wizard. (support.microsoft.com)
• Commercial / Enterprise ESU (up to three years): Sold through volume licensing and Cloud Service Providers. Year‑one pricing (commercial list) is $61 per device with prices doubling in successive years (Year Two, Year Three), reflecting an intentional escalation to encourage migration. ESU delivers security‑only updates (Critical and Important fixes); it does not include new features, non‑security bug fixes, or general product support. (learn.microsoft.com)
• Eligibility & limits: ESU updates require devices on 22H2, and consumer enrollment ties multiple devices (up to a limit) to a Microsoft account. ESU is expressly a time‑bound bridge — not a long‑term replacement for upgrading. (learn.microsoft.com)

Independent press outlets and specialist sites have repeated and clarified these points during the rollout; those reports match Microsoft’s published pricing and enrollment methods. (windowscentral.com)

---

Office 2016 and Office 2019: no ESU — what that means​

Unlike Windows 10, Microsoft has stated there will be no Extended Security Update (ESU) program for the perpetual Office releases (Office 2016 and Office 2019). After October 14, 2025, Microsoft will not deliver security updates or provide technical support for these Office versions. Microsoft’s migration guidance points customers toward Microsoft 365 Apps (subscription/cloud) or Office LTSC 2024 (volume licensed, fixed lifecycle) as the supported alternatives. (support.microsoft.com)
That lack of an ESU path for Office perpetual releases creates a sharp distinction:

• Windows 10 users who need more time can buy into ESU for a limited period.
• Office 2016/2019 users cannot buy an official patching bridge from Microsoft and therefore must either upgrade/migrate their Office installations or accept growing unpatched risk. This is a significant operational factor for businesses and for users with complex Access databases, macros, or legacy integrations. (techcommunity.microsoft.com)

---

Why Microsoft is pushing this change (short version)​

• Engineering focus: Maintaining compatibility with older platforms consumes resources. Consolidating development on Windows 11 and modern Office channels reduces fragmentation.
• Security and telemetry: New foundations, security primitives, and cloud integrations are easier to maintain on a narrower surface area.
• Business model: Subscription cloud services (Microsoft 365) deliver continuous updates and telemetry that drive feature innovation and recurring revenue; Microsoft has consistently pointed customers to those options. (techcommunity.microsoft.com)

These are practical reasons — but they have real tradeoffs for users who cannot upgrade hardware, run on-premises line‑of‑business (LOB) apps, or have strict regulatory constraints.

---

Immediate implications and risks​

• Security risk: Unpatched Office vulnerabilities are attractive targets for attackers. Running unsupported Office builds leaves desktop clients and integrated macros exposed. (support.microsoft.com)
• Compliance risk: Organizations bound by regulatory audits or internal policies may find unsupported software violates controls. Unsupported software can complicate insurance and liability assessments.
• Compatibility and interoperability: Cloud services and new Office features may drift away from legacy client compatibility, producing glitches or breakages over time. Microsoft warns of potential service degradation when older clients interact with modern cloud APIs. (support.microsoft.com)
• Operational cost: Forced last‑minute upgrades or emergency migrations can be far more expensive than planned, phased upgrade programs.
• Third‑party support: Vendors and ISVs may withdraw support for older Office and Windows combinations, creating knock‑on impacts for LOB applications.

---

Migration and mitigation options — consumer and small business playbook​

Below are concrete, prioritized options with practical steps.

1) If your PC is eligible for Windows 11 (best long‑term path)​

• Check compatibility with PC Health Check or the official Windows 11 requirements.
• Back up your data (use Windows Backup / cloud storage).
• Install Windows 11 via Settings → Windows Update or vendor recovery media.
• Migrate Office: if you have Office 2016/2019 perpetual installs, plan for:
• Moving to Microsoft 365 Apps (subscription, continuous updates), or
• Buying Office LTSC 2024 (perpetual, volume license/IT‑controlled) if you need a static, no‑feature‑update install.
• Test critical applications (macros, add‑ins, LOB files) before rolling out. (support.microsoft.com)

2) If your PC cannot run Windows 11 but you want to stay supported short‑term​

• Enroll in Windows 10 Consumer ESU (if you qualify) to receive security patches through Oct 13, 2026:
• Use the Settings → Windows Update enrollment wizard when it appears.
• Sign into a Microsoft account (required). Options: free via backup sync, redeem 1,000 Rewards points, or pay $30 USD per account. (support.microsoft.com)
• For Office 2016/2019: because there is no ESU, migrate Office:
• For home users: purchase Microsoft 365 Personal/Family (cloud, continuous updates).
• For small businesses: consider Microsoft 365 Business plans or Office LTSC 2024 if offline/perpetual is required. (microsoft.com)
• Harden the device: install reputable EDR/antivirus, enable network segmentation for high‑risk devices, and limit internet‑facing services. Consider using browsers in isolation or running document viewing in cloud sandboxes.

3) If you plan to defer upgrades indefinitely (higher risk)​

• Apply compensating controls: strict network isolation, robust endpoint protection, frequent backups, and explicit acceptance of risk in governance documents.
• Consider third‑party micropatching services that provide emergency in‑memory fixes for unpatched products — these are not Microsoft‑supported and carry operational tradeoffs.

---

Enterprise and IT administrator playbook (priority actions)​

• Inventory and prioritization: identify all systems running Windows 10/Office 2016/2019 and categorize by criticality and exposure.
• Testing and compatibility: test Windows 11 upgrades and Microsoft 365 Apps or Office LTSC 2024 in a staging environment; verify LOB app compatibility.
• ESU procurement planning: if ESU (commercial) is required, begin procurement early: Year‑one pricing is known and subsequent years escalate. Budget accordingly. (learn.microsoft.com)
• Security posture: harden exposed systems, accelerate migration for externally facing endpoints, and patch third‑party software.
• Communicate and train: inform users about changes to sign‑in requirements (consumer ESU requires Microsoft account), remediation timelines, and new workflows.
• Regulatory check: coordinate with compliance teams to document compensations and timelines.

---

Office-specific migration notes​

• Access and macros: Access desktop databases, macros, and VBA solutions are common blockers. Options:
• Move to Microsoft 365 Apps where Access desktop is included (subscription).
• Migrate data to SQL Server or Azure SQL and modernize front‑ends (longer journey).
• Use Office LTSC 2024 for stable on‑premises desktops where feature freeze is acceptable. (techcommunity.microsoft.com)
• Exchange and Skype for Business servers: Exchange Server 2016/2019 and Skype for Business Server 2015/2019 reach EOS around the same timeframe; Microsoft published separate options for server ESUs in some instances but timelines and conditions differ. Plan mail migrations carefully. (computerworld.com)
• Office LTSC 2024 vs Microsoft 365 Apps: LTSC is suitable for regulated, locked‑down environments that cannot accept ongoing feature updates; Microsoft 365 Apps provide continuous security and feature updates, cloud integration and AI features. The choice will depend on update policy, budget, and technical constraints. (microsoft.com)

---

Alternatives to Microsoft’s recommended path​

• Switch to a different OS: Chromebooks or Linux distributions (Ubuntu, Mint, or enterprise distributions) are viable for many users whose workflows are browser‑centric or who use cloud apps.
• Cloud desktops / DaaS: Windows 365 Cloud PC or Azure Virtual Desktop can be used to move workloads into supported cloud images — sometimes a faster path than replacing large fleets. (learn.microsoft.com)
• Third‑party micropatching: Commercial micropatching vendors offer emergency fixes for legacy products. These can be useful stopgaps but are not a substitute for an official vendor support contract.

---

Costs: direct and hidden​

• Direct license cost: Microsoft 365 subscriptions, Office LTSC purchase/licensing, Windows 11‑capable hardware if you replace PCs, or ESU fees ($30 consumer / $61 commercial first year).
• Migration labor: application testing, redeployment, retraining, and downtime.
• Operational overhead: additional security tooling, staging images, or cloud subscription changes.
• Compliance/insurance: uncovered risk from unsupported software may raise premiums or violate contractual requirements.

Early planning reduces the chance of emergency spending; budget teams should model several scenarios (fast migration, phased migration with ESU bridges, and appliance replacement).

---

Timeline and checklist (recommended)​

• Today – Early September 2025
• Inventory installations of Windows 10 (22H2) and Office 2016/2019.
• Identify high‑risk/external endpoints and LOB dependencies.
• Evaluate Windows 11 eligibility and necessary hardware changes.
• Within 2–4 weeks
• Begin testing Windows 11 in a pilot group (on eligible devices).
• Decide Office migration path (Microsoft 365 vs Office LTSC 2024).
• For non‑eligible devices, plan ESU enrollment workflow and permissions.
• By October 1, 2025
• Have a migration or ESU enrollment schedule in place.
• Communicate to end users and stakeholders about cut‑over and acceptable use.
• October 14, 2025
• Microsoft stops mainstream security updates for Windows 10 and support for Office 2016/2019.
• Devices not enrolled in ESU will no longer receive OS security patches; Office perpetual users receive no further fixes.
• Oct 15, 2025 – Oct 13, 2026
• Consumer ESU window (if enrolled) for Windows 10 devices; Office perpetual builds receive no ESU. (support.microsoft.com)

---

Strengths and weaknesses of Microsoft’s approach (critical analysis)​

Strengths

• Clear, fixed dates provide unambiguous migration planning milestones.
• ESU for Windows 10 gives a short runway for consumers and enterprises to migrate.
• Microsoft 365 Apps and Office LTSC 2024 present clear supported alternatives for different needs. (learn.microsoft.com)

Weaknesses / Risks

• No ESU for Office 2016/2019 forces immediate migration for Office users with no official patching bridge.
• Consumer ESU requires a Microsoft account for enrollment — a point of friction for privacy‑minded users and organizations that prefer local accounts. (support.microsoft.com)
• The one‑year consumer ESU window is short and may not be enough for large environments or complex LOB migrations, increasing the risk of rushed or incomplete migrations.
• The pricing escalation model for commercial ESU can become expensive if organizations rely on ESU for multiple years.

Where Microsoft provides clarity, the policy also compresses timelines in a way that can punish lagging or cash‑constrained organizations.

---

Final recommendations​

• Treat October 14, 2025 as a hard milestone and build a migration project plan now.
• If your device is eligible for Windows 11, plan to upgrade and move Office workloads to supported channels.
• If your device cannot run Windows 11, enroll immediately in the Windows 10 consumer ESU (or procure commercial ESU) if you require an extension — be mindful of the enrollment prerequisites (22H2, Microsoft account) and the coverage window to Oct 13, 2026. (support.microsoft.com)
• For Office 2016/2019 users, migrate to Microsoft 365 Apps or adopt Office LTSC 2024 for locked‑down environments; do not expect an ESU bridge from Microsoft for perpetual Office products. Begin compatibility testing for Access macros, add‑ins, and integrations. (microsoft.com)
• Use third‑party micropatching and isolation strategies only as stopgaps and document compensating controls for compliance purposes.

---

Microsoft’s October 14, 2025 deadline is less a surprise and more an inflection point. It forces choices that balance security, cost, and operational constraints. For many, the path is straightforward: upgrade eligible hardware to Windows 11 and move productivity to Microsoft 365 or Office LTSC 2024. For those who can’t or won’t, the ESU program for Windows 10 provides a tightly bounded lifeline — while Office 2016/2019 users will need to take immediate migration action because no ESU is available for those Office perpetual releases. Plan now, test early, and prioritize the most exposed assets; that approach turns a looming risk into a manageable IT program. (support.microsoft.com)

---

Source: BornCity End of support for Windows 10 and Office 2016/2019 in October 2025 – Part 1 | Born's Tech and Windows World