![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 15%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBT%3C/text%3E%3C/svg%3E)
28,661 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello Barbara Turner，
Thank you for posting in Q&A forum.
The 2036 rollover issue specifically affects systems using a 32-bit value to count the number of seconds since January 1, 1900. This 32-bit value will overflow on February 7, 2036, causing potential issues with timekeeping and synchronization.
Systems using a 64-bit value for time representation, such as the Network Time Protocol (NTP) version 4, do not face this problem because a 64-bit value can represent a much larger range of dates.
Windows 10 uses the Windows Time service (W32Time), which follows the Network Time Protocol (NTP) specification. The specific version of NTP implemented in Windows 10 is based on NTPv3, It will still be affected by the issue.
However, it's crucial to keep your system updated with the latest patches and updates from Microsoft to ensure all potential issues are addressed.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy Zhou
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.