76
35
EDIT 2015-SEP-30:
Seems I actually ended up with localtime enabled in Linux somehow, probably as a consequence of a reinstall some time ago. I switched Linux to UTC and now my configuration seems to be working fine.
Related to Does Windows 7 support UTC as BIOS time? and Does Windows 8 support UTC as BIOS time?, does Windows 10?
I've successfully used the method recommended in those two questions in the past with Windows 7 but it doesn't seem to be working with Windows 10. I believe I had the same problem with Windows 8.1. I'm not sure about Windows 8.
I've tried a multitude of different configurations for date/time settings (from right clicking the clock and selecting "Adjust Date/Time). My current configuration is:
Set time automatically: On
Time Zone: (UTC-05:00) Eastern Time (US & Canada)
Adjust for daylight saving time automatically: On
I've also tried instructing it not to set time automatically (which I think I may have done in Windows 7?) and not adjusting for daylight savings time.
I've tried setting the registry value (from the linked questions) to a QWORD instead as recommended in https://wiki.archlinux.org/index.php/System_time#UTC_in_Windows but it still had no effect.
Has anyone had any success in using UTC time in Windows 10 and if so was it necessary to do anything differently compared to Windows 7?
Thank you, though this does not resolve the problem (it sounds like you've tried the same as me) it's helpful to know someone else has this working in Windows 10. – Dylan – 2015-09-20T23:33:24.480
@Dylan Yep. The only though I have (if you did it really the same) is that they might have deactivated this feature on the Home Editions or similar. Using Enterprise here. But otherwise I have no idea. – larkey – 2015-09-20T23:38:02.333
4DWORD works fine also in 64 bit mode home edition. Also: note that ntpd may refuse to change if the time difference is too large (which it may be in case windows 10 already started writing to the hardware clock - if so, run ntpd as root ntpd -q). – j-a – 2016-09-23T20:00:54.343
1@j-a I could imagine that DWORD works most of the time but that the actual value is a QWORD, so there might be problems using DWORD if something isn't initialized properly or such – larkey – 2016-09-23T20:19:53.203
7Why does internet update have to be disabled? – gamen – 2016-11-16T16:27:27.403
3@gamen Good question actually, but it seems that MS is using the internet time to sync with the hardware clock while ignoring the Registry setting, ie. setting the clock to your localtime while interpreting it as UTC. – larkey – 2016-11-16T18:57:54.937
9@larkey I thought I'd try it to see what happened, and it works so far - I'll re-post if this changes; multiple reboots, switching between OS:es. My system time is in UTC, the local time is UTC+1. Set Time Automatically and Adjust for daylight saving time automatically are On, Set zime zone automatically is Off, and the RealTimeIsUniversal registry key QWORD is set to 1. I'm on x86_64, Windows 10 Pro (Build 10586). It might also be worth mentioning that I'm not using a Microsoft time server. – gamen – 2016-11-17T11:48:32.070
the .reg file worked for me, Windows 10 Enterprise (64 bit, but with the DWORD key as posted). – Brian Minton – 2016-11-19T22:29:04.363
1I had to disable internet time updating but could reactivate it afterwards, and now it seems to work fine in either case – Tobias Kienzler – 2017-01-07T19:50:13.407
8Just a comment in the sense of an affirmation: I have the 64bit version of Win10 and the DWORD version did not work. The QWORD-way was the right one for me. I did not have to enable or disable any other option, btw. – henry – 2017-05-06T10:32:53.310