Main Area and Open Discussion > General Software Discussion

How to manually set clock in Windows 10 Pro?

<< < (2/2)

Nod5:
Please, is there any way to set the clock MANUALLY?
-rjbull (October 30, 2020, 07:14 AM)
--- End quote ---

What Deozaan wrote. Or if you prefer the command line, open windows terminal and use the command "time".
https://ss64.com/nt/time.html

x16wda:
Worth mentioning Dimension4 here.

Shades:

* Right-click the clock in the tray.
* Select "Adjust Date/Time"
* Deselect "Set Time Automatically"
* Click "Change" below "Set the date and time manually"
* Set the time and date to your preference.
* Click "Change" to confirm your changes.
[ Invalid Attachment ]
[ Invalid Attachment ]
-Deozaan (October 30, 2020, 01:40 PM)
--- End quote ---

A change that may be altered back to what the time server at windows.com thinks your clock must be set to. To my knowledge that happens once a day.

Alteration to computer clocks were made by that time server on workstations and servers alike. As you may or may not know, I live in an area where 'el presidente' chooses the moment DST is applied. More often than not that was a different day than what the US or the EU are using for their DST changes.

You think you are irritated by predictable differences between the 2 most common DST systems? Hah! Try mixing a random DST change in, before or after those DST changes. Because sometimes government hated the US, sometimes government was unfriendly with the EU when DST needed to be applied. Politics petty? Damn right it is. Everywhere. And every 6 months a surprise.

How many meetings between employees of us and companies in the EU had to be rescheduled, because of those DST mishaps....

Anyway, Asuncion, the city where I live has its own time zone. To make matters even more fun. You know what truly solved almost all DST problems? Using practically any time server other than the one hiding behind the URL 'time.windows.com'. Yes, the default time server in Windows is the worst NTP time servers around. Seriously, 95% of all my semi-annual DST issues/conflicts went out of the door, by simply adjusting to a time server for the South-Americas. These are maintained by people who take time much more seriously than whoever is in control of the 'time.windows.com' time server.

Changing the clock like the instructions show you here in this thread...that gets old quick if you have to do that daily on every computer under your care for around 2 months a year.

You might think the time server at 'time.windows.com' isn't so bad, but that is only because you live in a time-zone with predictable DST changes. seriously, find out what NTP server is handling time for the continent you live on and use that server instead. After you have done so, I will be the first person you send your Christmas cards to from that moment on...yes, it is that much of a difference.

Look here for your (national/continental) NTP server:
https://www.ntppool.org/en/

As most computers in the world run on Windows, you would think that MS would put competent people to manage 'time.windows.com'. Instead, there are over 4000 different time servers active globally as of this moment. If that is not an indicator the default time server in Windows makes a mess of keeping time...

DST and time zones, from a programmer's perspective:  https://www.youtube.com/watch?v=-5wpm-gesOY
Hell....

rjbull:
Many thanks, folks! :)

I tried 4wd's advice to change to uk.pool.ntp.org, and so far, after a couple of days, things seem to be OK.  I was annoyed with myself for forgetting TIME in a console, considering how much I did at the command line in the old days: too much windows atrophies your brain...  I've also downloaded Dimension4 against need.  If a Windows update resets to time.windows.com, that's what I'll try next.

Navigation

[0] Message Index

[*] Previous page