Windows Time Service Not Syncing – Quick Fix for Error 0x8007264

Quick answer: If you're in a hurry, run Command Prompt as admin and type w32tm /resync. If that fails, check port 123 isn't blocked by your firewall or antivirus.

You're getting error 0x8007264 because Windows Time Service (W32Time) can't reach the time server. This happens when your firewall (Windows Defender or third-party) blocks UDP port 123, or the service is stuck. I see this most often after a Windows update or if you installed a VPN that messes with network settings. The good news: you don't need to be a sysadmin to fix it.

Here's what we'll do: restart the service, force a sync, then make sure the firewall isn't in the way. Follow the steps in order. Don't skip around or you'll waste time.

Step-by-Step Fix

1. Open Command Prompt as admin. Click Start, type cmd, right-click Command Prompt, pick "Run as administrator". Accept the UAC prompt.
2. Stop the time service. Type net stop w32time and press Enter. You'll see "The Windows Time service was stopped successfully." If you get an error, the service might not be running—that's fine, keep going.
3. Force a resync. Type w32tm /resync. Wait a few seconds. You should see "The command completed successfully." If you get error 0x8007264, don't panic—move to step 4.
4. Start the service again. Type net start w32time. You'll see "The Windows Time service was started successfully."
5. Check the time. Right-click the clock in the taskbar, pick "Adjust date/time", then click "Sync now" under "Synchronize with an Internet time server". Wait for the green checkmark. If it still fails, go to the alternative fixes below.

Alternative Fixes If the Main Fix Fails

Fix 1: Check Firewall for Port 123

Windows Defender or your antivirus might block NTP (port 123 UDP). Here's how to check:

• Open Windows Security (press Win + I, go to Update & Security > Windows Security > Firewall & network protection).
• Click "Allow an app through firewall".
• Find "Windows Time Service" in the list. Make sure both Private and Public are checked. If it's missing, click "Change settings", then "Allow another app", browse to C:\Windows\System32\svchost.exe (yes, it's the same host process for multiple services). Give it a name like "Windows Time".
• If you use a third-party antivirus (Norton, McAfee, etc.), open its settings and look for a network rule that blocks port 123. Disable it temporarily to test.

Fix 2: Use a Different Time Server

Sometimes time.windows.com is down or slow. Try a public NTP server:

1. Right-click the clock and pick "Adjust date/time".
2. Under "Synchronize with an Internet time server", click "Change settings".
3. Replace time.windows.com with time.google.com or pool.ntp.org. Click "Update now".
4. If it works, you're done. The default server is often the problem.

Fix 3: Reset W32Time Registry (Advanced)

If your registry got corrupted, use this. Open Command Prompt as admin and run:

w32tm /unregister
w32tm /register
net start w32time
w32tm /resync

The first command unregisters the service. You'll see a success message. The second registers it fresh. Then start and resync. This wipes your custom settings, so you'll need to set the time server again (see Fix 2).

Prevention Tip

Once it's fixed, set your PC to sync automatically. Go to Time & Language settings, turn on "Set time automatically". Also, if you use a VPN, check its settings—some VPNs block port 123 by default. I've had three users this month with the same issue from NordVPN. Whitelist NTP traffic in your VPN's firewall, and you won't see this error again.

That's it. Your clock should be right now. If not, reboot and try Fix 3—registry reset fixes 90% of stubborn cases.