
If you’re an ISV whose software touches a kiosk, a point-of-sale terminal, a manufacturing HMI, or any other fixed-function device, there’s a deadline you need on your radar. Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise 2016 LTSB both reach end of support on October 13, 2026. After that date, those devices get their final monthly security update and then they’re on their own.
This isn’t the Windows 10 story that made headlines last year. That was the consumer and standard business edition, and most of the coverage has moved on. The LTSB build is different. It was designed specifically for devices organizations don’t want to touch often, things like retail terminals, restaurant kitchen display systems, warehouse scanners, and medical devices, where stability matters more than new features. That’s exactly why it’s still running in production nearly a decade after release, and it’s likely sitting underneath more of your customers’ hardware than you’d guess.
Why this matters more than a typical OS sunset
Fixed-function devices tend to fly under the radar during IT planning cycles. Nobody’s actively managing them the way they manage laptops and servers, so an end-of-support date can slip by unnoticed until something breaks or an auditor asks about it. That’s a real problem for your customers, and it’s a real exposure for you as the software vendor whose application sits on top of that OS.
Once support ends, newly discovered vulnerabilities in that device stay open permanently. For a standalone machine, that’s bad enough. For a POS terminal or a kiosk connected to a broader network, it’s an entry point. An unpatched device processing payments or storing customer data can become the reason your customer fails a PCI DSS audit, a HIPAA review, or whatever compliance framework applies in their vertical. If your software is the thing running on that hardware, you’re going to get the call when something goes wrong, even if the OS was never your product.
The ESU bridge, and why it’s not a real long-term answer
Microsoft is offering an Extended Security Updates program as a temporary bridge, and it’s worth understanding the terms before you position it to customers. Pricing for Windows 10 Enterprise LTSB 2016 starts at $61 per device for the first year, discounted to $45 for devices managed through Intune or Windows Autopatch. Here’s the catch: the price doubles every consecutive year for up to three years, and enrollment is cumulative. If a customer waits until year two to enroll, they pay for year one retroactively too. By year three, that’s roughly four times the original cost per device.
Windows 10 IoT Enterprise 2016 LTSB, the edition most likely to be running your customers’ embedded hardware, follows a different path entirely. ESU pricing isn’t published; customers have to go through their device manufacturer or OEM to even get a quote. That’s an extra layer of friction most of your customers won’t have budgeted time for, and it’s worth flagging to them now rather than in month two of the countdown.
ESU was never meant to be a destination. Microsoft is explicit that it’s a pause button, not an alternative to migrating. Treating it as a permanent fix just delays a more expensive conversation and stretches your customers’ risk window in the meantime.
Turn the deadline into an opportunity, not just a warning
This is where the story shifts from risk to revenue. Every one of your customers running affected hardware needs a decision made in the next several months: pay escalating ESU costs, refresh to newer LTSC-based hardware, or in some cases, move the workload off Windows entirely if the device’s only real job is displaying a session or running a single application.
That’s a conversation you’re positioned to start. Reach out to customers now with an honest audit offer: help them inventory which devices are actually running the affected builds, what the ESU math looks like for their fleet size, and what a hardware refresh path would cost and how long it would take. Customers who hear about this deadline from you in September instead of discovering it during an audit in November will remember which vendor was looking out for them.
The deadline itself isn’t negotiable. How you show up for your customers between now and October 13, 2026 is.













