iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Windows 11 has two different ways to deal with time. To type a date and time into the PC, use Settings > Time & language > Date & time. To tell Windows which network time server it should use, configure the Windows Time Service (W32Time) from an elevated Command Prompt with w32tm. The Settings control changes the local clock; it does not provide a field for an arbitrary NTP server.
Choose the route that matches your goal before changing anything. A standalone PC can usually be configured with a manual peer, while a computer joined to an Active Directory domain normally follows the domain time hierarchy and may be controlled by policy.
Choose the correct Windows 11 time-setting method
The phrase “change the time server” is often confused with “change the time.” They are separate operations with different effects and permissions.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstall| What you need to do | Windows 11 route | Result |
|---|---|---|
| Enter a date and time yourself | Settings > Time & language > Date & time | Changes the computer’s local clock after automatic time is turned off. |
| Use a particular NTP host or address | Administrator Command Prompt with w32tm /config |
Sets a manual Windows Time Service peer and selects the manual source. |
| Inspect what W32Time is configured to use | w32tm /query /configuration |
Displays the client’s configured Windows Time Service parameters. |
| Override an organization’s domain time design | Local W32Time changes on a domain member | May conflict with Active Directory policy or the domain hierarchy; confirm with the administrator first. |
Microsoft describes W32Time as providing network clock synchronization without extensive configuration, but it also states that the service was not designed to be a highly accurate time source. A custom peer is therefore a configuration choice, not a guarantee of laboratory-grade timing.
#1 Best Overall
- Stratum 1 NTP with GPS Source
- Embedded View-only Webserver with Status & Graphs
- Admin Console via USB and SSH
- Optional Dual Redundant Power Inputs - DC & PoE
- JSON Encoded Raw Data for Custom Integration
What “manual” means in each route
In Settings, manual means that you type the value shown by the local clock. In W32Time, manual means that you identify the network peer or peers from which the service should obtain time. The second operation can continue to adjust the clock after the command is applied; it is not the same as leaving the clock at a value you entered once.
This distinction explains why a user can successfully change the displayed time and still see the old synchronization source later. The Settings page has a control for the local value, not an NTP-host text box. A custom source belongs in the Windows Time Service configuration.
Manually enter the date and time in Settings
Use this procedure when you simply need the displayed date or time to be corrected, for example on a standalone PC that is temporarily showing the wrong local value.
- Open Start, then select Settings.
- Open Time & language and select Date & time.
- Turn Set time automatically off.
- Find Set the date and time and select Change.
- Enter the desired date and time in the dialog.
- Select Change again to apply the value.
This edits the local clock only. The manual-entry dialog is not the place to type a DNS name or IP address for an NTP server. If your objective is to choose a network source that Windows will poll, use the W32Time procedure below instead.
What this setting does not change
- It does not create or replace a Windows Time Service peer.
- It does not convert a standalone computer into a time server for other devices.
- It does not prove that the clock is synchronized with any network source.
- It does not override a domain policy that manages time on an organization-owned computer.
Use this route for a one-time correction when you control the machine and know the correct local value. If the value changes back, that is a reason to investigate automatic synchronization or management policy rather than repeatedly editing the clock.
Configure a custom Windows Time Service peer
Microsoft’s documented method for a manual synchronization server uses w32tm. You need an administrator Command Prompt because the command changes Windows Time Service configuration.
Before you run the command
- Obtain the DNS name or IP address of the time server approved for your environment.
- Decide whether this is a standalone or workgroup PC. Domain members commonly use the Active Directory time hierarchy instead.
- Make sure you can open an elevated Command Prompt. A standard, non-elevated window may not be able to save the configuration.
- If the computer belongs to an organization, check with the administrator before replacing its configured source.
Do not choose a host merely because its name appears in an online example. The command syntax accepts names and addresses, but Microsoft’s configuration guidance does not designate one universally suitable public server. The correct peer depends on the network and the policy for the computer you are configuring.
Free tools Windows power users keep installed
One-click scans. No signup required.
Set one manual peer
- Open Start and type Command Prompt.
- Right-click Command Prompt and choose Run as administrator. Approve the User Account Control prompt if it appears.
- Run the following command, replacing the example host with the approved server:
w32tm /config /manualpeerlist:"ntpserver.example" /syncfromflags:manual /updateThe three switches have distinct jobs:
/manualpeerlistsupplies the peer list. Microsoft documents a space-delimited list of DNS names or IP addresses./syncfromflags:manualtells W32Time to use the manual source rather than another source-selection mode./updatenotifies W32Time that its configuration has changed.
Keep the quotation marks around the entire peer list. They are especially important when you specify more than one server, because the list is separated by spaces. A single peer is still written as a quoted value, as in the example.
Rank #2
- Stratum 1 NTP with GPS Source
- Embedded View-only Webserver with Status & Graphs
- Admin Console via USB and SSH
- JSON Encoded Raw Data for Custom Integration
- I/O Connector
The command changes the configured source; it does not by itself demonstrate that the peer is reachable, that name resolution succeeded, or that the clock has already synchronized. Treat configuration and operational verification as two separate tasks.
Configure more than one peer
For a client that uses multiple peers, Microsoft recommends preparing three or more time servers. A list therefore follows the same syntax, with each DNS name or IP address separated by a space inside the quotation marks:
w32tm /config /manualpeerlist:"ntp-a.example ntp-b.example ntp-c.example" /syncfromflags:manual /updateThe names in this example are placeholders for the servers selected by your organization or network design; Microsoft’s documentation does not endorse a universal public-server list. Use only hosts that are permitted and reachable in your environment.
Microsoft’s two-peer example assigns UseAsFallbackOnly (0x2) to the lower-priority peer. That behavior is a priority rule, not a claim that two peers are equivalent to the recommended three or more. If you need a two-peer arrangement, document which one is primary and how the fallback is intended to work.
Before applying a multi-peer list, check each name for spelling and confirm that the addresses belong to the intended time service. A typo in one entry can make troubleshooting confusing, especially when the other entries are valid. Keep the list in one pair of quotation marks; putting each name in a separate option changes the command structure.
Verify the W32Time configuration
Do not assume that a command produced a successful synchronization merely because it was entered. Microsoft provides a query command for inspecting the client configuration:
w32tm /query /configurationRun it in Command Prompt and review the output for the W32Time parameters that were configured. In particular, check that the manual peer list contains the intended DNS names or addresses and that the source-selection setting reflects the manual mode you requested.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What the query can and cannot tell you
- It can show the parameters currently configured for the client.
- It can help reveal a misspelled host, an empty peer list, or a setting that was not written as intended.
- It is configuration evidence, not a promise that the host responded or that the clock is already accurate.
- If a domain policy manages the computer, the configured values may be changed again by that policy.
To verify operational behavior, compare the observed clock and the organization’s expected source after allowing the environment to apply its normal synchronization behavior. Avoid reporting synchronization as successful unless you have actually checked the machine. If the query shows the expected values but the clock remains wrong, separate the configuration question from connectivity, policy, and accuracy questions.
Rank #3
- Up to 6000 visits per second
- Local area network synchronization timing accuracy: 0.5-2ms
- Support GPS, Beidou, GLONASS, QZSS NTP v2 (RFC 1119), NTP v3 (RFC 1305), NTP v4 (RFC5905)
- Internally integrated high- timing GNSS satellite receiver
- SNTP v3 (RFC 1769), SNTP v4 (RFC 2030)
Domain-joined computers require extra care
Most domain-member computers typically use the NT5DS client type and obtain time through the Active Directory domain hierarchy. This arrangement matters because Kerberos authentication and other Active Directory Domain Services functions depend on compatible time across participating systems.
Why a local override can be inappropriate
- A local manual peer can conflict with the hierarchy selected by the domain administrator.
- Group Policy or another management mechanism can replace a local setting.
- Different machines may drift into incompatible sources, creating authentication or operational problems.
- Troubleshooting becomes harder when one workstation no longer follows the same source as the rest of the domain.
Before running the manual-peer command on a work computer, determine whether it is organization-managed and ask the administrator which source is supported. A local setting is most appropriate when you control the machine and its time architecture, not when you are bypassing a managed domain design.
A domain member can therefore show a perfectly valid local command result and still not retain that choice. If policy reapplies the domain hierarchy, the later configuration is evidence of the management design, not necessarily a failed command. Record the intended source and involve the administrator rather than repeatedly forcing a local override.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesDecide between a local clock edit and a manual peer
Use this decision sequence to avoid changing the wrong layer.
- Is the displayed date or time simply wrong right now? Use the Settings procedure and enter the correct value.
- Do you need Windows to obtain time from a named network host? Use the elevated
w32tm /configcommand. - Is the PC joined to an Active Directory domain? Pause and confirm the domain time policy before changing the peer.
- Are you configuring multiple peers? Prepare three or more where practical, and understand the documented fallback behavior for a two-peer design.
- Does an application require unusually tight timing? Treat ordinary W32Time as insufficient until the high-accuracy requirements and Microsoft’s support boundary have been evaluated.
| Situation | Preferred action | Reason |
|---|---|---|
| One-time correction on a personally managed PC | Enter the value in Date & time settings | You are changing the local clock, not designing a synchronization service. |
| Standalone PC that must use a named network source | Configure a manual W32Time peer | The peer belongs to service configuration, not the Settings dialog. |
| Domain-member workstation | Follow the domain administrator’s design | The normal source is the Active Directory hierarchy and may be policy-controlled. |
| High-accuracy workload | Evaluate the appropriate supported architecture | W32Time is not designed as a highly accurate time source. |
Troubleshoot common configuration problems
The Settings page changes the clock, but the server is still the old one
This is expected when you used the manual-entry control. Settings changes the local value; it does not configure an NTP host. Run the W32Time command from an administrator Command Prompt if a custom peer is the actual requirement.
The command was rejected or had no visible effect
- Confirm that Command Prompt was opened with Run as administrator.
- Check the command spelling, including the leading slash on each switch.
- Keep the complete peer list inside quotation marks.
- Run
w32tm /query /configurationafterward to see what W32Time actually has configured.
If the query does not show the intended values, correct the command and inspect it again. If it does show them, the remaining issue may be reachability, policy, or the limits of the service’s accuracy rather than the syntax itself.
The wrong server appears in the query output
Recheck the hostname or IP address in /manualpeerlist, then inspect the configuration again. If the PC is domain-joined, policy may be restoring the domain hierarchy or another administrator-selected source. Do not repeatedly force local changes on a managed device; resolve the policy or design question with the administrator.
Recommended Free Tools
One peer works but a multi-peer list behaves unexpectedly
Verify that every peer is separated by a space and that the quotation marks surround the entire list. Review the priority design as well: Microsoft recommends three or more servers for multiple peers and documents UseAsFallbackOnly (0x2) for the lower-priority peer in a two-peer example.
Rank #4
- 1. GPS Satellite Time Synchronization: This NTP server receives global time signals from GPS satellites, ensuring nanosecond-level time synchronization accuracy, providing high reliability for your network equipment.
- 2. High-Precision NTP Service: Provides SNTP/NTP time synchronization with Daylight Saving Time (DST) support for finance, communications, and government.
- 3. Low Latency and High Performance: Optimized design with ultra-low network latency, ensuring multi-device sync accuracy to the millisecond level, ideal for applications where time precision is critical.
- 4.Flexible Dual-Power Deployment: Supports either AC power (wide voltage input 110V-264V) or standard PoE (IEEE 802.3af/at).
- 5. Easy-to-Use Web Management Interface: Supports easy installation and remote management. The intuitive interface makes it easy to monitor device status, configure settings, and maintain the system — ideal for IT administrators and technical teams.
The clock is close but not accurate enough
W32Time is intended for normal Windows network synchronization, not as a highly accurate time source. A manual peer does not change that service boundary. If a trading, measurement, industrial, scientific, or other time-sensitive workload has a defined accuracy requirement, use the architecture and support guidance appropriate to that requirement instead of assuming that another hostname will solve it.
The clock keeps changing after a manual entry
A value entered in Settings is only a local clock edit. Automatic synchronization, a configured W32Time source, or organizational management can subsequently apply another value. Decide whether the desired outcome is a persistent network source or merely a corrected display, then use the corresponding route and verify the resulting configuration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Security, reliability, and maintenance considerations
Use an approved source
The command accepts DNS names and IP addresses, but syntax alone does not make a server trustworthy or suitable. Select a source approved for your network, region, and operational policy. The Microsoft material describing the command does not nominate one universally appropriate public server.
Keep the peer list intentional
Every additional peer affects how W32Time evaluates available sources. Document why each server is present, which one has priority, and who owns it. For multiple peers, follow Microsoft’s recommendation to prepare three or more rather than copying an arbitrary list from an unrelated configuration.
Remember the authentication dependency
Consistent time is not merely cosmetic. Kerberos and Active Directory Domain Services rely on compatible clocks, which is why domain administrators normally control the hierarchy. A workstation that is manually pointed elsewhere can create symptoms that look like password, account, or network failures.
Recheck after management changes
On a managed PC, a policy refresh or administrative change can alter W32Time settings after you configure them locally. If the query output changes later, compare it with the organization’s intended policy rather than assuming that the local command failed.
Keep an operational record
For a machine that matters to a team, record whether it is standalone or domain-joined, the peer list that was approved, and the date of the change. This makes a later query easier to interpret and helps distinguish a deliberate fallback design from an accidental extra entry. It also prevents another administrator from mistaking a one-time Settings correction for a permanent synchronization configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick checklist
- For a one-time correction, turn off Set time automatically and use Change in Date & time settings.
- For a custom network source, use an elevated Command Prompt and the documented
w32tm /configsyntax. - Put multiple DNS names or IP addresses inside one quoted, space-delimited
/manualpeerlistvalue. - Use
w32tm /query /configurationto inspect the result. - Do not claim synchronization until the computer has been checked in its actual environment.
- Ask the domain administrator before overriding an Active Directory time hierarchy.
- Do not treat an ordinary W32Time peer as a high-accuracy timing solution.
- Document the approved peers and intended priority when configuring a managed or shared computer.
Frequently Asked Questions
Can I enter an NTP server in Windows 11 Date & time settings?
No. Settings lets you turn off automatic time and enter a local date and time. To choose a DNS name or IP address as the synchronization source, configure W32Time with an elevated Command Prompt and w32tm /config.
Best Value
- NTP Network Time Server with GPS
- Stratum 1 Time Source
- Includes GPS Patch Antenna and Power Supply
What is the command for one manual time server?
Use w32tm /config /manualpeerlist:"ntpserver.example" /syncfromflags:manual /update in an administrator Command Prompt, replacing the example host with an approved peer.
How do I specify multiple Windows time servers?
Put the DNS names or IP addresses in one quoted, space-delimited /manualpeerlist value. Microsoft recommends preparing three or more servers for a client using multiple peers.
What does UseAsFallbackOnly (0x2) mean?
Microsoft’s two-peer example assigns this flag to the lower-priority peer, making it a fallback rather than the preferred source. It is a priority rule and does not replace the recommendation to prepare three or more servers for multiple-peer configurations.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How can I see which W32Time settings are configured?
Run w32tm /query /configuration. Review the output for the peer list and source-selection parameters. The command shows configuration, not proof that a peer responded or that synchronization succeeded.
Should I change the peer on a domain-joined PC?
Usually not without the domain administrator’s approval. Domain members commonly use the NT5DS client type and synchronize through the Active Directory hierarchy, which may be enforced by policy and supports Kerberos and other AD DS functions.
Why did my manual setting disappear?
A domain policy or another management mechanism may have reapplied the organization’s intended W32Time configuration. Compare a later w32tm /query /configuration result with the administrator’s policy instead of repeatedly forcing a local override.
Does choosing a manual peer make Windows highly accurate?
No. Microsoft states that W32Time was not designed to function as a highly accurate time source. Applications with unusually tight timing requirements need an architecture and support approach appropriate to that accuracy target.
The Bottom Line
Use Settings when you need to type the local date and time. Use an elevated w32tm /config command when you need Windows 11 to use a specific synchronization peer, and verify the resulting parameters with w32tm /query /configuration. On domain-joined PCs, follow the organization’s time policy instead of overriding it locally.
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.
