Windows 8

  1. WINS could not initialize properly with the security subsystem. At initialization, WINS creates a security object and attaches ...
  2. WINS could not initialize the administrator interface because of a problem with the Remote Procedure Call (RPC) service. ...
  3. WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) association. Check to see if the message read ...
  4. WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
  5. WINS could not open a Push subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
  6. WINS could not open the log file. Check the log path specified in the registry under WINS\Parameters\LogFilePath and restart ...
  7. WINS could not properly set up the WINS database. Look at the application log for errors from the Exchange component, ESENT. ...
  8. WINS could not read the ConsistencyCheck value (type DWORD) from the Parameters\ConsistencyCheck subkey in the registry. ...
  9. WINS could not read the MaxRecsAtATime value (type DWORD) in the Wins\Parameters\ConsistencyCheck subkey of the registry. ...
  10. WINS could not read the UseRplPnrs value of the Wins\Parameters\ConsistencyCheck key. If this value is set to a non-zero ...
  11. WINS could not start because of a database error. WINS restored the old database from the backup directory and will come ...
  12. WINS could not start because the existent database must be converted to the Windows 2000 format. If this is the first invocation ...
  13. WINS could not start because the existing database needs to be converted to the Windows 2000 format. If this is the first ...
  14. WINS could not start due to a missing or corrupt database. Restore the database using WINS Manager (or winscl.exe found in ...
  15. WINS could not update the Owner ID-to-Address mapping table in the database. This means the in-memory table that maps to ...
  16. WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockname' to determine the ...
  17. WINS did not send a notification message to the WINS server whose address is given in the data section. There were a number ...
  18. WINS encountered a database error. This may or may not be a serious error. WINS will try to recover from it. You can check ...
  19. WINS encountered a PnP failure that caused it to terminate. The error code is contained in the second word of the data section. ...
  20. WINS encountered an error while deleting one or more records of a WINS. The WINS address is in the second DWORD in data section. ...
  21. WINS encountered an error while processing a push trigger or update notification. The error code is given in the data section. ...
  22. WINS found a name in the WINS database with a length of more than 255 characters. The name was truncated to 17 characters. ...
  23. WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did ...
  24. WINS has deleted records of a partner. The internal ID of the partner whose records were deleted, the minimum version number ...
  25. WINS has encountered an error that caused it to shut down.The exception code is the second DWORD of the data section. Check ...
  26. WINS has exceeded the wait time for all threads to terminate. The number of threads still active is given in the second DWORD ...
  27. WINS has found some database corruption. It will try to recover. This recovery process can take a long time. Do not kill ...
  28. WINS has received a PnP notification that the IP address of the server has changed. The old IP address and the new IP address ...
  29. WINS is scavenging a chunk of N records in the version number range from X to Y. N, X and Y (low word, high word for version ...
  30. WINS is scavenging the locally owned records from the database. The version number range that is scavenged is given in the ...
  31. WINS is trying to update the version number of a database record that it does not own. This is a serious error if the WINS ...
  32. WINS just did a consistency check on the records owned by the WINS with the address, %1. The number of records inserted, ...
  33. WINS performed a consistency check on the records. The number of records pulled, The address of the WINS whose records were ...
  34. WINS Pull thread encountered an error during the process of sending a push notification to another WINS. The error code is ...
  35. WINS pulled records from a WINS while doing %1. The partner's address and the owner's address whose records were pulled are ...
  36. WINS received a release for the non-owned name, %1. This name is owned by the WINS whose owner ID is given in the data section. ...
  37. WINS received a replica whose state is incorrect. For example, the state may be RELEASED or the replica might be an Internet ...
  38. WINS received an error while registering replicas. It will not register any additional replicas of this WINS at this time ...
  39. WINS received an error while trying to register a group's replica with name, %1. The replica is owned by the WINS with the ...
  40. WINS received an error while trying to register a unique replica with name %1. The replica is owned by WINS with address ...
  41. WINS responses are not secure, if you select this option, the responses from WINS will be forwarded as secure responses from ...
  42. WINS Reverse Lookup Received/sec is the average number of WINS reverse lookup requests received by the server in each second. ...
  43. WINS sent a name query or a name release with a certain transaction ID. It received a response to the request that differed ...
  44. WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on the computer forced the ...
  45. WINS will not start because the existing WINS database needs to be converted to the Windows 2000 format. WINS has initiated ...
  46. WINS's Replicator could not find any records in the WINS database. This means there are no active or tombstone records in ...
  47. WinSAT cannot obtain accurate measurements inside of a virtual machine. Please try again running directly on the native hardware. ...
  48. Winsock Catalog Provider Entry - Entry Type: %1!s! Description: %2!s! Provider ID: %3!s! Provider Path: %4!s! Catalog Entry ...
  49. WinSock startup successful : wVersion = %d.%d, wHighVersion = %d.%d vendorInfo addr = x, maxSockets = %d, maxudp = %d (0's ...
  50. WINSR responses are not secure, if you select this option, the responses from WINSR will be forwarded as secure responses ...
  51. Wired 802.1X Authentication failed. Network Adapter: %2 Interface GUID: %1 Peer Address: %3 Local Address: %4 Connection ...
  52. Wired 802.1X Authentication succeeded. Network Adapter: %2 Interface GUID: %1 Peer Address: %3 Local Address: %4 Connection ...
  53. Wired Network Policy Administration. Manage Wired Auto Configuration settings and IEEE 802.3 Security Settings for IEEE 802.3 ...
  54. Wireless 802.1x authentication failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
  55. Wireless 802.1x authentication started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
  56. Wireless 802.1x authentication succeeded. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
  57. Wireless 802.1x authentication was restarted. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: ...
  58. Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint. ...
  59. Wireless authentication failed. 3rd party wireless service required for this connection is not responding. Vendor identification ...
  60. Wireless connection attempt to "%ws" is taking longer than normal to complete The wireless router or access point keeps restarting ...
  61. Wireless connection attempt to "%ws" is taking longer than normal to complete This might be because the wireless (802.1X) ...
  62. Wireless connection attempt to "%ws" is taking longer than normal to complete Wireless authentication is experiencing timeouts. ...
  63. Wireless IHV security failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 ...
  64. Wireless IHV security started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 ...
  65. Wireless IHV security succeeded. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: ...
  66. Wireless LAN (WLAN) Service configures and starts the WLAN AutoConfig service, regardless of whether the computer has any ...
  67. Wireless network association failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: ...
  68. Wireless network association started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: ...
  69. Wireless network association succeeded. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
  70. Wireless network is blocked due to connection failure. Network Adapter: %1 Interface GUID: %2 Connection Mode: %5 Profile ...
  71. Wireless Network Policy Administration. Manage WLAN AutoConfig settings and IEEE 802.1X Security Settings for IEEE 802.11 ...
  72. Wireless security failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 Peer ...
  73. Wireless security started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 Authentication: ...
  74. Wireless security started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 Authentication: ...
  75. Wireless security stopped. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 Security ...