Windows 10: time wrong, while time zone is correct.

Every boot my computer's clock is 7 hours fast.
The time zone is correctly set to UTC -08:00
I have set it to synchronize with time.windows.com as well as time.nist.com, to similar results.

When clicking the "update now" button I get the error: "An error occurred while Windows was synchronizing with time.foo.com. This operation returned because the timeout period expired."

(and with traditional Microsoft incompetence this error message was placed in the actual dialog, so no copy and paste! I get to type everything out!)

Clicking it again successfully synchronizes it.

I DO NOT want to do this every damn boot, as it requires clicking through 5 separate dialogs. What the hell is up here?

:)

 

Time Zone is right- wrong time

What does rebooting do to the time?

How old is the computer? Has the motherboard battery ever been changed?

 

Time Zone is right- wrong time

Think maybe 8 out of 10 times that I install windows the time is off even if the time zone is correct. But usually off by even hours and minutes.

Something has changed though fairly recently - dont recall ever needing to manually start the w32time before running the sync.

some commands, Command prompt admin

sc start w32time

w32tm /resync /nowait time sync.

time /t current time

time to set current time

 

"time.foo.com" returns a message that it does not exist when pasted into the URL box [Address box]. One thing usually necessary is to enter the BIOS Setup during the bootup and set the time correctly. Then I sometimes find it necessary to go into Settings and turn Off the automatic check and set of the time.

 

I'm... not sure if you're serious... I'll clarify the wording. "foo" is the universal space filling "variable" so to speak when it comes to software, when the actual contents of whatever "foo" is replacing are not relevant. "bar" is also often used when "foo" is already in use.

I never actually tell it to go to "time.foo.com", I'm saying that "time.{windows,nist, etc}.com" is what I'm telling it to go to and that all behave the same.

 

Had to go with what was posted, if wrong then obviously it was done wrong, not my problem. In this day and age of technology one never knows what is accurate/valid and what is not.

 

Also I just took a look at the time in bios and it was also correct.

 

By the way, just set up a new desktop... guess what happens? time gets offset once again.

Same issue with attempting to update the time and getting the error message that the operation timed out. Do it again and it works. Has literally ANYONE had this issue?

 

Are you only running Windows on your machine?

Live Linux Distros often change the time.
Unfortunately LM18 does this after it has been installed (the first time I've ever experienced this with an installed Linux OS).

What I find weird is that Windows doesn't time sync during boot/login.

 

Excellent information lehnerus! I do in fact have ubuntu 16.04 installed on both machines. Now that you mention it this issue only started happening when I installed 16.04 (clean install) I'll get back to you if I can reproduce the issue either by simply booting into my linux partition, or by doing something in there. If not I'll continue to research.

Thanks tons lehnerus!

 

Linux uses UTC and sets it in bios while it remembers your time zone , while windows does it the other way round - thus Windows gets outta sync - but anyway, you can set the "Network time" off in Ubuntu and still sync with time.foo

 

The easy way is to go into /etc/default/rcS and cange UTC = yes to UTC = no.

There is a third party time sync TSR that you can run in Windows to use as a bandaid, if you forget to go into the Bios when using tools like Clonezilla to clone a drive.

 

I tried that fix in LM18 MATE about a month ago.
I didn't mention it, as (on my PC) it worked the first time (test run) but it hasn't worked since. *Sad

Note:
I haven't checked to see if something creates a new version of that "rcS" file at every boot/login.

 

It is a factor of two evils. This is where the other file is that affects clock settings.

2.4 How Linux keeps Track of Time Zones

You probably set your time zone correctly when you installed Linux. But if you have to change it for some reason, or if the local laws regarding DST have changed (as they do frequently in some countries), then you'll need to know how to change it. If your system time is off by some exact number of hours, you may have a time zone problem (or a DST problem).


Time zone and DST information is stored in /usr/share/zoneinfo (or /usr/lib/zoneinfo on older systems). The local time zone is determined by a symbolic link from /etc/localtime to one of these files. The way to change your timezone is to change the link. If your local DST dates have changed, you'll have to edit the file.

The Archwiki has saved my rear a few times when working with Linux. I always use Webmin on those machines that are servers. I used to swap between Linux Mint and Windows 10 when 10 first came out. I would keep a up to date cloned image on my NAS, so that I could use Clonezilla to swap the install on my Laptop that I had at that time. I do not even bother with dual boot on my Macbook Air, since my wife has Windows 10 on her laptop.

 

Thanks for that tip. *Smile

I haven't had any time to look into it yet (too busy battling Android+Java+MVC).