Windows 8

  1. The time provider NtpClient failed to establish a trust relationship between this computer and the %1 domain in order to ...
  2. The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are ...
  3. The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are ...
  4. The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will continue trying ...
  5. The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will fall back to the ...
  6. The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in %1 ...
  7. The time provider NtpServer encountered an error while digitally signing the NTP response for peer %1. NtpServer cannot provide ...
  8. The time provider NtpServer encountered an error while digitally signing the NTP response for symmetric peer %1. NtpServer ...
  9. The time provider NtpServer received a request from a client (%1) using a legacy protocol format. The request has been ignored ...
  10. The time sample was rejected because: Packet contains unreasonable root delay or root dispersion values. This may be caused ...
  11. The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization. ...
  12. The time sample was rejected because: The peer is not synchronized, or reachability has been lost in one, or both, directions. ...
  13. The time service attempted to create a named event which was already opened. This could be the result of an attempt to compromise ...
  14. The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be ...
  15. The time service discovered that the system time zone information was corrupted. Because many system components require valid ...
  16. The time service discovered that the system time zone information was corrupted. The time service tried to reset the system ...
  17. The time service encountered an error while reading its configuration from the registry and cannot start. The error was: ...
  18. The time service encountered an error while reading its configuration from the registry, and will continue running with its ...
  19. The time service encountered an error while refreshing its configuration in the registry and cannot start. The error was: ...
  20. The time service has been configured to use one or more input providers, however, none of the input providers are still running. ...
  21. The time service has detected that the system time needs to be changed by %1 seconds. The time service will not change the ...
  22. The time service has jumped the local system clock by %1 seconds. This occurs when the time source and local system time ...
  23. The time service has not synchronized the system time for %1 seconds because none of the time service providers provided ...
  24. The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller. ...
  25. The time service is configured to use one or more input providers, however, none of the input providers are available. The ...
  26. The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly ...
  27. The time the end user spent completing the Setup Specialize phase of the first boot process, and the time spent during the ...
  28. The time to complete the events that occurred after OOBE completed. Note: The sum of the child events does not equal the ...
  29. The time zone bias calculated between %2 and the current workstation is too large. The data specifies the number of 100ns ...
  30. The time zone was set successfully with the following parameters. Bias: %1 minute(s), Standard name: "%2", StandardDate.wYear: ...
  31. The timeout period has expired on a call to another WINS server. Assuming that the network and routers are working properly, ...
  32. The timeout value {0} is not within the recommended range of 2 to 10 seconds. DNS resolutions failures can occur if the value ...
  33. The Timer thread could not be signaled. This indicates this computer is extremely overloaded or that the WINS application ...
  34. The times of the backups displayed are based on the time zone of the current operating system that you are using. The time ...
  35. The timestamp is severely late compared to the current render position. Advise dropping everything up to the next key frame.%0 ...
  36. The token decryption certificate with the thumbprint %1 in the certificate store %2 has expired. Please renew the certificate ...
  37. The token decryption certificate with thumbprint %1 in the certificate store %2 will expire in %3 days. Please renew the ...
  38. The token type '%1' specified on the security token reference did not match the value type '%2' that was specified on the ...
  39. The Topic Assistant requires sample documents from at least two categories. Try again when sample documents for more categories ...
  40. The topic you are viewing does not have a table of contents location in the subset you are currently using. Would you like ...
  41. The topology is disconnected due to missing or disabled connections, disabled memberships, read-only memberships, or empty ...
  42. The topology is not fully connected. View disconnected members .The replication group will not function correctly unless ...
  43. The total computer time from the start of Setup to the time that the Start screen is ready for user input. Note: The sum ...
  44. The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the ...
  45. The total number of ATQ threads that are either waiting to service an incoming request, or are already servicing a request. ...
  46. The total number of available licenses had changed when the request was placed on the server. After removing as many licenses ...
  47. The total number of Buffer Overrun Errors for this connection. Buffer Overrun Errors when the software cannot handle the ...
  48. The total number of bytes in all Message Queuing messages that currently reside in the selected journal. For the Computer ...
  49. The total number of bytes in all Message Queuing messages that currently reside in the selected queue. For the Computer Queues ...
  50. The total number of bytes that arrived at the computer in the selected session. Only bytes in Message Queuing messages are ...
  51. The total number of bytes that were sent from the computer in the selected session. Only bytes in Message Queuing messages ...
  52. The total number of durable handles that are successfully reconnected. The ratio of "reconnected durable handles"/"total ...
  53. The total number of handles currently open by this process. This number is equal to the sum of the handles currently open ...
  54. The total number of heartbeats counted since startup. A heartbeat occurs once every 10 seconds while the service is running. ...
  55. The total number of incoming Message Queuing messages placed in queues on the selected computer by the Message Queuing service. ...
  56. The total number of licenses in this License Pack had changed to %d when the request was placed on the server. The License ...
  57. The total number of Message Queuing messages that currently reside in the selected journal. For the Computer Queues instance, ...
  58. The total number of Message Queuing messages that currently reside in the selected queue. For the Computer Queues instance, ...
  59. The total number of page fault exceptions intercepted by the hypervisor while executing guest code on the virtual processor. ...
  60. The total number of resilient handles that are successfully reconnected. The ratio of "reconnected resilient handles"/"total ...
  61. The total number of Serial Overrun Errors for this connection. Serial Overrun Errors occur when the hardware cannot handle ...
  62. The total number of times a document access has been retried. Having this number high may indicate a problem with accessing ...
  63. The total number of times a filter process was created or restarted. Having too many filter processes created indicates that ...
  64. The total number of times a thread has timed out waiting for the semaphore over the lifetime of the Secure Channel connection ...
  65. The total number of times the semaphore has been acquired over the lifetime of the Secure Channel connection (or since system ...
  66. The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. ...
  67. The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. ...
  68. The TPM has an invalid storage root key (SRK) authorization value and is not compatible with Windows security applications. ...
  69. The TPM is off and ownership has been taken. The TPM is currently locked out to prevent guessing passwords because an incorrect ...
  70. The TPM may not be in the correct state to perform this action. Try refreshing the TPM Management Console screen to see whether ...
  71. The TPM on this computer is currently locked out. The last owner password entered was ignored by the TPM. To perform this ...
  72. The TPM on this computer is currently locked out. The last owner password entered was ignored by the TPM. To reset the TPM ...
  73. The TPM owner password is incorrect. TPMs prevent guessing the owner password. Using the incorrect owner password once might ...
  74. The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions ...
  75. The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method ...