• This topic has 16 replies, 11 voices, and was last updated 6 years ago by tonyjohn29-spam.
Viewing 17 posts - 1 through 17 (of 17 total)
  • Why is my Windows 10 clock wrong?
  • gobuchul
    Free Member

    My laptop is showing the time 1 hour slow.

    I have checked the settings and it is set to automatically update for daylight saving, on the London time zone and set to update from the internet.

    It shows it successfully synced this morning but still shows the wrong time.

    Any ideas?

    Flaperon
    Full Member

    Search for “control panel”, then “clock” to bring up the traditional time setting options and try making the change from there. There’s a tab for internet time where you can force an update. Oh, and make sure the timezone is set to London, not GMT.

    (If that doesn’t work, then try the Modern settings pane instead by right-clicking on the time in the taskbar and choosing “Adjust date/time”).

    gobuchul
    Free Member

    Tried both the app and the control panel settings. No joy.

    sl2000
    Full Member

    Can you run the following commands in a powershell prompt and let me know what they say. It’s possible (but unlikely) that we’ll see something obviously wrong here that isn’t obvious in the Windows UI…

    get-date

    [System.TimeZone]::CurrentTimeZone

    get-itemproperty HKLM:\SYSTEM\CurrentControlSet\services\W32Time\Parameters NtpServer

    CaptainFlashheart
    Free Member

    Brexit

    yourguitarhero
    Free Member

    Microsoft’s internet services are out by an hour for 6 months of the year (between clocks changing in March and October), so my Outlook.com calendar appointments are out unless I manually change the clock on devices (Windows 10 desktops and Windows and Android phones). You have to set it to UTC then disable all automatic time/daylight saving updates and set the time manually.

    Been like that for years and I missed my haircut once

    Cougar
    Full Member

    NTP won’t work if the clock is too far out. Try manually setting it to a couple of minutes out and then force an update as above.

    gobuchul
    Free Member

    JackHammer
    Full Member

    Cos we’ve gone back to 1976 or something #Brexit.

    gobuchul
    Free Member

    NTP won’t work if the clock is too far out. Try manually setting it to a couple of minutes out and then force an update as above.

    Cougar wins the prize for best free IT support again. 😀

    That did the trick.

    Cheers.

    Cougar
    Full Member

    Oh, they’ve moved away from time.windows.com, I didn’t know that. It’s about, er, time.

    Try changing the server to a more local one – I’d recommend uk.pool.ntp.org

    Cougar
    Full Member

    Ah, cool. (-:

    scaredypants
    Full Member

    Cougar wins the prize for best free IT support again.

    What’s that they say – “Say nothing and have everyone think you’re a fool, or speak up and prove it”. Oh, OK then:

    I don’t doubt Cougar’s skillz but that’s still shite isn’t it – You can make your machine automatically sort out the time changes but only if you manually adjust it most of the way first ? 😯

    (my W10 just did it FWIW – I reckon you have a dodgy setting. Maybe it thinks it’s a phone & trying to sync with that sort of network or, err, something)

    😳

    mattyfez
    Full Member

    I had an issue when I built my new pc a few months back, after manually correcting it a few times it seemed to sort itself out, and it remains a mystery as it’s fine now.

    Cougar
    Full Member

    You can make your machine automatically sort out the time changes but only if you manually adjust it most of the way first ?

    It’s nothing to do with your machine. that’s how NTP works. It’s whole raison d’etre isn’t to magically set clocks, it’s to correct inaccurate ones. An NTP client will monitor local time against a “known good” remote time source and quietly adjust it by a few nanoseconds here and there if it starts to drift. If it’s too far out to start with, NTP assumes it’s wrong rather than inaccurate and leaves it alone.

    (For the benefit of the Windows haterz, it’s nothing to do with Windows either. NTP has been around since the mid-80s.)

    Cougar
    Full Member

    Oh, and,

    Any changes to things like daylight savings are handled by the OS. NTP has no concept of things like time zones, it’s a GMT time source (more correctly “UTC,” GMT is a time zone in itself). Windows knows the date BST starts and ends, and adds an hour to the UTC time in summer to give you the correct display time.

    Phones work differently, they don’t use NTP. The date and time are encoded into (I think) the GSM signal. Similarly with DAB radios.

    GlennQuagmire
    Free Member

    Windows and time zones is a bit of mash really. The correct time zone for the UK is “GMT Standard Time”. GMT is a time zone but was also used as a time standard. UTC (or Coordinated Universal Time) is a time standard and follows the same time as GMT. UTC ultimately replaces GMT as the “standard” used worldwide.

Viewing 17 posts - 1 through 17 (of 17 total)

The topic ‘Why is my Windows 10 clock wrong?’ is closed to new replies.