Windows command guide
How to Force a Windows Time Resync with w32tm
A wrong system clock can cause much more than the time in the taskbar looking odd. Secure websites can break, certificates can fail, domain sign-in can be rejected, and scheduled tasks may run at the wrong moment. When Windows is not syncing properly, forcing a time resync can solve issues that do not obviously look like clock problems at first.
This guide is written around the specific symptom-command match for force windows time resync, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
w32tm /resync /force
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: Secure websites or certificates report invalid dates
- Run the network repair line exactly as shown: w32tm /resync /force.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Disconnect and reconnect the adapter or reboot the PC if the reset changed saved network state.
- Verify raw connectivity, name resolution, and IP assignment before moving to router or driver troubleshooting.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
w32tm /resync /force
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
ipconfig /all
ping 1.1.1.1
nslookup example.com
What problem this command is trying to solve
This command targets a Windows clock that is out of sync with its expected time source.
- Secure websites or certificates report invalid dates.
- Domain or network sign-in behaves strangely.
- The PC clock keeps drifting or stays obviously incorrect.
How the command works
w32tm /resync /force tells the Windows Time service to sync the local clock against its configured time source instead of waiting for the normal schedule.
When it makes sense to run it
Use it when the clock is wrong and that time error is affecting sign-in, certificates, scheduling, or domain communication.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running w32tm /resync /force.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: secure websites or certificates report invalid dates.
- Check whether the failure is really system-wide and not just one website, one browser, or one Wi-Fi network.
What result to expect
After running w32tm /resync /force, compare the result against the symptom that brought you here. The most useful checkpoint is whether secure websites or certificates report invalid dates becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after w32tm /resync /force is to repeat the action that previously triggered the problem. If domain or network sign-in behaves strangely still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes connectivity, DNS, IP, proxy, or adapter state. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Make sure the Windows Time service is enabled and the PC can reach its time source. If the clock keeps drifting badly, CMOS battery or hardware time issues may also exist.
When this is probably the wrong fix
This is not the right first fix when one website is down, the ISP has an outage, or only one app is blocked by a firewall rule. Use it when the Windows networking stack or saved network state looks damaged.
What to do if it does not help
If w32tm /resync /force does not improve secure websites or certificates report invalid dates, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about connectivity, DNS, IP, proxy, or adapter state.
Frequently asked questions
Should I use w32tm /resync /force for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets a Windows clock that is out of sync with its expected time source.
What should I check right after w32tm /resync /force?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether secure websites or certificates report invalid dates becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on w32tm /resync /force alone?
This is not the right first fix when one website is down, the ISP has an outage, or only one app is blocked by a firewall rule. Use it when the Windows networking stack or saved network state looks damaged.