Windows 11 22H2 (W) End of Life: Oct 8, 2024 Action Plan

What Changes on October 8, 2024

On October 8, 2024, Microsoft will end all support for Windows 11 22H2 (the "W" version, build 10.0.22621). This is not a long-term servicing (LTS) release, so the cut-off is absolute. After that date:

• No new security patches will be issued.
• No bug fixes or stability updates will be released.
• Microsoft’s support SLAs expire — no phone, chat, or web case options.
• Devices will continue to function, but any newly discovered vulnerabilities will remain unpatched.

Why Full Migration Is No Longer Realistic

Given the 3-month window — approximately 12 weeks from today — migrating every affected device to a newer Windows version (e.g., Windows 11 23H2 or 24H2) is not feasible for most estates, especially those with custom applications, peripheral dependencies, or large-scale deployment processes. Assessment, testing, validation, and staged rollouts take time. A rushed migration carries higher risk of incompatibility and operational disruption.

What to Do in the Time Left: A 12-Week Action Checklist

Instead of attempting an unrealistic migration, focus on containment, hardening, and continuity. Use the following week-by-week plan to minimize exposure.

Week 1–2: Complete Inventory

• Identify every system running Windows 11 22H2 (W) using your asset management tool (SCCM, Intune, or third-party agent).
• Document the role of each device: user workstation, shared kiosk, developer machine, etc.
• Capture current patch status and any known deviations from baseline configuration.

Week 3–4: Isolate High-Risk Devices

• For systems that cannot be upgraded or replaced, apply network segmentation. Restrict inbound/outbound access to only essential services.
• Move devices with internet-facing applications or users with admin privileges to a separate VLAN with limited egress.
• Consider using Windows Defender Application Control or similar tools to block unauthorized executables.

Week 5–6: Harden Against Known Exploit Vectors

• Apply all remaining available updates from Microsoft (cumulative update for August/September 2024). After October 8, no further patches will be published.
• Enable Credential Guard, reduce local admin rights, and enforce strong password policies.
• Review and tighten firewall rules. Disable unnecessary services and ports.

Week 7–8: Document Exposure for Auditors and Insurers

• Create an inventory report that lists each EOL device, its business justification, and the risk acceptance or mitigation plan.
• If your organization carries cyber insurance, notify the underwriter or broker about the upcoming unsupported devices. Some policies require an exemption or waiver for EOL systems.
• Prepare a memo for internal audit detailing the timeline, the measures taken, and the residual risk.

Week 9–10: Procure Post-EOL Support

• Contact a third-party maintenance provider to arrange coverage for Windows 11 22H2 (W) from October 8 onward. Third-party support can deliver custom patches and security fixes for specific CVEs after Microsoft’s cutoff.
• Ensure the contract covers critical, high, and medium severity vulnerabilities for the specific build (10.0.22621).
• Confirm escalation paths and SLA response times before signing.

Week 11–12: Final Readiness Check

• Test that isolation controls are working — verify that segmented devices cannot reach sensitive internal assets or the internet unless explicitly allowed.
• Validate that the third-party support onboarding process is complete (e.g., agent deployment, reporting dashboard access).
• Update your incident response playbook to account for the fact that these devices will not receive automated patches from Microsoft.

A Realistic Post-October 8 Stance

After October 8, your Windows 11 22H2 (W) devices will be on a private support runway. You’ll rely on network controls, application whitelisting, and a third-party support contract to mitigate risk until migration can be completed in a later planning cycle. Continue tracking upgrade readiness for Windows 11 23H2 or 24H2, and schedule migration waves only after proper regression testing.

For more information on Microsoft’s lifecycle, see the official Microsoft lifecycle page or the community-maintained lifecycle source. To discuss post-EOL support options, contact us.