Seems that, some years ago, Microsoft added a “feature” to Windows Server, called “Secure Time Seeding”. This was supposed to offer alternative ways for a server machine to keep track of the correct time, in the event of failures in the more usual mechanisms. Unfortunately, this “feature” only seems to have introduced a new source of problems, where the server can suddenly throw its date and time setting off by as much as several months, often with unfortunate consequences for the applications running on it <https://arstechnica.com/security/2023/08/windows-feature-that-resets-system-clocks-based-on-random-data-is-wreaking-havoc/>. At this stage, Microsoft is still in the “no comment” stage of (not) responding to this problem. Reports of issues go right back to the introduction of the feature, back in 2016. They may only be happening intermittently, but it seems to me this is still enough to damage what trust there may still be left in Microsoft’s product.