How to resolve time issues and Windows Key Activation issues?

Charles 0 Reputation points
2026-08-28T09:35:49.1633333+00:00

Hi,

I've come across an issue with a machine running Windows Server 2019 where we are unable to change the time settings at all whilst running as administrator. Whenever changing any settings it defaults back to what it was. Currently all the settings appear correct with the time zone however it's 1 hour behind exactly. Changing it to be manually set doesn't work and it reverts back after a short time.

We believed this stemmed from an issue with Windows not activating properly on the system. Unfortunately we don't have the product key itself but appears to have been registered on the device

Windows Product Key.png

I have tried to locate the key through the registry editor but it's appears as something different to the last digits in the screenshot. I applied the one from the registry editor but this is failing to activate with issues connecting to the activation servers.

Has anyone experienced this issue or have any suggestions?

Windows for business | Windows Server | Devices and deployment | Licensing and activation
0 comments No comments

1 answer

Sort by: Most helpful
  1. Allan Solomon Mejia 7,995 Reputation points
    2026-08-28T19:48:08.3166667+00:00

    Hi @Charles

    I’d treat these as two separate issues. Windows activation normally doesn’t control whether you can manually change the system time.

    For the time issue, the clock changing and then reverting strongly suggests that Windows Time (W32Time), Group Policy, the domain hierarchy, or the virtualization host is setting it back. Domain-joined Windows Server systems normally synchronize from the AD domain hierarchy.

    From an elevated Command Prompt, check:

    w32tm /query /source
    w32tm /query /status
    w32tm /query /configuration
    

    If this is a domain member, the source should normally be the domain hierarchy. Also verify the configured time zone/DST, since being exactly one hour out often points to a time-zone or daylight-saving configuration issue rather than an incorrect clock.

    For activation, don’t rely on a product key recovered from the registry. It may be a generic KMS client key (GVLK) rather than the organization’s actual license key. Microsoft specifically uses GVLKs for KMS/volume-licensed systems.

    Check the actual licensing state with:

    slmgr /dlv
    slmgr /xpr
    

    /dlv should tell you the installed edition, license status, and activation channel (Retail/MAK/KMS, etc.). If it shows KMS, troubleshoot connectivity/DNS to the organization’s KMS host rather than trying to recover and reinstall the registry key.

    Start with those outputs before reinstalling Windows or purchasing/replacing a key. The time issue is very likely independent of the activation problem.

    Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.