If you have a handful of Windows PCs, it’s easy to assume they’re all “basically the same”. Then a support deadline hits, a few machines quietly fall behind, and you’re left wondering which ones matter and what breaks if you touch them.

Windows 11 version 23H2 Enterprise and Education reached end of updates on November 10, 2026. If any of your business PCs are still on 23H2, now is the time to move them to a supported Windows 11 version on a schedule you control.

What “end of updates” actually means for your business

When Microsoft ends updates for a Windows version, it stops releasing monthly security and quality updates for that specific version. Your PCs do not stop working on November 10, 2026. The risk is quieter than that.

Here’s what changes in practice:

  • No more security fixes for 23H2. If a new Windows vulnerability is patched next month, 23H2 devices do not get that fix.
  • Compliance and insurance questions get harder. Many frameworks and policies boil down to “supported operating systems with current security updates”. An out of support OS version is tough to defend.
  • Troubleshooting gets slower. When you call a vendor about an issue, one of the first questions is often “are you on a supported build?” Being behind turns a normal ticket into a dead end.

The goal is simple: get off 23H2 before it turns into a background source of avoidable risk and friction.

How to identify PCs that are still on Windows 11 23H2

Start with a clean list. You are looking for devices where the Windows version is 23H2.

A few practical ways to check:

  • On the PC itself (fast spot check). Press Windows key + R, type winver, and confirm the Version line.
  • In Settings (for a user-friendly check). Go to Settings, then System, then About, and look for Windows specifications.
  • In your management tool (best for a business). If you use Microsoft Intune or another RMM, pull a device report that includes OS version and build, then filter for 23H2.

If you find even a small pocket of 23H2 machines, treat it as a process issue, not a one-off. Usually it means some devices are missing policy, are off-network, or are excluded from feature updates.

Pick your target version, then plan the upgrade like a small project

The mistake we see most often is upgrading “whenever Windows offers it” on each PC. That’s how you end up with random downtime, a surprise app issue, and no clear rollback plan.

Instead, decide what you’re upgrading to, and roll it out in a predictable sequence.

A calm, low-drama approach looks like this:

  • Choose a supported Windows 11 version as your target. Most businesses aim for a current supported release, not the newest build on day one.
  • Create three groups (rings). A small pilot group, a larger early adopter group, then everyone else.
  • Set a timeline with real dates. For example: pilot this week, early adopters next week, broad rollout over the following two to four weeks.

If you are using Intune, Windows Update for Business style policies, WSUS, or Configuration Manager, you can control timing and stage deployments. The point is not to go slow forever. The point is to learn early on a few devices, then move quickly with confidence.

How to minimise downtime for staff

Most feature updates are straightforward, but they still cost real time. The upgrade itself, the post-reboot “settling”, and the first login can easily chew up part of a workday if you do it at the wrong moment.

A few habits that keep it painless:

  • Schedule upgrades outside peak hours. Evenings are fine, but early mornings often work better because someone is available if a laptop asks a question.
  • Make laptops predictable before the update. Ensure they are plugged in, have stable internet, and have enough free disk space.
  • Set expectations with staff. Tell them what they will see (restarts), how long it might take, and who to contact if they get stuck.
  • Have a back-out plan. If an executive laptop or a “single point of failure” workstation has trouble, you should already know the fastest way to get that person working again (spare device, remote desktop, or a rollback window where applicable).

This is also a good moment to check BitLocker recovery key escrow and make sure you can recover a device if it prompts for a key after firmware or OS changes.

Avoid the two classic surprises: line-of-business apps and drivers

Most Windows upgrades do not break mainstream apps. The problems usually come from the things that are unique to your business.

Line-of-business apps

If you have an accounting package, a medical or legal system, a manufacturing app, or anything tied to a local database or special plug-in, treat it as “must test”. Do not rely on hope.

  • List the apps that keep the business running. Billing, quoting, scheduling, label printing, anything tied to revenue or operations.
  • Confirm vendor support for your target Windows version. Some vendors are explicit about supported OS builds.
  • Test with real workflows. Logging in is not a test. Run a normal day’s tasks on a pilot PC: print, export, import, scan, sync, and generate reports.

Device drivers and peripherals

Driver issues are boring, and that’s why they catch teams off guard. The usual culprits are printers, label makers, scanners, speciality USB devices, and docking stations.

  • Identify “weird” hardware early. If only two people use the cheque printer, put them in the pilot.
  • Update firmware and drivers before the feature update. Especially for docks and Wi-Fi adapters.
  • Keep a known-good installer package handy. If a device needs a specific driver version, you do not want to be hunting for it mid-morning.

If you do these two workstreams properly, the broad rollout tends to be uneventful, which is exactly what you want.

A simple checklist you can run this week

If you want a quick plan to get moving:

  • Inventory. Pull a device list and flag anything on Windows 11 23H2.
  • Decide. Pick the Windows 11 version you are standardising on next.
  • Pilot. Upgrade 3 to 10 representative PCs, including at least one “fussy” setup (printer, scanner, dock, VPN user).
  • Validate. Confirm line-of-business apps, printing, and any device-specific workflows.
  • Roll out. Schedule the rest in waves, with clear comms and a fallback option.

Want a hand getting this done without drama?

If you would like help identifying your 23H2 devices, choosing the right target version, and running a staged upgrade that avoids app and driver surprises, the Flexnet Networks team can plan and manage the rollout with you.

Sources