Skip to content
FixingBook
Verifiedintermediateest. 15 minutes

Fix Windows Time Synchronization Failed (NTP Error)

Resolve issues where the Windows system clock shows the wrong time and fails to sync with internet time servers.

Confirmed working on: Windows 10 · Windows 11

Before you begin

Match the environmentUse this guide only for Windows 10, Windows 11 or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Your computer clock displays the wrong time, and attempts to sync via the settings app return a “Time synchronization failed” error. This prevents access to secure websites and disrupts background services relying on accurate timestamps.

Common causes

  • Unresponsive default Windows time server (time.windows.com)
  • Windows Time service stopped or disabled
  • Firewall blocking UDP port 123 used for NTP
  • Active Directory domain controllers enforcing invalid time policies

Solution 1: Change the NTP server

  1. Press Win + R, type control panel, and press Enter.
  2. Go to Clock and Region > Date and Time.
  3. Navigate to the Internet Time tab and click Change settings.
  4. Check the box for Synchronize with an Internet time server.
  5. Replace the default server with time.cloudflare.com or time.nist.gov.
  6. Click Update now, wait for confirmation, and click OK.
Expert Tip

Typing the server address manually is required as the dropdown list is limited and often outdated.

Solution 2: Restart the Windows Time service

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll down and locate the Windows Time service.
  3. Right-click the service and select Properties.
  4. Change the Startup type to Automatic.
  5. Click Start if the service is stopped, or click Restart to cycle it.
  6. Click Apply and OK.

Solution 3: Force synchronization via Command Prompt

  1. Press the Win key, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Type the following command and press Enter:
    w32tm /resync /force
  3. If you encounter an error, unregister and re-register the time service:
    net stop w32time
    w32tm /unregister
    w32tm /register
    net start w32time
    w32tm /resync

Solution 4: Check firewall port rules

  1. Open Windows Defender Firewall and select Advanced settings.
  2. Click on Outbound Rules and verify no custom rules block UDP port 123.
  3. Check your router configuration to ensure port 123 is open for outgoing traffic.
Caution

If your computer is joined to a company domain, you cannot change time settings manually. Your machine syncs automatically with the Domain Controller. Contact your IT administrator.

Confirm the result

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

Why is a wrong system clock a problem?

An incorrect clock breaks SSL/TLS certificates, preventing secure browsing and causing login failures on many websites.

Does dual-booting Linux cause time issues on Windows?

Yes, Linux stores hardware time in UTC, while Windows defaults to local time, causing a mismatch upon switching OS.

Did this fix work for you?

Weighted Consensus Protocol

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

FixingTeam10,000 rep

Official Project Maintainers

The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion