...
The Windows file system is based on the Gregorian calendar, which was instituted in 1582. Because of the constraints of the Gregorian calendar, you may get a “system clock has been set back” error indicating that the clock has been set back from a distant date in the future, for example 2022-10-16. ANSI C defines 32-bit time_t, which is interpreted as the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 to 03:14:07 UTC on 19 January 2038. The 32-bit time_t represents the time range between 1970 and 2038.
LM-X License Manager uses time_t, because this is the only portable representation of time across operating systems. If a file outside the range specified by time_t (for example 1750) is detected by Windows, the Windows API changes the time to the one that fits the range represented by the time_t, thereby resulting in LM-X informing the user that system clock check has been set back from a random date.
...