Windows clock keeps showing the wrong time

Separate display offset from clock synchronization

Open Settings > Time & language > Date & time. Confirm the intended time zone and any applicable daylight-saving setting. A successful time sync can still display the wrong local hour when the zone is wrong.

If only a calendar or web application shows the wrong time while the Windows clock agrees with the independent reference, inspect that application’s time-zone preference. Do not move the system clock to compensate for a single application.

Use the normal synchronization control

On a personal PC, check Set time automatically and use Sync now if offered. Record whether it succeeds and the displayed last synchronization time. A control that is unavailable or organization-managed is a reason to ask the administrator, not to overwrite policy.

If automatic time-zone detection chooses the wrong location, use the correct manual zone when permitted. Keep this separate from the automatic clock setting so you can tell whether the problem was location or time-source access.

Investigate a failed sync without replacing the source

Confirm ordinary network access and any required work VPN. Internet browsing does not prove the configured time service is reachable. On a managed PC, preserve the error and let IT check its intended time hierarchy.

For an authorized local diagnostic, open Command Prompt as administrator and run the read-only query below. Record Source and Last Successful Sync Time, or the exact service error. A local-clock source or missing recent sync is evidence to investigate, not permission to configure an arbitrary public server.

w32tm /query /status

Observe when the wrong time returns

After correcting the approved settings, compare after a normal restart and after an ordinary shutdown. Record whether the error appears before network access or only after connecting. If it occurs only after starting another operating system or resuming a virtual machine, include that sequence in the report.

A date that repeatedly resets after power-off can involve firmware clock retention, but that observation alone does not prove a particular battery has failed. Consult the PC maker before opening hardware or changing firmware settings.

Keep security and application evidence intact

An incorrect clock can accompany update or sign-in trouble, but correcting time is not proof that every application failure is fixed. Retest the original action and keep any remaining error separate.

Do not set an intentionally false date to bypass certificate warnings, disable time services, or repeatedly unregister and recreate the time service. On devices used for scheduled work or records, coordinate any significant correction with the responsible administrator.

Verification

• Compare the corrected Windows time and zone with the independent reference.
• Check after restart and the next ordinary shutdown/start cycle, recording whether synchronization completes.
• Retry the affected update, sign-in, or application action without bypassing security checks.

When to stop

Escalate a managed time source, repeated sync failure on a working network, or a date that resets after power-off. Give support the offset, timing, source query, and device context. Hardware clock retention and virtual-machine time need the relevant owner’s diagnosis.

Review the safe troubleshooting workflow before any broader recovery step.