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.