Windows / Modules / w32time.dll
w32time.dll
Windows Time Service
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Description |
|---|---|
| 0x00000002 | The time provider '%1' logged the following warning: %2 |
| 0x00000003 | The time provider '%1' logged the following message: %2 |
| 0x00000004 | The time provider '%1' failed to start due to the following error: %2 |
| 0x00000005 | The time provider '%1' returned the following error during shutdown: %2 |
| 0x00000006 | The time service encountered an error while reading its configuration from the registry, and will continue running with its previous configuration. The error was: %1 |
| 0x00000007 | The time provider '%1' returned an error while updating its configuration. The error will be ignored. The error was: %2 |
| 0x00000008 | The time provider '%1' returned an error when notified of a polling interval change. The error will be ignored. The error was: %2 |
| 0x00000009 | The time provider '%1' returned an error when notified of a time jump. The error will be ignored. The error was: %2 |
| 0x0000000A | The time provider '%1' returned an error when asked for time samples. The error will be ignored. The error was: %2 |
| 0x0000000B | Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is not a member of a domain. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. |
| 0x0000000C | Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. |
| 0x0000000D | Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but the computer is joined to a Windows NT 4.0 domain. Windows NT 4.0 domain controllers do not have a time service and do not support domain hierarchy as a time source. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient. |
| 0x0000000E | The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in %1 minutes. |
| 0x0000000F | The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will fall back to the remaining configured time sources, if any are available. The error was: %1 |
| 0x00000010 | Time Provider NtpClient: An unexpected error occurred during DNS lookup of the manually configured peer '%1'. This peer will not be used as a time source. The error was: %2 |
| 0x00000011 | Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will try the DNS lookup again in %3 minutes. The error was: %2 |
| 0x00000012 | The time provider NtpClient failed to establish a trust relationship between this computer and the %1 domain in order to securely synchronize time. NtpClient will try again in %3 minutes. The error was: %2 |
| 0x00000013 | Logging was requested, but the time service encountered an error while trying to set up the log file: %1. The error was: %2. Please make sure that 'Local Service' has permission to write to the file or directory. |
| 0x00000014 | Logging was requested, but the time service encountered an error while trying to write to the log file: %1. The error was: %2 |
| 0x00000015 | The time service is configured to use one or more input providers, however, none of the input providers are available. The time service has no source of accurate time. |
| 0x00000016 | The time provider NtpServer encountered an error while digitally signing the NTP response for peer %1. NtpServer cannot provide secure (signed) time to the client and will ignore the request. The error was: %2 |
| 0x00000017 | The time provider NtpServer encountered an error while digitally signing the NTP response for symmetric peer %1. NtpServer cannot provide secure (signed) time to the peer and will not send a packet. The error was: %2 |
| 0x00000018 | Time Provider NtpClient: No valid response has been received from domain controller %1 after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: %2 |
| 0x00000019 | The time provider NtpClient cannot determine whether the response received from %1 has a valid signature. The response will be ignored. The error was: %2 |
| 0x0000001A | Time Provider NtpClient: The response received from domain controller %1 has a bad signature. The response may have been tampered with and will be ignored. |
| 0x0000001B | Time Provider NtpClient: The response received from domain controller %1 is missing the signature. The response may have been tampered with and will be ignored. |
| 0x0000001C | The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are accessible. NtpClient has no source of accurate time. |
| 0x0000001D | The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for %1 minutes. NtpClient has no source of accurate time. |
| 0x0000001E | The time service encountered an error while reading its configuration from the registry and cannot start. The error was: %1 |
| 0x0000001F | The time service discovered that the system time zone information was corrupted. Because many system components require valid time zone information, the time service has reset the system time zone to GMT. Use the Date/Time control panel to set the correct time zone. |
| 0x00000020 | The time service discovered that the system time zone information was corrupted. The time service tried to reset the system time zone to GMT, but failed. The time service cannot start. The error was: %1 |
| 0x00000021 | The time service has jumped the local system clock by %1 seconds. This occurs when the time source and local system time are far enough apart that clock rate adjustments cannot be made to reach the time specified by the time source. |
| 0x00000022 | The time service has detected that the system time needs to be changed by %1 seconds. The time service will not change the system time by more than %2 seconds. Verify that your time and time zone are correct, and that the time source %3 is working properly. |
| 0x00000023 | The time service is now synchronizing the system time with the time source %1 with reference id %2. Current local stratum number is %3. |
| 0x00000024 | The time service has not synchronized the system time for the last %1 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients after %2 seconds. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization. You can control the frequency of the time source rediscovery using ClockHoldoverPeriod W32time config setting. Modify the EventLogFlags W32time config setting if you wish to disable this message. |
| 0x00000025 | The time provider NtpClient is currently receiving valid time data from %1. |
| 0x00000026 | The time provider NtpClient has not received response from server %1. |
| 0x00000027 | The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. |
| 0x00000028 | The time provider '%1' was stopped with error %2. |
| 0x00000029 | The time service has been configured to use one or more input providers, however, none of the input providers are still running. The time service has no source of accurate time. |
| 0x0000002A | The time service attempted to create a named event which was already opened. This could be the result of an attempt to compromise your system's security. |
| 0x0000002B | The time provider '%1' returned an error when notified of a network configuration change. The error will be ignored. The error was: %2 |
| 0x0000002C | The time provider NtpClient encountered an error and was forced to shut down. The error was: %1 |
| 0x0000002D | The time provider NtpServer encountered an error and was forced to shut down. The error was: %1 |
| 0x0000002E | The time service encountered an error and was forced to shut down. The error was: %1 |
| 0x0000002F | Time Provider NtpClient: No valid response has been received from manually configured peer %1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: %2 |
| 0x00000030 | Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will continue to try the DNS lookup every %3 minutes. This message will not be logged again until a successful lookup of this manually configured peer occurs. The error was: %2 |
| 0x00000031 | The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will continue trying to locate an AD DC every %1 minutes. This message will not be logged again until after a domain controller is found. |
| 0x00000032 | The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself. |
| 0x00000033 | Time Provider NtpClient: The time sample received from peer %1 differs from the local time by %2 seconds. The observed transmission delay from the server was %3 milliseconds. |
| 0x00000034 | The time service has set the time with offset %1 seconds. |
| 0x00000035 | The time provider NtpClient fails sending request to server %1. |
| 0x00000036 | The time service encountered an error while refreshing its configuration in the registry and cannot start. The error was: %1 |
| 0x0000005A | NoAuth |
| 0x0000005B | NtDigest |
| 0x0000005C | The peer is unreachable. |
| 0x0000005E | The time sample was rejected because: Duplicate timestamps were received from this peer. |
| 0x0000005F | The time sample was rejected because: Message was received out-of-order. |
| 0x00000060 | The time sample was rejected because: The peer is not synchronized, or reachability has been lost in one, or both, directions. This may also indicate that the peer has incorrectly sent an NTP request instead of an NTP response. |
| 0x00000061 | The time sample was rejected because: Round-trip delay too large. |
| 0x00000062 | The time sample was rejected because: Packet not authenticated. |
| 0x00000063 | The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization. |
| 0x00000064 | The time sample was rejected because: The peer's stratum is less than the host's stratum. |
| 0x00000065 | The time sample was rejected because: Packet contains unreasonable root delay or root dispersion values. This may be caused by poor network conditions. |
| 0x00000066 | Maintains date and time synchronization on all clients and servers in the network. If this service is stopped, date and time synchronization will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start.%0 |
| 0x00000067 | The server fails authenticating a request with netlogon failure. |
| 0x00000068 | The client fails sending out a request. |
| 0x00000069 | The client fails authenticating a response with netlogon failure. |
| 0x0000006A | The client fails authenticating a response with a bad signature. |
| 0x0000006B | The client fails authenticating a response with a missing signature. |
| 0x00000070 | The peer is unresolved. |
| 0x00000081 | NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000082 | NtpClient was unable to set a domain peer to use as a time source because of failure in establishing a trust relationship between this computer and the '%3' domain in order to securely synchronize time. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000083 | NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1. |
| 0x00000084 | NtpClient was unable to set a domain peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been specified as manual peer in NtpServer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000085 | NtpClient was unable to set a domain peer to use a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000086 | NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000087 | NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000088 | NtpClient was unable to set a manual peer to use as a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 |
| 0x00000089 | NtpClient succeeds in resolving manual peer %1 after a previous failure. |
| 0x0000008A | NtpClient succeeds in resolving domain peer %1 after a previous failure. |
| 0x0000008B | The time service has started advertising as a time source. |
| 0x0000008C | The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller. |
| 0x0000008D | The time service has stopped advertising as a time source because there are no providers running. |
| 0x0000008E | The time service has stopped advertising as a time source because the local clock is not synchronized. |
| 0x0000008F | The time service has started advertising as a good time source. |
| 0x00000090 | The time service has stopped advertising as a good time source. |
| 0x00000091 | The time service has stopped advertising as a time source. |
| 0x00000092 | The RODC has received %1 requests in the previous %2 minutes. %3 have resulted in success, and %4 have resulted in failure. |
| 0x0000009B | NtSignature |
| 0x0000009C | The RODC was unable to forward a time sync request from client RID %1 because the client's RID value is too large and the domain peer (%2) does not support the uplevel timesync authentication format. |
| 0x0000009D | The time provider NtpServer received a request from a client (%1) using a legacy protocol format. The request has been ignored per the RequireSecureTimeSyncRequests policy setting. By default, this message will be logged only once per day per unique client address. |
| 0x0000009E | The time provider '%1' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. |
| 0x0000009F | W32time is unable to communicate with Netlogon Service. This failure prevents NTPClient from discovering and using domain peers, besides causing problems with correct W32time service state being advertised by Netlogon. This could be a temporary condition that resolves itself shortly. If this warning repeats over a considerable period of time, ensure the Netlogon service is running and is responsive and restart W32time service to reintiaize the overall state. The error was %1 |
| 0x00000115 | added |
| 0x00000116 | subtracted |
| 0x00000118 | Error %1 registering an RPC endpoint. Please restart the Windows Time Service for it to become fully functional. |
| 0x00007256 | e Service 0x00000001 The time provider '%1' logged the following error: %2 |
| 0x50000002 | Error |
| 0x50000003 | Warning |
| 0x50000004 | Information |
| 0x90000001 | Microsoft-Windows-Time-Service |
| 0x90000002 | System |
| 0xB0000101 | W32time service has started at %1 (UTC), System Tick Count %2. Configuration: %3 Time Providers: %4Clock Rate:%5 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000102 | W32time service is stopping at %1 (UTC), System Tick Count %2 with return code: %3 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000103 | NTP Client provider periodic status: Ntp Client is receiving time data from the following NTP Servers: %1 and the chosen reference time server is %2. System Tick Count %3. IFTSTMP:%4. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000104 | W32time Service periodic configuration and status message Configuration: %1 Time Providers: %2 Current Status: Leap Indicator: %3 Stratum: %4 Precision: %5 RootDelay: %6 RootDispersion: %7 ReferenceId: %8 Last Successful Sync Time: %9 (UTC) Source: %10 Poll Interval: %11 Phase Offset: %12 Clock Rate: %13 State Machine: %14 Time Source Flags: %15 Server Role: %16 Last Sync Error: %17 Time Since Last Good Sync: %18 System Tick Count: %19 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000105 | W32time service has set the system time to %1(UTC). Previous system time was %2(UTC). System Tick Count: %3 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000106 | W32time service has adjusted the system clock rate by %1 PPM and the new nominal clock rate is %2. Previous nominal clock rate was %3. System Tick Count: %4. Clock adjustments below %5 PPM are not logged. Performance counters are recommended to efficiently track small adjustment values. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000107 | W32time Service configuration parameters have been updated. This may impact the fine-grained time synchronization accuracy. Updated Configuration: %1 Updated Time Providers: %2System Tick Count: %3 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000108 | NTP Client observed a change peer reachability. Ntp Client is now receiving time data from the following NTP Servers: %1. System Tick Count: %2. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000109 | The time service is now synchronizing the system time with the reference time source %1 with reference id %2. Current local stratum number is %3, System Tick Count: %4. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB000010A | W32time Service received notification to rediscover its time sources and/or resynchronize time. Reason Code:%1 System Tick Count: %2 Reason code description: 0 : An explicit time resynchronization request from an administrator 1 : Power state changes on this machine 2 : Changes to the network interface or to the network topology 3 : State changes within W32time that require time synchronization The actions that follow this notifcation may impact fine-grained time synchronization accuracy.For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB000010B | NTP provider is receiving timestamps from the network stack. These typically help reduce the jitter in time error calculations and improve time sync accuracy. Current Tick Count:%1 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB000010C | NTP provider is not receiving any timestamps from the network stack, which may result in lowered time sync accuracy. This is the default configuration and the behavior on service startup. This can also occur if there are conflicting settings for a NIC or due to actual runtime issues. Current Tick Count:%1 For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000110 | Leap second configuration: Enabled: %1 (Local) Count: %2 (Local) Current Offset from UTC(Seconds): %3 (Local) Runtime state consistent with settings: %4 Newest Leap Seconds List (Local): %5 System Tick Count: %6. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000111 | A leap second will be %1 at %2 UTC (%3 local time). The local system data on this leap second matches with the data from the time provider %4. System Tick Count: %5. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000112 | The time provider %4 has signaled a leap second should be %1 at %2 UTC (%3 local time). However, there is no matching local system data. Please make sure you are synchronizing time from a time source that supports leap seconds and apply the latest Windows patches to avoid seeing this message. System Tick Count: %5. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000113 | Per configuration, W32time service attempted to add a leap second %1 UTC to local settings. Result: %2. System Tick Count: %3. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000114 | The local system data indicates that a leap second will be %1 at %2 UTC (%3 local time). This information is not corroborated by the current chosen time provider %4. W32time service will update the system data to excude this leap second. Please make sure you are synchronizing time from a time source that supports leap seconds and ensure you have applied the latest Windows patches. System Tick Count: %5. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 0xB0000117 | W32time could not update the local system time data on leap seconds. Please make sure you are synchronizing time from a time source that supports leap seconds and ensure you have applied the latest Windows patches. System Tick Count: %1. For more information, see https://go.microsoft.com/fwlink/?linkid=845961. |
| 121 entries | |