I keep having to deal with this issue every now and then so I figured I might as well record what commands are needed to fix it up 99% of the time:
w32tm /config /manualpeerlist:"time.nist.gov time.windows.com time-nw.nist.gov time-a.nist.gov time-b.nist.gov time-a.timefreq.bldrdoc.gov time-b.timefreq.bldrdoc.gov time-c.timefreq.bldrdoc.gov utcnist.colorado.edu" /syncfromflags:manual /update
and then (note you can replace the server list with your own – these should work from anywhere but may not be suitable for intranets for instance)
w32tm /resync
Simple but fixes up lots of little time related issues.
NOTE
Just a reminder to people who host their virtual machines (VM) that some of time related issues are caused by VM picking up time synchronization from the host such as Hyper-V. In that case the above needs to be applied to the Hyper-V server as well.