WsmRes.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

Code	Found in	Description
0x72775	78.11011	The WinRM service is not listening for requests since it failed to listen on at least one address and port. Remote management using WinRM will fail. User Action Configure listeners by enabling GPO policy for Auto Configuration of listeners or manually create a listener using WinRM command line tool.
0x72776	78.11011	The WinRM service is not listening for %1 requests because there was a failure binding to the URL (%2) in HTTP.SYS. Another process is registered to listen on the WinRM service URL prefix. User Action Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address.
0x72777	78.11011	The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. Another process is registered to listen on the WinRM client URL prefix. User Action Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address.
0x72778	78.11011	The WinRM service is not listening for HTTPS requests because there was a failure binding to the URL (%1) in HTTP.SYS. No remote requests will be serviced on that URL. User Action Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. Additional Data The error code received from HTTP.sys is %2: %%2
0x72779	78.11011	The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. User Action Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. Additional Data The error code received from HTTP.sys was %2: %%2
0x7277e	78.11011	The WinRM service cannot validate the client certificate because the revocation status of the certificate or one of the certificates in the certificate chain is either offline or stale. User Action Please ensure that the Certificate Revocation List is accessible and up-to-date.
0x7277f	78.11011	User authentication using Basic authentication scheme failed. Additional Data Unexpected error received from LogonUser %1: %%1.
0x72780	78.11011	The client certificate exceeded the maximum size allowed by the WinRM service. User Action Please use a different client certificate or a different authentication mechanism.
0x72781	78.11011	Request processing failed because the WinRM service cannot load data or event source: DLL="%1" User Action Please check if "%1" exists. Additional Data Loading %1 failed with error="%2" (%%2).
0x72782	78.11011	The SSL configuration for IP %1 and port %2 is shared with another service, such as Internet Information Services (IIS).
0x72787	78.11011	The WinRM service is unable to start because of a failure during initialization. Additional Data The error code is %1.
0x72788	78.11011	The WinRM service has received an unsecure HTTP connection from %1. This is not a secure configuration. User Action Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire.
0x72789	78.11011	The WinRM service has been configured to accept basic authentication for unsecure HTTP connections. This is not a secure configuration. User Action Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire.
0x72790	78.11011	The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (%1) in HTTP.SYS. No remote requests will be serviced on that URL. User Action Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. Additional Data The error code received from HTTP.sys is %2: %%2
0x72791	78.11011	The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. User Action Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. Additional Data The error code received from HTTP.sys was %2: %%2
0x72792	78.11011	IP Filter %1 specified in the GPO policy for Auto Configuration of listeners is invalid and it will be ignored. Due to this issue, the WinRM service cannot use the autoconfigured listener. "" is used to indicate that the service should listen on all available IPs on the machine. When "" is used, other ranges cannot be specified in the filter. User Action Remove other IP ranges if "*" needs to be included in the IP Filter.
0x72793	78.11011	The IP Range %1 is invalid and it will be ignored. Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using "," as delimiter. Example IPv4 ranges: 2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22 Example IPv6 ranges: 3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 User Action Correct the IP filter %1 using the syntax described above.
0x72794	78.11011	The WinRM service is not listening for policy changes because there was a failure registering for changes to the contents of the WS-Management policy key. No group policy change will be serviced. User Action Stop and restart the WinRM service. Additional Data The error code was %1.
0x72798	78.11011	The WinRM service encountered a catastrophic security failure. The service can no longer run under its security context. User Action Stop and restart the WinRM service. Additional Data The error code is %1.
0x72799	78.11011	The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the IP address does not exist on the destination computer. This listener was ignored during migration. User Action Create the listener again with the correct IP address.
0x7279a	78.11011	The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the IP address %3 does not exist on the destination computer. This listener was ignored during migration. User Action Create the listener again with the correct IP address.
0x7279b	78.11011	The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the MAC address %3 does not exist on the destination computer. This listener was ignored during migration. User Action Create the listener again with the correct MAC address.
0x7279c	78.11011	The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the MAC address %3 does not exist on the destination machine. This listener was ignored during migration. User Action Create the listener again with the correct MAC address.
0x7279d	78.11011	The WinRM service cannot migrate the listener with IP address %1, Port %2 and Transport %3. A listener that has Address=%4 and Transport=%5 configuration already exists.
0x7279e	78.11011	The WinRM service cannot migrate the listener with Address %1 and Transport %2. A listener that has the same Address and Transport configuration already exists.
0x7279f	78.11011	The WinRM service had a failure during migration. User Action Create the configuration again using the WinRM command line tool. Additional Data The error code is: %1 %%1
0x727a0	78.11011	The WinRM service had a failure reading the current configuration and is stopping. User Action Use the following command to restore defaults: winrm invoke Restore winrm/config @{} Then add any custom configuration settings and restart the service. Additional Data The error code is: %1 %%1
0x727a1	78.11011	The WinRM service had a failure applying the current configuration and is stopping. User Action Check for previous event log messages and restart the service.
0x727a2	78.11011	The WinRM service had a failure reading the current configuration and is stopping. User Action Use the following command to restore defaults: winrm invoke Restore winrm/config @{} Then add any custom configuration settings and restart the service. Additional Data The error code is: %1 %%1
0x727a3	78.11011	The host name pattern "%1" is invalid and it will be ignored. Host name patterns must not be empty and they can contain at most one wildcard (""). "" pattern can be used to indicate all hosts; if this pattern is used, no other pattern can show up in the list. Special string "" can be used to indicate all host names that do not have a '.' User Action Correct the host name pattern using the syntax described above.
0x727a4	78.11011	The WinRM service is listening for WS-Management requests. User Action Use the following command to see the specific IPs on which WinRM is listening: winrm enumerate winrm/config/listener
0x727a5	78.11011	The WinRM service is not listening for WS-Management requests. User Action If you did not intentionally stop the service, use the following command to see the WinRM configuration: winrm enumerate winrm/config/listener
0x727a6	78.11011	The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. User Action Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: winrm get winrm/config/service Additional Data Listener transport: %1 Listener address: %2
0x727a7	78.11011	The WinRM service had a failure (%1) reading configuration during ip address change notification. Service will continue running with old configuration. User Action If immediae changes are required manually restart the service
0x727a8	78.11011	The WinRM service successfully processed an address change notification.
0x727a9	78.11011	The WSMan IIS module failed to read configuration. The error received was %1: %%1 %2. User Action Make sure both the schema and validation files are present and valid.
0x727aa	78.11011	The WinRM service failed to create the following SPNs: %1; %2. Additional Data The error received was %3: %%3. User Action The SPNs can be created by an administrator using setspn.exe utility.
0x727ab	78.11011	The WSMan service failed to read configuration of the following plugin: %1. The error received was %2: %%2 %3. User Action Make sure this plugin configuration is valid.
0x727ac	78.11011	The WinRM service failed to initialize CredSSP. Additional Data The error received was %1. User Action Configure CertificateThumbprint setting under the WinRM configuration for the service. Use the thumbprint of a valid certificate and make sure that Network Service has access to the private key of the certificate.
0x727ad	78.11011	The WinRM service received an error while trying to unloading a data or event source: DLL="%1" User Action Please check if there is an updated version of this file available: "%1". Additional Data Shutting down %1 failed with error="%2" (%%2).
0x727ae	78.11011	The WinRM service is listening on the default %1 port %2 and on %1 (Compatibility) port %3 for WS-Management requests. %1 port %3 is no longer the default port for the WinRM service. If you want to disable the listener on the (Compatibility) port %3, run the following command: Winrm set winrm/config/service @{%4="False"}
0x727af	8.11011	The WinRM service has terminated %1 unauthenticated connections over the past %2 minutes to maintain healthy system state. This will likely happen if the service is overloaded or if the service is under an authentication based attack. Action: Enable and observe Windows Remote Management Analytic log and look for warning events with Id 1843. These include additional information about the clients that got abruptly terminated.
0x10000001	78.11011	Soap Trace
0x10000002	78.11011	Client
0x10000003	78.11011	Server
0x10000004	78.11011	Security
0x10000005	78.11011	QuotaViolation
0x10000006	78.11011	Activity Transfer
0x10000007	78.11011	Error
0x10000038	78.11011	Classic
0x30000001	78.11011	Start
0x30000002	78.11011	Stop
0x4033c351	78.11011	The WS-Management service cannot process the request because the URI contains a '?' but no key was present.
0x4033c352	78.11011	The WS-Management service cannot process the request. The URI contains a key: (%1). But WS-Management cannot find a value because no '=' was found.
0x4033c353	78.11011	The WS-Management service cannot process the request because the URI contains a value in parentheses followed by '%1!c!'. The URI should either end or a new key should start following a '+'.
0x4033c354	78.11011	The WS-Management service cannot process the request. The resource URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters).
0x4033c355	78.11011	The WS-Management service cannot process the request. The filter dialect URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters).
0x4033c356	78.11011	The WS-Management service cannot process the request. The SOAP packet contained a WS-Addressing Action element that was longer (%1!d! characters) that the maximum length that is supported (%2!d! characters).
0x4033c357	78.11011	The WS-Management service cannot process the request. The URI contains more keys than maximum number that WS-Management supports (%1!d!).
0x4033c358	78.11011	The WS-Management service cannot process the request. The URI contains a duplicate key (%1).
0x4033c359	78.11011	The WS-Management service cannot process the request. The URI lacks a closing or an opening parenthesis.
0x4033c35a	78.11011	The WS-Management service does not support concurrent pull operations for enumerations.
0x4033c35b	78.11011	The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints.
0x4033c35c	78.11011	Not used. To be removed.
0x4033c35d	78.11011	The WS-Management service cannot process the request. The resource URI does not support the %1 operation.
0x4033c35e	78.11011	The WS-Management service cannot process the request. The operation id %1 is larger than expected.
0x4033c35f	78.11011	ProvSysException, ErrorCode=%1!d!, Message=%2.
0x4033c360	78.11011	The function: "%1" failed unexpectedly. Error=%2!d!.
0x4033c361	78.11011	The function "%1" failed unexpectedly. Error=%2!d!, GetLastError=%3!d!.
0x4033c362	78.11011	The function "%1" failed unexpectedly. Hresult=%2!X!.
0x4033c363	78.11011	Could not access the WS-Management catalog from %1. The catalog contains the metadata that describes resources, or logical endpoints.
0x4033c364	78.11011	The function: "%1" failed unexpectedly. GetLastError=%2!d!.
0x4033c365	78.11011	Unexpected result from internal function: "%1". GetLastError: %2!d!. File: %3:%4!d!
0x4033c366	78.11011	A call to the function "%1" supplied an invalid parameter.
0x4033c367	78.11011	A call to the function "%1" supplied an invalid parameter. The invalid parameter = %2.
0x4033c368	78.11011	The WS-Management service does not support the request.
0x4033c369	78.11011	The WS-Management cannot locate the data source with the specified id (%1).
0x4033c36a	78.11011	The WS-Management service cannot process the request. The number of outstanding requests exceeds the maximum number allowed.
0x4033c36b	78.11011	The WS-Management service cannot process the request. The SOAP packet contains a WS-Management ResourceURI element that is either invalid, duplicated, or too long.
0x4033c36c	78.11011	The WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing MessageID element that was either invalid, duplicated, or too long.
0x4033c36d	78.11011	The WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing To element that was either invalid, duplicated, or too long.
0x4033c36e	78.11011	The WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing Action element that is either invalid, duplicated, or too long.
0x4033c36f	78.11011	The WS-Management service cannot process the request. The SOAP packet does not contain a valid WS-Addressing ReplyTo element. The element is duplicated or is not the WS-Addressing anonymous URI. http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous.
0x4033c370	78.11011	The WS-Management service cannot process the request. The SOAP packet does not contain a valid WS-Addressing FaultTo element. The element is duplicated or is not the WS-Addressing anonymous URI. http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous.
0x4033c371	78.11011	The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-Management Locale element. The element is duplicated or does not match the system locale.
0x4033c372	78.11011	The WS-Management service cannot process the request. The SOAP packet does not contain a valid enumeration context ID element. The incoming Pull or Release packet should contain a body entry containing an WS-Enumeration EnumerationContext.
0x4033c373	78.11011	The WS-Management service cannot process the request. WS-Management cannot identify the enumeration context ID in the SOAP packet. The packet may have been invalid, or the operation may have timed out.
0x4033c374	78.11011	The WS-Management service could not identify the subscription context ID in the SOAP packet that was received. The packet may have been invalid, or the operation may have timed out.
0x4033c375	78.11011	The WS-Management service received a SOAP packet that contained a request to do a %1 operation. This operation requires a single element in the body.Number of elements found in the soap body was %2!d!.
0x4033c376	78.11011	The WS-Management service cannot process the request. The SOAP packet contains the request to do a %1 operation. This operation requires a single element in the body.
0x4033c377	78.11011	The WS-Management service cannot process the request. The SOAP packet does not have all the fields that are required.
0x4033c378	78.11011	The WS-Management service cannot process the request. The input XML contains an unrecognized XML element: "%1". Ensure that the spelling of the element name is correct.
0x4033c379	78.11011	The WS-Management service cannot process the configuration request. XML element %1 must contain sub-elements and none are present.
0x4033c37a	78.11011	The WS-Management service cannot process the request. The XML contains an invalid boolean value: "%1". Valid boolean values are "true", "false", "1", or "0".
0x4033c37b	78.11011	The WS-Management service cannot process the request. The XML contains an invalid integer value "%1". Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length.
0x4033c37c	78.11011	The WS-Management service cannot process the request. The XML contains an invalid security descriptor "%1";received error (%2!d!) from ConvertStringSecurityDescriptorToSecurityDescriptor.
0x4033c37d	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid security descriptor: "%1". The security descriptor is missing an owner.
0x4033c37e	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid security descriptor: "%1". The security descriptor is missing a group.
0x4033c37f	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid security descriptor: "%1". The security descriptor is missing a discretionary access control list (DACL).
0x4033c380	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid security descriptor: "%1". WS-Management does not support the access control entry (ACE) type: %2!d!.
0x4033c381	78.11011	Invalid security descriptor "%1"; access right must be a combination of GR (generic read = WSManGet, WSManEnumerate, WSManSubscribe), GW (generic write = WSManPut, WSManCreate, WSManDelete), or GX (generic execute = WSManInvoke) GA (generic all)
0x4033c382	78.11011	The WS-Management service cannot process the configuration request. The request has a blank setting. %1 cannot be "" (blank or empty string) or NULL.
0x4033c383	78.11011	The WS-Management service cannot process the configuration request. WS-Management configuration received an invalid URL. The URL prefix cannot start or end with a '/'.
0x4033c384	78.11011	The WS-Management service cannot process the configuration request. The XML contains a URL with an invalid character. The URL prefix cannot contain %1!c!.
0x4033c385	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid integer setting: %1 that is too small: %2!lu!. The value must be %3!lu! or more.
0x4033c386	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid integer setting: %1 that is too large: %2!lu!. The value must be %3!lu! or less.
0x4033c387	78.11011	The WS-Management service cannot process the request. The XML contains an invalid port number: %1!lu! The value must be %2!lu! or more.
0x4033c388	78.11011	The WS-Management service cannot process the request. The XML contains an invalid port number that is too large: %1!lu! The value must be %2!lu! or less.
0x4033c389	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid setting type: %1!d!.
0x4033c38a	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid setting: %1!d!.
0x4033c38b	78.11011	The WS-Management service cannot process the configuration request. The XML contains an invalid setting %1. The value is longer than the maximum length of %2!d!
0x4033c38c	78.11011	The WS-Management service cannot process the configuration request because it cannot enable the %1 privilege. This privilege is required to set security on registry keys. The error code is %2!d!.
0x4033c38d	78.11011	The WS-Management service cannot process the configuration request because it cannot open a registry key. The error code is %1!d!.
0x4033c38e	78.11011	The WS-Management service cannot process the configuration request. The XML contains an unknown URI: %1.
0x4033c38f	78.11011	The WS-Management service cannot process the configuration request. The XML contains a repeated element: %1.
0x4033c390	78.11011	The WS-Management service cannot process the configuration request. The XML contains a complex element: %1. WS-Management configuration requires a simple element.
0x4033c391	78.11011	The WS-Management service cannot process the configuration request. The XML contains a simple element: %1. WS-Management configuration requires a complex element.
0x4033c392	78.11011	The WS-Management service cannot process the configuration request. The WS-Addressing Action URI (%1) and resource URI (%2) do not match. The %3 action can only be used on the %4 resource.
0x4033c393	78.11011	The WS-Management service cannot process the configuration request. This action requires input XML with an element name of %1 and no parameters.
0x4033c394	78.11011	Not used. To be removed.
0x4033c395	78.11011	The WS-Management service cannot process the request. The user does not have permission for the %1 operation on the %2 resource.
0x4033c396	78.11011	The WS-Management service cannot process the request. The XML contains an invalid timeout field in the SOAP header: %1.
0x4033c397	78.11011	The WS-Management service cannot process the request. The URI does not contain keys, but the class is not a singleton.
0x4033c398	78.11011	The WS-Management service cannot process the request. The XML contains a timeout value that is too small: %1!lu!. The timeout value must be larger than %2!lu!.
0x4033c399	78.11011	The WS-Management service cannot process the request. The SOAP header %1 contains the mustUnderstand attribute, but it is not a known header by this WS-Management implementation. This could be caused by the use of a version of the protocol which is not supported, or may be an incompatibility between the client and server implementations.
0x4033c39a	78.11011	The WS-Management service cannot process the request. The SOAP batch parameter %1 is invalid.
0x4033c39b	78.11011	The WS-Management service cannot process the request. The SOAP packet did not contain a valid Timeout element, was duplicated or the duration was not a valid xs:Duration. For example, the timeout PT30S is 30 seconds.
0x4033c39c	78.11011
0x4033c39d	78.11011	The WS-Management service cannot process the request. The data source failed to return the result.
0x4033c39e	78.11011	The WS-Management service cannot process the request. The data source failed to return the result URI from an operation to create a new instance.
0x4033c39f	78.11011	WS-Management could not connect to the specified destination: (%1:%2!d!).
0x4033c3a0	78.11011	The operation was aborted.
0x4033c3a1	78.11011	WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (%1!lu!) is: %2.
0x4033c3a2	78.11011	The server certificate on the destination computer (%1:%2!d!) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10
0x4033c3a3	78.11011	WS-Management cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error.
0x4033c3a4	78.11011	WS-Management cannot process the request. The HTTP response from the destination computer was not in the same format as the request. A Unicode request packet may have been sent and an ANSI packet received.
0x4033c3a5	78.11011	The client specified username and password in the request to the destination computer. But the destination computer requested a client certificate.
0x4033c3a6	78.11011	WS-Management cannot process the request. The response received from the destination computer includes element %1. But this element does not match what is expected.
0x4033c3a7	78.11011	WS-Management cannot process the request. The element %1 is missing from the response sent by the destination computer.
0x4033c3a8	78.11011	WS-Management encountered an invalid internal parameter.
0x4033c3a9	78.11011	The WS-Management service cannot process the configuration request because the certificate thumbprint in the request is not a valid hex string: %1.
0x4033c3aa	78.11011	The WS-Management service does not support concurrent event delivery operations.
0x4033c3ab	78.11011	The WS-Management service encountered an internal error.
0x4033c3ac	78.11011	The WS-Management service cannot process the request. The response from the destination computer is invalid.
0x4033c3ad	78.11011	The WS-Management service cannot process the request because it cannot find the requested System.
0x4033c3ae	78.11011	The WS-Management service cannot process the request because the URI contains incorrect keys that WS-Management cannot process.
0x4033c3af	78.11011	The WS-Management service cannot process the request because port %1 is invalid.
0x4033c3b0	78.11011	The WS-Management service cannot process the request because IP address %1 is invalid.
0x4033c3b1	78.11011	The WS-Management service cannot process the configuration request because the transport is not supported by the service: %1. The value should be one of the accepted values: %2.
0x4033c3b2	78.11011	The WS-Management service cannot process the configuration request because the configuration for a static listening address requires an empty MAC address setting.
0x4033c3b3	78.11011	The WS-Management service cannot process the request because the SOAP packet contained an invalid or duplicate WS-Management SelectorSet element.
0x4033c3b4	78.11011	The data source encountered the error: %1.
0x4033c3b5	78.11011	The WS-Management service cannot process the configuration request. After a listener is configured, you cannot change the value of the IP address or of the port number.
0x4033c3b6	78.11011	The WS-Management service received an invalid SOAP packet. The packet contains an invalid or missing WS-Management Delivery mode.
0x4033c3b7	78.11011	The WS-Management service cannot process the configuration request. The configuration of a dynamic ip address requires a MAC address setting.
0x4033c3b8	78.11011	The WS-Management service cannot process the configuration request. The SSL configuration for IP %1 and port %2 is owned by another service and cannot be shared.
0x4033c3b9	78.11011	The WS-Management service cannot process the request. The value for the selector %1 is invalid.
0x4033c3ba	78.11011	The WS-Management service cannot process the request because the maximum envelope size header was invalid or duplicated.
0x4033c3bb	78.11011	The WS-Management service cannot process the request because the maximum envelope size requested is (%1!lu!) too small. The size must be %2!lu! or larger.
0x4033c3bc	78.11011	The WS-Management service cannot process the request because the maximum envelope size requested is (%1!lu!) too large. The size must be %2!lu! or smaller.
0x4033c3bd	78.11011	The WS-Management service cannot process the request because the timeout value is too large: %1!lu! The timeout value must be less than %2!lu!.
0x4033c3be	1011	The WS-Management service cannot process the request. The computed response packet size (%1!lu!) exceeds the maximum envelope size that is allowed (%2!lu!).
0x4033c3bf	78.11011	An arithmetic operation failed in function "%1". The error code is %2!d!.
0x4033c3c0	78.11011	The WS-Management service cannot process the request. The MAC address for the network adapter does not have the dynamic IP address.
0x4033c3c1	78.11011	The WS-Management service cannot process the enumeration request. The server is already executing the maximum number of enumerations. Retry later.
0x4033c3c2	78.11011	The WS-Management service cannot process the request because the Endpoint Reference does not contain a WS-Addressing Address element.
0x4033c3c3	78.11011	WS-Management service cannot process the request because the WS-Addressing Address in the Endpoint Reference (EPR) contains one or more unexpected child elements.
0x4033c3c4	78.11011	The WS-Management service cannot process the request because the WS-Addressing EndPointReference (EPR) contained an unexpected XML element.
0x4033c3c5	78.11011	The WS-Management service cannot process the request because the WS-Addressing EndPointReference (EPR) contained an unexpected XML element.
0x4033c3c6	78.11011	The WS-Management service cannot process the request because the WS-Addressing EndPointReference contains a repeated child element: %1.
0x4033c3c7	78.11011	Not used.
0x4033c3c8	78.11011	The WS-Management service cannot process the request because the service does not support the action: %1.
0x4033c3c9	78.11011	The WS-Management service cannot process the request because the filter or dialect has syntax errors, contains both a WS-Enumeration and WS-Management version of the filter, other semantic problems, or is too complex.
0x4033c3ca	78.11011	The data source cannot add another item to a WS-Management message envelope because a single element in the batch exceeded the envelope size.
0x4033c3cb	78.11011	The WS-Management service cannot process the request. The SOAP packet that WS-Management received did not contain a valid %1 element.
0x4033c3cc	78.11011	The WS-Management service cannot process the request because the XML in the SOAP packet is invalid.
0x4033c3cd	78.11011	The WS-Management service cannot process the request. The URI generated from the CIM path is too long. The maximum supported length is %1!d! characters.
0x4033c3ce	78.11011	The WS-Management service cannot process the request. The key %2 in an instance of class %3 has an unexpected CIM type.
0x4033c3cf	78.11011	The WS-Management service cannot process the request because the request contains an embedded object or array of embedded objects. WS-Management does not support retrieving or updating instances containing embedded objects or arrays of embedded objects.
0x4033c3d0	78.11011	The WS-Management service cannot process the request because a WMI instance contains an invalid char16 value: %1.
0x4033c3d1	78.11011	The WS-Management service cannot process the request because the XML contains an unknown CIM type for the property: %1.
0x4033c3d2	78.11011	The WS-Management service cannot process the request because the XML contains an invalid datetime value (%1) in a WMI instance.
0x4033c3d3	78.11011	The WS-Management service cannot process the request. The request contains an XML element (%1) that does not represent a string property. Only string properties can be empty. To specify a null value, add the xsi:nil attribute to the element.
0x4033c3d4	78.11011	The WS-Management service cannot process the request. When setting an array property to null, only one element with that name can be present in the input XML. Property: %1.
0x4033c3d5	78.11011	The WS-Management service cannot process the request because it contains several XML elements with the same name for a property that is not an array. Property: %1.
0x4033c3d6	78.11011	The WS-Management service cannot process the request because it contains an invalid type for a property qualifier on an instance or on the class. Property: %2 Qualifier: %1.
0x4033c3d7	78.11011	The WS-Management service cannot process the request because it contains an invalid empty string for representing a number.
0x4033c3d8	78.11011	The WS-Management service cannot process the request because it contains an invalid character. WS-Management cannot convert the string to a number. String: %1. Ensure that the string represents the correct datatype.
0x4033c3d9	78.11011	The WS-Management service cannot process the request. WS-Management cannot convert a string to an unsigned number. The request contains an unexpected minus sign. String: %1. Ensure that the string represents the correct datatype.
0x4033c3da	78.11011	The WS-Management service cannot process the request because the service cannot convert string %1 to a number with %2!d! bits. The string does not represent a number in the allowed range. Ensure that the string represents the correct datatype.
0x4033c3db	78.11011	The WS-Management service cannot process the request because the request contains an invalid boolean value (%1) for element %2. The value must contain "true", "false", "1", or "0".
0x4033c3dc	78.11011	The WS-Management service cannot process the request. An element of the array named %1 contains the xsi:nil attribute. The array cannot have a NULL element.
0x4033c3dd	78.11011	The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1. Ensure that the string represents the correct datatype.
0x4033c3de	78.11011	The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1. CIM datetime type does not accept more than 99999999 days.
0x4033c3df	78.11011	The WS-Management service cannot process the request. The request contains an invalid datetime. The string %1 does not represent any of these types: xs:dateTime, xs:date, or xs:time.
0x4033c3e0	78.11011	The WS-Management service cannot process the request because it contains an invalid value for a system property: %1. The value is not a string or it is an empty string.
0x4033c3e1	78.11011	The WS-Management service cannot process the request because the XML simple content is invalid: %1.
0x4033c3e2	78.11011	The WS-Management service cannot process the request because a class has an invalid Singleton qualifier. The class is %1. The type is not boolean or the value is not 'TRUE'.
0x4033c3e3	78.11011	The WS-Management service cannot process the request. The element for a datetime value must have exactly one child and no mixed content.
0x4033c3e4	78.11011	The WS-Management service cannot process the request. An element in a datetime property has an incorrect name: %1.
0x4033c3e5	78.11011	The WS-Management service cannot process the request because it cannot convert the string (%1) to a double value. Ensure that the type that the string represents is correct.
0x4033c3e6	78.11011	The WS-Management service cannot process the request because it cannot convert the string (%1) to a floating point value. The value is too large. Ensure that the type that the string represents is correct.
0x4033c3e7	78.11011	The element for a endpoint reference value must have one and only one child.
0x4033c3e8	78.11011	The WS-Management service cannot process the request. The action URI (%1) is invalid. Method %2 does not exist in class %3.
0x4033c3e9	78.11011	The WS-Management service cannot process the request. The elements for an array property (%1) must be in consecutive order.
0x4033c3ea	78.11011	The WS-Management service cannot process the configuration request. The SSL configuration for IP %1 and port %2 is shared with another service. Client certificates for Mutual configuration must map to a user account. The other service does not have this http configuration.
0x4033c3eb	78.11011	The WS-Management service failed to set the user certificate for user authentication.
0x4033c3ec	78.11011	The WS-Management service cannot guarantee that all data is returned in the requested locale as some data sources may not be able to comply. Resend the remote request with locale as a hint (the SOAP header should have mustUnderstand="false").
0x4033c3ed	78.11011	The WS-Management service cannot perform the configuration operation. A listener with Address=%1 and Transport=%2 configuration already exists. You have to delete the existing listener first in order to be able to create it with the same Address and Transport values.
0x4033c3ee	78.11011	The WS-Management service cannot process the request because the Endpoint Reference does not contain a WS-Management ResourceURI element.
0x4033c3ef	78.11011	The xsi:type attribute is missing from element (%1). This attribute is required for embedded objects.
0x4033c3f0	78.11011	The WS-Management FragmentTransfer element has no text content.
0x4033c3f1	78.11011	The WS-Management FragmentTransfer element contains one or more child elements.
0x4033c3f2	78.11011	The SOAP packet that was received did not contain a valid WS-Management FragmentTransfer element, or was duplicated.
0x4033c3f3	78.11011	The response received from the destination machine includes unexpected element %1.
0x4033c3f4	78.11011	There is no filter specified for the given dialect.
0x4033c3f5	78.11011	The specified class does not exist in the given namespace.
0x4033c3f6	78.11011	No instance found with given property values.
0x4033c3f7	8.11011	The WS-Management service cannot process the request. The WQL query is invalid.
0x4033c3f8	8.11011	Invalid policy setting %1; The specified value %2!lu! is below the minimum required value of %3!lu!.
0x4033c3f9	78.11011	Invalid policy setting %1; value must be no larger than %3!lu!, but given %2!lu!
0x4033c3fa	78.11011	Invalid policy setting %1; the policy has the wrong type.
0x4033c3fb	78.11011	Invalid policy setting %1;
0x4033c3fc	78.11011	Invalid listener address %1.
0x4033c3fd	78.11011	An exception was thrown (%1!d!) while parsing the following fragment path : %2.
0x4033c3fe	78.11011	Syntax error at position %1!d! for the following fragment path : %2.
0x4033c3ff	78.11011	Lexical error at position %1!d! for the following fragment path : %2.
0x4033c400	78.11011	Parsing error (%1!d!) at position %2!d! for the following fragment path : %3.
0x4033c401	78.11011	An absolute fragment path must start with the class name present in the resource URI.
0x4033c402	78.11011	Node %1 is invalid : the previous node must correspond to a WMI object and this node must a property of that object or the previous node must correspond to a datetime property and this node must have one of these values (Datetime, Date, Time, Interval or CIM_DateTime).
0x4033c403	78.11011	Cannot apply text() function to array, object, datetime or reference properties.
0x4033c404	78.11011	The fragment path selected an unknown attribute. Only 'type' and 'nil' can be used.
0x4033c405	78.11011	The position of the element must be a non-zero positive integer. Value %1!lu! was given.
0x4033c406	78.11011	Node %1 does not correspond to an array property; position context cannot be used for it.
0x4033c407	78.11011	An attribute was selected by the fragment path, but updating attributes is not supported.
0x4033c408	78.11011	The input XML is not valid for this fragment-level Put operation : it must contain a single element (the WS-Management XmlFragment element), which must have a simple content or be empty; empty content is allowed only for string properties.
0x4033c409	78.11011	Node %1 selects a key property, but keys cannot be updated.
0x4033c40a	78.11011	The input XML is not valid for this fragment-level Put operation : it must contain a single element (the WS-Management XmlFragment element), which must have a single child with name matching the property to be updated; the child can have empty content only if the operation updates a string property.
0x4033c40b	78.11011	The fragment path cannot select a property more than %1!d! levels deep.
0x4033c40c	78.11011	The WS-Management service cannot process the request. The request contains more options than maximum supported(%1!d!).
0x4033c40d	78.11011	The WS-Management service cannot process the request because the SOAP packet that was received contained a invalid WS-Management OptionSet element, or it was duplicated.
0x4033c40e	78.11011	The WS-Management service Wmi plugin does not support the specified OptionSet because MustComply for one of the options is set.
0x4033c40f	78.11011	The resource URI does not support options.
0x4033c410	78.11011	The WS-Management service does not support the specified compression scheme (%1).
0x4033c411	78.11011	The config setting %1 cannot be changed because is controlled by policies. The policy would need to be set to "Not Configured" in order to change the config setting.
0x4033c412	78.11011	There exists no property corresponding to index %1!d! in the specified array.
0x4033c413	78.11011	WS-Management does not allow changes to a listener created automatically by the group policy. The policy "Allow Auto Configuration of listeners on WinRm service" would need to be set to "Not Configured" in order to create a new listener for same Address and Transport or to modify an already existing listener.
0x4033c414	78.11011	It is not allowed to change the value of the address or of the transport for a configured listener.
0x4033c415	78.11011	The WS-Management service cannot process the request because appending port number to service principal name cannot be executed. Appending port number to the service principal name of the remote server requires a version of WinHTTP.dll that implements WINHTTP_OPTION_SPN option flag.
0x4033c416	78.11011	The requested operation cannot be performed. No default authorization schemes are available when using HTTPS. Username and password must be specified.
0x4033c417	78.11011	The fragment path must not contain tokens longer than 1023 characters.
0x4033c418	78.11011	Unit test plugin for Windows Remote Management
0x4033c419	78.11011	WMIv1 plugin for Windows Remote Management
0x4033c41a	78.11011	SEL plugin for Windows Remote Management
0x4033c41b	78.11011	Test plugin for Windows Remote Management
0x4033c41c	78.11011	Test plugin for Windows Command Shell
0x4033c41d	78.11011	Event collector plugin for Windows Remote Management
0x4033c41e	78.11011	Built-in catalog plugin for Windows Remote Management
0x4033c41f	78.11011	WinRM failed to load the plugin DLL for %1. Loading the DLL failed for the path %2 with error code %3!d!. The plugin may be unavailable or the DLL may not be properly installed.
0x4033c420	78.11011	WinRM cannot process the request because the request is missing the element titled '%1'.
0x4033c421	78.11011	WinRM cannot process the request because a selector set contains text. Selector sets must contain only '%1' elements.
0x4033c422	78.11011	WinRM cannot process the request because a selector set contains an unrecognized element. Selector sets must contain only '%1' elements.
0x4033c423	78.11011	WinRM cannot process the request because a '%1' element is missing a '%2' attribute.
0x4033c424	78.11011	WinRM cannot process the request because a selector contains multiple child elements.
0x4033c425	78.11011	WinRM cannot process the request because a selector contains both text and a child element. Remove the text.
0x4033c426	78.11011	WinRM cannot process the request because an option set contains text. Option sets must contain only '%1' elements.
0x4033c427	78.11011	WinRM cannot process the request because an option set contains an unrecognized element. Option sets must contain only '%1' elements.
0x4033c428	78.11011	WinRM cannot process the request because an option contains multiple child elements or complex content.
0x4033c429	78.11011	WinRM cannot process the request because a key is either "" (blank or empty string) or NULL.
0x4033c42a	78.11011	WinRM cannot process the request because an option contains a name attribute which is either "" (blank or empty string) or NULL.
0x4033c42b	78.11011	WinRM cannot process the request because a WMI option value is NULL.
0x4033c42c	78.11011	WinRM cannot process the request because a non-array WMI option occurred more than once. WMI array options must use the prefix 'wmiarray:'.
0x4033c42d	78.11011	WinRM cannot process the request because a WMI option was defined both as an array option and as a non-array option. WMI options must occur exactly once with the prefix 'wmi:' or at least once with the prefix 'wmiarray:'.
0x4033c42e	78.11011	The xsi:type attribute (%1) does not identify an existing class.
0x4033c42f	78.11011	The XML namespace URI (%1) is invalid. Check the documentation for constructing the namespace URI for a CIM class.
0x4033c430	78.11011	The SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable.
0x4033c431	78.11011	The SSL certificate is invalid.
0x4033c432	78.11011	The SSL certificate was revoked.
0x4033c433	78.11011	The SSL certificate is signed by an unknown certificate authority.
0x4033c434	78.11011	The SSL certificate contains a common name (CN) that does not match the hostname.
0x4033c435	78.11011	The SSL certificate is expired.
0x4033c436	78.11011	The SSL certificate is not appropriate for server authentication.
0x4033c437	78.11011	Encountered an internal error in the SSL library.
0x4033c438	78.11011	The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Management catalog. For getting Windows Remote Management configuration, use the following resource URI: %2.
0x4033c439	78.11011	Cannot update an instance of class %1 using a representation of an instance for class %2; please provide a representation of an instance for class %1.
0x4033c43a	78.11011	Built-in catalog plugin for Windows Remote Management
0x4033c43b	78.11011	Built-in catalog plugin for Windows Command Shell
0x4033c43c	78.11011	The WS-Management service cannot process the request because an embedded object or reference element contains mixed content.
0x4033c43d	78.11011	The WS-Management service cannot process the request because a date-time element or simple property contains child elements.
0x4033c43e	78.11011	The WS-Management service cannot process the request because an element ("%1") is missing from the input XML. Non-array properties cannot be missing from the input XML.
0x4033c43f	78.11011	WinRM cannot process the request because the XML parser unexpectedly reached the end of input.
0x4033c440	78.11011	Not used. To be removed.
0x4033c441	78.11011	Not used. To be removed.
0x4033c442	78.11011	Not used. To be removed.
0x4033c443	78.11011	Not used. To be removed.
0x4033c444	78.11011	Not used. To be removed.
0x4033c445	78.11011	WinRM cannot process the request because the input XML uses an undefined XML namespace.
0x4033c446	78.11011	Not used. To be removed.
0x4033c447	78.11011	Not used. To be removed.
0x4033c448	78.11011	Not used. To be removed.
0x4033c449	78.11011	The WinRM migrated configuration from R2 is corrupted. The listener configuration is not valid.
0x4033c44a	78.11011	The WinRM configuration is corrupted. Use the following command to restore defaults: winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{} Then add any custom configuration settings.
0x4033c44b	78.11011	The WS-Management service cannot process the request. The SOAP packet does not contain a valid subscription ID element. The incoming Unsubscribe request should contain a header entry with the reference property element obtained from the Subscribe response.
0x4033c44c	78.11011	WinRM cannot process the configuration request. The hostname pattern is invalid: "%1" Hostname patterns must contain one or more patterns. A pattern can contain at most one wildcard (""). The special pattern "" can be used to indicate all hostnames that do not have a '.'. To trust all hosts use "" as the only pattern.
0x4033c44d	78.11011	The WinRM client cannot process the request. The WinRM client received an 'access denied' error from the server and it tried to send again the message, but the configuration changed and the new settings did not allow the message to be re-sent. Try the request again with an authentication mechanism that is allowed by the updated configuration.
0x4033c44e	78.11011	The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: %1 %2 %3 %4 %5
0x4033c44f	78.11011	The WinRM client cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error. Specify one of the authentication mechanisms supported by the server. If Kerberos mechanism is used, verify that the client computer and the destination computer are joined to a domain. Possible authentication mechanisms reported by server: %3 %4 %5 %6 %7
0x4033c450	78.11011	The WinRM client cannot process the request. The WinRM client tried to use %1 authentication mechanism, but the destination computer (%2:%3!d!) returned an 'access denied' error. Change the configuration to allow %1 authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: %4 %5 %6 %7 %8
0x4033c451	78.11011	The WS-Management service cannot process the request. The WS-Eventing NotifyTo element might be missing from the WS-Eventing Delivery section or it might be invalid. It might be longer than the maximum length allowed.
0x4033c452	78.11011	The WS-Management service cannot process the request. The WS-Addressing Address element is missing from the WS-Eventing NotifyTo section.
0x4033c453	78.11011	The WS-Management service cannot process the request. The SOAP packet contains an WS-Addressing Address element in the WS-Eventing NotifyTo section that is either invalid, duplicated, or too long.
0x4033c454	78.11011	The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing expiration element that is either invalid, duplicated, not supported, or too long.
0x4033c455	78.11011	The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing locale element that is either invalid, duplicated, not supported, or too long.
0x4033c456	78.11011	The WS-Management service cannot process the request. The SOAP packet contains an WS-Management heartbeat element that is invalid.
0x4033c457	78.11011	The WS-Management service cannot process the request. This request is valid only when the -remote option is specified.
0x4033c458	78.11011	The WinRM client cannot process the request. API was called with no session.
0x4033c459	78.11011	Not used. To be removed.
0x4033c45a	78.11011	Not used. To be removed.
0x4033c45b	78.11011	The WS-Management service cannot process the configuration request. The XML contains a value longer than the maximum length of %1!d!
0x4033c45c	78.11011	WinRM cannot process the request. The requested locale '%1' contains an invalid language code.
0x4033c45d	78.11011	WinRM cannot process the request. The requested locale '%1' contains an invalid country code.
0x4033c45e	78.11011	The WS-Management service cannot process the request. The batch is smaller (%1!d! bytes) than the minimum size that is supported (%2!d! bytes).
0x4033c45f	78.11011	The WS-Management service cannot process the request. The WS-Eventing EndTo element is missing from the WS-Eventing Delivery section, or is invalid.
0x4033c460	78.11011	WinRM cannot process the configuration request. The service resource URI (%1) only supports the following actions: %2 and %3.
0x4033c461	78.11011	WinRM cannot process the configuration request. This action requires input XML with an element name of %1.
0x4033c462	78.11011	WinRM cannot process the configuration request. This action requires input XML with an element name of %1.
0x4033c463	78.11011	Create a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine.
0x4033c464	78.11011	Created a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine.
0x4033c465	78.11011	Could not create a WinRM listener on %1://%2.
0x4033c466	78.11011	Enable the WinRM listener on %1://%2.
0x4033c467	78.11011	Enabled the WinRM listener on %1://%2.
0x4033c468	78.11011	Could not enable the WinRM listener on %1://%2.
0x4033c469	78.11011	This resource requires the following selectors: %1 %2
0x4033c46a	78.11011	This resource requires no selectors.
0x4033c46b	78.11011	Start the WinRM service.
0x4033c46c	78.11011	Set the WinRM service type to delayed auto start.
0x4033c46d	78.11011	Set the WinRM service type to auto start.
0x4033c46e	78.11011	WinRM service started.
0x4033c46f	78.11011	Could not start the WinRM service: %1
0x4033c470	78.11011	WinRM service type changed successfully.
0x4033c471	78.11011	Could not change the WinRM service type: %1
0x4033c472	78.11011	The WinRM service cannot process the request. A configuration setting or group policy setting denies access to the resource URI (%1).
0x4033c473	78.11011	The action URI (%1) is invalid.
0x4033c474	78.11011	The following authentication mechanisms were specified in the request: %1 %2 %3 %4 %5 %6
0x4033c475	78.11011	Not used. To be removed.
0x4033c476	78.11011	The WS-Management service cannot process the request. The URI contains a invalid character (%1).
0x4033c477	8.11011	WinRM cannot process the request. The following error with errorcode 0x%1!x! occurred while using %2 authentication: %3 Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
0x4033c478	78.11011	Unable to check the status of the WinRM service.
0x4033c479	78.11011	Unable to check the status of the firewall.
0x4033c47a	78.11011	Enable the WinRM firewall exception.
0x4033c47b	78.11011
0x4033c47c	78.11011	Unable to enable the firewall for WinRM.
0x4033c47d	78.11011	Warning: The WinRM firewall exception could not be enabled for all active profiles.
0x4033c47e	78.11011	WinRM firewall exception enabled.
0x4033c47f	78.11011	The WinRM client received an HTTP status code of %1!d! from the remote WS-Management service.
0x4033c480	78.11011	The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element.
0x4033c481	78.11011	WinRM cannot process the configuration request. This action requires input XML containing an element name of %1 with value "http" or "https".
0x4033c482	78.11011	The Windows Remote Shell cannot process the request. The server is already executing the maximum number of concurrent shells an user can remotely open on the same system. Retry later.
0x4033c483	78.11011	The Windows Remote Shell cannot process the request. The server exceeded the maximum number of users concurrently performing remote operations on the same system. Retry later.
0x4033c484	78.11011	The Windows Remote Shell cannot process the request. The server attempted to apply the quota limits for the Remote Shell object, however the system determined that the limits were invalid. Please correct the configuration settings, the settings can be viewed using the following command "winrm get winrm/config/winrs".
0x4033c485	78.11011	The Windows Remote Shell received a request to perform an operation on a command identifier that does not exist. Either the command has completed execution or the client specified an invalid command identifier.
0x4033c486	78.11011	The Windows Remote Shell cannot process the request because it requires the following selector: %1. Retry with the correct selector.
0x4033c487	8.11011	The request for the Windows Remote Shell with ShellId %1 failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.
0x4033c488	78.11011	Only one rsp:Send can be outstanding per instance of the shell or command. Resend the rsp:Send request after a rsp:SendResponse is received.
0x4033c489	78.11011	Only one rsp:Receive can be outstanding per instance of the shell or command. Resend the rsp:Receive request after a rsp:ReceiveResponse is received.
0x4033c48a	78.11011	Only one rsp:Signal can be outstanding per instance of the shell or command. Resend the rsp:Signal request after a rsp:SignalResponse is received.
0x4033c48b	78.11011	The WS-Management service cannot process the request with a wsman:Locale different from that used in the initiating wxf:Create request. Resend the remote request without locale or with the same locale initially used by wxf:Create.
0x4033c48c	78.11011	The Windows Remote Shell cannot process the request. It is not permitted for other users then the initial creator to make use of a running shell instance, even if they have permissions to create shells themselves with the same or even greater privileges. The administrator can enumerate all running shell instances, also get and delete a running shell instance.
0x4033c48d	78.11011	The Windows Remote Shell cannot process the request. The resource URI is not valid or the service cannot find the resource identified by the resource URI and selectors. The wsman:ResourceURI value should be %1 or be defined in the CustomRemoteShell table. Check the documentation or use the following command for information on how to populate CustomRemoteShell table: "winrm help customremoteshell". The selectors are relative to the resource URI. Retry the request with the correct resource URI or selectors.
0x4033c48e	78.11011	The Windows Remote Shell cannot process the request. The command id returned from the shell plugin is empty.
0x4033c48f	78.11011	The Windows Remote Shell cannot process the request. The WS-Addressing action URI is invalid. The valid actions are Command, Receive, Send and Signal. Check the Windows Remote Shell documentation for information on how to construct an action URI.
0x4033c490	78.11011	The Windows Remote Shell cannot process the request. The SequenceId element is empty or invalid.
0x4033c491	78.11011	The Windows Remote Shell cannot process the request. The computed response packet size exceeds the maximum envelope size that is allowed.
0x4033c492	78.11011	The WS-Management service cannot process the fragment filter because the specified XPath filter is not supported. Try simplifying the path and try again.
0x4033c493	78.11011	The Windows Remote Shell cannot process the request. The SOAP packet contains an element %1 that is invalid. Retry the request with the correct XML element.
0x4033c494	78.11011	The WinRM client cannot process the request. The following setting is read-only and cannot be modified: %1. Remove this setting from the command and try again.
0x4033c495	78.11011	Subscription Manager plugin for Windows Remote Management
0x4033c496	78.11011	The WS-Management service cannot process the request. The SOAP packet contains a MachineID element that was either invalid, duplicated, or too long.
0x4033c497	78.11011	The WS-Management service configuration contains ambiguous entries in the URI security table: more than one pattern matches the following resource URI: %1. Authorization process cannot continue. Fix the entries in the URI security table and try the request again.
0x4033c498	78.11011	Windows Remote Management
0x4033c499	78.11011	Full Control(All Operations)
0x4033c49a	78.11011	Read(Get,Enumerate,Subscribe)
0x4033c49b	78.11011	Write(Put,Delete,Create)
0x4033c49c	78.11011	Execute(Invoke)
0x4033c49d	78.11011	Only one Command can be outstanding per instance of the shell. You must terminate the command using Signal as the last message in all cases, whether the command is terminated early or run to completion. Resend the Command request after a SignalResponse is received.
0x4033c49e	78.11011	The filter contains a property (%1) that does not exist in the class.
0x4033c49f	78.11011	The filter contains a property (%1) that is of an unsupported type. Filtering is not supported on properties with the following types: datetime, reference, object, and array.
0x4033c4a0	78.11011	The resource URI (%1) does not support unfiltered enumeration. One of the following filter dialects is required: %2.
0x4033c4a1	78.11011	It is not allowed to change the value of the Issuer,Subject or the URI for a configured certmapping entry.
0x4033c4a2	78.11011	This resource requires the following selectors: %1 %2 %3
0x4033c4a3	78.11011	This resource requires the following selector: %1
0x4033c4a4	78.11011	The following selector is not a key property of the resource accessed : %1. Use selectors that are key properties for the resource that you want to access.
0x4033c4a5	78.11011	WinRM cannot process the request because the input XML contains an invalid XML header.
0x4033c4a6	78.11011	WinRM cannot process the request because the input XML contains a mismatched element. The ending name does not match the starting name.
0x4033c4a7	78.11011	WinRM cannot process the request because the input XML contains an invalid attribute or element name.
0x4033c4a8	78.11011	WinRM cannot process the request because the input XML contains an invalid attribute.
0x4033c4a9	78.11011	WinRM cannot process the request because the input XML contains a syntax error.
0x4033c4aa	78.11011	WinRM cannot process the request because the input XML contains too many nested levels of elements.
0x4033c4ab	78.11011	WinRM cannot process the request because an XML element has content or child elements but is marked as NULL with the xsi:nil attribute.
0x4033c4ac	78.11011	WinRM cannot process the request because a boolean attribute contains an invalid boolean value.
0x4033c4ad	78.11011	The WinRM client cannot process the request. The batch items must be at least: %1!d!
0x4033c4ae	78.11011	The WinRM client cannot process the request. The max characters must be at least: %1!d!
0x4033c4af	78.11011	The resource URI (%1) supports unfiltered enumeration and the following filter dialects: %2.
0x4033c4b0	8.11011	Invalid session option %1; The specified value %2!lu! is below the minimum required value of %3!lu!.
0x4033c4b1	78.11011	Invalid session option %1; the value is too large: %2!lu!. The value must be %3!lu! or less.
0x4033c4b2	78.11011	Invalid session option %1; the type of the option is not valid.
0x4033c4b3	78.11011	This resource requires the following selector: %1
0x4033c4b4	78.11011	The configuration XML is not valid. The configuration XML contains an unexpected XML element: "%1" while element: "%2%" is expected at this point. Ensure that the elements are in correct sequence and that the spelling of the element name is correct.
0x4033c4b5	78.11011	The configuration XML is not valid. The configuration XML contains an invalid XML element: "%1". Ensure that the elements are in correct sequence and that the spelling of the element name is correct.
0x4033c4b6	78.11011	The configuration XML is not valid. The namespace for XML element: "%1" is not correct.
0x4033c4b7	78.11011	The configuration XML is not valid. Too many instances of XML element: "%1" found.
0x4033c4b8	78.11011	The configuration XML is not valid. The XML element: "%1" is expected but not found.
0x4033c4b9	78.11011	The configuration XML is not valid. Text for XML element: "%1" is not expected.
0x4033c4ba	78.11011	The configuration XML is not valid. Either attribute: "%1" is not expected for element: "%2" or its namespace is invalid.
0x4033c4bb	78.11011	The configuration XML is not valid. Attribute: "%1" is repeated for element: "%2".
0x4033c4bc	78.11011	The configuration XML is not valid. Attribute: "%1" is required for element: "%2".
0x4033c4bd	8.11011	The configuration XML is not valid. The configuration value length for attribute %1 exceeded the maximum limit of 10240 characters.
0x4033c4be	78.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid integer. Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length.
0x4033c4bf	78.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid boolean. Valid boolean values are "true" and "false".
0x4033c4c0	8.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid capability type. Valid capability types are "Identify", "Get", "Put", "Create", "Delete", "Invoke", "Enumerate", "Subscribe" and "Shell".
0x4033c4c1	8.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid plugin name. Plugin name cannot be empty and cannot exceeded 255 characters. Plugin name should not have any preceding space or tab characters. The plugin name should not contain backslash and double quote characters.
0x4033c4c2	78.11011	The configuration XML is not valid. SDK Version: "%1" is currently not supported.
0x4033c4c3	78.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid xml rendering type. Valid xml rendering types are "text" and "XmlReader".
0x4033c4c4	78.11011	The configuration XML is not valid. Resource Uri: "%1" is registered more than once in the plugin configuration.
0x4033c4c5	78.11011	The configuration XML is not valid. Resource Uri: "%1" is not valid. Plugin resource Uris cannot have WSMan configuration root uri as a prefix.
0x4033c4c6	78.11011	The configuration XML is not valid. Resource Uri: "%1" cannot be exposed by more than one plugin.
0x4033c4c7	78.11011	The configuration XML is not valid. Capability: "%1" is defined multiple times for resource uri: "%2".
0x4033c4c8	78.11011	The configuration XML is not valid. Fragments are not supported for capability: "%1".
0x4033c4c9	78.11011	The configuration XML is not valid. Filters are not supported for capability: "%1".
0x4033c4ca	78.11011	The configuration XML is not valid. Resource uri: %1 cannot simultaneously support shell capability with other capabilities.
0x4033c4cb	78.11011	The configuration XML is not valid. Value of attribute "name" does not match the given selector.
0x4033c4cc	78.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid file path. Valid file path should be absolute, reside in the system32 directory and should point to an existing file.
0x4033c4cd	78.11011	The WS-Management service cannot process the request. Configuration for plugin: "%1" is corrupted. This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration winrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz Or use the following command to restore default plugin configuration. Note that all external plugins will be unregistered during this restore operation. winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{}
0x4033c4ce	78.11011	The WS-Management service cannot process the request. The selector for plugin configuration cannot exceed 255 characters.
0x4033c4cf	78.11011	The WS-Management service cannot perform the configuration operation. A plugin configuration with plugin name=%1 already exists. You have to delete the existing plugin configuration first in order to be able to create it with the same plugin name.
0x4033c4d0	8.11011	An error occurred while reading the IIS configuration. File: %1 Line: %2 Issue: %3
0x4033c4d1	78.11011	The WSMan client cannot process the request. The authentication mechanism requested by the proxy is not supported by the client. The only proxy authentication mechanisms supported are Negotiate, Basic or Digest. Possible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5
0x4033c4d2	78.11011	The WSMan client received a redirect status from the server, but the server did not give the actual redirect location to use.
0x4033c4d3	78.11011	Configure CertificateThumbprint setting for the service, to be used for CredSSP authentication.
0x4033c4d4	78.11011	Configured CertificateThumbprint setting for the service.
0x4033c4d5	78.11011	Could not configure CertificateThumbprint setting for the service.
0x4033c4d6	78.11011	The WS-Management service cannot process the request. This user is allowed a maximum number of %1!d! concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user.
0x4033c4d7	78.11011	The WS-Management service cannot process the request. This user is allowed a maximum number of %1!d! concurrent operations, which has been exceeded. Close existing operations for this user, or raise the quota for this user.
0x4033c4d8	78.11011	The WS-Management service cannot process the request. The user load quota of %1!d! requests per %2!d! seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least %3!d! milliseconds.
0x4033c4d9	78.11011	The WS-Management service cannot process the request. The system load quota of %1!d! requests per %2!d! seconds has been exceeded. Send future requests at a slower rate or raise the system quota. The next request from this user will not be approved for at least %3!d! milliseconds.
0x4033c4da	78.11011	The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered.
0x4033c4db	78.11011	The WSMan provider host process did not return a proper response. A provider in the host process may have behaved improperly.
0x4033c4dc	78.11011	The configuration XML is not valid. Initialization xml attribute values for "Name" and "Value" cannot be empty.
0x4033c4dd	78.11011	Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.
0x4033c4de	78.11011	Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.
0x4033c4df	78.11011	Could not configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.
0x4033c4e0	78.11011	The authorization plugin returned the following error: %1.
0x4033c4e1	78.11011	The WS-Management service cannot process the request. This service is configured to allow a maximum of %1!d! concurrent shell users, which has been exceeded. Retry your request after sometime or raise the quota for concurrent shell users.
0x4033c4e2	78.11011	The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-Management ActivityId element. The element is duplicated or is not in the correct format. The ActivityId should be a 128 bit value in the UUID format specified as a string.
0x4033c4e3	78.11011	The WS-Management service cannot guarantee that the ActivityId will be used as the tracing is turned OFF by default. Resend the remote request with ActivityId as a hint (the SOAP header should have mustUnderstand="false").
0x4033c4e4	78.11011	The WS-Management service cannot process the request. The configuration setting "%1" is deprecated and cannot be changed. Remove this setting and try again.
0x4033c4e5	78.11011	The configuration XML is not valid. Attribute value: "%1" is not a valid architecture type. Valid architecture types are "32" on a 32-bit system; "32" and "64" on a 64-bit system.
0x4033c4e6	78.11011	The WSMan client cannot process the request. Proxy is not supported under HTTP transport. Change the transport to HTTPS and specify valid proxy information and try again.
0x4033c4e7	78.11011	The WSMan client cannot process the request. Proxy is not supported when the authentication mechanism with the server is Kerberos or CredSSP. Change the authentication mechanism to Negotiate or Digest or Basic and try again.
0x4033c4e8	78.11011	The configuration XML is not valid. Resource Uri: "%1" is not valid. The Resource URI does not conform to RFC 3986. Change the Resource URI in the configuration XML and try again.
0x4033c4e9	78.11011	The WS-Management service cannot process the request. The SOAP packet did not contain a valid remote shell CompressionType element. The element is duplicated, is not marked as must understand or is not in the correct format. The only supported compression type is "xpress".
0x4033c4ea	78.11011	The configuration XML is not valid. Resource Uri: "%1" is reserved for the WSMan shell manager.
0x4033c4eb	78.11011	The configuration XML is not valid. The provider "%1" supports the %2 method but it could not be loaded. Verify that the provider exports the %2 method properly.
0x4033c4ec	78.11011	Windows Remote Management - Compatibility Mode (HTTP-In)
0x4033c4ed	8.11011	Configure "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.
0x4033c4ee	8.11011	Configured "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.
0x4033c4ef	8.11011	Could not configure "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.
0x4033c4f0	8.11011	The WS-Management service cannot process the request because the SOAP packet does not contain a valid SessionID element. Verify that the SessionID element is not a duplicate or GUID and retry the operation.
0x4033c4f1	8.11011	The WinRM service cannot process the request because the WinRS shell instance is already processing a connect operation.
0x4033c4f2	8.11011	The configuration XML is not valid. The value for the attribute "%1" must be between %2 and %3.
0x4033c4f3	8.11011	The configuration XML is not valid. The attribute "%1" can be specified only if the attribute "%2" is also specified.
0x4033c4f4	8.11011	The configuration XML is not valid. The attribute "%1" can be non-zero only if the attribute "%2" is set to true.
0x4033c4f5	8.11011	The configuration XML is not valid. The attribute "%1" can be specified only if the attribute "%2" is set to true, the attribute "%3" is specified, and the attribute "%4" is at least %5.
0x4033c4f6	8.11011	The configuration XML is not valid. The attribute "%1" must be specified to change the attribute "%2".
0x4033c4f7	8.11011	The configuration XML is not valid. The plugin "%1" is a default plugin and its attributes cannot be modified.
0x4033c4f8	8.11011	An error %1!d! was encountered while subscribing to a Group Policy change notification.
0x4033c4f9	8.11011	The configuration XML is not valid. A plugin cannot simultaneously support the shell capability with other capabilities.
0x4033c4fa	8.11011	The configuration XML is not valid. The quota %1 is not valid for this plugin.
0x4033c4fb	8.11011	The configuration XML is not valid. The attribute value "%1" must be changed to a valid Server Buffering Mode value of either "%2"or "%3".
0x4033c4fc	8.11011	The WS-Management service cannot process the request. This user has exceeded the maximum number of %1!d! concurrent shells for plugin "%2". Close the existing shells or raise the plugin quota for this user.
0x4033c4fd	8.11011	The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent users allowed for plugin "%2". Retry the request later or raise the quota for concurrent users.
0x4033c4fe	8.11011	The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent shells allowed for plugin "%2". Retry the request later or raise the Maximum Shells per Plugin quota.
0x4033c4ff	8.11011	The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations allowed for plugin "%2". Retry the request later or raise the Maximum Shells per Plugin quota.
0x4033c500	8.11011	The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations per user allowed for plugin "%2". Retry the request later or raise the Maximum Operations per User quota.
0x4033c501	8.11011	The WS-Management service cannot process the command. This service has exceeded its maximum of %1!d! concurrent commands per shell allowed for plugin "%2". Retry the request later or raise the Maximum Commands per Shell quota.
0x4033c502	8.11011	The WS-Management service cannot process the command. The service does not have minimum required resources to start a new operation for the plugin "%1". Try the request later or lower the minimum requirement for the plugin.
0x4033c503	8.11011	The WS-Management service cannot process the request. The WS-Management service cannot accept subscriptions to an indication class, when either the filter or the dialect is specified. Retry with filter removed.
0x4033c504	8.11011	The verification of the runAs user credentials failed with the error %1!d!.
0x4033c505	8.11011	The WS-Management service cannot process the request. The CIM namespace %1 is invalid.
0x4033c506	8.11011	The WS-Management service cannot process the request. The class %1 does not exist in the %2 namespace.
0x4033c507	8.11011	Configure service to allow remote requests.
0x4033c508	8.11011	Configure service to allow authenticating requests using Kerberos protocol.
0x4033c509	8.11011	Configure service to allow authenticating requests using Negotiate protocol.
0x4033c50a	8.11011	Could not configure one or more configuration settings for the service.
0x4033c50b	8.11011	Configured required settings for the service.
0x4033c50c	8.11011	Modify the GP setting "Allow remote server management through WinRM" to either "Not Configured" or "Enabled".
0x4033c50d	8.11011	Modify the GP setting "Disallow Kerberos authentication" to either "Not Configured" or "Disabled".
0x4033c50e	8.11011	Modify the GP setting "Disallow Negotiate authentication" to either "Not Configured" or "Disabled".
0x4033c50f	8.11011	Modify the GP setting "Allow remote server management through WinRM" to either "Not Configured" or "Disabled".
0x4033c510	8.11011	The WinRM client cannot process the request because the XML contains an unsupported type (%1).
0x4033c511	8.11011	The WS-Management service cannot process the request because no CIM namespace was specified. Choose a valid CIM namespace and try again.
0x4033c512	8.11011	Enabled remote access.
0x4033c513	8.11011	Unable to enable remote access.
0x4033c514	8.11011	Disabled remote access.
0x4033c515	8.11011	Unable to disable remote access.
0x4033c516	8.11011	The WinRM client cannot process the request. "AllowRemoteAccess" setting is read-only and cannot be modified. Use the following commands instead to change the remote access behavior: winrm invoke EnableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service winrm invoke DisableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service
0x4033c517	8.11011	The WS-Management service cannot process the configuration request. The service resource URI %1 only supports the following actions: %2, %3 and %4.
0x4033c518	8.11011	The WS-Management service cannot process the configuration request. The configuration resource URI %1 only supports the following action: %2.
0x4033c519	8.11011	WinRM cannot process the request. The following error occurred while using %1 authentication: Cannot find the computer %2. Verify that the computer exists on the network and that the name provided is spelled correctly.
0x4033c51a	8.11011	The WS-Management service cannot process the request. There was no matching certificate mapping found for the requested resource URI.
0x4033c51b	8.11011	The WS-Management service cannot process the request. Retry requests are not supported.
0x4033c51c	8.11011	The WS-Management service cannot process the request. Operations involving multiple messages from the client are not supported.
0x4033c51d	8.11011	The WS-Management service cannot process the request. The configuration XML is not valid. The value for Quota %1 cannot be less than value for %2.
0x4033c51e	8.11011	WinRM cannot process the request. The following error with error code 0x%1!x! occurred while using Negotiate authentication: %2 This can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified. If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request. Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated. For more information about how to edit the TrustedHosts list, run the following command: winrm help config.
0x4033c51f	8.11011	Unable to enable remote access because of the following reason: %1.
0x4033c520	8.11011	The WS-Management service cannot process the request. The requested IdleTimeout of %1!d! is outside the allowed range. Specify an IdleTimeout value between %2!d! and %3!d!, and retry the operation.
0x4033c521	8.11011	WinRM cannot process the request. The following error occurred while using Kerberos authentication: The computer %1 is unknown to Kerberos. Verify that the computer exists on the network, that the name provided is spelled correctly, and that the Kerberos configuration for accessing the computer is correct. The most common Kerberos configuration issue is that an SPN with the format HTTP/%1 is not configured for the target. If Kerberos is not required, specify the Negotiate authentication mechanism and resubmit the operation.
0x4033c522	8.11011	The WinRM client cannot process the request. Property "%1" with MI type %2 does not match the expected type from the schema: %3. Specify the correct type and retry the operation.
0x4033c523	8.11011	The metadata failed to be retrieved from the server, due to the following error: %1
0x4033c524	8.11011	The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x%1!x!
0x4033c525	8.11011	The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing Encoding element that is either not valid, duplicated, not supported, or too long.
0x4033c526	8.11011	The WS-Management service cannot process the request. The object contains an unrecognized property: "%1". Verify that the spelling of the property name is correct.
0x4033c527	8.11011	The WinRM client cannot process the request. The object contains an unrecognized property: "%1". Verify that the spelling of the property name is correct.
0x4033c528	8.11011	The WS-Management service cannot process the request. The object contains an unrecognized argument: "%1". Verify that the spelling of the argument name is correct.
0x4033c529	8.11011	The WinRM client cannot process the request. The object contains an unrecognized argument: "%1". Verify that the spelling of the argument name is correct.
0x4033c52a	8.11011	The WS-Management service cannot process the request. The method name "%1" is not valid. Verify that the spelling of the method name is correct.
0x4033c52b	8.11011	The WinRM client cannot process the request. The method name "%1" is not valid. Verify that the spelling of the method name is correct.
0x4033c52c	8.11011	%1 The network connection to %2 has been interrupted. Attempting to reconnect for up to %3!d! minutes...
0x4033c52d	8.11011	%1 Attempting to reconnect to %2 ...
0x4033c52e	8.11011	%1 The network connection to %2 has been restored.
0x4033c52f	8.11011	%1 The reconnection attempt to %2 failed.
0x4033c530	8.11011	%1 The reconnection attempt to %2 failed while trying to retrieve the CIM schema needed for the operation.
0x4033c531	8.11011	The WS-Management service cannot process the request. You must be an administrator in order to access the WinRS shell instance.
0x4033c532	8.11011	The WS-Management service cannot process the request. The WinRS shell instance is not accessible over a remote connection.
0x4033c533	1011	Unable to look up SID of group: "%1". Ensure that the group is valid.
0x4033c534	1011	Username specified looks like a Manged Service Account. Passwords to such accounts are managed and should not be specified.
0x4033c535	1011	The verification of the Managed Service Account failed with error %1!d!. Ensure that the account is valid.
0x50000002	78.11011	Error
0x50000003	8.11011	Warning
0x50000004	78.11011	Information
0x70000001	78.11011	WSMan API Initialize
0x70000002	78.11011	WSMan API Deinitialize
0x70000003	78.11011	WSMan Session initialize
0x70000004	78.11011	WSMan Session deinitialize
0x70000005	78.11011	WSMan API call
0x70000006	78.11011	Auto-detecting proxy settings
0x70000007	78.11011	User authentication
0x70000008	78.11011	User authorization
0x70000009	78.11011	Request handling
0x7000000a	78.11011	Response handling
0x7000000b	78.11011	Winrm service start/stop
0x7000000c	78.11011	Winrm configuration
0x7000000d	78.11011	Winrm Operation
0x7000000e	8.11011	WinRM MI Protocol Handler
0x7000000f	8.11011	WinRM MI Session
0x70000010	8.11011	WinRM MI Operation
0x70000011	8.11011	Winrm Verbose Message
0x80338000	78.11011	The WS-Management service cannot process the request. The service cannot find the resource identified by the resource URI and selectors.
0x80338001	78.11011	The WS-Management service cannot process the request. The WS-Addressing action URI is invalid. Check the documentation for information on how to construct an action URI.
0x80338002	78.11011	The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format. Check the documentation or use the following command for information on how to construct a resource URI: "winrm help uris".
0x80338003	78.11011	An error was encountered inside the plugin.
0x80338004	78.11011	The WS-Management service cannot complete the request. The WSManEnumerator object is full and no more items can be added.
0x80338005	78.11011	The WS-Management configuration is corrupted. Use the following command to restore defaults: winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{} Then add any custom configuration settings.
0x80338006	78.11011	The WS-Management service cannot process a pull request because a pull operation is already in progress.
0x80338007	78.11011	The WS-Management enumeration session is finished or cancelled and cannot be used. Start a new enumeration.
0x80338008	78.11011	The event subscription is already closed and cannot be used. Start a new subscription.
0x80338009	78.11011	The event subscription session is closing and cannot be used. Start a new subscription.
0x8033800a	78.11011	The application or script that has an event subscription did not request a pull operation within the heartbeat interval. The subscription session was closed. Start a new subscription.
0x8033800b	78.11011	The event source did not return events within the heartbeat interval. The subscription session was closed. Start a new subscription.
0x8033800c	78.11011	The WS-Management service does not support the specified timeout. The value specified is smaller than the minimum allowed value for this setting. Change the timeout value and try the request again.
0x8033800d	78.11011	The WS-Management service does not support the SOAP version specified in the request.
0x8033800e	78.11011	The WS-Management service does not support the encoding specified in the request.
0x8033800f	78.11011	The WS-Management service cannot process the request. The request contains one or more invalid SOAP headers.
0x80338010	78.11011	The WS-Management service cannot process a SOAP header in the request that is marked as mustUnderstand by the client. This could be caused by the use of a version of the protocol which is not supported, or may be an incompatibility between the client and server implementations.
0x80338011	78.11011	The WS-Management service cannot process the request. The request does not have all the expected SOAP headers.
0x80338012	78.11011	The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
0x80338013	78.11011	The WS-Management service does not support the action specified in the request.
0x80338014	78.11011	The WS-Management service cannot process the request because the resource is offline. Retry the request later when the resource is online.
0x80338015	78.11011	The WS-Management service cannot identify the format of the object passed to a Put or Create method. The input XML may not be appropriate for the resource or uses the wrong schema for the resource. Change the input XML in the request.
0x80338016	78.11011	The expiration time passed to the WS-Management Enumerate method is not valid. The time value may be zero or refer to a time in the past. Change the expiration time and try the request again.
0x80338017	78.11011	The data source does not support expiration time. Remove the expiration time from the request and try the request again.
0x80338018	78.11011	The data source does not support filtering. Remove the filter from the request and try the request again.
0x80338019	78.11011	The filter dialect (the type associated with the filter) was not supported for this resource. Change the filter dialect or remove it from the request and try the request again.
0x8033801a	78.11011	The data source could not process the filter. The filter might be missing or it might be invalid. Change the filter and try the request again.
0x8033801b	78.11011	The WS-Enumeration context in the enumeration is not valid. Enumeration may have been completed or canceled. You cannot use this enumeration context anymore. Start a new enumeration.
0x8033801c	78.11011	The pull operation did not get any data in the MaxTime duration. But the enumeration is still valid. The client can attempt to do another pull request to retrieve data.
0x8033801d	78.11011	The WS-Management service cannot renew the enumeration. Start a new enumeration.
0x8033801e	78.11011	The WS-Management service does not support the delivery mode for the specified resource. The client should change the subscription to use one of the supported delivery modes.
0x8033801f	78.11011	The expiration time of the subscription is invalid. The time is either not supported, zero or a time that happened in the past. Change the expiration time and try the request again.
0x80338020	78.11011	The expiration time specified for subscription was invalid. Specify the expiration time as a duration.
0x80338021	78.11011	The event source does not support filtering. Remove the filter from the request and try the request again.
0x80338022	78.11011	The event source cannot process the specified filter. Change the filter or remove it from the request and try the request again.
0x80338023	78.11011	The event source cannot process the subscription.
0x80338024	78.11011	The WS-Management service cannot renew the event subscription. Create a new subscription.
0x80338025	78.11011	The WS-Management service cannot complete the WS-Eventing request because the request had some unknown or invalid content and could not be processed.
0x80338026	78.11011	The WS-Management service cannot process the response because it is larger than the maximum size allowed.
0x80338027	78.11011	The WS-Management service cannot process the request because the request packet does not have a valid SOAP body.
0x80338028	78.11011	The resumption context specified in the subscription is invalid. It may have expired, or be in the wrong format.
0x80338029	78.11011	The WS-Management service cannot complete the operation within the time specified in OperationTimeout.
0x8033802a	78.11011	The event source does not support subscriptions that can be resumed.
0x8033802b	78.11011	The WS-Management service does not support the type of resumption requested by the subscription.
0x8033802c	78.11011	The request contains character encoding that is unsupported. WS-Management only supports requests that are encoded in UTF-8 or UTF-16. Change the character encoding in the request and try the request again.
0x8033802d	78.11011	The URI is longer than the maximum length allowed.
0x8033802e	78.11011	The WS-Management service cannot process the request because the subscription ID is invalid.
0x8033802f	78.11011	The WS-Management service cannot process the batch request. The request must specify either MaxItems, MaxCharacters, or MaxTime.
0x80338030	78.11011	The receiver of the event did not acknowledge the event delivery. Submit the subscription again without the acknowledgement option.
0x80338031	78.11011	The WS-Management service cannot process the request because the WS-Addressing Action URI in the request is not compatible with the resource.
0x80338032	78.11011	The WS-Management service cannot complete the WS-Addressing Action URI in the request because the resource was already in use.
0x80338033	78.11011	The WS-Management service cannot create the resource because it already exists.
0x80338034	78.11011	The WS-Management service cannot complete the request because the receiver does not accept the delivery of events. The receiver requests that the subscription be cancelled. Event receivers return this message to force the cancellation of a subscription.
0x80338035	78.11011	The WS-Management service cannot process the request because the encoding of the request exceeds an internal encoding limit. Reconfigure the client to send messages which fit the encoding limits of the service.
0x80338036	78.11011	The WS-Management service cannot authenticate the sender.
0x80338037	78.11011	The WS-Management service does not support the format of the WS-Addressing Endpoint Reference.
0x80338038	78.11011	The bookmark in the subscription is invalid. The bookmark may be expired or corrupted. Issue a new subscription without any bookmarks or locate the correct bookmark.
0x80338039	78.11011	The WS-Management service cannot process the request because one or more options are not valid. The option names or values may not be valid or they are used in incorrect combinations. Retrieve the catalog entry for the resource and determine how to correct the invalid option values.
0x8033803a	78.11011	The WS-Management service cannot process the request because a parameter for the operation is not valid.
0x8033803b	78.11011	The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format. Check the documentation or use the following command for information on how to construct a resource URI: "winrm help uris".
0x8033803c	78.11011	The WS-Management service requires a valid System URI to process the request.
0x8033803d	78.11011	The WS-Management service cannot process the request because the selectors for the resource are not valid.
0x8033803e	8.11011	The requested metadata is not available at the current address. Retry the request with a new address.
0x8033803f	78.11011	The WS-Management service is busy servicing other requests. Retry later.
0x80338040	78.11011	The WS-Management service cannot rename the resource. The selectors for the resource are not correct. The resource may exist already, the address may be incorrect, or the resource URI may be invalid. Change the request and retry.
0x80338041	78.11011	The SOAP XML in the message does not match the corresponding XML schema definition. Change the XML and retry.
0x80338042	78.11011	The WS-Management service does not support the specified feature. Remove the unsupported feature from the request and retry.
0x80338043	78.11011	The WS-Management service cannot process the request because the XML is invalid.
0x80338044	78.11011	The WS-Management service cannot process the request because the URI contains an unexpected selector.
0x80338045	78.11011	The event source is attempting to deliver an event when a delivery is in progress already.
0x80338046	78.11011	The WS-Management service cannot locate the system.
0x80338047	78.11011	The maximum envelope size in the request is too large. Change the maximum envelope size and try the request again.
0x80338048	78.11011	The response that the WS-Management service computed exceeds the maximum envelope size in the request.
0x80338049	78.11011	The response that the WS-Management service computed exceed the internal limit for envelope size.
0x8033804a	78.11011	The WS-Management service cannot process the request because the URI contains too many selectors.
0x8033804b	78.11011	The WS-Management service cannot process the request because it contains too many options.
0x8033804c	78.11011	The WS-Management service does not support the character set used in the request. Change the request to use UTF-8 or UTF-16.
0x8033804d	78.11011	The operation succeeded and cannot be reversed but the result is too large to send.
0x8033804e	78.11011	The WS-Management service does not support white space in the request XML.
0x8033804f	78.11011	The WS-Management service does not support the filter dialect in the request. The filter dialect is the type of filter, such as XPath or WQL.
0x80338050	78.11011	The WS-Management service cannot process the request because it contains a bookmark that is expired.
0x80338051	8.11011	The WS-Management provider does not support the specified option set because mustComply for one of the options is set to true. Change mustComply for one of the options to false.
0x80338052	78.11011	The WS-Management service cannot process the request because one or more of the options has an invalid name.
0x80338053	78.11011	The WS-Management service cannot process the request because one or more of the options has an invalid value.
0x80338054	78.11011	The WS-Management service cannot process the request. A parameter that is required for the operation is not the correct type.
0x80338055	78.11011	The WS-Management service cannot process the request. A parameter name is invalid.
0x80338056	78.11011	The WS-Management service cannot process the request because the XML content has invalid values.
0x80338057	78.11011	The WS-Management service cannot process the request because the XML content has missing values.
0x80338058	78.11011	The WS-Management service cannot identify the format of the object passed to a Put or Create method. The XML namespace for the input XML is invalid. Change the XML namespace for the input XML in the request.
0x80338059	78.11011	The WS-Management service cannot process the request because an XML fragment in the URI is invalid.
0x8033805a	78.11011	The WS-Management service cannot process the request because the request did not contain all required selectors.
0x8033805b	78.11011	The WS-Management service cannot process the request because the request contained invalid selectors for the resource.
0x8033805c	78.11011	The WS-Management service cannot process the request because a value for a selector is of the wrong type.
0x8033805d	78.11011	The WS-Management service cannot process the request because a value for the selector is invalid.
0x8033805e	78.11011	The WS-Management service cannot process the request because the selectors for the resource are ambiguous.
0x8033805f	78.11011	The WS-Management service cannot process the request because the request contains duplicate selectors.
0x80338060	78.11011	The WS-Management service cannot process the request because the request contains invalid selectors for the target resource.
0x80338061	78.11011	The WS-Management service cannot process the request because the request contains an invalid URI for the target resource.
0x80338062	78.11011	The WS-Management service cannot process the request because the request contains an invalid target system.
0x80338063	78.11011	The WS-Management service cannot process a Create request because the target already exists.
0x80338064	78.11011	The WS-Management service does not support the mode of authorization.
0x80338065	78.11011	The client does not support acknowledgment.
0x80338066	78.11011	The data source does not support timeouts for the operation.
0x80338067	78.11011	The WS-Management service does not support the locale.
0x80338068	78.11011	The WS-Management service does not support the expiration time.
0x80338069	78.11011	The WS-Management service does not retry deliveries.
0x8033806a	78.11011	The event source does not support heartbeats.
0x8033806b	78.11011	The event source does not support bookmarks.
0x8033806c	78.11011	The WS-Management service does not support the configuration for MaxItems.
0x8033806d	78.11011	The WS-Management service does not support the configuration for MaxTime.
0x8033806e	78.11011	The WS-Management service does not support the value in the configuration for MaxEnvelopeSize.
0x8033806f	78.11011	The event source does not support the MaxEnvelopePolicy.
0x80338070	78.11011	The WS-Management service does not support unfiltered enumeration.
0x80338071	78.11011	The WS-Management service does not support insecure addresses.
0x80338072	78.11011	The WS-Management service does not support format mismatch.
0x80338073	78.11011	The WS-Management service does not support the format of the security token.
0x80338074	78.11011	The service returned a response that indicates that the method is unsupported.
0x80338075	78.11011	The WS-Management service does not support the specified media type.
0x80338076	78.11011	The WS-Management service does not support the addressing mode.
0x80338077	78.11011	The WS-Management service does not support fragment transfer.
0x80338078	78.11011	The client sent a request before the enumeration was initialized.
0x80338079	78.11011	The WS-Management service failed to locate the component that can process the request.
0x8033807a	78.11011	A syntax error occurred in the query string for the resource URI.
0x8033807b	78.11011	The MAC that is configured is not in the list of enabled DHCP adapters on the computer.
0x8033807c	78.11011	The MAC address that is configured does not have any unicast addresses.
0x8033807d	78.11011	The WS-Management service cannot find the dynamic IP address on the adapter with the configured MAC address.
0x8033807e	78.11011	The WS-Management service cannot process the request because the envelope size in the request is too small.
0x8033807f	78.11011	The WS-Management service cannot process the request. The EndPointReference contains more nested EndPointReferences than WS-Management supports.
0x80338080	78.11011	The WS-Management service cannot initialize the request.
0x80338081	78.11011	The WS-Management service cannot process the request because the timeout header in the request is invalid.
0x80338082	78.11011	The WS-Management service cannot find the certificate that was requested.
0x80338083	78.11011	The WS-Management service cannot process the request. The data source failed to return results for the request.
0x80338084	78.11011	The enumeration is invalid because previous Pull request failed.
0x80338085	78.11011	The WS-Management service cannot change a mutual configuration.
0x80338086	78.11011	The WS-Management service does not support the specified enumeration mode.
0x80338087	78.11011	The WS-Management service cannot guarantee that all data is returned in the requested locale as some data sources may not be able to comply. Resend the remote request with locale as a hint (the SOAP header should have mustUnderstand="false")
0x80338088	78.11011	The WSMan group policy configuration is corrupted.
0x80338089	78.11011	The listener address specified is invalid. The address can be specified in one of the following formats: *, IP:, MAC:. Change the listener address and try the request again.
0x8033808a	78.11011	Cannot change GPO controlled setting.
0x8033808b	78.11011	The client is attempting to concurrently receive events from a single subscription session.This is not supported.
0x8033808c	78.11011	The source is sending event batches faster than the subscriber can consume. This can happen if acknowledgments are not specified for the subscription and new events are arriving from the source before the client has consumed them.
0x8033808d	78.11011	The source is sending events in a connection that did not match the security restrictions imposed by the client.
0x8033808e	1011	The WS-Management client cannot process the request. The event source identity does not match the identity of the machine that the client subscribed to.
0x8033808f	78.11011	The client could not start a valid listener to receive subscription events based on the specified input settings.
0x80338090	78.11011	The fragment path dialect is not supported for this resource.
0x80338091	78.11011	Cannot execute the Fragment-Level operation. The fragment path cannot be missing if the fragment dialect is specified.
0x80338092	78.11011	Cannot execute the Fragment-Level operation because of invalid value for the fragment dialect.
0x80338093	78.11011	Cannot execute the Fragment-Level operation because the fragment path is invalid. Check the syntax of the fragment path string. Also check the spelling and the case of the property names in the fragment path string: they have to match the spelling and the case of the resource properties.
0x80338094	78.11011	The specified batch parameter is incompatible with the specified event delivery mode. This can happen if batchSettings for a specific mode are passed for a different mode. For example, batchSettings like "MaxItems" and "MaxLatency" are not compatible with single event push mode or pull mode.
0x80338095	78.11011	The connectivity test from the push subscription source to the client failed. This can happen if the client machine initiating the push subscription is unreachable from the server machine where the event source is located. Possible reasons include firewall or some other network boundary. Modify subscription to use Pull based subscription.
0x80338096	78.11011	The subscribe packet had an EndTo element address that does not match the NotifyTo element address or it was invalid. For subscription the EndTo element need not be present in the subscription request. If it exists then it's address should match the address specified in NotifyTo element.
0x80338097	78.11011	The event source sent an event packet whose header could not be processed by the client. This can happen if it was malformed or if the header had a mustUnderstand attribute that could not be understood by the client.
0x80338098	78.11011	An operation is being attempted on a session that is being closed.This can happen if the session that is being used is also being closed by another thread.
0x80338099	78.11011	The listener on which the subscription session was established is no longer valid. This can happen if the WSMAN service listener configuration has been changed and a subscription was already active and using one of the configurations that was deleted.
0x8033809a	78.11011	The system failed to load the plugin.
0x8033809b	78.11011	The WS-Management service on the remote machine with which this subscription had been set up has requested that the subscription be closed. This can happen if the WS-Management service on the remote machine was being shutdown. To correct this problem restart the WS-Management service on the remote machine and re-create the subscription.
0x8033809c	78.11011	The event source was unable to deliver events to the client.This can happen due to network issues preventing the source from connecting to the client.
0x8033809d	78.11011	An unknown security error occurred.
0x8033809e	78.11011	The event source cancelled the subscription session.
0x8033809f	78.11011	TrustedHosts list contains an invalid hostname or hostname pattern.
0x803380a0	78.11011	The subscribe packet does not have NotifyTo element in the delivery section.
0x803380a1	78.11011	The subscribe packet does not have Address element in the NotifyTo section.
0x803380a2	78.11011	The subscribe packet contains invalid Address in the NotifyTo section.
0x803380a3	78.11011	The subscribe packet contains invalid Locale value in the delivery section.
0x803380a4	78.11011	The subscribe packet contains invalid heartbeat value.
0x803380a5	78.11011	The WS-Management service cannot process the request. This request is valid only when the -remote option is specified.
0x803380a6	78.11011	The WS-Management service does not support the options feature for the specified resource. Remove the options from the request and retry.
0x803380a7	78.11011	The subscribe packet contains batch size value which is smaller than supported value.
0x803380a8	78.11011	The WS-Management service cannot process the subscribe request. The delivery mode is either invalid or missing.
0x803380a9	78.11011	The WS-Management service cannot process the request. The provider method was not found.
0x803380aa	78.11011	The WinRM client could not create a push subscription because there are no listeners configured that match the specified hostname and transport, or because there is no enabled firewall exception on the port used by the selected listener. Change the hostname and transport, create an appropriate firewall exception, or run winrm quickconfig.
0x803380ab	78.11011	The WinRM client could not process the request because credentials were specified along with the 'no authentication' flag. No user name, password or client certificate should be specified with the 'no authentication' option.
0x803380ac	78.11011	The WinRM client cannot process the request. An invalid flag was specified for this request. Remove or change the invalid flag and try the request again.
0x803380ad	8.11011	The WinRM client cannot process the request. The request must specify only one authentication mechanism. If the No Authentication flag is set, no authentication mechanism should be specified. Change the request to specify only one authentication mechanism or 'no authentication' and try again.
0x803380ae	78.11011	The WinRM client cannot process the request. The SPN Server Port can only be used when the authentication mechanism is Negotiate or Kerberos. Remove the SPN Server Port or change the authentication mechanism and try the request again.
0x803380af	78.11011	The WinRM client cannot process the request. The request must not include credentials when using a smart card or default certificate. Remove the credentials or change the authentication mechanism and try the request again.
0x803380b0	78.11011	The WinRM client cannot process the request. Requests must include user name and password when Basic or Digest authentication mechanism is used. Add the user name and password or change the authentication mechanism and try the request again.
0x803380b1	78.11011	The WinRM client cannot process the request. Requests must not include user name and password when a certificate is used for authentication. Remove the user name and password or change the authentication mechanism and try the request again.
0x803380b2	78.11011	The WinRM client cannot process the request. Requests must include credentials if they specify the following flag: WSManFlagCredUsernamePassword. Add the credentials or remove the WSManFlagCredUsernamePassword flag and try the request again.
0x803380b3	78.11011	The WinRM client cannot process the request. Requests with credentials must include the following flag: WSManFlagCredUsernamePassword. Add the flag or remove the credentials and try the request again.
0x803380b4	78.11011	The WinRM client cannot process the request. Requests must include the certificate thumbprint when a certificate is used for authentication. Change the request to include the certificate thumbprint and try again.
0x803380b5	78.11011	The WinRM client cannot process the request. Requests must include the type of certificate to use for authentication. Change the request to include the type of the certificate and try again.
0x803380b6	78.11011	The WinRM client cannot process the request. Requests must include the location (machine or user certificate store) of the certificate used for authentication. Change the request to include the location of the certificate and try again.
0x803380b7	78.11011	The WinRM client cannot process the request. The certificate structure was incomplete. Change the certificate structure and try the request again.
0x803380b8	78.11011	The WinRM client cannot process the request. Credentials must not be provided for local requests. Remove the credentials and try the request again.
0x803380b9	78.11011	The WinRM client cannot process the request. Connection options must not be provided for local requests. Remove the connection options and try the request again.
0x803380ba	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManCreateSession function is null or zero. Change the request to include the missing parameter and try again.
0x803380bb	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManEnumerate function is null or zero. Change the request to include the missing parameter and try again.
0x803380bc	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManSubscribe function is null or zero. Change the request to include the missing parameter and try again.
0x803380bd	78.11011	The WinRM client cannot process the request. The parameter that should contain the result of the request is null. Change the request to include the missing parameter and try again.
0x803380be	78.11011	The WinRM client cannot process the request. The request is missing the session or enumeration handle. Change the request to include the missing parameter and try again.
0x803380bf	78.11011	The WinRM client cannot process the request. The resource URI must not be "" (blank or empty string) or NULL. Change the resource URI and try the request again.
0x803380c0	78.11011	The WinRM client cannot process the request. The resource locator was invalid. Change the resource locator and try the request again.
0x803380c1	78.11011	The WinRM client cannot process the request. The input XML must not be "" (blank or empty string) or NULL. Change the input XML and try the request again.
0x803380c2	78.11011	The WinRM client cannot process the request. The maximum number of elements to be retrieved in a batch is too small. Change the value for the maximum number of elements in a batch and try the request again.
0x803380c3	78.11011	The WinRM client cannot process the request. The maximum number of characters to be retrieved in a batch is too small. Change the value for the maximum number of characters in a batch and try the request again.
0x803380c4	78.11011	The WinRM client cannot process the request. The action URI must not be "" (blank or empty string) or NULL. Change the action URI and try the request again.
0x803380c5	78.11011	The WinRM client cannot process the request. The heartbeat interval must be greater than 0. Change the heartbeat interval and try the request again.
0x803380c6	78.11011	The WinRM client cannot process the request. The request must contain one and only one delivery mode. Change the request to contain only one delivery mode and try again.
0x803380c7	78.11011	The WinRM client cannot process the request. The request contained multiple settings for the policy regarding the maximum envelope size. Change the request to contain only one setting for the policy and try again.
0x803380c8	78.11011	The WinRM client cannot process the request. The request contained an expiration time, but did not specify if it was absolute or relative. Change the request to specify the type of the expiration time (absolute or relative) and try again.
0x803380c9	78.11011	The WinRM client cannot process the request. The request specified the type of the expiration time (absolute or relative) but it did not contain an expiration time. Change the request to include the expiration time and try again.
0x803380ca	78.11011	The WinRM client cannot process the request. The pull subscription request contained flags related to a push subscription. Change the flags and try the request again.
0x803380cb	8.11011	The WinRM client cannot process the request because the push subscription request contained an unsupported delivery transport. HTTP and HTTPS are the only currently supported transports. Change the delivery transport and try the request again.
0x803380cc	78.11011	The WinRM client cannot process the request. The delivery address for push subscriptions was too long. Change the delivery address and try the request again.
0x803380cd	78.11011	The WinRM client cannot process the request. The request contained the compression option but contained an unrecognized value. Change the value for the compression option and try the request again.
0x803380ce	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEndSubscriptionNotification function is null or zero. Change the request to include the missing parameter and try again.
0x803380cf	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEvents function is null or zero. Change the request to include the missing parameter and try again.
0x803380d0	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManGetBookmark function is null or zero. Change the request to include the missing parameter and try again.
0x803380d1	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManDecodeObject function is null or zero. Change the request to include the missing parameter and try again.
0x803380d2	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManEncodeObject(Ex) function is null or zero. Change the request to include the missing parameter and try again.
0x803380d3	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddObject function is null or zero. Change the request to include the missing parameter and try again.
0x803380d4	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorNextObject function is null or zero. Change the request to include the missing parameter and try again.
0x803380d5	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManConstructError function is null or zero. Change the request to include the missing parameter and try again.
0x803380d6	78.11011	The WinRM service cannot process the request. Push subscriptions are not supported for local session. Change subscription type to Pull and try again.
0x803380d7	78.11011	The WinRM client cannot process the request. The unencrypted flag only applies to the HTTP transport. Remove the unencrypted flag or change the transport and try again the request.
0x803380d8	78.11011	The WinRM client cannot process the request. Certificate parameters are not valid when the HTTP transport is also specified. Remove the certificate parameters or change the transport and try again the request.
0x803380d9	78.11011	The WinRM client cannot process the request. The connection string should be of the form [://][:][/] where transport is one of "http" or "https". Transport, port and suffix are optional. The host may be a hostname or an IP address. For IPv6 addresses, enclose the address in brackets - e.g. "http://[1::2]:80/wsman". Change the connection string and try the request again.
0x803380da	78.11011	The WinRM client cannot process the request. The connection string contains an unsupported transport. Valid transports are "http" or "https". Change the connection string and try the request again.
0x803380db	8.11011	The WinRM client cannot process the request because the port specified in the connection string is not valid. Verify the port and retry the request. Valid values are between 1 and 65535. Change the value for port and try the request again.
0x803380dc	78.11011	The WinRM client cannot process the request. The port specified in the configuration is invalid. Valid values are between 1 and 65535. Change the value for port and try the request again.
0x803380dd	78.11011	The WinRM service cannot process the request. WSMAN_FLAG_SEND_HEARTBEAT flag requires the event enumerator to be empty. Change the flag or change the event enumerator and try the request again.
0x803380de	78.11011	The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change the client configuration and try the request again.
0x803380df	78.11011	The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
0x803380e0	78.11011	The WinRM client cannot process the request. Digest authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
0x803380e1	78.11011	The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client configuration. Change the client configuration and try the request again. If this is a request for the local configuration, use one of the enabled authentication mechanisms still enabled. To use Kerberos, specify the local computer name as the remote destination. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password.
0x803380e2	78.11011	The WinRM client cannot process the request. Kerberos authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
0x803380e3	78.11011	The WinRM client cannot process the request. Certificate authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
0x803380e4	78.11011	The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
0x803380e5	8.11011	The WinRM client cannot process the request. Default credentials with Negotiate over HTTP can be used only if the target machine is part of the TrustedHosts list or the Allow implicit credentials for Negotiate option is specified.
0x803380e6	78.11011	The WinRM client cannot process the request. The CertificateThumbprint property must be empty when the SSL configuration will be shared with another service.
0x803380e7	78.11011	The WinRM client cannot process the request. The CertificateThumbprint property must not be "" (blank or empty string) or NULL.
0x803380e8	78.11011	The WinRM client cannot process the request. The WinRM client tried to create an SSL configuration for a pair of IP address and port according to the request, but the SSL configuration for that pair is owned by another service and cannot be shared. Use a different IP address and port combination and try the request again.
0x803380e9	78.11011	The WinRM client cannot process the request. The certificate CN and the hostname that were provided do not match.
0x803380ea	78.11011
0x803380eb	78.11011	The WinRM client cannot process the request. When HTTP is the transport, the Certificate thumbprint must be blank. HTTP does not use the Certificate thumbprint.
0x803380ec	78.11011	The WinRM client cannot process the request. The IP Filter is invalid. Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using , as delimiter. * is used to indicate that the service should listen on all available IPs on the machine. When * is used, other ranges in the filter are ignored. If filter is blank, the service doesn't listen on any address. For example, if service should be restricted to listen on only IPv4 addresses, IPv6 filter should be left empty. Example IPv4 filters: 2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22 Example IPv6 filters: 3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562
0x803380ed	78.11011	The WinRM client cannot process the request. The input XML modifies selectors or keys for the instance. You cannot create a new instance or change the identity of an instance by changing the keys. Change the input XML and try the request again.
0x803380ee	78.11011	The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to "Server Authentication". Retry the request with a certificate that has the correct EKU.
0x803380ef	78.11011	The WinRM client cannot process the request. The response from the destination computer does not include any results.
0x803380f0	78.11011	The WinRM client cannot process the request. The response to a create request did not contain a valid end point reference. The ResourceCreated element was not found or did not contain valid content.
0x803380f1	78.11011	The WinRM client cannot process the request. The response from the destination computer does not contain a valid SOAP enumeration context.
0x803380f2	78.11011	The WinRM client cannot process the request. The response from the destination computer contains a WS-Management FragmentTransfer header but the content of the body is not wrapped by the WS-Management XmlFragment wrapper.
0x803380f3	78.11011	The WinRM client cannot process the request. The response from the destination computer contains one or more invalid SOAP headers.
0x803380f4	78.11011	The WinRM client cannot process the request. It cannot find any SOAP Headers or Body elements in the response from the destination computer.
0x803380f5	78.11011	The WinRM client cannot process the request. The destination computer returned an empty response to the request.
0x803380f6	78.11011	The WinRM client cannot process the request. The destination computer returned an invalid SOAP fault.
0x803380f7	78.11011	The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
0x803380f8	78.11011	The WinRM client cannot process the request. The HTTP response from the destination computer was not in the same format as the request. A Unicode request packet may have been sent and an ANSI packet received.
0x803380f9	78.11011	The WinRM client cannot process the request. The encrypted message body has an invalid format and cannot be decrypted. Ensure that the service is encrypting the message body according to the specifications.
0x803380fa	78.11011	The WinRM client cannot process the request. The resource URI is not valid: it does not contain keys, but the class selected is not a singleton. To access an instance which is not a singleton, keys must be provided. Use the following command to get more information in how to construct a resource URI: "winrm help uris".
0x803380fb	78.11011	The WinRM client cannot process the request. The resource URI for an enumeration operation with WQL filter must not contain keys and the class name must be '*' (star). Use the following command to get more information in how to construct a resource URI: "winrm help uris".
0x803380fc	78.11011	The WS-Management identification operation is only available on remote sessions.
0x803380fd	78.11011	Subscribe operation with Push delivery mode is only available on remote sessions.
0x803380fe	78.11011	The subscription manager address is invalid. The response was not received from the address to which the subscription request was sent.
0x803380ff	78.11011	Only subscriptions with Pull delivery mode are supported by the plugin.
0x80338100	78.11011	WinRM cannot process the request because the WMI object contains too many levels of nested embedded objects.
0x80338101	78.11011	The WS-Management service cannot process the request. It does not support retrieving a WMI object that contains a property of type CIM_REFERENCE and the value of that property contains a remote machine name.
0x80338102	78.11011	The WS-Management service cannot process the request. The WMI service reported that the WMI provider could not perform the requested operation.
0x80338103	78.11011	The WS-Management service cannot process the request. A value retrieved from the WMI service or the WMI provider is invalid.
0x80338104	78.11011	The WS-Management service cannot process the request. The WMI service returned an 'access denied' error.
0x80338105	78.11011	The WS-Management service cannot process the request. The WMI provider returned an 'access denied' error.
0x80338106	78.11011	The WS-Management service cannot process the request. An 'access denied' error was received when connecting to the WMI service on the computer specified.
0x80338107	78.11011	The WS-Management service cannot process the request because the filter XML is invalid.
0x80338108	78.11011	The WS-Management service cannot process the request. The resource URI for an Enumerate operation must not contain keys.
0x80338109	78.11011	Cannot execute the Fragment-Level operation because the fragment path contains either "" (blank or empty string) or NULL. Change the value of the fragment path and try the request again.
0x8033810a	78.11011	The WinRM client cannot process the request. The response received from the destination machine contains invalid characters and cannot be processed.
0x8033810b	78.11011	The WinRM client cannot process the request. Kerberos authentication cannot be used when the destination is an IP address. Specify a DNS or NetBIOS destination or specify Basic or Negotiate authentication.
0x8033810c	8.11011	The WinRM client cannot process the request. Kerberos authentication cannot be used with implicit credentials if the client computer is not joined to a domain. Use explicit credentials or specify a different authentication mechanism than Kerberos.
0x8033810d	78.11011	The WinRM client cannot process the request. The batch settings parameter is invalid.
0x8033810e	78.11011	The WinRM client cannot process the request. If you do not specify an authentication mechanism or you specify Kerberos, then you cannot use "localhost" or "127.0.0.1" or "[::1]" for the remote host name. You can explicitly specify a different authentication mechanism than Kerberos or specify the remote host as a DNS name or NetBIOS name.
0x8033810f	78.11011	The WinRM client received an unknown HTTP status code from the remote WS-Management service.
0x80338110	78.11011	The WinRM client received a HTTP redirect status code from the remote WS-Management service. WinRM does not support redirects.
0x80338111	8.11011	The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota.
0x80338112	78.11011	The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL.
0x80338113	78.11011	The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
0x80338114	78.11011	The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element.
0x80338115	78.11011	Cannot create a WinRM listener on HTTPS because this machine does not have an appropriate certificate. To be used for SSL, a certificate must have a CN matching the hostname, be appropriate for Server Authentication, and not be expired, revoked, or self-signed.
0x80338116	78.11011	Firewall does not allow exceptions; WinRM cannot be setup for remote access.
0x80338117	78.11011	The Windows Remote Management (WinRM) service cannot be configured for remote access because Group Policy does not allow local firewall changes. Check the Group Policy settings to allow local firewall exceptions and add WinRM to the firewall exceptions.
0x80338118	8.11011	The WinRM client cannot process the request because the selector name is not valid. Change the selector name and retry the request.
0x80338119	78.11011	The WS-Management service does not support the encoding type specified.
0x8033811a	78.11011	The WS-Management service cannot process the request because the selector values do not match a known resource, or the resource is offline. Retry the request later when the resource is online, or try a different selector.
0x8033811b	78.11011	The WS-Management service cannot process the request because the a header in the request is invalid.
0x8033811c	78.11011	The expiration time specified for enumeration was invalid. Specify the expiration time as a duration.
0x8033811d	78.11011	The WS-Management service received a request which specified a maximum number of elements, but the service does not support this feature. Retry the request without this element specified.
0x8033811e	78.11011	The WS-Management service cannot process the request. The WMI provider returned an 'invalid parameter' error.
0x8033811f	78.11011	The WinRM client cannot process the request. The request must contain one and only one enumeration mode. Change the request to contain only one enumeration mode and try again.
0x80338120	78.11011	The WinRS client cannot process the request. An invalid flag was specified for this request. Remove or change the invalid flag and try the request again.
0x80338121	78.11011	The WinRS client cannot process the request. One of the parameters required is null or zero. Change the request to include the missing parameter and try again.
0x80338122	78.11011	The data source could not process the filter. The filter might be missing, invalid or too complex to process. If a service only supports a subset of a filter dialect (such as XPath level 1), it may return this fault for valid filter expressions outside of the supported subset. Change the filter and try the request again.
0x80338123	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddEvent function is null or zero. Change the request to include the missing parameter and try again.
0x80338124	78.11011	The WinRM client cannot process the request. The object parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is Object or ObjectAndEPR.
0x80338125	78.11011	The WinRM client cannot process the request. The EPR parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is EPR or ObjectAndEPR.
0x80338126	8.11011	WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.
0x80338127	78.11011	Not used. To be removed.
0x80338128	78.11011	The WinRS client cannot process the Receive request because the shell plugin returned an empty response to the request.
0x80338129	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033812a	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WinrsCloseShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033812b	78.11011	The WinRS client cannot process the request. The parameter required for the WinrsFreeCreateShellResult function is null or zero. Change the request to include the missing parameter and try again.
0x8033812c	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is null or zero. Change the request to include the missing parameter and try again.
0x8033812d	78.11011	The WinRS client cannot process the request. The parameter required for the WinrsFreeRunCommandResult function is null or zero. Change the request to include the missing parameter and try again.
0x8033812e	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033812f	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSMansReceiveShellOutput function is null or zero. Change the request to include the missing parameter and try again.
0x80338130	78.11011	The WinRS client cannot process the request. The parameter required for the WinrsFreePullResult function is null or zero. Change the request to include the missing parameter and try again.
0x80338131	78.11011	The WinRS client cannot process the request. One of the parameters required for the WinrsPull function is null or zero. Change the request to include the missing parameter and try again.
0x80338132	78.11011	The WinRS client cannot process the request. The parameter required for the WinrsCloseReceiveHandle function is null or zero. Change the request to include the missing parameter and try again.
0x80338133	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is null or zero. Change the request to include the missing parameter and try again.
0x80338134	78.11011	The WinRS client cannot process the request. One of the parameters required for the WinrsPush function is null or zero. Change the request to include the missing parameter and try again.
0x80338135	78.11011	The WinRS client cannot process the request. The parameter required for the WinrsCloseSendHandle function is null or zero. Change the request to include the missing parameter and try again.
0x80338136	78.11011	The WinRS client cannot process the request. One of the parameters required for the WinrsGet function is null or zero. Change the request to include the missing parameter and try again.
0x80338137	78.11011	The WS-Management service does not support the specified polymorphism mode. Try changing the polymorphism mode specified, and try again.
0x80338138	78.11011	The WS-Management service cannot process the request because the specified URI is not supported on the service side. Retry the request with local session.
0x80338139	78.11011	The WS-Management service cannot process the request. A DMTF resource URI was used to access a non-DMTF class. Try again using a non-DMTF resource URI.
0x8033813a	78.11011	The WS-Management service cannot process the request. The DMTF class in the repository uses a different major version number from the requested class. This class can be accessed using a non-DMTF resource URI.
0x8033813b	78.11011	The WS-Management service cannot process the request. The resource URI and __cimnamespace selector attempted to use different namespaces. Try removing the __cimnamespace selector or using a DMTF resource URI. If a non-DMTF resource URI is used with a __cimnamespace selector, the namespaces must match.
0x8033813c	78.11011	The WS-Management client cannot process the request. To use the WSManSubscribe API the user has to be running under Network Service account. No other account is supported currently for push subscriptions.
0x8033813d	78.11011	The WS-Management client cannot process the request. The event source machine is not joined to a domain. To set up a push subscription session to an event source the source has to be connected to a domain. To fix this problem either join the event source machine to a domain or use PULL as the delivery mode for the subscription.
0x8033813e	78.11011	The WS-Management client cannot process the request. The subscriber machine is not joined to a domain. To set up a push subscription session to an event source, the subscriber machine has to be connected to a domain. To fix this problem either join the subscriber machine to a domain or use PULL as the delivery mode for the subscription.
0x8033813f	78.11011	The WinRM client cannot process the request because it is trying to update a read-only setting. Remove this setting from the command and try again.
0x80338140	78.11011	The WinRS client cannot process the request. The server cannot set Code Page. You may want to use the CHCP command to change the client Code Page to 437 and receive the results in English.
0x80338141	78.11011	Not used. To be removed.
0x80338142	78.11011	Not used. To be removed.
0x80338143	78.11011	The WS-Management client received too many results from the server. The server implementation should never return more items than are specified by the client.
0x80338144	8.11011	The WinRM client cannot process the request. A certificate thumbprint was specified together with a user name or password. Only one credentials type can be specified. Remove the credentials type that does not correspond to the intended authentication mechanism and retry the request.
0x80338145	78.11011	The WinRM client cannot process the request. The flag that specifies the authentication mechanism to use is incorrect. Remove or change the invalid flag and try the request again.
0x80338146	78.11011	The WinRM client cannot process the request. When an authentication mechanism is not specified, only user name and password credentials are allowed. If you want to use a different type of credentials then you need to specify the authentication mechanism. Specify the authentication mechanism or the correct credentials and try the request again.
0x80338147	78.11011	The WinRM client cannot process the request. For authentication mechanisms that require the credentials of an user account, both user name and password must be specified. Specify the missing user name or password and try the request again.
0x80338148	8.11011	The WinRM client cannot process the request. If you are using a machine certificate, it must contain a DNS name in the Subject Alternative Name extension or in the Subject Name field, and no UPN name. If you are using a user certificate, the Subject Alternative Name extension must contain a UPN name and must not contain a DNS name. Change the certificate structure and try the request again.
0x80338149	78.11011	The WinRM Shell client cannot process the request. One of the environment variable name passed to the WSManCreateShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033814a	78.11011	An operation is being attempted on a shell that is being closed. This can happen if the shell that is being used is also being closed by another thread.
0x8033814b	78.11011	The WinRM Shell client cannot process the request. One of the stream id name passed to the WSManCreateShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033814c	78.11011	The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again.
0x8033814d	78.11011	The WinRM Shell client cannot process the request. The command handle passed to the WSMan Shell function is not valid. The command handle is valid only when WSManRunShellCommand function completes successfully. Change the request including a valid shell handle and try again.
0x8033814e	78.11011	The WinRM Shell client cannot process the request. One of the argument value passed to the WSManRunShellCommand function is null or zero. Change the request to include the missing parameter and try again.
0x8033814f	78.11011	An operation is being attempted on a command that is being closed. This can happen if the command handle that is being used is also being freed by another thread.
0x80338150	78.11011	The WinRM Shell client cannot process the request. The stream id index from within WSMAN_STREAM_ELEMENT passed to the WSManSendShellInput function is invalid. The stream id index should be an index from within inputStreamSet array passed to the WSManCreateShell function. Change the request with a valid index and try again.
0x80338151	78.11011	Not used. To be removed.
0x80338152	78.11011	The WS-Management operations to update the certificate mapping store of the WINRM service config can only be done remotely.
0x80338153	78.11011	The WINRM certificate mapping configuration store has reached an internal limit and cannot create any more entries. Remove some entries and try again.
0x80338154	78.11011	The WINRM certificate mapping configuration operation cannot be completed because the user credentials could not be verified. Please check the username and password used for mapping this certificate and verify that it is a non-domain account and try again.
0x80338155	78.11011	The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to "Client Authentication". Retry the request with a certificate that has the correct EKU.
0x80338156	78.11011	The WinRM client cannot process the request. A certificate thumbprint was specified, but the following flag is missing: WSManFlagUseClientCertificate. Add the flag and try the request again.
0x80338157	78.11011	The WinRM client cannot process the request. The following flags cannot be specified together: WSManFlagUseClientCertificate and WSManFlagCredUsernamePassword. Remove one of the flags and try the request again.
0x80338158	78.11011	The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid. CustomRemoteShell URI should start with WinRM shell resource URI prefix: "http://schemas.microsoft.com/wbem/wsman/1/windows/shell". The URI should not contain invalid characters including '*', '?', white spaces and tabs. The CustomRemoteShell URI cannot be longer than 1023 characters.
0x80338159	78.11011	The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid. Windows command shell URI ("http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd") cannot be a CustomRemoteShell URI.
0x8033815a	78.11011	The WinRM client cannot process the request because the process path specified for the CustomRemoteShell table entry is invalid. The process path should be absolute and should point to an existing executable.
0x8033815b	78.11011	Not used. To be removed.
0x8033815c	78.11011	The WinRM client cannot process the request because the provided security descriptor is invalid.
0x8033815d	78.11011	The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo is too complex or uses a structure not understood by the service. The WinRM service supports a single layer of policy assertions underneath a wsp:ExactlyOne element.
0x8033815e	78.11011	The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo does not contain any options that the service can comply with. The WinRM service supports the following profiles: Negotiate or Kerberos over HTTP, Negotiate or Kerberos over HTTPS, and mutual certificate authentication over HTTPS using issuer thumbprints.
0x8033815f	78.11011	The WinRM service cannot process the request because the wsman:ConnectionRetry element in the DeliverTo is invalid.
0x80338160	78.11011	WinRM cannot make the configuration change. The URI supplied for the certificate mapping operation is not valid. It must contain at least one character. It must not contain internal whitespace. It must not contain '?' character. A prefix may be specified by using "*" as the last character. The URI cannot be longer than 1023 characters.
0x80338161	78.11011	WinRM cannot make the configuration change. The Subject used for the certificate mapping operation is not valid. It must contain at least one character. It must contain at most one "*" character which should be the first character. (This may be the only character in which case it matches all subjects). The Subject cannot be longer than 1023 characters.
0x80338162	78.11011	WinRM cannot make the configuration change because the Issuer used for the certificate mapping operation is not valid. The certificate identified by the issuer thumbprint must be present in the machine "Trusted Root Certification Authorities" or "Intermediate Certification Authorities" store. The certificate must have key usage that allows it to sign other certificates.
0x80338163	78.11011	The WinRM client cannot process the request because the type field in the WSMAN_ALLOWED_PUBLISHERS argument is invalid. Collector-initiated subscriptions must use WSMAN_SINGLE_PUBLISHER and Source-initiated subscriptions must use WSMAN_MULTIPLE_PUBLISHERS.
0x80338164	78.11011	The WinRM client cannot process the request because the delivery retry parameters are invalid. If delivery retry is requested, the deliveryRetryInterval and deliveryRetryAttempts fields must both be nonzero.
0x80338165	78.11011	The WinRM client cannot process the request. The required WSMAN_ALLOWED_PUBLISHERS settings is null or zero. Change the request to include the missing parameter and try again.
0x80338166	78.11011	The WinRM client cannot process the request because client certificate subject filters were specified without any issuers. When using client certificate authentication, specify at least one issuer thumbprint.
0x80338167	78.11011	The WinRM client cannot process the request because the subscription contains no domain or non-domain sources. Subscriptions using WSMAN_MULTIPLE_PUBLISHERS must specify either a security descriptor or an issuer list or both.
0x80338168	78.11011	The WinRM service cannot process the request because the subscription manager returned invalid enumeration results. The m:Subscription XML object or m:Version element is missing or invalid.
0x80338169	78.11011	WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.
0x8033816a	78.11011	WinRM cannot make the configuration change. The Password used for updating the certificate mapping configuration is not valid. It cannot be longer than 255 characters.
0x8033816b	78.11011	WinRM cannot make the configuration change. The Password used for updating the certificate mapping configuration is not valid. A user account used for configuring a certificate mapping cannot have a blank password.
0x8033816c	78.11011	WinRM cannot make the configuration change. The credential used for updating or creating the certificate mapping configuration is not valid. The credential consists of both Password and UserName being supplied together in a pair.
0x8033816d	78.11011	The WinRM service executed an operation and the provider returned inconclusive information regarding success or failure of the operation. The status was marked as failed, but no error code was given.
0x8033816e	78.11011	The WS-Management service on the remote machine cannot process the shell request. This can happen if the WS-Management service on the remote machine was being shutdown. To correct this problem restart the WS-Management service on the remote machine and re-send the shell request.
0x8033816f	78.11011	The WinRM service cannot process the request. The URI parameter is the key to CustomRemoteShell table and cannot be modified.
0x80338170	78.11011	The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.
0x80338171	78.11011	The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure.
0x80338172	78.11011	The WinRM service cannot make the configuration change. The selector keys of Subject, URI or Issuer cannot be changed by overriding the selector key value in the body.
0x80338173	78.11011	The WinRM client cannot process the request because it received an HTML error packet.
0x80338174	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManInitialize function is null or zero. Change the request to include the missing parameter and try again.
0x80338175	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManInitialize API call. Remove or change the invalid flag and try the call again.
0x80338176	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManDeinitialize API call. Remove or change the invalid flag and try the call again.
0x80338177	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is null or zero. Change the request to include the missing parameter and try again.
0x80338178	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is invalid. Change the invalid parameter and try again.
0x80338179	78.11011	The WinRM client cannot process the request. One of the parameters required to get a session option is invalid. Change the invalid parameter and try again.
0x8033817a	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033817b	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManCreateShell API call. Remove or change the invalid flag and try the call again.
0x8033817c	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManCloseShell API call. Remove or change the invalid flag and try the call again.
0x8033817d	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManCloseCommand API call. Remove or change the invalid flag and try the call again.
0x8033817e	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseShell function is null or zero. Change the request to include the missing parameter and try again.
0x8033817f	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseCommand function is null or zero. Change the request to include the missing parameter and try again.
0x80338180	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is null or zero. Change the request to include the missing parameter and try again.
0x80338181	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManRunShellCommand API call. Remove or change the invalid flag and try the call again.
0x80338182	78.11011	The WinRM client cannot process the request. You must wait for the WSManRunShellCommand API call to complete before calling WSManCloseShellOperationEx API.
0x80338183	78.11011	The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element. The CommandResponse element was not found or did not contain valid content.
0x80338184	78.11011	The WinRM client cannot process the request. The OptionSet element is invalid. Change the request to include a valid OptionSet element and try again.
0x80338185	78.11011	The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element. The CommandId element was not found or did not contain valid content.
0x80338186	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null or zero. Change the request to include the missing parameter and try again.
0x80338187	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManSignalShell API call. Remove or change the invalid flag and try the call again.
0x80338188	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is null or zero. Change the request to include the missing parameter and try again.
0x80338189	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManSendShellInput API call. Remove or change the invalid flag and try the call again.
0x8033818a	78.11011	The WinRM client cannot process the request. An invalid parameter was specified for the WSManSendShellInput API call. streamData parameter should be specified in binary format using WSMAN_DATA_TYPE_BINARY type. Change the invalid parameter and try the call again.
0x8033818b	78.11011	The WinRM Shell client cannot process the request. The stream name passed to the WSManSendShellInput function is not valid. The input stream name should be specified as part of the input streams during shell creation using WSManCreateShell function. Change the request including a valid input stream name and try again.
0x8033818c	78.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManReceiveShellOutput function is null or zero. Change the request to include the missing parameter and try again.
0x8033818d	78.11011	The WinRM Shell client cannot process the request. The stream or list of streams passed to the WSManReceiveShellOutput function is not valid. The desired stream names should be specified as part of the output streams during shell creation using WSManCreateShell function. Change the request including valid desired streams and try again.
0x8033818e	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManReceiveShellOutput API call. Remove or change the invalid flag and try the call again.
0x8033818f	78.11011	The WinRM client cannot process the request. The response to a Receive request did not contain a valid ReceiveResponse element. The ReceiveResponse element was not found or did not contain valid content.
0x80338190	78.11011	The WSMan plugin configuration is corrupted.
0x80338191	78.11011	The file path specified is either not absolute, not in the system32 directory, or not valid.
0x80338192	78.11011	The file specified does not exist.
0x80338193	78.11011	The WSMan extension failed to read IIS configuration.
0x80338194	78.11011	The WinRM client cannot process the request. The locale option is invalid. Change the locale and try again.
0x80338195	78.11011	The WinRM client cannot process the request. The UI language option is invalid. Change the UI language and try again.
0x80338196	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManGetErrorMessage function is null or zero. Change the request to include the missing parameter and try again.
0x80338197	78.11011	The WinRM client cannot process the request. The language code parameter is invalid. The language code parameter should be either NULL or a valid RFC 3066 language code. Change the language code and try the request again.
0x80338198	78.11011	The WinRM client cannot process the request. An invalid flag was specified for the WSManGetErrorMessage API call. Remove or change the invalid flag and try the call again.
0x80338199	78.11011	The WinRM service cannot process the request because the request needs to be sent to a different machine. Use the redirect information to send the request to a new machine.
0x8033819a	78.11011	The WinRM client cannot process the request. The flag that specifies the proxy authentication mechanism to use is incorrect. Remove or change the invalid flag and try the request again.
0x8033819b	78.11011	The WinRM client cannot process the request. The credentials for proxy authentication are not specified correctly. Both user name and password credentials must be valid. Specify the correct credentials and try the request again.
0x8033819c	78.11011	The WinRM client cannot process the request. The proxy access type is incorrect. Use one of the proxy access type flags; the flags cannot be combined. Change the invalid proxy access type and try the request again.
0x8033819d	78.11011	The WinRM client cannot process the request. The direct connection to the server option cannot be used with non empty proxy authentication data. Change the invalid proxy access type or use empty proxy authentication data and try the request again.
0x8033819e	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is null or zero. Change the request to include the missing parameter and try again.
0x8033819f	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is invalid. Change the invalid parameter and try again.
0x803381a0	78.11011	The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsString function is invalid. Change the invalid parameter and try again.
0x803381a1	78.11011	The WinRM client cannot process the request. Requests must include user name and password when CredSSP authentication mechanism is used. Add the user name and password or change the authentication mechanism and try the request again.
0x803381a2	78.11011	The WinRM client cannot process the request. CredSSP authentication is currently disabled in the client configuration. Change the client configuration and try the request again. CredSSP authentication must also be enabled in the server configuration. Also, Group Policy must be edited to allow credential delegation to the target computer. Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer. For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com
0x803381a3	78.11011	The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer. Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer. For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com.
0x803381a4	78.11011	The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer because the computer is not trusted. The identity of the target computer can be verified if you configure the WSMAN service to use a valid certificate using the following command: winrm set winrm/config/service @{CertificateThumbprint=""} Or you can check the Event Viewer for an event that specifies that the following SPN could not be created: WSMAN/. If you find this event, you can manually create the SPN using setspn.exe . If the SPN exists, but CredSSP cannot use Kerberos to validate the identity of the target computer and you still want to allow the delegation of the user credentials to the target computer, use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Fresh Credentials with NTLM-only Server Authentication. Verify that it is enabled and configured with an SPN appropriate for the target computer. For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com. Try the request again after these changes.
0x803381a5	78.11011	The WS-Management service cannot process the request. The maximum number of concurrent shells for this user has been exceeded. Close existing shells or raise the quota for this user.
0x803381a6	78.11011	The WS-Management service cannot process the request. The maximum number of concurrent operations for this user has been exceeded. Close existing operations for this user, or raise the quota for this user.
0x803381a7	78.11011	The WS-Management service cannot process the request. The load quota for this user has been exceeded. Send future requests at a slower rate or raise the quota for this user.
0x803381a8	78.11011	The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future requests at a slower rate or raise the system quota.
0x803381a9	78.11011	The WS-Management service cannot complete the authorization under the given token. A previous authorization attempt for the same user resulted in a different token. The user record will be revoked and the next request will reauthorize.
0x803381aa	78.11011	An application tried to retrieve the HTTP Redirect location from the session when no redirect error (ERROR_WSMAN_REDIRECT_REQUESTED) was returned. The application needs to be updated so as to only retrieve the location after this error is returned.
0x803381ab	78.11011	The WS-Management service cannot process the request. The maximum number of users executing shell operations has been exceeded. Retry after some time or raise the quota for concurrent shell users.
0x803381ac	78.11011	The WS-Management service cannot process the request. The service is configured to not accept any remote shell requests.
0x803381ad	78.11011	The WS-Management service cannot complete the Pull operation for the enumeration because the wsman:MaxEnvelopeSize, wsen:MaxCharacters or wsen:MaxElements parameters differ from those specified to the enumeration. The application needs to specify the same parameters for Pull as were specified for the enumeration.
0x803381ae	78.11011	The WinRM service cannot process the request because it is trying to update a deprecated setting. Remove this setting from the command and try again.
0x803381af	78.11011	The WS-Management service cannot process the configuration settings. A Security element contains a URI that does not match its parent Resource element.
0x803381b0	78.11011	The WinRM client cannot process the request. Allow implicit credentials for Negotiate authentication option is only valid for HTTPS transport. Remove the allow implicit credentials for Negotiate authentication option and try the request again.
0x803381b1	78.11011	The WinRM client cannot process the request. Setting proxy information is not valid when the HTTP transport is specified. Remove the proxy information or change the transport and try the request again.
0x803381b2	78.11011	The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is Kerberos. Remove the proxy information or change the authentication mechanism and try the request again.
0x803381b3	78.11011	The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is CredSSP. Remove the proxy information or change the authentication mechanism and try the request again.
0x803381b4	78.11011	The WinRM client cannot process the request. The request must specify only one authentication mechanism for proxy. Change the request to specify only one authentication mechanism and try again.
0x803381b5	78.11011	The WinRM client received a redirect error from the server when it is not appropriate. The only time a redirect error can be reported correctly is during the authorization of a user. This would result in a properly formatted redirect response from the server that includes the redirect endpoint.
0x803381b6	78.11011	The WinRM service received a redirect error from an authorization plug-in where the redirect location was too long.
0x803381b7	78.11011	The WinRM service received a HTTP redirect message redirecting the client but the location URL is invalid.
0x803381b8	78.11011	The WinRM service cannot process the request. The Channel Binding Token Hardening Level (CbtHardeningLevel) value is invalid. The valid values are "None", "Relaxed" and "Strict". Change the CbtHardeningLevel value and try again.
0x803381b9	78.11011	The WinRM client cannot process the request because the server name cannot be resolved.
0x803381ba	78.11011	The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https".
0x803381bb	78.11011	The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TrustedHosts run the following command: winrm help config.
0x803381bc	78.11011	The WinRM client cannot process the request. Custom Remote Shell has been deprecated and cannot be used.
0x803381bd	78.11011	The WinRM client cannot process the request. The feature in use has been deprecated and cannot be used.
0x803381be	78.11011	The WinRM client used a parameter to specify the use of SSL while specifying http in the connection string.
0x803381bf	8.11011	The WinRM service cannot process the request because the security for this resource URI cannot be changed.
0x803381c0	8.11011	The WinRM service cannot process the request. The enumeration request expects a selector based filter to specify the shell identifier.
0x803381c1	8.11011	The WinRM service cannot process the request. The enumeration of end point resources for shell commands is not supported.
0x803381c2	8.11011	The WinRM Shell client cannot process the request because the shell name has exceeded 255 characters in length.
0x803381c3	8.11011	The WinRM runAs configuration operation cannot be completed because the user credentials could not be verified. Verify that the username and password used for configuration are valid and retry the operation.
0x803381c4	8.11011	The WinRM service cannot process the request because the WinRS shell instance is currently disconnected.
0x803381c5	8.11011	The WinRM service cannot process the request. This WinRS shell instance does not support disconnect and reconnect operations because it was created by an older WinRS client or its provider does not support the disconnect operation.
0x803381c6	8.11011	The WinRM service cannot process the request because the WinRS shell instance is connected to a different client.
0x803381c7	8.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManDisconnectShell function is null or zero. Change the request to include the missing parameter and try again.
0x803381c8	8.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShell function is null or zero. Change the request to include the missing parameter and try again.
0x803381c9	8.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShell function is null or zero. Change the request to include the missing parameter and try again.
0x803381ca	8.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShellCommand function is null or zero. Change the request to include the missing parameter and try again.
0x803381cb	8.11011	The WinRM client cannot process the request. The body response is not a valid connect request response.
0x803381cc	8.11011	The WinRM Shell client cannot process the request. The command is currently terminating or was terminated.
0x803381cd	8.11011	The WinRM service cannot process the request. The WinRS shell instance is currently connected to a different client.
0x803381ce	8.11011	The WinRM client encountered an error while communicating with the WinRM service during the disconnect operation. The shell has been disconnected and the streams were possibly suspended abruptly.
0x803381cf	8.11011	The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell instance that is already disconnected.
0x803381d0	8.11011	The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell instance that is currently connected.
0x803381d1	8.11011	An error was encountered while subscribing to the Group Policy change notification.
0x803381d2	8.11011	The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShellCommand function is null or zero. Change the request to include the missing parameter and try again.
0x803381d3	8.11011	The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell command instance that is currently connected.
0x803381d4	8.11011	The WinRM service cannot process the request because the command ID specified by the client is not a valid GUID. Modify the request and retry the request.
0x803381d5	8.11011	The WinRM service cannot process the request because the shell ID specified by the client is not a valid GUID. Provide a valid ID and try again.
0x803381d6	8.11011	The WinRM service cannot process the request. A command already exists with the command ID specified by the client.
0x803381d7	8.11011	The WinRM service cannot process the request. A resource already exists with the shell ID specified by the client.
0x803381d8	8.11011	The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell command instance that is disconnected.
0x803381d9	8.11011	The WS-Management service cannot process the request. The resource URI for the Subscribe operation must not contain keys.
0x803381da	8.11011	The WinRM client cannot process the request. A flag that is not valid was specified for the WSManDisconnectShell method. Remove or change the flag and retry the operation.
0x803381db	8.11011	The WinRM client cannot process the request because the command handle is not associated with the provided shell handle.
0x803381dc	8.11011	The WS-Management service did not receive a response for an extended semantics operation within the timeframe specified in the OperationTimeout setting.
0x803381dd	8.11011	The WS-Management service is configured to not allow remote requests.
0x803381de	8.11011	The WS-Management service cannot process the request because the stream is currently disconnected.
0x803381df	8.11011	The creation of a new Shell failed. Verify that the RunAsPassword value is correctly configured and that the Group Policy setting "Disallow WinRM from storing RunAs credentials" is Disabled or Not Configured. To enable WinRM to store RunAs credentials, change this Group Policy setting to Disabled.
0x803381e0	8.11011	The supplied plugin configuration XML is not valid. To enable WinRM to store RunAs credentials, change the "Disallow WinRM from storing RunAs credentials" Group Policy setting to Disabled.
0x803381e1	8.11011	The WinRM client cannot process the request because the XML instance does not match the class schema provided by the server.
0x803381e2	8.11011	The WinRM client cannot process the request because the XML contains an unsupported type. Verify the XML and retry the operation.
0x803381e3	8.11011	The WS-Management service cannot process the request. The service is configured to reject remote connection requests for this plugin.
0x803381e4	8.11011	The WS-Management service cannot process the request. This user has exceeded the maximum number of concurrent shells allowed for this plugin. Close at least one open shell or raise the plugin quota for this user.
0x803381e5	8.11011	The WS-Management service cannot process the request. The maximum number of users executing remote operations has been exceeded for this plugin. Retry the request later or raise the quota for concurrent users.
0x803381e6	8.11011	The WS-Management service cannot process the request. The maximum number of concurrent shells allowed for this plugin has been exceeded. Retry the request later or raise the Maximum Shells per Plugin quota.
0x803381e7	8.11011	The WS-Management service cannot process the request. The maximum number of concurrent operations allowed for this plugin has been exceeded. Retry the request later or raise the Maximum Operations per Plugin quota.
0x803381e8	8.11011	The WS-Management service cannot process the request. This user has exceeded the maximum number of allowed concurrent operations. Retry the request later or raise the Maximum Operations per User quota.
0x803381e9	8.11011	The WS-Management service cannot process the request. The maximum number of concurrent commands per shell has been exceeded. Retry the request later or raise the Maximum Commands per Shell quota.
0x803381ea	8.11011	The WS-Management service cannot process the request. There are not enough resources available to process this operation. Retry the operation later or close one or more of the currently running operations.
0x803381eb	8.11011	The WinRM client cannot process the request because the MI Deserializer cannot be created.
0x803381ec	8.11011	The WinRM client cannot process the request because the metadata could not be deserialized.
0x803381ed	8.11011	The WinRM client cannot process the request because the metadata failed to be retrieved from the server.
0x803381ee	8.11011	The WinRM client cannot process the request because a WinRM session could not be created.
0x803381ef	8.11011	The WinRM client cannot process the request because the target object has a key property set to NULL. Incomplete objects cannot be used as the target of an operation.
0x803381f0	8.11011	The WinRM client cannot process the request as the server identity could not be verified. If the identity of the server is trusted, add it to the TrustedHosts list and retry the request. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TrustedHosts, run the following command: winrm help config
0x803381f1	8.11011	The WinRM client cannot process the request because the octet string array type is not supported.
0x803381f2	8.11011	The WS-Management service cannot process the request. The requested IdleTimeout is outside the allowed range.
0x803381f3	8.11011	The WinRM client cannot process the request because insufficient metadata is available. The application does not allow all properties to be returned as strings, but the server does not support correctly typing the properties. Change the request to allow all properties to be returned as strings and retry the request.
0x803381f4	8.11011	The WinRM client cannot process the request because the MI_OperationOptions contained both a Resource URI and a Resource URI Prefix. Specify only one of these two options and try again.
0x803381f5	8.11011	The WinRM client cannot process the request because keysOnly and WSMAN_ENUMERATIONMODE_OBJECTONLY were specified at the same time. These two settings are incompatible. Remove the WSMAN_ENUMERATIONMODE_OBJECTONLY option, or set keysOnly to MI_FALSE, and retry the request.
0x803381f6	8.11011	The WinRM client cannot process the request because the class name is not valid. Supply a valid class name or set the Resource URI option and retry the request.
0x803381f7	8.11011	The subscribe packet contains an Encoding value that is not valid in the delivery section.
0x803381f8	8.11011	The WinRM client cannot process the request. The destination computer name must be a hostname or an IP address, and must not be a URL. To use an IPv6 address, enclose the address in brackets, like the following: "[::1]". The transport, port number, and URL prefix may be controlled by setting the appropriate destination options. Change the destination computer name string and retry the operation.
0x803381f9	8.11011	The server does not support WS-Management Identify operations. Skip the TestConnection part of the request and try again.
0x803381fa	8.11011	The WS-Management service cannot process the operation. The operation is being attempted on a client session that is unusable. This may be related to a recent restart of the WS-Management service. Please create a new client session and retry the operation if re-executing the operation does not have undesired behavior.
0x803381fb	1011	The WS-Management service cannot process the operation. An attempt to create a virtual account failed. Ensure that WinRM service is running as Local System and that it has TCB privilege enabled.
0x803381fc	1011	The WS-Management service cannot process the operation. Virtual account feature is only available in Windows 7, Server 2008 R2 and above.
0x803381fd	1011	The WS-Management service cannot process the operation. An attempt to logon using the configured RunAs Managed Service Account failed.
0x803381fe	1011	The WS-Management service cannot process the operation. An attempt to query mapped credential failed. This will happen if the security context associated with WinRM service has changed since the credential was originally mapped.
0x90000001	78.11011	Microsoft-Windows-Windows Remote Management
0x90000002	78.11011	Microsoft-Windows-WinRM/Operational
0x90000003	78.11011	Microsoft-Windows-WinRM/Analytic
0xb0000002	78.11011	Initializing WSMan API
0xb0000003	78.11011	Initialization of WSMan API failed, error code %1
0xb0000004	78.11011	Deinitializing WSMan API
0xb0000005	78.11011	Deinitialization of WSMan API failed, error code %1
0xb0000006	78.11011	Creating WSMan Session. The connection string is: %1
0xb0000007	78.11011	WSMan Create Session operation failed, error code %1
0xb0000008	78.11011	Closing WSMan Session
0xb0000009	78.11011	Closing WSMan Session failed, error code %1
0xb000000a	8.11011	Setting WSMan Session Option (%1) - %2 with value (%3) completed successfully.
0xb000000b	8.11011	Creating WSMan shell with the ResourceUri: %1 and ShellId: %2
0xb000000c	78.11011	WSMan shell creation failed, error code %1
0xb000000d	8.11011	Running WSMan command with CommandId: %1
0xb000000e	78.11011	Running WSMan command failed, error code %1
0xb000000f	78.11011	Closing WSMan command
0xb0000010	78.11011	Closing WSMan shell
0xb000001c	78.11011	Access Denied error: the %1 API caller does not match the creator of the application object
0xb000001d	78.11011	Initialization of WSMan API completed successfuly
0xb000001e	78.11011	Deinitialization of WSMan API completed successfuly
0xb000001f	78.11011	WSMan Create Session operation completed successfuly
0xb0000020	8.11011	Setting WSMan Session Option (%1) - %2 failed, error code %3.
0xb0000021	78.11011	Closing WSMan Session completed successfuly
0xb0000025	78.11011	Closing WSMan shell failed, error code %1
0xb0000026	78.11011	Closing WSMan command failed, error code %1
0xb0000028	78.11011	Closing WSMan %1 operation failed, error code %2
0xb0000029	8.11011	The WinRM protocol handler has began loading for application %1.
0xb000002a	8.11011	The WinRM protocol handler completed unloading.
0xb000002b	8.11011	The WinRM protocol handler unloaded prematurely due to the following error: %2.
0xb000002c	8.11011	The WinRM protocol handler started to create a session at the following destination: %1.
0xb000002d	8.11011	The WinRM protocol handler closed the session.
0xb000002e	8.11011	The WinRM protocol session closed prematurely due to the following error: %2.
0xb000002f	8.11011	The WinRM protocol session began an operation of type %1 to the server. The operation accesses class %3 under the %2 namespace.
0xb0000030	8.11011	The WinRM protocol session successfully completed the operation.
0xb0000031	8.11011	The WinRM protocol operation failed due to the following error: %2.
0xb0000054	78.11011	The maximum number of users (%1) executing shell operations has been exceeded. Retry after sometime or raise the quota for concurrent shell users.
0xb0000055	78.11011	The %1 user is allowed a maximum number of %2 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user.
0xb0000056	78.11011	The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. Error code %1
0xb0000057	78.11011	The WSMan host process was unexpectedly terminated. Error code %1
0xb000005a	8.11011	RunAs was disabled by Group Policy; WSMan service has erased all RunAs credentials.
0xb000005b	8.11011	Creating WSMan shell on server with ResourceUri: %1
0xb0000083	78.11011	Received redirect status code from Network layer; status: 302 (HTTP_STATUS_REDIRECT); location: %1
0xb0000084	78.11011	WSMan operation %1 completed successfully
0xb0000087	78.11011	Re-sending the request as a result of ERROR_WINHTTP_CANNOT_CONNECT, using next proxy
0xb0000088	78.11011	Re-sending the request as a result of ERROR_WINHTTP_NAME_NOT_RESOLVED, using next proxy
0xb0000089	78.11011	Network layer returned ERROR_WINHTTP_NAME_NOT_RESOLVED - The server name cannot be resolved. Aborting the operation
0xb000008a	78.11011	The client got a timeout from the network layer (ERROR_WINHTTP_TIMEOUT)
0xb000008b	78.11011	The client got a login failure from the network layer (ERROR_WINHTTP_LOGIN_FAILURE)
0xb000008e	78.11011	WSMan operation %1 failed, error code %2
0xb0000091	8.11011	WSMan operation %1 started with resourceUri %2
0xb00000a1	8.11011	%1
0xb00000a2	78.11011	Authenticating the user failed. The credentials didn't work.
0xb00000a3	78.11011	The authentication mechanism (%1) requested by the client is not supported by the server. Possible authentication mechanisms reported by server: %2 %3 %4 %5 %6
0xb00000a4	78.11011	The destination computer (%1) returned an 'access denied' error. Verify your credentials are correct.
0xb00000a5	78.11011	The authentication mechanism requested by the proxy is not supported by the client. The only proxy authentication mechanism supported are Negotiate, Basic or Digest. Possible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5
0xb00000ab	78.11011	Authenticating the user with the proxy failed. The credentials didn't work.
0xb00000ac	78.11011	The server certificate on the destination computer (%1:%2) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10. Fix the server certificate and try again.
0xb00000c0	8.11011	The authorization of the user failed with error %1
0xb00000c1	1011	Request for user %1 (%2) will be executed using WinRM virtual account %3 (%4)
0xb00000d0	78.11011	The Winrm service is starting
0xb00000d1	78.11011	The Winrm service started successfully
0xb00000d2	78.11011	The WinRM service is unable to start because of a failure during initialization. The error code is %1
0xb00000d3	78.11011	The Winrm service is stopping
0xb00000d4	78.11011	The Winrm service was stopped successfully
0xb00000d5	78.11011	The WSMan service could not load current configuration settings as the settings are corrupted. The service is started with default settings instead. User Action Use the following command to restore defaults: winrm invoke Restore winrm/config @{}
0xb00000d6	78.11011	The WSMan client could not load current configuration settings as the settings are corrupted. The client is operating with default settings instead. User Action Start the WinRM service and use the following command to restore defaults: winrm invoke Restore winrm/config @{}
0xb00000d8	8.11011	The WSMan service failed to restart the plugins marked for AutoRestart. The error code received was %1.
0xb00000d9	8.11011	The WSMan service failed to restart the %1 plugin on service startup. The error code received was %2.
0xb00000da	8.11011	The WSMan service successfully restarted the following plugin on service startup: %1.
0xb00000db	8.11011	The WSMan shell instance %1 will no longer support disconnect reconnect functionality because a non-supported request was sent by the client.
0xb00000e0	78.11011	%1
0xb00000e5	8.11011	The WinRM %1 failed to register for group policy change notifications. The error code is %2.
0xb00000e6	8.11011	Deletion of registry key %1 resulted in access denied. If this registry entry is not marked specifically as read only, this seems like a potential issue.
0xb00000fe	8.11011	Activity Transfer
0xb000011b	78.11011	Plug-in reporting context for operation %1
0xb000011c	78.11011	Plug-in reporting data object for operation %1
0xb000011d	78.11011	Plug-in reporting data object and EPR for operation %1
0xb000011e	78.11011	Plug-in reporting data object and bookmark for operation %1
0xb000011f	78.11011	Plug-in reporting data for operation Receive
0xb0000120	78.11011	Plug-in reporting operation complete for %1
0xb0000121	78.11011	Plug-in getting operational information for parameter %1 and operation %2
0xb0000122	78.11011	Plug-in reporting the authorization for user %1 completed with error code %2
0xb0000123	78.11011	Plug-in reporting the authorization operation completed with error %1 for operation %2 and ResourceUri %3
0xb0000124	78.11011	Updating the quota for the user %1 with error code %2 maxAllowedConcurrentShells=%3 maxAllowedConcurrentOperations=%4 timeslotSize=%5 maxAllowedOperationsPerTimeslot=%6
0xb0000134	8.11011	The plugin called WSManPluginGetConfiguration with the parameter %1 and obtained a return value of %2.
0xb0000135	8.11011	The plugin called WSManPluginReportCompletion with the parameter %1 and obtained a return value of %2.
0xb0000136	8.11011	The plugin %1 is being shut down because it was idle for longer than the configured HostIdleTimeoutSecs quota.
0xb0000137	8.11011	Signaling WSMan command failed, error code %1
0xb0000138	8.11011	Signaling WSMan command
0xb0000139	8.11011	Sending input to the command
0xb000013a	8.11011	Sending input to the shell
0xb000013b	8.11011	Sending input operation failed, error code %1
0xb000013c	8.11011	Calling into WSMan to receive output from the shell
0xb000013d	8.11011	WSMan receive operation failed, error code %1
0xb000013e	8.11011	Calling into WSMan to receive output from the command
0xb000013f	8.11011	Getting message for error code %1 completed successfully. The languageCode parameter was: %2
0xb0000140	8.11011	Getting WSMan Session Option (%1) - %2.
0xb0000141	8.11011	Signaling WSMan shell
0xb0000142	8.11011	Signaling WSMan shell, error code %1
0xb0000143	8.11011	Closing WSMan operation
0xb0000144	8.11011	Closing WSMan %1 operation completed successfully
0xb0000145	8.11011	Disconnecting shell with Id : %1
0xb0000146	8.11011	Disconnecting shell failed, error code %1
0xb0000147	8.11011	Reconnecting shell with Id : %1
0xb0000148	8.11011	Reconnecting shell failed, error code %1
0xb0000149	8.11011	Connecting shell with Id : %1
0xb000014a	8.11011	Connecting shell failed, error code %1
0xb000014b	8.11011	Reconnecting shell command with Id : %1
0xb000014c	8.11011	Reconnecting shell command failed, error code %1
0xb000014d	8.11011	Connecting shell command with Id : %1
0xb000014e	8.11011	Connecting shell command failed, error code %1
0xb0000200	8.11011	Auto-detecting proxy settings
0xb0000201	8.11011	Proxy AutoDetect done. Proxy list: %1 Bypass list: %2
0xb0000202	8.11011	Setting proxy info Proxy list: %1 Bypass list: %2
0xb0000303	78.11011	SOAP [client sending index %1 of %2 total chunks (%3 bytes)] %4
0xb0000304	78.11011	SOAP [listener receiving index %1 of %2 total chunks (%3 bytes)] %4
0xb0000306	78.11011	The %1 user is allowed a maximum number of %2 concurrent operations, which has been exceeded. Close existing operations for this user, or raise the quota for this user.
0xb0000307	78.11011	The user load quota of %1 requests per %2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for the %3 user. The next request from this user will not be approved for at least %4 milliseconds.
0xb0000308	78.11011	The system load quota of %1 requests per %2 seconds has been exceeded. Send future requests at a slower rate or raise the system quota. The next request from the user %3 will not be approved for at least %4 milliseconds.
0xb000030c	8.11011	The WinRM %1 has encountered network connectivity issues.
0xb000030d	8.11011	The WinRM Client is attempting to re-establish a network connection.
0xb000030e	8.11011	The WinRM Service has detected a new network connection from the client.
0xb000030f	8.11011	The WinRM %1 has successfully re-established a network connection.
0xb0000310	8.11011	The WinRM %1 failed to re-establish a network connection and is reporting a failure.
0xb0000311	8.11011	The WSMan host process was started for user %1.
0xb0000312	8.11011	The WSMan host process was terminated for user %1.
0xb0000313	8.11011	Sending the request for operation %1 to destination machine and port %2:%3
0xb0000314	8.11011	Processing client request for operation %1
0xb0000315	8.11011	Entering the plugin for operation %1 with a ResourceURI of <%2>
0xb0000316	8.11011	Leaving the plugin for operation %1
0xb0000317	8.11011	The WinRM service failed to enumerate DASH/SMASH specifications with MI error: %1.
0xb0000401	8.11011	Sending response error packet for ActionURI: %1
0xb0000402	78.11011	SOAP [client receiving index %1 of %2 total chunks (%3 bytes)] %4
0xb0000403	78.11011	SOAP [listener sending index %1 of %2 total chunks (%3 bytes)] %4
0xb0000411	78.11011	Enumeration is shutting down
0xb0000413	78.11011	Subscription is shutting down
0xb0000415	8.11011	Received the response from Network layer; status: 200 (HTTP_STATUS_OK)
0xb0000416	8.11011	An extended semantics callback timed out for the %1 operation.
0xb0000417	8.11011	Received the response from Network layer; status: %1
0xb0000418	8.11011	Sending HTTP error back to the client due to a transport failure. The HTTP status code is %1 The error code is %2
0xb0000419	8.11011	Sending timeout response for operation: %1
0xb000041a	8.11011	Sending response for operation %1
0xb000041b	8.11011	Received the response from Network layer; status: %1
0xb000041d	8.11011	WSMan operation %1 got suspended because of WSMan Shell disconnection.
0xb000041e	8.11011	WSMan operation %1 resuming because of WSMan Shell reconnection.
0xb000050b	78.11011	Network layer AutoLogon policy was set to Low as a result of a HTTP 401 response from Network layer
0xb000050c	78.11011	Network layer AutoLogon policy was set to High
0xb000050d	8.11011	The chosen authentication mechanism is %1
0xb000050e	8.11011	Sending HTTP 401 response to the client and disconnect the connection after sending the response
0xb000050f	8.11011	User %1 authenticated successfully using %2 authentication
0xb0000510	8.11011	The authentication using client certificate with subject %1 done successfully
0xb0000511	8.11011	Authenticating the user using %1 mechanism
0xb0000600	8.11011	Authorizing the user
0xb0000601	8.11011	The authorization of the user was done successfully
0xb0000730	78.11011	An error was encountered while processing an operation. Error Code: %1 Error String:%2
0xb0000731	78.11011	An error was encountered while processing an operation. Error Code: %1
0xb0000732	78.11011	Extra information. Refer to the XML parameters for more details.
0xb0000733	8.11011	An unauthenticated connection from client %1 is terminated.
0xb0000800	8.11011	[Filename:- %1; Line:- %2; Function:- %3;] %4
0xb0000801	8.11011	[Filename:- %1; Line:- %2; Function:- %3; ErrorCode:- %4] %5
0xb0010132	78.11011	The WinRM service loaded the following plugin: %1 (%2)
0xb0010133	78.11011	The WinRM service unloaded the following plugin: %1 (%2)
0xc007c403	78.11011	The WinRM service is stopping because there was a failure registering for changes to the IP addresses. User Action Restart the WinRM service. Additional Data The error code was %1.
0xc007c404	78.11011	The WinRM service is stopping because there was a failure registering for changes to the configuration. User Action Restart the WinRM service. Additional Data The error code was %1.
0x803381ff	11	The event source of the push subscription is in disable or inactive on the Event controller server.
0xb000000a	7	Setting WSMan Session Option (%1) with value (%2) completed successfuly
0xb000000b	7	Creating WSMan shell with the ResourceUri: %1
0xb000000d	7	Running WSMan command
0xb0000011	7	Signaling WSMan shell
0xb0000012	7	Signaling WSMan shell, error code %1
0xb0000013	7	Closing WSMan operation
0xb0000014	7	Sending input to the shell
0xb0000015	7	Sending input operation failed, error code %1
0xb0000016	7	Calling into WSMan to receive output from the shell
0xb0000017	7	WSMan receive operation failed, error code %1
0xb0000018	7	Calling into WSMan to receive output from the command
0xb000001a	7	Getting message for error code %1 completed successfully. The languageCode parameter was: %2
0xb000001b	7	Getting WSMan Session Option (%1)
0xb0000020	7	Setting WSMan Session Option (%1) failed, error code %2
0xb0000022	7	Getting message for error code %1 failed, the resulting error code is %2
0xb0000023	7	Signaling WSMan command failed, error code %1
0xb0000024	7	Signaling WSMan command
0xb0000027	7	Closing WSMan %1 operation completed successfully
0xb0000029	7	Sending input to the command
0xb0000040	7	Auto-detecting proxy settings
0xb0000041	7	Proxy AutoDetect done. Proxy list: %1 Bypass list: %2
0xb0000042	7	Setting proxy info Proxy list: %1 Bypass list: %2
0xb0000050	7	Sending the request for operation %1 to destination machine and port %2:%3
0xb0000051	7	Processing client request for operation %1
0xb0000052	7	Entering the plugin for operation %1 with a ResourceURI of <%2>
0xb0000053	7	Leaving the plugin for operation %1
0xb0000081	7	Received the response from Network layer; status: %1
0xb0000082	7	Received the response from Network layer; status: %1
0xb0000085	7	Sending response error packet for ActionURI: %1
0xb0000086	7	Sending response for operation %1
0xb000008c	7	Sending HTTP error back to the client due to a transport failure. The HTTP status code is %1 The error code is %2
0xb000008d	7	Sending timeout response for operation: %1
0xb000008f	7	Received the response from Network layer; status: 200 (HTTP_STATUS_OK)
0xb00000a0	7	Authenticating the user using %1 mechanism
0xb00000a6	7	The chosen authentication mechanism is %1
0xb00000a8	7	Sending HTTP 401 response to the client and disconnect the connection after sending the response
0xb00000a9	7	User %1 authenticated successfully using %2 authentication
0xb00000aa	7	The authentication using client certificate with subject %1 done successfully
0xb00000c0	7	Authorizing the user
0xb00000c1	7	The authorization of the user was done successfully
0xb00000c2	7	The authorization of the user failed with error %1
0xb00000ff	7	Activity Transfer
0xb0000507	7	The destination computer (%1) returned an 'access denied' error. Possible authentication mechanisms reported by server: %2 %3 %4 %5 %6. Verify your credentials are correct.
0x4033c3be	78.1	The WS-Management service cannot process the request.The computed response packet size (%1!lu!) exceeds the maximum envelope size that is allowed (%2!lu!).
0x4033c3f7	7	The WQL query is invalid.
0x4033c3f8	7	Invalid policy setting %1; value must be atleast %3!lu!, but given %2!lu!
0x4033c477	7	WinRM cannot process the request. The following error occured while using %1 authentication: %2 Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
0x4033c487	7	The Windows Remote Shell cannot process the request; the selector value %1 specified in the request was not found.
0x4033c4b0	7	Invalid session option %1; value must be atleast %3!lu!, but given %2!lu!
0x4033c4bd	7	The configuration XML is not valid. Config value length for attribute: "%1" exceeded 1023 characters.
0x4033c4c0	7	The configuration XML is not valid. Attribute value: "%1" is not a valid capability type. Valid capability types are "Get", "Put", "Create", "Delete", "Invoke", "Enumerate", "Subscribe" and "Shell".
0x4033c4c1	7	The configuration XML is not valid. Attribute value: "%1" is not a valid plugin name. Plugin name cannot be empty and cannot exceeded 255 characters. Plugin name should not have any preceding space or tab characters. Plugin name should also not have backslash characters.
0x4033c4d0	7	An error has occured while reading IIS configuration. File: %1 Line: %2 Issue: %3
0x8033803e	7	The metadata that was requested is not available at the current address. Retry with new addresse.
0x80338051	7	The WS-Management service does not support options.
0x8033808e	78.1	The WS-Management client cannot process the request.The event source identity does not match the identity of the machine that the client subscribed to.
0x803380ad	7	The WinRM client cannot process the request. The request must specify only one authentication mechanism. If the flag for 'no authentication' is used, no auhentication mechanism should be specified. Change the request to specify only one authentication mechanism or 'no authentication' and try again.
0x803380cb	7	The WinRM client cannot process the request. The push subcription request contained a delivery transport that is not supported. Only HTTP and HTTPS transports are supported. Change the delivery transport and try the request again.
0x803380db	7	The WinRM client cannot process the request. The port specified in the connnection string is invalid. Valid values are between 1 and 65535. Change the value for port and try the request again.
0x803380e5	7	The WinRM client cannot process the request. Default credentials can be used only with Kerberos authentication or Negotiate authentication under HTTPS if the Allow implicit credentials for Negotiate is specified. Explicit credentials must be provided if any other authentication scheme is specified.
0x8033810c	7	The WinRM client cannot process the request. Kerberos authentication cannot be used if the client computer or the destination computer are not joined to a domain. Specify a different authentication mechanism than Kerberos.
0x80338111	7	The WinRM client sent a request to the remote WS-Management service and got a response saying the request was too large.
0x80338118	7	The WinRM client cannot proces the request, The selector name is invalid, Change the selector name and try the request again.
0x80338126	7	The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled.
0x80338144	7	The WinRM client cannot process the request. A certificate thumbprint was specified together with a user name or password. Only one type of credentials can be specified. Remove the credentials that does not correspond to the authentication mechanism that you indend to use and try the request again.
0x80338148	7	The WinRM client cannot process the request. If you are using a machine certificate, it must contain a DNS name in the Subject Alternative Name extension or in the Subject Name field, and no UPN name. If you are using an user certificate, it must contain an UPN name in the Subject Alternative Name extention, and no DNS name. Change the certificate structure and try the request again.
1300 entries