Microsoft Long Term Service Channel

What is Windows LTSC?

Personal Computers are not the only hardware that may run a copy of Windows.  Examples could include medical equipment, digital signs, cash machines, etc.

Each of these examples, require dedicated hardware, which may be high precision and very expensive.  When purchasing  a cataract surgery solution, for example, the expectation is it will last many years and it won't go wrong during an eye operation!

Since the hardware's shelf live is much greater than that of a standard PC and reliability is of upmost concern, it requires the OS driving that hardware to provide that same support, without compromising the product.

This is where Microsoft's Long Term Service Channel comes into play.  Unlike their mainstream OS versions, LTSC is locked in time and does not receive the same new features and updates that would be expected with mainstream versions of their OS.  The support agreement included with LTSC is based upon security and actual issues reported by those using LTSC.

To provide some idea on scope, LTSC does not include the likes of Edge, Cortana, One Note, MSFT Store and many more applications and lacks inclusion of newer features.  All of this is with the aim to ensure the hardware continues to function as it did the day it was produced.

This is a stark contrast to their mainstream Windows releases, which include many updates to applications and newer features.

For this reason, the LTSC version of Microsoft is not intended for PC use and should only be installed on devices that have these specific restraints.

For example, LTSC versions include Internet Explorer, since it is no longer receiving updates (beyond security).   This could lead to websites not being viewable as designed.

How does this impact FileWave?

Microsoft offer the following statement for their 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."

As expected, FileWave must react to the newer features introduced into the mainstream release of any Operating System.  As Microsoft introduce these new features, the FileWave Developer Team beaver away, sometimes to utilise these new features, whilst other times having to react to changes and enhancements in OS updates, forcing the FileWave products to also move forward.

This is in no way limited to FileWave code, but to any code that FileWave leverages, e.g. 3rd party code.  Since FileWave does not have full control over the newer features introduced by Microsoft or support of all included 3rd party code, it is foreseeable, that an LTSC version may fall far enough behind the mainstream versions and no longer function as intended with FileWave.

There are times when 3rd party code must be replaced with alternate code, which could be driven by lack of support from that supplier, particularly where security is involved.  When transitioning to newer 3rd party tools, there could be limitations regarding support of older OS versions.

Due to the design of Long Term Service OS for Windows, FileWave cannot guarantee the same timeframe of support as Microsoft offer.  The very nature of LTS Windows releases, avoids fundamental code changes that is seen in their mainstream releases.  To ensure product efficiency, security and features, it can be necessary to include newer FileWave code which will no longer be appropriate for LTS versions, where the LTS version no longer falls inline with its mainstream equivalent.

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
LTSB (1607 equivalent)	Aug 2016	Oct 2016	Oct 2026

Despite the mainstream end date of LTSB being 2016, it was seen that FileWave Client versions were still functioning up to the beginning of 2025.  However, it was entirely plausible that this impact could have been sooner and Microsoft's expectation is migration to LTSC.

As seen in our downloads page, we are unable to test all possible versions of every OS.  We highlight the versions fully tested and then list some versions which would be expected to work, based upon those tested.

Yet, due to the above details, it is not possible to suggest FileWave will be able to function, either entirely or in part, on older Microsoft code.

In essence, when the LTSC equivalent version is no longer in mainstream support, it is now effectively legacy code still.  Microsoft's agreement plan does not prevent this code from being legacy.

What Options Exist?

Typically, older versions of FileWave Client still function with newer versions of FileWave Server.  Where newer versions of FileWave software is released, products that are no longer in mainstream release should be tested thoroughly before considering upgrading.  If satisfied the Client still functions, it is by internal choice whether the FileWave Client is upgraded or not.  It may be just certain features are lost, rather than the whole client no longer functioning.

If unsure, it may be prudent to cease upgrades of the FileWave Client software for those dedicated devices.

There are times when FileWave must make some crucial change, which will prevent certain older versions of Client from communicating any further with the FileWave Server.  These changes are always stressed in our downloads documentation.  If this is likely to impact devices from being managed at all, then rigorous testing should be attempted, before upgrading a production environment.  The outcome may therefore mean it is no longer possible to upgrade FileWave appliances at all, until these older clients are no longer of concern.

Not upgrading FileWave appliances, in particular the FileWave Server, could have security concerns.

In the main, history has shown it is likely that these LTSC versions that are no longer in mainstream support, will still be able to function as hoped, however this cannot be relied upon as the FileWave product advances.