Back to News

Managed IT · Sep 15, 2026

Still running Windows 10? What the September 2026 updates tell you

Microsoft shipped its September security update for Windows 10 on September 8 (KB5122878), followed by an out-of-band fix on September 14 (KB5129236) for Remote Desktop and some USB audio problems. It also published an Extended Security Updates (ESU) licensing preparation package for Windows 10 versions 21H2 and 22H2.

None of that is headline news. It matters anyway, because a lot of small businesses still have Windows 10 machines in the back office, on the shop floor, or at the front desk, and many owners are not sure what "supported" means anymore.

Patched is not the same as supported

Here is the line from Microsoft's own documentation that every owner should read: Extended Security Updates provide monthly critical and important security updates for eligible Windows 10 devices, but no new features, no non-security updates, and no technical support.

In practice, that means an ESU machine gets security fixes and nothing else. If a non-security bug breaks a printer driver or a line-of-business app, you are on your own. If a software vendor drops Windows 10 support for their next version, ESU does not change that.

ESU is a bridge. It buys time to replace or upgrade hardware on your schedule instead of in a panic. It is not a place to live.

The quiet risk: machines nobody is tracking

The Windows 10 devices that worry me are not the ones on someone's desk. Those get noticed. The risky ones are the PC running the time clock, the old workstation connected to a CNC machine, or the reception computer that has not been rebooted in months.

These machines often are not enrolled in ESU, are not getting updates at all, and sit on the same network as everything else. When ransomware groups look for a way in, an unpatched machine like that is exactly what they want.

A simple plan for the next 90 days

You do not need a big project to get this under control. You need a list and a decision for each line on it.

  1. Inventory every Windows device. Include the ones in closets and on shop floors. Note the Windows version and whether it is receiving updates.
  2. Sort them into three groups. Upgrade to Windows 11 now, enroll in ESU and replace later, or isolate because it runs equipment that cannot be upgraded.
  3. Confirm ESU devices are actually patched. Enrollment does not help if updates are failing silently. Check the update history on each device.
  4. Isolate what cannot be upgraded. Put legacy machines on their own network segment with no general internet access.
  5. Set a replacement budget. Spread hardware refreshes across the next few quarters so this does not become an emergency.

Watch the out-of-band updates

The September 14 out-of-band release is a good example of why someone has to be watching. Microsoft pushed a fix outside the normal Patch Tuesday schedule because the earlier update caused problems. If nobody is paying attention to these, you either miss the fix or end up with a Remote Desktop problem nobody can explain.

This is the unglamorous part of IT: reading release notes, testing updates on one machine before rolling them out, and following up when something breaks.

What this means for your business

  • If you have Windows 10 machines, they need either an upgrade, ESU enrollment, or isolation. "Leave it alone" is not one of the options.
  • ESU keeps security patches flowing but does not include technical support or bug fixes.
  • The machines most likely to cause trouble are the ones nobody thinks about. Start your inventory there.
  • Budget replacements over time so you are not buying ten PCs in one week.

If you would rather hand this off, keeping devices patched, tracked, and replaced on a sensible schedule is what our Managed IT service is for.

Sources