Overview
Windows computers automatically synchronize their system clock with a time source. In some cases, the clock may become out of sync, which can cause issues with authentication, domain services, certificates, and applications.
You can manually force a time synchronization using the w32tm command from an elevated Command Prompt.
When to Use This
Use this procedure if:
- A computer’s clock is incorrect
- Authentication or domain logon errors occur
- Kerberos or certificate errors appear
- A system recently joined the domain
- Time synchronization appears stuck or outdated
Steps to Force a Time Sync
1. Open an Elevated Command Prompt
You must run the command prompt as an administrator.
Option 1
- Press Windows Key + X
- Select Command Prompt (Admin) or Windows PowerShell (Admin)
Option 2
- Open the Start Menu
- Search for cmd
- Right-click Command Prompt
- Select Run as administrator
2. Run the Time Resync Command
Type the following command and press Enter:
w32tm /resync
If successful, you will see a message similar to:
Sending resync command to local computer
The command completed successfully.
This forces the computer to immediately synchronize its time with its configured time source.
Troubleshooting Time Sync Issues
If the resync command fails with errors such as:
- "The service has not been started"
- "The computer did not resync because no time data was available"
You can reset the Windows Time service.
Step 1 – Stop the Time Service
net stop w32time
Step 2 – Unregister the Time Service
w32tm /unregister
Step 3 – Register the Time Service Again
w32tm /register
Step 4 – Start the Time Service
net start w32time
Step 5 – Force Time Sync Again
w32tm /resync
Verify the Current Time Source
To check the current synchronization status and time source, run:
w32tm /query /status
This command displays:
- Current time source
- Last synchronization time
- Poll interval
- System clock status
Notes
- Domain-joined computers normally synchronize time with the domain controller.
- Incorrect time can cause authentication failures due to Kerberos time tolerance limits.
- Ensure the Windows Time service (w32time) is running if synchronization fails.