Currently, we believe this issue is caused by a mysterious problem in Windows. Below is an interesting (but lengthy) article about the phenomenon, including a workaround. Aside from that, there's not much else we can do from a Lansweeper perspective.
https://arstechnica.com/security/2023/08/windows-feature-that-resets-system-clocks-based-on-random-d...
If you check the Windows event log on the affected asset, you'll notice that the Windows clock was set to a future time, then shortly afterward, it was corrected back. We've observed this phenomenon a few times over the years, but it remains a relatively uncommon event.
