This method is buggy in pre-7 versions of Windows, but it resolves the issue on the Windows side of the equation, rather than on the Linux end: you don't have to set Linux to use localtime.
Taken from the most glorious and esteemed Arch Linux Wiki:
One reason users often set the RTC in localtime is to dual boot with
Windows (which uses localtime).
However, Windows [can handle the RTC being UTC] with a simple registry fix. It is recommended to configure Windows to use UTC, rather than Linux to use localtime.
regedit, add a
DWORD value with hexadecimal value
1 to the registry:
You can do this from an Administrator Command Prompt running:
reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f
Alternatively, create a *.reg file (on the desktop) with the following content
and double-click it to import it into registry:
Windows Registry Editor Version 5.00
If the above appears to have no effect, and a 64-bit variant of Windows is being used, using a
QWORD value instead of a
DWORD value may resolve the issue.
Windows ask to update the clock due to DST changes, let it. It will
leave the clock in UTC as expected, only correcting the displayed
The hardware clock and system clock time may need to be updated
after setting this value. If you are having issues with the offset of
the time, try reinstalling tzdata and then setting your time zone
# timedatectl set-timezone America/Los_Angeles