Windows clock (bottom-right corner) shows diffrent time than system timer ('Time' command result in Command Prompt)

Anonymous
2024-03-22T15:20:29+00:00

I have an issue recently (for the past few weeks) where the System clock (Synchronized with the domain) is accurate but the clock in the task bar (bottom-right) corner) is different; sometimes 35 minutes, other times; 3 hours.

A restart resolves the issue; anther issue linked to this is the icons (open applications) in the task bar are not displayed. Nothing abnormal is logged in Application, or Systems logs.

Any suggestions?

Windows for business | Windows Client for IT Pros | Performance | System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-25T06:31:18+00:00

    Hello,

    Thank you for posting in Microsoft Community forum.

    Based on the description, I understand your question is related to Windows clock displaying the incorrect time in the taskbar.

    1. Press the Windows key + R
    2. Type "services.msc" and press Enter.
    3. Locate the Windows Time service and right-click on it.
    4. Select "Stop"
    5. Right-click on the service again and select "Start" to restart it.

    If this does not resolve the issue, you can try syncing the clock manually by following these steps:

    1. Right-click on the clock in the taskbar and select "Adjust date/time."
    2. Under the "Date and time" section, toggle the "Set time automatically" switch off and then on again.
    3. Click on the "Sync now" button to manually sync the clock.

    If the issue persists, you may want to check with your IT department to ensure that the domain time is set correctly and that there are no issues with the domain controller.

    Hope this helps!

    Have a nice day. 

    Best Regards,

    Molly

    0 comments No comments
  2. Anonymous
    2024-03-25T12:52:28+00:00

    Thanks Molly; appreciate the suggestion. That resolves the issue; but it is a stop-gap fix. Our workstations are synchronized to the Windows AD (FSMO master) Since the time is off, the icons on the Start Menu, also, "disappear" (can't think of a better word).

    This is happening to multiple; not all (Windows 11 Pro) workstations; but the Windows 10 clients are fine. These are Dell, HP, and Lenovo out-of-box workstations (so OEMs build image may not be the culprit). I did not notice any significant Windows Event Log entry that could relate to this issue.

    Any suggestions?

    0 comments No comments
  3. Anonymous
    2024-03-28T07:43:18+00:00

    Hello,

    You're welcome! I'm afraid that is the current workaround for this issue, it is also recommended to report your feedback to Microsoft through this website:

    Ideas · Community (microsoft.com)

    Have a nice day. 

    Best Regards,

    Molly

    0 comments No comments
  4. Anonymous
    2024-09-18T04:23:15+00:00

    I was having issues with this very same issue on my Acer computer and tried all sorts of fixes found on forums to no avail. I took it into Geek Squad and they told me that my internal battery was failing. But my laptop was also pretty old and slowing down so I downloaded a widget to display the correct time and overlaid it until I invested in a new computer.

    I bought a new HP a couple weeks ago and am having the same issue. Reading this, it sounds like this is a Microsoft glitch. What more is being done about it since March?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-09-20T14:45:11+00:00

    KarlaK73,

    Glad that resolved the issue for you. Appreciate the guidance. I am not convinced a similar process would resolve the issue for me. I have multiple, out-of-the box, workstations joined to a Windows AD Domain that exhibiting the same behavior multiple times per day; and a restart resolves the issue.

    0 comments No comments