<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on Matt Ellis</title><link>https://matt-ellis.dev/tags/windows/</link><description>Recent content in Windows on Matt Ellis</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Tue, 30 May 2023 10:17:56 +0100</lastBuildDate><atom:link href="https://matt-ellis.dev/tags/windows/atom.xml" rel="self" type="application/rss+xml"/><item><title>Hardware clocks and dual boot</title><link>https://matt-ellis.dev/rambles/hardware-clocks-and-dual-boot/</link><pubDate>Tue, 30 May 2023 10:17:56 +0100</pubDate><guid>https://matt-ellis.dev/rambles/hardware-clocks-and-dual-boot/</guid><description>&lt;p&gt;So completely random (as always I guess) but I started noticing a problem with my
windows PC when booting it up in the evening. I&amp;rsquo;d be working away or more likely playing
games when I&amp;rsquo;d notice that the time on my PC was an hour behind the time on my phone?&lt;/p&gt;
&lt;p&gt;So after a bit of research and learning about hardware clocks (RTC, real time clock), it
turns out that the issue was due to my dual boot linux setup. Windows reads the hardware
clock on startup and then uses the system clock from then on. Windows interprets the
time set in the hardware clock based on local time, and so here in the UK it is UTC/GMT
+1 hour (during summer). On the otherhand, when Linux boots up, it assumes that the time
stored in the hardware clock is UTC and so it&amp;rsquo;s actually &amp;ldquo;an hour behind&amp;rdquo;.&lt;/p&gt;</description></item></channel></rss>