Windows 10

  1. The WinRM client cannot process the request. The request must contain one and only one enumeration mode. Change the request ...
  2. The WinRM client cannot process the request. The request must not include credentials when using a smart card or default ...
  3. The WinRM client cannot process the request. The request must specify only one authentication mechanism for proxy. Change ...
  4. The WinRM client cannot process the request. The request must specify only one authentication mechanism. If the No Authentication ...
  5. The WinRM client cannot process the request. The request specified the type of the expiration time (absolute or relative) ...
  6. The WinRM client cannot process the request. The required WSMAN_ALLOWED_PUBLISHERS settings is null or zero. Change the request ...
  7. The WinRM client cannot process the request. The resource locator was invalid. Change the resource locator and try the request ...
  8. The WinRM client cannot process the request. The resource URI for an enumeration operation with WQL filter must not contain ...
  9. The WinRM client cannot process the request. The resource URI is not valid: it does not contain keys, but the class selected ...
  10. The WinRM client cannot process the request. The resource URI must not be " (blank or empty string) or NULL. Change the resource ...
  11. The WinRM client cannot process the request. The response from the destination computer contains a WS-Management FragmentTransfer ...
  12. The WinRM client cannot process the request. The response from the destination computer contains one or more invalid SOAP ...
  13. The WinRM client cannot process the request. The response from the destination computer does not contain a valid SOAP enumeration ...
  14. The WinRM client cannot process the request. The response received from the destination machine contains invalid characters ...
  15. The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element. ...
  16. The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element. ...
  17. The WinRM client cannot process the request. The response to a create request did not contain a valid end point reference. ...
  18. The WinRM client cannot process the request. The response to a Receive request did not contain a valid ReceiveResponse element. ...
  19. The WinRM client cannot process the request. The SPN Server Port can only be used when the authentication mechanism is Negotiate ...
  20. The WinRM client cannot process the request. The unencrypted flag only applies to the HTTP transport. Remove the unencrypted ...
  21. The WinRM client cannot process the request. The WinRM client received an 'access denied' error from the server and it tried ...
  22. The WinRM client cannot process the request. The WinRM client tried to create an SSL configuration for a pair of IP address ...
  23. The WinRM client cannot process the request. The WinRM client tried to use %1 authentication mechanism, but the destination ...
  24. The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change ...
  25. The WinRM client cannot process the request. When an authentication mechanism is not specified, only user name and password ...
  26. The WinRM client cannot process the request. When HTTP is the transport, the Certificate thumbprint must be blank. HTTP does ...
  27. The WinRM client cannot process the request. You must wait for the WSManRunShellCommand API call to complete before calling ...
  28. The WinRM client could not create a push subscription because there are no listeners configured that match the specified ...
  29. The WinRM client could not process the request because credentials were specified along with the 'no authentication' flag. ...
  30. The WinRM client encountered an error while communicating with the WinRM service during the disconnect operation. The shell ...
  31. The WinRM client received a HTTP redirect status code from the remote WS-Management service. WinRM does not support redirects. ...
  32. The WinRM client received a redirect error from the server when it is not appropriate. The only time a redirect error can ...
  33. The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information ...
  34. The WinRM client received an HTTP server error status (500), but the remote service did not include any other information ...
  35. The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This ...
  36. The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured ...
  37. The WinRM configuration is corrupted. Use the following command to restore defaults: winrm invoke Restore http://schemas ...
  38. The WinRM protocol session began an operation of type %1 to the server. The operation accesses class %3 under the %2 namespace. ...
  39. The WinRM runAs configuration operation cannot be completed because the user credentials could not be verified. Verify that ...
  40. The WinRM service cannot make the configuration change. The selector keys of Subject, URI or Issuer cannot be changed by ...
  41. The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the IP address %3 does not exist on ...
  42. The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the MAC address %3 does not exist ...
  43. The WinRM service cannot migrate the listener with Address %1 and Transport %2. A listener that has the same Address and ...
  44. The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the IP address does not exist on the ...
  45. The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the MAC address %3 does not exist on ...
  46. The WinRM service cannot migrate the listener with IP address %1, Port %2 and Transport %3. A listener that has Address=%4 ...
  47. The WinRM service cannot process the request because it is trying to update a deprecated setting. Remove this setting from ...
  48. The WinRM service cannot process the request because the command ID specified by the client is not a valid GUID. Modify the ...
  49. The WinRM service cannot process the request because the request needs to be sent to a different machine. Use the redirect ...
  50. The WinRM service cannot process the request because the shell ID specified by the client is not a valid GUID. Provide a ...
  51. The WinRM service cannot process the request because the subscription manager returned invalid enumeration results. The m:Subscription ...
  52. The WinRM service cannot process the request because the WinRS shell instance is already processing a connect operation. ...
  53. The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo does not contain any options ...
  54. The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo is too complex or uses a structure ...
  55. The WinRM service cannot process the request. A configuration setting or group policy setting denies access to the resource ...
  56. The WinRM service cannot process the request. Push subscriptions are not supported for local session. Change subscription ...
  57. The WinRM service cannot process the request. The Channel Binding Token Hardening Level (CbtHardeningLevel) value is invalid. ...
  58. The WinRM service cannot process the request. The enumeration of end point resources for shell commands is not supported. ...
  59. The WinRM service cannot process the request. The enumeration request expects a selector based filter to specify the shell ...
  60. The WinRM service cannot process the request. The URI parameter is the key to CustomRemoteShell table and cannot be modified. ...
  61. The WinRM service cannot process the request. This WinRS shell instance does not support disconnect and reconnect operations ...
  62. The WinRM service cannot process the request. WSMAN_FLAG_SEND_HEARTBEAT flag requires the event enumerator to be empty. Change ...
  63. The WinRM service cannot validate the client certificate because the revocation status of the certificate or one of the certificates ...
  64. The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the ...
  65. The WinRM service encountered a catastrophic security failure. The service can no longer run under its security context. ...
  66. The WinRM service executed an operation and the provider returned inconclusive information regarding success or failure of ...
  67. The WinRM service failed to create the following SPNs: %1; %2. Additional Data The error received was %3: %3. User Action ...
  68. The WinRM service failed to initialize CredSSP. Additional Data The error received was %1. User Action Configure CertificateThumbprint ...
  69. The WinRM service had a failure (%1) reading configuration during ip address change notification. Service will continue running ...
  70. The WinRM service had a failure applying the current configuration and is stopping. User Action Check for previous event ...
  71. The WinRM service had a failure during migration. User Action Create the configuration again using the WinRM command line ...
  72. The WinRM service had a failure reading the current configuration and is stopping. User Action Use the following command ...
  73. The WinRM service has been configured to accept basic authentication for unsecure HTTP connections. This is not a secure ...
  74. The WinRM service has received an unsecure HTTP connection from %1. This is not a secure configuration. User Action Set AllowUnencrypted ...
  75. The WinRM service has terminated %1 unauthenticated connections over the past %2 minutes to maintain healthy system state. ...