Machines running Windows 10 Enterprise LTSB 2016 or Windows 10 IoT Enterprise LTSB 2016 will stop receiving free security patches on October 13, 2026. That deadline—firm and non-negotiable—forces organizations to make a hard choice: pay for a temporary lifeline, migrate to a supported platform, or retire the hardware entirely.

The October 2026 Deadline: Who’s Affected

The end-of-support deadline applies specifically to the 2016 Long-Term Servicing Branch (LTSB) release—version 1607, built on the 14393 codebase. These aren’t ordinary Windows 10 PCs. They live in factories, hospitals, retail kiosks, and research labs, often bolted to specialized equipment and running software that can’t simply be swapped out. If your device reports “Version 1607” and an OS build starting with “14393” when you run winver, this is your deadline.

It’s easy to confuse this with the broader Windows 10 support cutoff. That came earlier: October 14, 2025, when all mainstream editions of Windows 10 (barring the LTSC/LTSB family) saw their final free update. LTSB 2016 had its own, longer extended support phase, which now reaches its natural conclusion. Organizations must check every device individually—asset records and model names aren’t enough. A PC might have been reloaded, reimaged, or mislabeled. Only a hands-on verification of the OS build will do.

Extended Security Updates: A Paid Bridge, Not a Permanent Fix

For organizations that can’t meet the deadline, Microsoft offers Extended Security Updates (ESU) for LTSB 2016. This is a separate paid program, distinct from the ESU offering for standard Windows 10 versions. It delivers critical and important security patches for enrolled devices, but nothing else: no new features, no design changes, no technical support beyond what you’ve already paid for.

ESU is a time-boxed bridge, not a destination. According to documentation reviewed by WindowsForum, you’ll need to purchase the correct entitlement for your exact edition (Enterprise LTSB or IoT Enterprise LTSB) and activate it using a key provided through your volume licensing or OEM channel. The activation process isn’t universal—methods differ based on how you bought the license, and isolated devices may require a separate offline procedure. Once activated, every enrolled machine needs a named owner and a dated exit plan. ESU solves only the security-update gap; it doesn’t magically make an old application compatible, extend hardware life, or satisfy regulatory auditors.

What a “Successful” Migration Actually Looks Like

Migration is the preferred route when hardware can still run a supported OS and application vendors cooperate. But don’t assume that “LTSC” means “just upgrade.” Windows 10 Enterprise LTSC 2021 (the next long-term channel release) has its own lifecycle, ending mainstream support in 2027 and extended support in 2032—but that’s not forever, and it may require a clean installation rather than an in-place upgrade.

Before committing to any migration target:

  • Ask your application or equipment vendor for the exact supported Windows edition and release—not just “Windows 10.”
  • Verify that all drivers exist: storage, network, serial, imaging, and any proprietary acquisition boards.
  • Confirm that the chosen Windows edition is available through the correct licensing channel (Enterprise LTSC and IoT Enterprise LTSC are not interchangeable).
  • Test the full workload on a non-production machine: application launch, data acquisition, network access, backup/restore, and update installation.

A migration that doesn’t pass the real workload isn’t a migration—it’s a failed experiment. If the target OS can’t keep your lab instruments running, the fallback should be ESU, but only as a temporary, owned exception.

Preparing Your Device for ESU

If you’ve decided ESU is unavoidable, start with a rigorous device inventory:

  1. Confirm the OS edition, version (1607), and full build number.
  2. Install all prerequisite servicing and security updates that Microsoft requires for ESU activation. A fully patched LTSB 2016 system is the baseline.
  3. Purchase the correct ESU entitlement for the coverage period you need. Do not reuse keys or procedures from other ESU programs.
  4. Secure the activation key in an approved secrets management system—never in a spreadsheet or a support ticket.
  5. Follow Microsoft’s current LTSB 2016 ESU activation procedure to the letter. Activate during a maintenance window.

After activation, verify the servicing path: deploy an applicable ESU-covered update to a test device, restart, check update history, then test the application and attached equipment. Only then should you roll out to production machines. If activation fails, stop and troubleshoot—repeated failed attempts can lock you out.

Practical Steps for IT Administrators

With the October 2026 deadline approaching, every LTSB 2016 device needs one of three labels: migrate, replace, or ESU. Administrators should:

  • Reconcile the physical inventory with network scans, endpoint management databases, and procurement records. A device that’s “running Windows 10” isn’t specific enough.
  • Assign an application owner and an operational owner to each device. These people own the exit plan.
  • Obtain written vendor support statements for the proposed target—whether that’s a newer LTSC release, a standard Windows 11 edition, or a completely different platform.
  • Reserve test hardware and maintenance windows now; don’t wait until September 2026.
  • Budget separately for ESU fees, migration engineering, application upgrades, and hardware replacement. These are distinct cost centers.
  • Review each ESU exception on a fixed schedule. The goal is to shrink the exception list, not grow it.

Remember that subtle configuration differences—a different firmware revision, a specialty PCIe card, a dongle that silently handles licensing—can make two identical PC models behave completely differently. Inventory by individual device, not by model number.

Looking Ahead

Microsoft’s long-term servicing channel isn’t going away. Windows 11 IoT Enterprise LTSC is already available, and a future Windows 11 Enterprise LTSC release is expected. But the clock is ticking for the 2016 vintage. Even after paying for ESU, every organization should watch for the next generational shift: if your LTSB 2016 system runs equipment that will outlast the next LTSC edition’s lifecycle, you may need to plan an intermediate migration or negotiate custom support.

The essential takeaway is this: ESU gives you time, not an excuse. The October 13, 2026 deadline isn’t a suggestion. The devices that keep your production line moving, your cash registers ringing, or your patients safe deserve a plan that’s as precise as the machinery they control.