Repair Windows Time Sync for Login and Certificate Errors

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

1. Start from the exact symptom on this page: Websites or apps report certificate or secure connection errors
2. Run the network repair line exactly as shown: w32tm /query /status net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync.
3. This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
4. Disconnect and reconnect the adapter or reboot the PC if the reset changed saved network state.
5. 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.

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.

What problem this workflow is trying to solve

It targets authentication, TLS, certificate, update, and trust issues caused by a damaged or unhealthy Windows time service state.

• Websites or apps report certificate or secure connection errors.
• Sign-in flows fail even though credentials are correct.
• The system clock drifts or refuses to sync properly.

How the workflow works

The sequence checks current time status, stops the Windows Time service, unregisters and registers it again, starts it cleanly, and then forces a resync so trust-sensitive services can recover.

When it makes sense to run it

Use it when time-related trust problems keep returning and a normal one-line resync did not hold.

Before you run this command

• Open an elevated Command Prompt or PowerShell window before running w32tm /query /status net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync.
• Confirm that the symptom really matches this guide, especially if you are seeing signs such as: websites or apps report certificate or secure connection errors.
• 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 /query /status net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync, compare the result against the symptom that brought you here. The most useful checkpoint is whether websites or apps report certificate or secure connection errors 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 /query /status net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync is to repeat the action that previously triggered the problem. If sign-in flows fail even though credentials are correct 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

Administrator rights are required. If the device is domain-joined, there may also be policy-controlled time settings upstream, so local repair may need to be paired with domain-side checks.

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 /query /status net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync does not improve websites or apps report certificate or secure connection errors, 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.