Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe message means Windows Time (W32Time) could not obtain a valid response from its configured Network Time Protocol (NTP) source. The practical fix is to identify whether the PC is domain-joined, retry synchronization with w32tm /resync /rediscover, then troubleshoot the specific failing layer: the server name and DNS, the network path, the NTP response, or the Active Directory time hierarchy. Do not permanently switch a managed domain computer to an Internet server without checking with your administrator.
What the synchronization error actually means
Windows uses the Windows Time service, also called W32Time, to keep the system clock aligned with a time source. It communicates with that source using the Network Time Protocol (NTP). When you see “An error occurred while Windows was synchronizing with time.windows.com,” the service reached the point of requesting a correction but did not complete a usable exchange. A timeout is one possible result; w32tm /resync may instead report that no time data was available.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | $119.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
This is normally a configuration or communications problem rather than a failed clock chip. Common causes include a misspelled or unresolvable server name, a blocked NTP request or reply, a captive-portal network, a VPN or perimeter firewall, an NTP server that is not advertising time, or a domain hierarchy that is misconfigured. The correct remedy depends first on the computer’s management role.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →First determine whether the PC is domain-joined
Domain-joined computer
A computer joined to an Active Directory Domain Services (AD DS) domain normally takes time from the domain hierarchy. Domain controllers obtain time according to the organization’s configuration, and member computers follow that chain. A local setting that names an Internet server can therefore be temporary, ignored, or contrary to policy. If this is a work laptop or office desktop, treat the domain hierarchy as authoritative and involve the administrator before changing peers or registry values.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Workgroup or personal computer
A computer that is not joined to a domain commonly uses an Internet NTP source such as time.windows.com. On these systems, checking the configured server, DNS resolution, and the local network is usually the fastest route to a fix. Windows edition and organization policy can change the labels shown in the graphical interface, so the command-line results are more reliable than relying on one particular Settings layout.
| Device role | Expected authority | Safe first action | Who may need to act |
|---|---|---|---|
| AD DS member | Domain time hierarchy | Rediscover the domain source and verify the domain-controller configuration | Domain or network administrator |
| Workgroup/personal PC | Configured Internet NTP server | Check the server name, DNS, network access, and retry synchronization | Local administrator or network provider |
| Managed test device | Organization’s documented policy | Use the approved peer and record any temporary override | Device-management administrator |
Use the supported retry command
Open Command Prompt with Run as administrator. A normal user prompt may not have enough rights to control the service or apply a source change. Start with the command that asks Windows to find its network source again and immediately request synchronization:
- Open Start, type
cmd, right-click Command Prompt, and select Run as administrator. - Run
w32tm /resync /rediscover. - Wait for the result. A successful response indicates that the service accepted a fresh time sample; an error such as “no time data was available” means the next diagnostic step is required.
/resync requests an immediate synchronization. /rediscover tells W32Time to rediscover available network time sources first, which is particularly useful after reconnecting to a domain or changing networks. Repeating the same command without correcting the underlying failure will not fix a blocked path or invalid server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Find which layer is failing
Work through these checks in order. Stop when the cause is identified; avoid making several unrelated changes at once because that removes the evidence needed to diagnose the problem.
1. Verify the configured source
Inspect the Internet Time setting or the organization’s documented W32Time configuration and confirm that the NTP hostname is spelled exactly as intended. An invalid NTPServer value, an obsolete name, or a server that no longer advertises time can all produce the same synchronization message. If the machine is domain-joined, verify that its source is the expected domain controller or hierarchy rather than assuming an Internet peer is appropriate.
2. Check name resolution
The configured hostname must resolve through DNS before Windows can send a useful request. Test the name with your organization’s normal DNS diagnostic method, or ask the network administrator to confirm that the name resolves from the affected network. If the name fails only on a VPN, guest Wi-Fi, or one office segment, the problem is likely that network’s DNS path rather than the Windows clock.
3. Measure the NTP exchange with /stripchart
W32Time includes a measurement command that can query a chosen target and display the offset. From an elevated Command Prompt, use:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →w32tm /stripchart /computer:<target> /dataonly /samples:5
Replace <target> with the same NTP hostname or approved domain time source you are investigating. Repeated offsets show that replies are arriving; a timeout or absence of samples points to a transport, firewall, DNS, or non-advertising-server problem. The command measures the target; it does not permanently change the computer’s source.
4. Check the NTP network path
NTP synchronization uses UDP port 123. A local Windows Firewall rule, a perimeter firewall, a router, a VPN tunnel, or a captive network can block either the outgoing request or the returning response. Microsoft’s troubleshooting distinction is useful: if no request leaves the PC, inspect the local firewall first; if requests leave but no response returns, investigate a non-Microsoft firewall or another device between the PC and the server.
Do not disable every firewall as a permanent “fix.” Ask the administrator to permit the required traffic for the approved source, and restore any temporary test rule immediately. On a public network, complete the browser sign-in for the captive portal before testing time synchronization; a network that has not authorized the device may discard NTP traffic.
5. Compare with a phone hotspot
Connect briefly to a trusted phone hotspot and run the same retry command. A Microsoft Q&A case reports synchronization succeeding after such a network change. That result is valuable evidence that the original Wi-Fi, router, VPN, or perimeter firewall is filtering or mishandling NTP. It is a diagnostic comparison, not a guaranteed permanent solution, and it does not prove that the hotspot is suitable for routine work.
6. Check whether the source itself is usable
An NTP hostname can resolve correctly and still fail to provide time. Some servers are unreachable from a particular region, overloaded, restricted by policy, or not advertising NTP service. If DNS works and the network path is open but /stripchart receives no valid samples, give the server-side administrator the target name, time of the test, and the exact W32Time error rather than repeatedly changing local settings.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Use the symptom to choose the remedy
| Observed result | Most likely layer | Appropriate next step |
|---|---|---|
| The configured name does not resolve | DNS or invalid peer name | Correct the hostname or restore the organization’s DNS path |
/stripchart cannot obtain samples and no request leaves the PC |
Local Windows Firewall or endpoint policy | Have an administrator review the outbound NTP rule |
| Requests leave, but no reply returns | Router, VPN, perimeter firewall, captive network, or remote server | Test another approved network and have the network owner trace UDP 123 |
| Internet source works on a workgroup PC only after a network change | Original network filtering | Fix that network instead of changing the clock permanently |
| Domain member repeatedly reverts to an unexpected source | AD DS policy or hierarchy | Ask the domain administrator to verify controller and PDC configuration |
| Source responds, but the service still rejects synchronization | W32Time state or policy | Restart the service under approved policy, then retry and capture the result |
Domain computers require a different fix
On a domain member, a successful one-time synchronization with an Internet server can mask a broken domain hierarchy. Administrators should verify which domain controller is authoritative, whether the intended source is advertising NTP, and how the forest-root or PDC configuration obtains time. Local changes may be overwritten at the next policy refresh, and forcing a public peer can create inconsistent time across the domain.
If you are a user rather than the domain administrator, provide IT with the computer name, whether the error occurs on multiple networks, the output or wording from w32tm /resync /rediscover, and the result of the /stripchart test. That information separates a client firewall issue from a controller or policy issue without asking you to alter managed settings.
Manually configure a peer only for an approved non-domain or test scenario
Microsoft documents a manual-peer procedure for a non-domain or controlled test computer. In an elevated Command Prompt, the configuration pattern is:
w32tm /config /manualpeerlist:<NTP_server_IP_Address>,0x8 /syncfromflags:MANUAL
Replace the placeholder with the approved server address. Then restart the Windows Time service using your organization’s approved service-management method and run w32tm /resync. A typical local restart is:
- Run
net stop w32time. - Run
net start w32time. - Run
w32tm /resync.
This is not a universal repair. A manually entered address can become stale, bypass domain policy, or fail when the server is reachable only from a particular network. Keep a record of the original setting so it can be restored after testing. If the machine is managed, obtain approval before running the configuration command.
Why changing the clock server may not solve the error
The visible clock is not the root cause
Windows can display a plausible time while the service is unable to validate a fresh sample. Manually setting the clock may make a login or certificate appear to work temporarily, but it does not repair DNS, UDP transport, or the domain hierarchy. Use it only under an administrator’s recovery procedure.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchChanging servers can hide a policy problem
If a domain policy keeps restoring the original source, repeated local edits create confusion rather than stability. The durable correction belongs in the domain configuration, not on each workstation.
Time accuracy claims have limits
Microsoft states that Windows Server 2016 and later can be configured for accuracy of 1 millisecond or better relative to UTC under optimal conditions. That is an engineering capability for suitable deployments, not a promise that every consumer PC, Wi-Fi link, or Internet server will maintain that accuracy. Network delay, source quality, hardware, virtualization, and policy all affect the result.
When to escalate
- Escalate to IT or a domain administrator when the PC is domain-joined, policy keeps changing the source, several employees have the same error, or a domain controller is not advertising time.
- Escalate to the network owner when a hotspot succeeds but the normal network fails, or when requests leave the PC without replies.
- Escalate to the NTP service owner when DNS resolves and the path is open but the target supplies no valid samples.
- Handle locally when a workgroup PC has a simple name-resolution error or a transient network interruption and the approved source works after correction.
Give the recipient exact evidence: the device role, configured source, network used, command entered, complete error text, and whether /stripchart produced samples. Avoid reporting only that “the clock is wrong”; the failure layer determines the fix.
Prevent the error from returning
- Keep the approved NTP hostname documented and check it after DNS or network changes.
- Permit NTP traffic only to the sources authorized by your organization’s firewall policy.
- For domain environments, monitor the controller hierarchy and the authoritative PDC configuration instead of editing individual clients.
- After changing networks, VPN profiles, or captive-portal settings, run a controlled synchronization test before declaring the issue fixed.
- Record temporary manual-peer changes and remove them when the test ends.
The durable solution is the one that matches the computer’s role and repairs the failed layer. A retry command can confirm recovery, but it cannot substitute for correcting DNS, allowing the NTP exchange, restoring a responding source, or repairing the domain hierarchy.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
