Using UTC in Windows can cause some problems
There's a fair amount of evidence to show that when you run Windows with UTC time, things get hairy:
Most people shouldn't get touched by this, but I know plenty of times I've been bugged (namely, every single debugger reads the BIOS clock and attempts to not de-botch itself) when using Windows with UTC time. In my experience, Windows 8 also will force BIOS time into being Un-DST adjusted Localtime. Dangerous!
Local time adjustment applied twice by Windows and Arch
After setting both Arch and Windows to use UTC, my time had a problem where it seemed that the localtime seemed to have adjusted twice for my local timezone. Upon further examination of the settings in Windows, I set the Time Zone in windows to GMT. This fixed my issue and I believe this is because The time zone adjustment was applied twice first by Arch (timedatectl set timezone) and then again by windows (Date and Time -> Time Zone in windows). I think it is a reasonable mistake by anyone setting up a dual boot to set the timezone in both operating systems, and I am not sure if this is worth mentioning in the article. I am also not completely sure if this is what caused my problem and wonder if someone could try to reproduce this situation.
- Did you add/modify the registry key per Time#UTC_in_Windows? What version of Windows are you using?
- -- Jstjohn (talk) 06:40, 9 July 2013 (UTC)