New
#11
Try this
EDIT: I suspect that Set time zone automatically will be maintained and the Time zone has been entered below grays out and isn't changeable then and set time automatically will follow along and be correct.
Clock reverts to wrong time after a reboot
-
-
-
New #13
Turn off Set time zone automatically to enable a manual Time zone change. This is how mine is set and there are no issues...
In fact this is how it was set when I did a clean install on this system.
-
New #14
Yep! Same as I posted page #1.
Clock reverts to wrong time after a reboot - Windows 10 Forums
-
New #15
I had similar problem with Win 7 on a Acer laptop, each boot up, clock was a minute faster. even in the BIO's.
-
New #16
I saw that my settings were different than what worked for sygnus21 & Dick. It looks like the recommendation to check the BIOS since it's most likely UEFI. My BIOS isn't, it's Legacy. So checking the UEFI BIOS definitely makes sense.
-
New #17
Sorry I missed that. Got caught up in posting about the BIOS check. After posting that, I saw the other post and replied. Wish I could delete it now
Maybe I'm misunderstanding your post, but whether "legacy" or UEFI it makes no difference, a date and time will be there so check to make sure both date and time are correct.
-
New #18
I’m not good at multi-quoting so I’m just summarizing some items
On inconsistent time differences
At first the difference in time was “an hour behind or sometimes further” in post #1.
In post #9 the time reverted to 12:58, in post #10 it’s mentioned the time should have been 16:58 so that’s a 4-hour difference.
In post #7 shows a 3-hour difference “The time should be showing as 16:45 but as you can see it's sat at 13:45”
Stokesyboy those variable time differences match up with your comment “sometimes further”
--- Maybe it would make sense to contact technical support for the products support site.
Is this time difference a recently new issue the user has?
Stokesyboy post #3 “I have tried setting a trigger to start the service when the user logs on but this doesn't seem to work.”
sygnus21post #17
“Maybe I'm misunderstanding your post, but whether "legacy" or UEFI it makes no difference, a date and time will be there so check to make sure both date and time are correct.”
I need to clarify that. I didn’t think there shouldn’t be any difference as you mention, but I was questioning myself: why do my settings work and what is the difference? So Legacy vs. UEFI came to mind. I wasn’t questioning the setup you & Dick have. Sometimes when trying to differentiate some reasoning I admit it needs improvement on how to do so.
Oh my, another idea just came to mind
Is it possible there is "poor" or "inconsistent" connection with the Time Server when trying to use it?
-
-
New #19
Out of all the time issues I've had (very few) I've only had one where the Time server was involved, and switching that from Microsoft to Government solved that issue. And if I remember, that particular issue was when I was running XP some years ago. Outside of that I can't think of another instance where the "Time Server" was an issue. For the most part, if there's a Time issue it's usually BIOS involved whether CMOS battery related or a simple mistake is setting the date/time.
Anyway I've not heard back from the OP so I'm not sure what their fix was. If you're having the issue, the suggestions here would apply to you as well. And you'd be doing all a favor if you reported back on what you tried or didn't try and if the issue is resolved.
Thanks.
-
Quote
Related Discussions
