Skip to content
  • There are no suggestions because the search field is empty.

Why WISE Group Systems Run Windows LTSC Instead of Windows Pro

An explanation of the Windows Long-Term Servicing Channel, why WISE Group specifies it on delivered systems and how it compares with Windows Pro on updates, lifecycle and security.

Overview

Most corporate IT policies are written for office computing. They assume a fleet of laptops and desktops used by people, running Windows Pro or Windows Enterprise, kept on the newest release, and patched automatically. For that estate, the policy is sound.

WISE Group systems are not office computers. They are continuously operating measurement and monitoring systems: helideck monitoring, environmental monitoring, data acquisition, CCTV and reporting platforms. They acquire sensor data, apply validated processing, and present results that operational decisions depend on. For that role we specify Windows LTSC (Long-Term Servicing Channel).

This article explains what LTSC is, why we use it, and how to respond when your IT department asks why the system is not running Windows Pro. It is written to be forwarded to IT colleagues directly.

Important: speak to us before changing the operating system on a delivered system

If you are considering an operating system change, an in-place Windows upgrade, or a rebuild of a WISE Group system, please contact your WISE Group representative first. Unauthorised changes may affect measurement validity, invalidate system verification, and void support agreements.

What Windows LTSC Is

Windows LTSC is a Microsoft release channel intended for devices where the function of the machine must not change over its service life: industrial controllers, medical equipment, instrumentation, point-of-sale terminals and similar fixed-purpose systems.

An LTSC release is a snapshot of Windows that stays as it is. It receives monthly security and quality updates from Microsoft, exactly as other editions do, but it does not receive annual feature updates. The user interface, the bundled components, the driver model and the API surface remain fixed for the supported life of the release. In-box Windows apps that gain new functionality over time are not included, so the consumer application set found on a general-availability Windows installation is absent.

It is not a stripped-down or unsupported version of Windows. It is a fully licensed, fully patched Microsoft product with a deliberately long and deliberately uneventful support lifecycle.

Why We Specify LTSC for Monitoring Systems

Measurement integrity depends on a fixed configuration. Our systems are commissioned, verified and, where regulations require it, accepted against standards such as CAP 437 in a specific, documented software configuration. A feature update that changes graphics handling, serial or network stack behaviour, display scaling or power management can alter how data is acquired or presented. On an office PC that is an inconvenience. On a monitoring system it is a data quality risk.

Feature updates arrive when they arrive, not when it suits the site. Windows Pro releases are supported for roughly two years each, which means a Pro machine must accept a major feature update every couple of years to stay in support. Those updates are large, they require reboots, and occasionally they fail or require rework. LTSC removes that cycle entirely: the release you commission is the release you operate.

Availability matters more than novelty. These systems run continuously and are often relied upon during marine or aviation operations. An unexpected restart, a "setting up your device" screen, or a changed dialog box in front of an operator during a helicopter approach is an operational problem, not a cosmetic one. LTSC keeps the machine predictable.

Long, planned lifecycles. Each LTSC release has a fixed support life published by Microsoft: five years for the Enterprise LTSC releases and ten years for the IoT Enterprise LTSC releases. Compare that with roughly two years per Windows Pro release. It lets hardware and software refresh be planned around maintenance windows and capital cycles instead of Microsoft's release calendar. Always check the lifecycle date for the specific release your system runs, rather than assuming a general figure.

Smaller surface, fewer moving parts. No Store, no consumer applications, no automatic app installation. Less installed software means fewer components to patch, fewer things to fail, and a cleaner baseline to validate and troubleshoot.

Supportability. Because every system of a given type runs the same fixed baseline, our support engineers can reproduce faults reliably and give you a definitive answer. A fleet of machines each on a different Windows feature release makes that materially harder and slower.

Windows LTSC and Windows Pro Compared

Windows LTSC Windows Pro
Intended use Fixed-purpose and industrial systems General-purpose office and personal computing
Feature updates None during the supported life of the release New feature release each year; one must be installed within 24 months to stay in support
Security and quality updates Monthly, same as other editions Monthly
Support life per release Fixed and published per release: five years (Enterprise LTSC) or ten years (IoT Enterprise LTSC) Approximately two years per release
Configuration stability Fixed for the life of the release Changes with each feature update
Bundled consumer apps and Store Not included Included
Domain join, Group Policy, BitLocker Supported Supported
Managed by WSUS, Intune or Configuration Manager Supported Supported
Suitability for continuously operating measurement systems Designed for it Not designed for it

What Your IT Department Needs to Know About Security and Compliance

The most common concern raised about LTSC is that it is somehow less secure or less manageable. It is neither.

It is patched on the same schedule. LTSC receives the same monthly Microsoft security updates as Windows Pro and Enterprise, delivered through the same channels: Microsoft Intune, Configuration Manager, WSUS or Windows Update. Vulnerabilities affecting the code in the delivered release are remediated in the normal monthly cycle.

One honest limitation. Because LTSC does not take feature updates, it receives security fixes for the code it contains but not new security features introduced in later Windows releases. If your hardening baseline requires a specific newer control, raise it with us and we will confirm whether the delivered release supports it.

