To make MS Windows calculate the time from the hardware clock as UTC.Ĭreate a file named WindowsTimeFixUTC.reg with the following contents and then double click on it to merge the contents with the registry: Windows Registry Editor Version 5.00 Note: This method was not initially supported on Windows Vista and Server 2008, but came back with Vista SP2, Windows 7, Server 2008 R2 and Windows 8/8.1. If you are OK with your hwclock (BIOS) to be in UTC, then change windows to be UTC. If you want your hwclock to show the time in your timezone, then you will need to change linux to not be UTC, which means make linux use localtime. The conflict usually comes about because Linux uses the the hwclock set in UTC, while Windows uses the hwclock set to the localtime zone. I would highly suspect Ubuntu and Windows disagreeing on whether the hwclock is localtime or UTC. UPDATE: It turns out that switching from Ubuntu to Windows triggers the 5 hour offset every time, so it was indeed an issue with the hardware clock being set to Universal/Local by Ubuntu/Windows, respectively. It would seem to me that Windows is occasionally syncing with the wrong time zone, but I have no idea how to verify or correct that. What strikes me as strange is that the time is exactly five hours off, not a minute more, even adjusting for DST. This question is very similar to my own, but the issue there was caused by the hardware clock being off, and the clock shown in BIOS on my computer is set to the correct time. ![]() ![]() I've looked through similar time-related issues on the internet, but none seemed to match mine. I currently have Ubuntu 16.04 installed in a dual boot configuration (the problem started before I installed Ubuntu), and I haven't seen any similar issues with the Ubuntu clock. It only happens on Windows startup, but not every time. This issue started immediately after erasing my hard drive and reinstalling Windows 10 from scratch, so it's not caused by anything I've installed since then. This operation returned because the timeout period expired." "An error occurred while Windows was synchronizing with. I have internet time set to sync with, and when manually synchronizing the time, it correctly sets the clock, although the following error message appears when doing so: I've checked my time zone settings and it's set to the correct time zone. It adjusts for Daylight Savings Time as well staying 5 hours ahead. ![]() So if it's noon where I live (Eastern time zone), the clock says 5pm. Sometimes when I start up Windows 10, my clock displays a time that is 5 hours ahead of the current time. I've been having this strange issue with my system clock.
0 Comments
Leave a Reply. |