Plan FileWave Compatibility for Windows Enterprise LTSC

What Windows Enterprise LTSC is

Windows Enterprise Long-Term Servicing Channel (LTSC) is intended for special-purpose devices that perform a fixed task, such as medical systems, digital signs, or kiosks.

These systems usually need a stable feature set for years and should have little dependence on apps that change frequently.

LTSC receives monthly quality updates, including security fixes, but does not receive the regular feature updates delivered to the general availability channel. New feature sets arrive in later LTSC releases.

Microsoft's Windows Enterprise LTSC overview lists each LTSC release, its equivalent general availability release, and the servicing model.

App and feature availability differs by LTSC release. Check the documentation for the exact release instead of relying on a blanket list of included or missing apps.

Microsoft recommends the general availability channel for ordinary user PCs that need current Windows features and broad third-party application support.

Microsoft does not recommend LTSC for most or all PCs in an organization. Use it for a defined special-purpose workload with a tested application and management plan.

Browser availability also differs by release. For example, Windows 11 Enterprise LTSC 2024 includes Microsoft Edge and does not include Internet Explorer.

How does this impact FileWave?

Microsoft gives this compatibility warning for LTSC releases:

"Since the feature set for LTSC doesn't change for the lifetime of the release, over time there might be some external tools that don't continue to provide legacy support."

FileWave must support changes in current Windows releases and in the third-party components used by FileWave Client.

An LTSC release can remain under Microsoft support after an external library or management component stops supporting that Windows generation. Microsoft lifecycle support therefore does not guarantee compatibility with every FileWave Client release.

Security or supplier support may require FileWave to replace a dependency, and the replacement may not run on an older LTSC release.

Check the exact LTSC release against the platform-support table for the FileWave version you plan to deploy. Do not infer FileWave compatibility from Microsoft's end-of-support date alone.

Taking a look at some lifetime examples, Windows 10 2016 LTSB was Microsoft's offering, pre-dating LTSC:

	Release Date	Mainstream End Date	Long Term End Date
Windows 10 2016 LTSB (1607 equivalent)	Aug 2, 2016	Oct 12, 2021	Oct 13, 2026

Windows 10 2016 LTSB has now passed Microsoft’s extended-support end date of October 13, 2026; mainstream support ended October 12, 2021. Treat this table as a historical lifecycle example, not a supported-OS recommendation. A FileWave Client that still connects does not restore Microsoft support or demonstrate that the device can safely remain in service.

FileWave's Downloads pages list operating systems that are fully tested and those expected to work for each release.

If an LTSC release is absent from those tables, treat it as unverified and test it before changing either the FileWave Server or Client.

Record the Windows edition, LTSC release, FileWave Client version, and required device workflow in the test plan. The word LTSC alone is not a compatibility result.

Plan upgrades

For devices still running Windows 10 2016 LTSB, have the device or application owner plan an operating-system upgrade or replacement. If a fixed-purpose application prevents an immediate change, involve the security owner in the interim isolation and risk decision. Do not treat a successful FileWave pilot as an extension of the operating system’s lifecycle.

Before upgrading FileWave, pilot the target Server and Client combination on representative LTSC devices. Older FileWave Clients can often communicate with newer Servers, but feature support and minimum-version requirements still need verification.

If the newest Client is not compatible, hold the Client version only on the affected LTSC devices while you test an operating-system or application replacement plan.

Review the target FileWave release page for minimum Client and Server compatibility before production rollout. Test inventory, Fileset deployment, remote actions, and any device-specific workflow the LTSC system must keep performing.

Do not leave the FileWave Server unpatched solely to preserve an old LTSC endpoint. Escalate the compatibility decision to FileWave Technical Support and plan isolation or replacement for the affected device.

Retest the LTSC workflow before every FileWave upgrade. Prior success proves only the versions and functions that were tested at that time.