Windows Server 2022 is leaving mainstream support. Time to plan, not panic.
Microsoft has set the date: on October 13, 2026 the product moves into extended support — five more years of free security updates, but no new features. For hotels, manufacturers, retailers and other businesses running their own VMware infrastructure, this isn't a reason to panic tomorrow, but a cue to start budgeting now. Three to four years is the horizon on which a server estate is usually refreshed anyway, so it's smart to sync your cycle with Microsoft's dates rather than react at the last minute.
Windows Server 2022 lifecycle
| Stage | Date | What it means |
|---|---|---|
| Mainstream ends | October 13, 2026 | End of full support: features, drivers, security updates. |
| Extended support until | October 14, 2031 | Security updates only, at no extra cost. |
| Hotpatching (Datacenter: Azure Edition) | October 2027 | Extended one year past the mainstream end date. |
What actually changes
Microsoft server products have two lifecycle phases: mainstream support (new features, full technical support, regular updates) and extended support (critical security patches only, no new features). Moving into extended support doesn't "kill" the server — it keeps receiving security updates for the whole period, through October 14, 2031.
The catch is elsewhere: extended support is a technically "frozen" product. No new drivers, no performance improvements, no fresh cloud-service integrations. Microsoft will no longer take feature requests or ship non-security fixes.
Clarification. The separate paid Extended Security Updates (ESU) program is a measure for after extended support ends, and for much older products. For Windows Server 2022 in 2026 it is not required: within the 2026–2031 window, security patches are free. So the case for a planned migration isn't "paid support is more expensive" — it's total cost of ownership: aging drivers, no new integrations, and a pricier emergency upgrade at the end of the cycle.
What it means locally — for businesses
In hotels and factories, Windows Server is often baked into critical systems: the hotel PMS, MES/SCADA layers, domain controllers, file and terminal servers for accounting. These systems go years without updates "because they work" — which is exactly where risk builds up when it turns out the OS has long been in extended support and new integrations and drivers are no longer available.
An added local factor is currency swings and budgeting. Windows Server and VMware licenses track exchange rates, so a migration stretched out over time costs substantially less than an emergency upgrade forced at the end of the cycle, when demand and integrator rates traditionally spike.
VMware context. Since 2024 Broadcom has discontinued VMware perpetual licenses and moved everything to subscription: the catalog is condensed into a few bundles (VCF / VVF / vSphere Standard / Enterprise Plus), priced per physical core with a 16-core-per-CPU minimum. First quotes have often landed 2–5× above the old cost. Confirm the current model for your environment directly with your supplier.
Practical migration checklist for 2026–2027
1. Inventory servers in the VMware cluster
List every Windows Server 2022 VM via vCenter — a guest-OS report is available through standard VMware means (verify the exact path for your vCenter version).
For each VM record its role (domain controller, file server, app, database), business criticality and owner.
Flag which servers are physical (bare-metal) and which are virtualized — the migration plan differs.
2. Assess app compatibility with Windows Server 2025
Check official Windows Server 2025 support with the vendors of your key software (PMS, ERP, 1C, specialized production tools) — it often lands well after the OS release.
Separately verify peripheral drivers: printers, barcode scanners, specialized equipment.
Verify for your business: whether a specific app has an official Windows Server 2025 compatibility statement can only be confirmed by contacting the vendor directly.
3. Build a test environment
Stand up a separate test cluster, or at least a separate datastore, for clones of critical VMs.
Test the migration on clones, not on production systems.
Document the downtime each system needs — it's the basis for the phased migration schedule.
4. Cost out the licenses
Compare Windows Server 2025 license cost (factoring in Software Assurance / CSP agreements) against continuing on the current version within free extended support.
Budget VMware licensing separately — the model has changed; confirm current terms with your supplier.
Verify for your business: exact terms and pricing for paid extended security support (only relevant closer to 2031) should be confirmed with a Microsoft partner or distributor for your licensing model.
5. Schedule the phased migration by criticality
First, non-critical test/auxiliary servers — build your muscle on low-risk systems.
Then file servers and internal apps, with a rollback plan.
Migrate domain controllers carefully, following the recommended domain functional-level order (verify the
Install-ADDSDomainControllercommand sequence in current Microsoft docs for Windows Server 2025).Migrate the most critical production/PMS systems last, in a planned window with minimal business impact (e.g. a hotel's low season).
Bottom line: this isn't an emergency — it's a planning milestone. The fastest first move is a vCenter VM inventory: it reveals the real scope of work and anchors your budget.
FAQ
Will Windows Server 2022 stop working after October 13, 2026?
No. The server keeps running and receiving critical security updates throughout extended support — until October 14, 2031, at no extra charge. The issue isn't a shutdown; it's the absence of new features, slower support and a potentially higher cost of ownership over time.
Should we just move to Linux instead of Windows Server 2025?
It depends on the apps. If your main workload runs on a Linux-friendly stack (web on Laravel/PHP, PostgreSQL/MySQL databases), moving can cut licensing costs substantially. But if your infrastructure rests on Active Directory and Windows-only software (1C, specialized PMS/ERP), a full switch to Linux isn't realistic — and Windows Server 2025 is the logical step.
How long does a full server-estate migration take?
It depends on server count and system criticality. For a company with 10–20 virtual servers, a realistic horizon is 6–12 months including testing, vendor coordination and budgeting. Exact timelines should be scoped individually for your infrastructure.
What if an app doesn't support Windows Server 2025 yet?
Keep that server on Windows Server 2022 within extended support while pressing the vendor on certification timelines. This is normal practice — extended support exists precisely for such transition periods.
Sources
BleepingComputer — Windows Server 2022 to reach end of mainstream support in 90 days
Microsoft Lifecycle Policy — learn.microsoft.com/lifecycle/windows-server-2022
Microsoft 365 Admin — 90-day reminder: mainstream end Oct 13 2026 / extended until Oct 14 2031