
Which Windows Is That? A Calm 10-Minute Version Check Before November 10
Your computer may be working perfectly today. But what if it quietly stops receiving the security updates that protect your business?
For some Windows PCs, that happens next week. Microsoft has confirmed that the November 10, 2026 security update is the final one for Windows 11 version 23H2 in its Enterprise and Education editions. After that, those PCs keep working, but no new security fixes arrive.
Most small offices, clinics and nonprofits don't know the version on every desk, and they shouldn't have to memorize it. This week is a good moment to look, calmly, once.
Why the version number matters
Microsoft releases a new Windows 11 version each year, and each has its own end date. The edition matters too: Enterprise and Education versions get about a year longer than Home and Pro. Dates below are from Microsoft's lifecycle pages for Home and Pro and Enterprise and Education.
Windows 11 version | Home and Pro: updates end | Enterprise and Education: updates end |
|---|---|---|
23H2 | November 2025 (ended) | November 10, 2026 (final update) |
24H2 | October 2026 (ended) | October 2027 |
25H2 | October 2027 | October 2028 |
26H2 (released September 29, 2026) | October 2028 | October 2029 |
A PC on an older version can look perfectly healthy. The gap stays invisible until someone tries to use a flaw that will never be fixed on that machine.
Windows 10 has its own rules
Regular Windows 10 (version 22H2, the final version) reached end of support in October 2025. Business PCs can keep receiving security fixes through Microsoft's paid Extended Security Updates (ESU) program, bought a year at a time for up to three years. A separate consumer ESU option exists, but it doesn't cover PCs managed by an organization. Some special editions, such as Windows 10 Enterprise LTSC, follow their own longer support dates. If you still have Windows 10, note each machine's edition and whether it's enrolled.
Microsoft recommends moving eligible devices to 25H2. From 24H2, that step is a small "enablement package", because the two versions share the same code. On many PCs it installs much like a monthly update, but not always right away: Microsoft may hold a device back with a compatibility "safeguard hold" until a known app or driver issue is resolved.
PCs on 23H2 need a full upgrade, which deserves a little planning. Before any upgrade, check:
A verified backup, ideally one you have test-restored.
Free disk space, so the upgrade can download and install.
Hardware and driver compatibility with Windows 11's requirements.
BitLocker recovery keys, saved where you can find them; Windows can ask for one after some system changes.
Critical business apps (practice management, accounting, imaging) supporting the new version.
These are the usual reasons an otherwise simple upgrade becomes disruptive.
Our Seven Layers of Cyber Armor are Device, Endpoint, Identity, Network, Backup, Proactive and Insurance. Version management mainly strengthens three:
Device: each computer runs a version that still receives security fixes.
Endpoint: your security tools protect a system that is still being patched.
Proactive: you find gaps on a quiet weekday, not during an incident.
Backup supports all of it, so you can recover safely if an upgrade misbehaves.
The first step doesn't require buying anything. It simply requires knowing what you have. Upgrades, app testing, replacing older hardware or ESU licences can carry costs, and it's better to see those coming.
Ask each person to open Settings > System > About (Microsoft's steps) and send you the "Edition" and "Version" lines, or a screenshot. Thank them. One PC takes under a minute; gathering answers from 30 or 50 computers takes longer, so start with a simple table: device, user, edition, version, next step.
Then sort the list into three groups:
Supported and up to date for your device and business applications: continue routine updates and monitoring.
Small step (24H2 Home/Pro): already past their end date, so plan the move to 25H2 soon.
Bigger step (23H2, anything older, or Windows 10 without ESU or a longer-support edition): plan an upgrade or replacement, checklist first.
Missing November 10 by a few days won't break anything overnight. But each month on an unsupported version is a month of fixes that machine won't receive.
Ten minutes to get started. A clearer picture of what needs attention.
One thing to do this week: Before Tuesday, November 10, start a simple device table: for each office PC, note the edition and version from Settings > System > About. Flag anything on 23H2, 24H2 Home/Pro, or Windows 10 without ESU, and check backup, disk space, BitLocker key and key apps before booking its upgrade.
From MicroAge Richmond - Team Jahan: If you'd like a second pair of eyes on your list, or a calm, unhurried plan for the upgrades it turns up, our Richmond team is always happy to help. Real people, real solutions, at a pace that suits your office.
Sources
Microsoft Learn: Windows 11 Enterprise and Education lifecycle (23H2 ends after the Nov 10 2026 update; 24H2 to Oct 2027; 25H2 to Oct 2028; 26H2 released Sep 29 2026, to Oct 2029)
Microsoft Learn: Windows 11 Home and Pro lifecycle (23H2 ended Nov 2025; 24H2 ended Oct 2026; 25H2 to Oct 2027; 26H2 to Oct 2028)
Windows Experience Blog: How to get the Windows 11 2025 Update (Sep 30 2025): 25H2 enablement package from 24H2, safeguard holds, 23H2 needs a full OS swap
Microsoft Learn: Extended Security Updates program for Windows 10: 22H2 only, up to three years for organizations, bought annually
Microsoft Learn: Windows release health, supported versions: Windows 10 LTSC dates
Microsoft Support: Find information about your Windows device
