New
#1
Something keeps changing my Windows time (new cmos battery)
Summary: my BIOS time was four hours off, I changed it to the correct time and now at various times my Windows time changes to four hours behind. No event of the time change in the event viewer.
This is a new motherboard and the BIOS time stays constant (read other posts saying a bad cmos battery can cause time to change). At first my Windows time kept losing about 3 minutes even after manually changing it and making sure the internet time is running. So I figured it was a problem with the BIOS time and changed it to the correct time (moved it up 3 hours 57 minutes - overlooked this when initially setting it up). Booted into Windows and the time was 4 hours behind. So I manually changed the time and thought nothing of it. Came back to the computer many hours later and the time was back to 4 hours off. Went to check the Windows internet time setting, which was set to run, and clicked update now. This set the time to the correct date/time, so the timezone settings, Windows time process, etc. are correct. Over the next few days the time kept moving back four hours after an extended period of time (and sometimes reboots - this was not consistent). I did the unregister/register w32tm and some other things with no luck.
The one odd thing about this is whenever I manually changed the time or the internet time changed it I always found an entry in the event log about the change. However whenever "whatever" is changing my time it is not logged, at least in the event viewer.
For now I "fixed" this by keeping the BIOS time four hours ahead. Yes this is a workaround but I would really like to find out what is changing the time. I ran sysinternals autoruns and there are a ton of things running at startup and is not going to be easy to check each one.
My guess is it must be some program/process running that checks the BIOS time against the Windows time but the timezone set in that program/process is not correct (must have been installed with incorrect BIOS time and related that to the Windows timezone.... just a thought).
Just wondering if anyone experienced this or has thoughts on what can be doing this or how to troubleshoot.
Thanks
Jay