Eaglet, If you your hardware clock is set to UTC you should never use the -localtime flag because it will give you incorrect (and potentially very confusing) results. You can add multiple crontab files if you need to, but the only thing you have to remember. The -utc and -localtime flags to hwclock are to tell hwclock which timescale the hardware clock is set to ( hwclock assumes UTC, so the -utc flag is redundant). You’ll now need to launch a command prompt window as an administrator and execute the following command. It requires 3 things: hardware clock being set correctly (to either UTC or local time), your OS knowing whether hardware clock is set to UTC or local time, and your OS knowing your time zone. Even with the registry fix, Windows will continue to write local time. So as you can see, your OS showing you the correct local time is a complex operation. Thu Mar 5 10:35: # yep, that's the correct local time Therefore, when "date" or "hwclock" command puts it all together, it should spit out my correct local time: VMware products use multiple methods to detect tickless timekeeping. # So hardware clock is set to the correct UTC time, OS knows to interpret hardware clock as UTC, and my timezone is correct. Many PC-based operating systems use tick counting to keep time. That line tells the OS how to interpret the hardware clock.
![force windows to use utc clock dual boot force windows to use utc clock dual boot](https://mspx.kapilarya.com/Windows-10-wrong-time-2.png)
# Notice the third line in the output above. # Hmmm, hardware clock says it's 15:35, so it's obviously set to UTC. Time read from Hardware Clock: 5 15:35:32 Changing Linux to use local time is easier and more reliable than Windows replacement to use UTC, so dual-boot Linux / Windows systems usually use local time. $ sudo hwclock -get -debug | grep "Time read" # this command will show exactly what the hardware clock is saying