Windows 10 21H2 (LTS) EOL: Jan 2027 Action Plan

Last-Call Action Plan: Windows 10 21H2 (LTS) EOL in 12 Weeks

Microsoft Windows 10 21H2 (LTS) – version 10.0.19044 – reaches end of life on January 12, 2027. That is roughly 12 weeks from today. This is a long-term support release, and its final security patch will arrive before that date. If you still have systems running this edition, a full migration to Windows 11 or a later Windows 10 release is no longer realistic for most estates. The pressing question is: What can you do in the time left to avoid unacceptable risk?

What Changes on January 12, 2027

After the EOL date:

• No more security patches. Microsoft will stop releasing cumulative updates, including fixes for zero-day vulnerabilities.
• No more hotfixes or bug fixes. Any non-security issues will remain unresolved.
• No vendor SLAs. Your existing support contract term ends; Microsoft will no longer respond to support tickets for this OS.

The operating system will still boot and run applications, but it becomes an unmanaged risk. Compliance frameworks, insurance policies, and audit requirements will demand documented mitigation or removal.

Your 12-Week Action Checklist

Work through these steps sequentially. Each block represents approximately two weeks.

Weeks 1–2: Complete Inventory

• Locate every system running Windows 10 21H2 (LTS). Use SCCM, PDQ, or manual network scanning. Confirm the exact build (10.0.19044).
• Record each system’s role, criticality, and network exposure.
• Identify any systems already at EOL that may have been overlooked.

Weeks 3–4: Risk Assessment

• Categorize systems by risk: internet-facing, domain-joined, isolated lab, air-gapped.
• Assess regulatory impact (PCI-DSS, HIPAA, SOX, etc.).
• Determine which systems can be decommissioned immediately vs. those that must remain.

Weeks 5–6: Isolate and Harden

• Segment affected systems on a separate VLAN or subnet.
• Apply strict firewall rules (inbound/outbound) to limit lateral movement.
• Disable unnecessary services and admin accounts.
• Enforce application whitelisting (AppLocker, WDAC) if possible.
• Increase monitoring and alerting on unsupported hosts.

Weeks 7–8: Document Exposure for Auditors and Insurers

• Create a formal register of all unsupported systems, including justification for continued use.
• List each mitigation (isolation, hardening, monitoring).
• Obtain sign-off from system owners, risk management, and legal.
• Share the register with internal audit and external insurers before the EOL date.

Weeks 9–10: Evaluate Support Options

• Check if Microsoft offers paid Extended Security Updates (ESU) for Windows 10 21H2 (LTS). If so, compare cost and scope.
• Evaluate third-party maintenance providers. Third-party support typically costs 40–70% less than the OEM renewal and can deliver critical patches, technical support, and security fixes for unsupported OS releases.
• Request contract terms that match your required SLAs (response times, patch turnaround, severity levels).

Weeks 11–12: Finalize Coverage

• Sign a support contract that begins on January 13, 2027 — the day after vendor support ends.
• If using internal resources, confirm staffing and escalation paths.
• Communicate the final plan to stakeholders: IT operations, security, compliance, and business owners.

How Third-Party Support Can Help

After January 12, 2027, you cannot rely on Microsoft for patches or support. Third-party support providers specialize in keeping legacy platforms secure and running. They can provide:

• Custom hotfixes and security patches, including backported fixes for CVE-level vulnerabilities.
• Technical support for OS-level issues (crashes, performance, configuration).
• Assistance with migration planning and risk documentation.

Without a support contract, you are fully exposed. With one, you gain a safety net that buys time for a methodical upgrade.

Next Steps

The window is narrow but actionable. Start inventory today, isolate critical systems, and secure a support arrangement before December. Vendor pages for Microsoft software provide product lifecycle details. For a no-obligation discussion of post-EOL options, contact our team.

Time is short — but a planned, documented response is far better than a scramble in February 2027.