Windows 10 22H2 EOL Oct 14: Containment Plan

What Changes on October 14, 2025?

On that date, Microsoft will stop issuing security patches, bug fixes, or any form of updates for Windows 10 version 22H2 (build 10.0.19045). This is not an LTS release, so there is no paid extended support option from Microsoft. Your vendor SLAs for this OS version will become void. After October 14, any new vulnerability discovered in Windows 10 22H2 will remain unpatched by Microsoft, putting your systems at risk.

Why Full Migration Is No Longer Realistic in 90 Days

A complete migration to Windows 11 or a newer Windows 10 version for an entire enterprise—especially one with custom applications, peripheral dependencies, or compliance requirements—typically takes 6–12 months. With only three months left, most IT teams cannot finish testing, deployment, and user training. The goal now shifts from eliminating Windows 10 22H2 to containing and protecting it until a migration is feasible.

Your 90-Day Action Plan: Week by Week

Use the following checklist to prioritize actions between now and October 14, 2025. Adjust the timeline based on your estate size, but do not skip any step.

Weeks 1–2: Inventory and Risk Assessment

• Discover every instance of Windows 10 22H2 in your environment (including virtual machines, remote office systems, and test/dev machines).
• Identify business-critical systems that cannot be upgraded or replaced quickly. Document the reason for each delay.
• Assess network exposure: Are these machines on a segmented network? Do they have internet access? Can they be isolated?

Weeks 3–4: Isolate and Harden

• Move all Windows 10 22H2 systems to a dedicated VLAN with restricted egress (only to necessary internal services, no direct internet access).
• Apply existing security baselines (e.g., Microsoft Security Compliance Toolkit) to reduce the attack surface.
• Disable unnecessary services, RDP if not required, and enforce application whitelisting.
• Enable extended logging (e.g., advanced audit policy, Sysmon) on these systems.

Weeks 5–6: Document for Auditors and Insurers

• Create a formal risk acceptance document that lists every Windows 10 22H2 system, its business justification, and the compensating controls you have implemented.
• Present this document to your compliance officer and, if applicable, your cyber insurance provider. Many insurers require explicit acknowledgment of unpatched systems.
• Update your incident response plan to include procedures for handling a compromise on an unsupported OS.

Weeks 7–8: Secure a Third-Party Support Contract

• Evaluate third-party support for Windows 10 22H2. Providers like 3rd Party Support can deliver security patches and technical support after Microsoft's end-of-life date, ensuring you maintain compliance and protection.
• Negotiate a contract that covers the systems you cannot migrate before October 14. Aim for at least a 12-month term to give you time to complete your migration.
• Ensure the support provider can deliver patches for the specific build 10.0.19045 and has a proven track record with Microsoft Windows.

Weeks 9–10: Test and Validate

• Deploy a test patch from your third-party support provider on a non-production Windows 10 22H2 system. Validate that it installs cleanly and does not break applications.
• Run a mock incident response drill assuming one of the unsupported systems is compromised. Verify that your isolation and logging measures work.

Weeks 11–12: Final Preparations

• Confirm your third-party support contract is active and the support portal is accessible.
• Notify all stakeholders (IT team, management, end users) that Windows 10 22H2 will no longer receive Microsoft updates after October 14.
• Schedule a post-EOL review for November 2025 to assess the effectiveness of your controls and plan the next migration wave.

How Third-Party Support Keeps You Safe After EOL

Third-party maintenance for Windows 10 22H2 provides exactly what Microsoft stops offering: security patches, bug fixes, and technical support. Unlike Microsoft's general availability, third-party support is customizable—you pay only for the systems you need covered, and the patches are delivered directly to your environment. This means you can extend the safe life of Windows 10 22H2 by 12 months or more, giving you a realistic window to complete migration without exposing your organization to unpatched vulnerabilities.

Final Steps Before October 14

You have 90 days. Use them to inventory, isolate, document, and contract. Do not wait for a crisis. Contact us today to discuss how we can support your Windows 10 22H2 estate after Microsoft's end-of-life date.