As noted previously, Microsoft has improved timekeeping in Windows 10 and as of 2018-06-01 FILETIME is now TAI - 37 seconds instead of UTC.
Yesterday Dan Cuomo posted a blog entry https://techcommunity.microsoft.com/t5/Networking-Blog/How-NOT-to-test-the-Windows-Time-Service/ba-p/411592 which has explicit apologies for how bad time once was on Microsoft and refers back to a February post https://techcommunity.microsoft.com/t5/Networking-Blog/Top-10-Networking-Features-in-Windows-Server-2019-10-Accurate/ba-p/339739 which states that Microsoft will not smear (except, of course, when the system is configured to run the old way without leap seconds) with references to financial regulation agencies and Matsakis, Levine, Lombardi at ION last year. I am impressed that Microsoft has managed to go somewhere that POSIX still refuses to go. -- Steve Allen <s...@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 https://www.ucolick.org/~sla/ Hgt +250 m _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs