Microsoft has issued a 30-day operational reminder for Windows Server 2022: mainstream support ends October 13, 2026. This is a lifecycle advisory—not a new security release, Patch Tuesday release, out-of-band patch, preview update, or Insider build.[1]
Reporting cutoff: September 11, 2026 at 7:09 p.m. EDT (23:09 UTC). Official Microsoft and Apple sources were rechecked at that point.
What actually changes on October 13
Windows Server 2022 does not suddenly stop booting, and Microsoft is not ending all security servicing on October 13. Microsoft says the product will move from mainstream support to extended support, with monthly security updates continuing at no additional cost through October 14, 2031.[1][2]
The important loss is support breadth. Under Microsoft’s Fixed Lifecycle Policy, mainstream support includes security updates, incident-support options, and the ability to request non-security updates; extended support keeps paid support and security updates but does not accept requests for warranty support, design changes, new features, or new non-security updates.[3]
Good news
The catch
- Requests for new non-security fixes and product-design changes end with mainstream support.[3]
- Waiting until 2031 to begin planning can turn an orderly migration into a rushed hardware, application, licensing, and backup project.
- A supported operating system does not make an unsupported application, driver, backup agent, or line-of-business stack supported.
Affected and not affected
| System or edition | What today’s reminder means | Action |
|---|---|---|
| Windows Server 2022 Standard, Datacenter, or Essentials | Windows Server 2022 Standard, Datacenter, and Essentials are affected by this support milestone. Mainstream support ends October 13, 2026; extended support continues through October 14, 2031.[2] | Patch now, inventory workloads, and decide whether to remain on 2022 during extended support or migrate. |
| Windows Server 2022 Datacenter: Azure Edition Hotpatch | Affected by the mainstream-support transition, but Microsoft says Hotpatch update support has been extended through October 2027.[1] | Confirm enrollment and the specific Hotpatch servicing path; do not assume every Server 2022 deployment receives this extension. |
| Windows Server 2025 | Not the product reaching this milestone. Microsoft identifies Server 2025 as the newer LTSC release.[1] | Use it as a migration candidate only after application, role, driver, licensing, and recovery testing. |
| Windows 11 or Windows 10 PCs | Not governed by this Server 2022 notice. Client editions have separate servicing timelines.[5] | Follow the applicable client-version lifecycle and update history instead. |
| macOS | Not affected. Apple’s public security-release table showed no same-day macOS release at the cutoff; the latest listed public Mac security release was macOS Tahoe 26.6.2 on August 17.[7] | Keep Software Update enabled and follow Apple’s separate security-release record. |
Patch level to verify now
Microsoft’s current Windows Server release table identifies the September 2026 “B” security update for Server 2022 as KB5122882 and build 20348.5622.[4][5] Installing that update does not extend the October lifecycle date; it establishes the current servicing baseline.[2][4]
KB5122882 includes security fixes plus quality changes for certificate-authority compatibility, Morocco’s time-zone transition, an intermittent Hyper-V stop error affecting a limited number of virtual machines, network failover, and Remote Desktop audio redirection.[4]
Microsoft also lists a known WSUS limitation: synchronization error details are not displayed after KB5070884 or later updates because that functionality was temporarily removed while addressing CVE-2025-59287.[4] That does not mean synchronization is necessarily failing; it means the usual error detail may be unavailable.
boot.stl file or the media may fail to start with error 0xc0430001.[4] Treat installation-media maintenance as a tested change, not a copy-and-hope task.What home users should do
Most home users do not run Windows Server 2022. If your household only uses Windows 10 or Windows 11 PCs, this particular deadline is not yours. Check Settings → System → About for the edition and version before acting. Do not buy a new PC or alter a home Windows installation because a server lifecycle notice appeared in your feed.
If a home lab, media server, or family-business server really does run Server 2022, install approved backups, verify a restore path, bring the system to the current security baseline, and document which roles and applications depend on it before planning an upgrade.
What businesses should do in the next 30 days
- Inventory every Server 2022 instance. Include physical servers, virtual machines, cloud instances, failover nodes, templates, offline images, disaster-recovery replicas, and powered-off systems.
- Record workload ownership. Map Active Directory, DNS, DHCP, file services, print services, Remote Desktop, Hyper-V, SQL workloads, backup agents, security software, and vendor applications to a named owner.
- Confirm the security baseline. Verify KB5122882 or a later applicable cumulative update and confirm the resulting build, not merely a “successful” deployment status.[4]
- Check vendor support separately. Ask whether the application, database, hardware, hypervisor, driver, and management stack support Server 2022 during extended support and whether they support Server 2025.
- Choose a deliberate path. Staying on Server 2022 during extended support can be reasonable when dependencies are supported and risk is owned. Migration may be better when new features, non-security fixes, or a longer platform runway matter.
- Build a pilot ring. Test backups, restores, authentication, certificates, scheduled tasks, network paths, printing, monitoring, and application transactions on a representative non-production system.
- Assign exceptions. Every delayed migration should have an owner, reason, compensating controls, review date, and tested recovery plan.
Do not confuse this with Patch Tuesday
The September 2026 Windows security release arrived September 8, three days before this reminder. Our separate September Patch Tuesday guide covers the security release and exploited vulnerabilities; today’s advisory is about Server 2022’s support phase.[6]
Microsoft’s Security Update Guide was revised again on September 11. The same-day revision set included acknowledgement-only entries explicitly described as informational, alongside newly published Edge/Chromium and other product records; that revision activity does not turn today into a second Windows operating-system Patch Tuesday.[6]
For the separate Azure Edition Hotpatch extension, see our Windows Server 2022 Hotpatch explainer. The extension is useful context, but it is not a blanket extension of mainstream support for every Server 2022 installation.
FAQ
Will Windows Server 2022 stop working on October 13?
No. Microsoft’s notice describes a transition from mainstream to extended support, not a shutdown or activation cutoff.[1]
Will Server 2022 still receive security updates?
Microsoft says monthly security updates continue at no additional cost through October 14, 2031, subject to the product’s servicing requirements.[1][2]
Is October 13 the final Server 2022 security update?
No. Microsoft says the October 2026 security update is the last mainstream-support update; security updates continue during extended support.[1]
Should every business migrate immediately to Server 2025?
Not blindly. Migration should follow workload inventory, compatibility testing, backup and restore validation, pilot deployment, and an owned rollback plan. Microsoft identifies Server 2025 as the newer LTSC release, but that does not prove every application is ready for it.[1]
Does installing KB5122882 change the lifecycle deadline?
No. KB5122882 is the current September security baseline for Server 2022; lifecycle dates are maintained separately.[2][4]
Did Apple release a Mac security update today?
No same-day public macOS security release appeared in Apple’s security-release table at our cutoff. Apple’s Developer page listed macOS 27.0 RC on September 9, which is a release candidate, not proof of a new public production macOS security update.[7][8]
Bottom line
Patch Windows Server 2022, but do not panic-migrate it. Use the October 13 milestone to verify ownership, dependencies, recovery, vendor support, and a tested upgrade path. The operational risk is not that every server fails next month; it is reaching the end of mainstream support without knowing which workloads still depend on the platform.
Sources
- Microsoft: Windows message center — same-day 30-day Windows Server 2022 reminder.
- Microsoft Lifecycle: Windows Server 2022 — product support dates.
- Microsoft Fixed Lifecycle Policy — mainstream and extended support scope.
- Microsoft: KB5122882 for Windows Server 2022 — build, fixes, known issue, and deployment cautions.
- Microsoft: Windows Server release information — servicing table and latest build.
- MSRC: September 2026 Security Updates CVRF — September release and revision history.
- Apple security releases — public Apple security-release table.
- Apple Developer Software Releases — macOS 27.0 RC listing.