5 ms·
>The time on all contemporary computers is always Unix Epoch Time, which is close to (but not exactly) UTC. I think Windows computers set the hardware clock to
by ericye16 6y ago
>The time on all contemporary computers is always Unix Epoch Time, which is close to (but not exactly) UTC.
I think Windows computers set the hardware clock to local time by default, actually.
- rzzzt 6y agoThere is a way to switch the behavior in either systems, although each comes with its own caveat: https://www.howtogeek.com/323390/how-to-fix-windows-and-linux-showing-different-times-when-dual-booting/ https://www.howtogeek.com/323390/how-to-fix-windows-and-linu...
- TeMPOraL 6y agoThere must be. I dual-boot between Ubuntu and Windows 10, and whenever I boot up Windows, the clock is behind one or two hours (DST-depending), until it re-syncs itself from the Internet after a while. Ubuntu seems immune, though. So either Ubuntu is smarter about reading the hardware clock, or Windows side writes to the clock differently than it reads from it.
- kasabali 6y agoYou need to configure Windows for using UTC when it's dual booting with Linux.
- cmurf 6y agoLast time I checked three years ago, the UEFI spec states that the hardware clock (rtc) is set to "current local time". UEFI runtime service's GetTime() includes TimeZone value in minutes offset from UTC, and a Daylight bitmask. Windows, Linux, macOS, all set the timezone value to 0x07FF which is defined as EFI_UNSPECIFIED_TIMEZONE which is to be treated as local time (but without a timezone). In effect, it's the same mess as BIOS. It shows how specs can just be thwarted.
- doctor_eval 6y agoI haven't played with Windows since the 90s and just assumed that would have been fixed by now! It seems really silly to set the RTC to local time. Especially given that most devices are mobile these days. Put it to sleep in Melbourne and it wakes up in Singapore...