It is manageable with your existing tooling. LTSC is an Enterprise-class edition. It supports Active Directory or Entra domain join, Group Policy and MDM policy, BitLocker full-disk encryption, Microsoft Defender Antivirus and Defender for Endpoint, Windows Firewall, application control, and centralised logging and audit, and it enrols and reports in Intune, Configuration Manager and WSUS as an Enterprise-edition device. Your existing hardening baseline can generally be applied. The one area that may need a different approach is Store-based application delivery, since LTSC omits in-box Store apps. Tell us your management platform and we will confirm the specifics for your installation.

It is properly licensed. Systems are supplied with valid Microsoft licensing appropriate to the edition delivered. Licence documentation is available on request.

Fewer components means a smaller attack surface. Removing the Store and in-box consumer applications removes whole categories of vulnerability and unwanted software behaviour from the machine.

Browser handling. Where a browser is required on the system, it is maintained on its own update channel independently of the operating system release, so browser security fixes are not tied to the Windows feature cycle.

Note for network and security teams

Our systems are normally deployed on a segregated operational network with defined, documented interfaces to business systems. Where SCADA, TMS, PI or cloud telemetry integration is in scope, the connectivity and port requirements are documented per project. Ask your WISE Group representative for the network and security documentation covering your specific installation.

Common IT Objections and Our Response

What IT says Our response
"Our policy is that every Windows machine must run Windows Pro or Enterprise." LTSC is an Enterprise-class Windows edition, licensed and patched by Microsoft. The policy's intent (a supported, managed, patched Windows platform) is met. LTSC additionally meets a requirement office policy does not consider: configuration stability on a continuously operating measurement system.
"Windows 10 is end of life, so this machine is out of support." The October 2025 end-of-support date applies to the general-availability editions of Windows 10, not to Windows 10 LTSC, which has its own lifecycle. Check the Microsoft lifecycle date for the specific LTSC release before treating a system as out of support. See Windows OS Upgrade Policy for DADAS Systems for the transition path.
"LTSC doesn't get security updates." It does: monthly, through the same Microsoft channels as every other edition. What it does not get is annual feature updates.
"We can't manage it with our tooling." LTSC supports domain join, Group Policy, MDM, Intune, Configuration Manager, WSUS, BitLocker and Defender, and reports in your inventory and patching tools as an Enterprise-edition device. Store-based app delivery is the one likely gap; tell us your platform and we will confirm.
"Our vulnerability scanner flags the build as outdated." Scanners often infer risk from the Windows feature release number. Assess LTSC systems against the patch level of the LTSC release rather than against the current general-availability build number.
"We'll just upgrade it in place to the latest Windows." Please do not. An in-place upgrade bypasses the validation the system was commissioned against and may affect data acquisition and presentation. Where a newer operating system is required, we supply new hardware preloaded and validated by WISE Group. This is not a customer self-service process. Contact us to plan it, ideally alongside a scheduled maintenance visit.
"Can't we just run Windows Pro instead?" Windows Professional is the documented minimum baseline in our published requirements, but it is not the validated configuration and it carries the feature-update cycle and configuration drift described above. For some system types (DADAS servers in particular) our published policy is that only LTSC editions are supported. If your policy rules out LTSC, raise it with us at project definition so it can be agreed in writing as a defined exception, with the limits on validation and support stated. It is not a configuration to select unilaterally.

Where Windows Pro Is Appropriate

The distinction is between the system and the way people access it.

Delivered systems (servers, industrial PCs and appliances supplied by WISE Group) are specified with Windows LTSC. This is the configuration we validate, verify and support.

Client stations (the desktops, laptops or thin clients used to view the system through a web client or client software) are treated differently. Client stations supplied by WISE Group are specified in line with the published requirements for the product concerned; for DADAS, see DADAS Hardware and Software Requirements. Where a client station is a customer-provided office PC, it should follow your standard IT policy: keep it on the latest supported version of Windows, patch it as you patch everything else, and replace it when it no longer meets requirements. Microsoft's own guidance is that LTSC is not intended for general-purpose PCs across an organisation, so there is normally no reason to place a customer office PC on LTSC.

Where customer policy makes Windows LTSC impossible on a delivered system, Windows Professional is the documented minimum baseline in our published requirements. It is not, however, the validated configuration, and for some system types our published policy is that only LTSC editions are supported. Raise it with us before delivery so the implications for validation, update handling and support can be agreed in writing as a defined exception, rather than discovered later.

If Your IT Policy Still Requires Windows Pro

Raise it with us early – ideally at project definition, and in any case before any change is made to a delivered system.

Contact your WISE Group representative or submit a ticket through the Customer Support Portal. We can provide a written technical position for your IT governance or change-approval process, documentation of the licensing and security posture of the delivered configuration, and, where an exception is not achievable, an assessment of what running Windows Pro would mean for your specific installation.

Key Takeaway

Windows LTSC is not an older or lesser version of Windows. It is the Microsoft release channel designed for exactly what our systems do: run continuously, in a fixed and validated configuration, for years. It receives the same monthly security updates as Windows Pro and is managed with the same tooling – it simply does not change underneath you.

Corporate policies requiring Windows Pro are written for office computing and generally accommodate fixed-purpose industrial systems once the distinction is understood. Client PCs should follow your standard policy. Delivered WISE Group systems should stay on the configuration they were validated in. Any change should be planned with us first.


Related: DADAS Hardware and Software Requirements · Windows OS Upgrade Policy for DADAS Systems · System Verification for Regulatory and Third-Party Requirements

Do not change the operating system on a delivered WISE Group system independently. Contact WISE Group Support first to discuss your specific installation.