Windows 10

  1. The WinRM service is listening for WS-Management requests. User Action Use the following command to see the specific IPs ...
  2. The WinRM service is listening on the default %1 port %2 and on %1 (Compatibility) port %3 for WS-Management requests. %1 ...
  3. The WinRM service is not listening for %1 requests because there was a failure binding to the URL (%2) in HTTP.SYS. Another ...
  4. The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (%1) in HTTP.SYS. No ...
  5. The WinRM service is not listening for HTTPS requests because there was a failure binding to the URL (%1) in HTTP.SYS. No ...
  6. The WinRM service is not listening for policy changes because there was a failure registering for changes to the contents ...
  7. The WinRM service is not listening for requests since it failed to listen on at least one address and port. Remote management ...
  8. The WinRM service is not listening for WS-Management requests. User Action If you did not intentionally stop the service, ...
  9. The WinRM service is stopping because there was a failure registering for changes to the configuration. User Action Restart ...
  10. The WinRM service is stopping because there was a failure registering for changes to the IP addresses. User Action Restart ...
  11. The WinRM service must be restarted before a UI can be displayed for the SecurityDescriptor selection. Restart the WinRM ...
  12. The WinRM service must be restarted before a UI can be displayed for the SecurityDescriptor selection. Restart the WinRM ...
  13. The WinRM service received an error while trying to unloading a data or event source: DLL="%1" User Action Please check if ...
  14. The WinRM Shell client cannot process the request. One of the argument value passed to the WSManRunShellCommand function ...
  15. The WinRM Shell client cannot process the request. One of the environment variable name passed to the WSManCreateShell function ...
  16. The WinRM Shell client cannot process the request. One of the parameters required for the WinrsCloseShell function is null ...
  17. The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseCommand function is null ...
  18. The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseShell function is null ...
  19. The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShell function is null ...
  20. The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShellCommand function ...
  21. The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null ...
  22. The WinRM Shell client cannot process the request. One of the parameters required for the WSManDisconnectShell function is ...
  23. The WinRM Shell client cannot process the request. One of the parameters required for the WSManReceiveShellOutput function ...
  24. The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShell function is ...
  25. The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShellCommand function ...
  26. The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is ...
  27. The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is ...
  28. The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null ...
  29. The WinRM Shell client cannot process the request. One of the parameters required for the WSMansReceiveShellOutput function ...
  30. The WinRM Shell client cannot process the request. One of the stream id name passed to the WSManCreateShell function is null ...
  31. The WinRM Shell client cannot process the request. The command handle passed to the WSMan Shell function is not valid. The ...
  32. The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The ...
  33. The WinRM Shell client cannot process the request. The stream id index from within WSMAN_STREAM_ELEMENT passed to the WSManSendShellInput ...
  34. The WinRM Shell client cannot process the request. The stream name passed to the WSManSendShellInput function is not valid. ...
  35. The WinRM Shell client cannot process the request. The stream or list of streams passed to the WSManReceiveShellOutput function ...
  36. The WinRS client cannot process the request. An invalid flag was specified for this request. Remove or change the invalid ...
  37. The WinRS client cannot process the request. One of the parameters required for the WinrsGet function is null or zero. Change ...
  38. The WinRS client cannot process the request. One of the parameters required for the WinrsPull function is null or zero. Change ...
  39. The WinRS client cannot process the request. One of the parameters required for the WinrsPush function is null or zero. Change ...
  40. The WinRS client cannot process the request. One of the parameters required is null or zero. Change the request to include ...
  41. The WinRS client cannot process the request. The parameter required for the WinrsCloseReceiveHandle function is null or zero. ...
  42. The WinRS client cannot process the request. The parameter required for the WinrsCloseSendHandle function is null or zero. ...
  43. The WinRS client cannot process the request. The parameter required for the WinrsFreeCreateShellResult function is null or ...
  44. The WinRS client cannot process the request. The parameter required for the WinrsFreePullResult function is null or zero. ...
  45. The WinRS client cannot process the request. The parameter required for the WinrsFreeRunCommandResult function is null or ...
  46. The WinRS client cannot process the request. The server cannot set Code Page. You may want to use the CHCP command to change ...
  47. The WINSEnableLMHostsLookup parameter specifies the lookup files containing mappings of IP addresses to host names. If available, ...
  48. The WINSEnableLMHostsLookup parameter specifies whether local lookup files are used. Lookup files will contain mappings of ...
  49. The WINSEnableLMHostsLookup property indicates whether local lookup files are used. Lookup files will contain a map of IP ...
  50. The WINSHostLookupFile property contains a path to a WINS lookup file on the local system. This file will contain a map of ...
  51. The WINSScopeID parameter specifies the Scope ID value that will be appended to the end of the computer's NetBIOS name. Systems ...
  52. The WINSScopeID property provides a way to isolate a group of computer systems that communicate with each other only. The ...
  53. The Wired AutoConfig (DOT3SVC) service is responsible for performing IEEE 802.1X authentication on Ethernet interfaces. If ...
  54. The wireless access point the computer is connected to does not support WMM Power Save Mode. The wireless network adapter ...
  55. The wireless capability setting on this computer does not match the requirements of "%ws" The selected radio type (802.11a/b/g) ...
  56. The wireless connectivity problems on this computer might be caused by an incorrect network security key or low signal strength ...
  57. The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change ...
  58. The wireless network adapter settings on this computer don't match the requirements of "%ws" The connection mode for ( "ad ...
  59. The wireless network adapter settings on this computer don't match the requirements of "%ws" The selected data rate (802.11a/b/g) ...
  60. The wireless network policy storage could not be opened due to insufficient access rights. You must be an administrator. ...
  61. The wireless network settings on this computer don't match the requirements of "%ws" The wireless setting for the connection ...
  62. The wireless router or access point may have lost Internet connectivity The wireless connection on this computer appears ...
  63. The wireless security settings on this computer do not match the settings on "%ws" EAP type or properties are not correct. ...
  64. The wireless security settings on this computer do not match the settings on "%ws" The wireless authentication settings on ...
  65. The wireless security settings on this computer do not match the settings on "%ws" The wireless authentication settings on ...
  66. The wireless security settings on this computer do not match the settings on "%ws" The wireless authentication settings on ...
  67. The wireless setting for the connection mode ("ad hoc" vs. "infrastructure") doesn't match the requirements of this network ...
  68. The wireless settings for the network adapter on this computer don't match the settings of "%ws" The selected data rate is ...
  69. The wizard can search for other hardware and automatically install it for you. Or, if you know exactly which hardware model ...
  70. The wizard can't finish erasing this disc. Please try to erase it again. If this problem continues, there might be a problem ...
  71. The wizard cannot be started because of one or more of the following conditions: - There are no trusted certification authorities ...
  72. The wizard cannot reset the password because this reset disk is invalid. This disk may be for a different account, or a newer ...
  73. The wizard could not authenticate to Active Directory Lightweight Directory Services instance %1 using the supplied credentials. ...
  74. The wizard could not detect the setting for this hardware; therefore, you must enter these settings on the next screen before ...
  75. The wizard could not read operational attributes from the remote Active Directory Lightweight Directory Services instance ...