I use both Linux and Microsoft Windows on one of my PCs. \u00a0Linux by choice, Windows due to compatibility issues with some drivers\/software that I need for my work.<\/p>\n
I noticed that my Windows clock was misbehaving. \u00a0It was 2 or 3 (when using summer time) hours early, meaning it was displaying UTC time and not my local time (UTC+2, UTC+3 respectively).<\/p>\n
That was weird! \u00a0I had set the timezone correctly. \u00a0If I set the correct time manually, Windows would alter the hardware clock, and this would cause Linux to display the shifted time now.<\/p>\n
After a bit of googling, I found out that Windows is at fault here, as it can’t interpret the hardware time correctly. \u00a0It takes the BIOS time as its local time, and adds or subtracts the timezone difference to set the Windows time.<\/p>\n
There is a registry fix for Windows to deal with this. \u00a0You can create a .reg file with the following lines and import it into your registry, or edit the registry manually (use regedit), as I did, since the .reg file import didn’t work for me in Windows 7.<\/p>\n
[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\TimeZoneInformation]\r\n\"RealTimeIsUniversal\"=dword:00000001<\/pre>\nThis will cause Windows to display the time correctly, and not set the wrong time in the BIOS.<\/p>\n
Linux, on the other hand, correctly interprets the hardware clock time as UTC time.<\/p>\n
After the fix, both OSes display the correct time for my timezone. \u00a0Yay!<\/p>\n
If one only uses a single OS on his computer, there is no such issue. \u00a0I, at least, \u00a0haven’t encountered it.<\/p>\n
I dual boot Debian Linux and Windows 7 Professional and came across this issue, your mileage may vary.<\/p>\n","protected":false},"excerpt":{"rendered":"
I use both Linux and Microsoft Windows on one of my PCs. \u00a0Linux by choice, Windows due to compatibility issues with some drivers\/software that I need for my work. I noticed that my Windows clock was misbehaving. \u00a0It was 2 or 3 (when using summer time) hours early, meaning it was displaying UTC time and … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[19,20],"tags":[],"_links":{"self":[{"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/posts\/79"}],"collection":[{"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/comments?post=79"}],"version-history":[{"count":7,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/posts\/79\/revisions"}],"predecessor-version":[{"id":216,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/posts\/79\/revisions\/216"}],"wp:attachment":[{"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/media?parent=79"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/categories?post=79"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thinkdebian.net\/blog\/wp-json\/wp\/v2\/tags?post=79"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}