The Windows Time service does not indicate the value of the Leap Indicator when the Windows Time service receives a packet that includes a leap second. Therefore, after the leap second occurs, the NTP client that is running Windows Time service is one second faster than the actual time. This time difference is resolved at the next time synchronization. This behavior will mitigate any potential issues that a leap second could cause.
For more information, please see the following Microsoft article: