If your software interacts with fixed-function devices such as kiosks, point-of-sale terminals, or manufacturing HMIs, a critical deadline looms on the horizon. Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise 2016 LTSB will reach their end of support on October 13, 2026. Following this date, these devices will receive their final monthly security update, after which they will be left to fend for themselves.
This situation differs significantly from the more widely publicized Windows 10 consumer and standard business editions. The LTSB build was specifically crafted for devices that organizations prefer to leave untouched for extended periods—think retail terminals, kitchen display systems in restaurants, warehouse scanners, and medical devices. Stability is paramount in these environments, which is why many of these systems continue to operate nearly a decade after their initial release, often hidden beneath the surface of your customers’ hardware.
Why this matters more than a typical OS sunset
Fixed-function devices often go unnoticed during IT planning cycles. Unlike laptops and servers, they are not actively managed, making it easy for an end-of-support date to slip by until a malfunction occurs or an auditor raises a question. This oversight poses a significant risk for your customers and creates a liability for you as the software vendor whose application runs on that operating system.
Once support concludes, any newly discovered vulnerabilities will remain unaddressed. For standalone machines, this is concerning enough, but for POS terminals or kiosks connected to broader networks, it becomes a potential entry point for security breaches. An unpatched device that processes payments or stores sensitive customer data could jeopardize your customer’s compliance with PCI DSS, HIPAA, or other relevant regulations. When issues arise, your software will be scrutinized, regardless of whether the operating system was ever your responsibility.
The ESU bridge, and why it’s not a real long-term answer
To mitigate this situation, Microsoft is providing an Extended Security Updates (ESU) program as a temporary solution. Understanding the terms is crucial before presenting this option to customers. For Windows 10 Enterprise LTSB 2016, the pricing starts at per device for the first year, dropping to for devices managed through Intune or Windows Autopatch. However, there’s a significant catch: the cost doubles each consecutive year for up to three years, and enrollment is cumulative. If a customer delays enrollment until the second year, they will have to pay for the first year retroactively as well. By the third year, the cost per device could be approximately four times the original price.
Windows 10 IoT Enterprise 2016 LTSB, which is likely powering many of your customers’ embedded devices, follows a different pricing model entirely. The ESU pricing is not publicly available; customers must contact their device manufacturer or OEM for a quote. This additional layer of complexity may not be accounted for in your customers’ budgets, making it essential to address this issue sooner rather than later.
It’s important to note that ESU was never intended to serve as a permanent solution. Microsoft has made it clear that this program is merely a temporary measure, not a substitute for migration. Relying on it as a long-term fix only postpones a more costly discussion and extends your customers’ exposure to risk.
Turn the deadline into an opportunity, not just a warning
This is where the narrative shifts from risk management to revenue generation. Each of your customers operating affected hardware must make a decision in the coming months: continue to pay rising ESU fees, upgrade to newer LTSC-based hardware, or potentially transition their workload away from Windows entirely if the device’s primary function is simply to display a session or run a single application.
This presents an opportunity for you to initiate meaningful conversations. Proactively reach out to your customers with an honest audit offer: assist them in identifying which devices are running the affected builds, calculate the ESU costs based on their fleet size, and outline the expenses and timelines associated with a hardware refresh. Customers who learn about this deadline from you in advance will appreciate your foresight and support, distinguishing you as a vendor who genuinely cares about their business.
The deadline itself is fixed and unyielding. However, how you engage with your customers in the lead-up to October 13, 2026, is entirely within your control.