I’ve written enough about the challenges of Windows devices and the real-time clock that you’ve probably heard this one before: Windows stores the time in the real-time clock in the local time zone, which causes problems if you install a new OS on the device and it boots up in a different default time zone […]Windows 10 and a PC’s real-time clock — Out of Office Hours
Mike makes a good point here. So much behavior today in setup/deployment/config of PCs and updates to PCs is guided by practice set back in IBM PC/AT Bios days. Real-time clocks should all be UTC with the offset calculated by location, or sync based NTP settings. That way you’re always at least “correct” to UTC, you just need to refine the display of that UTC counter to the human being running the computer. By now, one would have thought this was solved or coordinated. But it’s all just random, with set workflows, and production steps for each and every computer manufacturer. Me personally, I’m going to follow Mike’s sterling example. I’m going to set my Win10 Registry setting to use the UEFI UTC real clock for my system clock and be done with it.