System Error Codes (12000-15999)
deal with errors. If you are an end-user that is experiencing difficulty with an application you are installing
or running, contact customer support for the software that is displaying the error message. To obtain support
for a Microsoft product, go to
The System Error Codes are very broad. Each one can occur in one of many hundreds of locations in the system.
Consequently the descriptions of these codes cannot be very specific. Use of these codes requires some amount of
investigation and analysis. You need to note both the programmatic and the run-time context in which these errors
occur. Because these codes are defined in WinError.h for anyone to use, sometimes the codes are
returned by non-system software. Sometimes the code is returned by a function deep in the stack and far removed
from your code that is handling the error.
The following list describes
system error codes (errors 12000 to 15999). They are
returned by the GetLastError function when many functions
fail. To retrieve the description text for the error in your application, use the
FormatMessage function with the
12000 – 12175 (0x2EE0)
See Internet Error Codes and
The specified quick mode policy already exists.
The specified quick mode policy was not found.
The specified quick mode policy is being used.
The specified main mode policy already exists.
The specified main mode policy was not found.
The specified main mode policy is being used.
The specified main mode filter already exists.
The specified main mode filter was not found.
The specified transport mode filter already exists.
The specified transport mode filter does not exist.
The specified main mode authentication list exists.
The specified main mode authentication list was not found.
The specified main mode authentication list is being used.
The specified default main mode policy was not found.
The specified default main mode authentication list was not found.
The specified default quick mode policy was not found.
The specified tunnel mode filter exists.
The specified tunnel mode filter was not found.
The Main Mode filter is pending deletion.
The transport filter is pending deletion.
The tunnel filter is pending deletion.
The Main Mode policy is pending deletion.
The Main Mode authentication bundle is pending deletion.
The Quick Mode policy is pending deletion.
The Main Mode policy was successfully added, but some of the requested offers are not supported.
The Quick Mode policy was successfully added, but some of the requested offers are not supported.
IKE authentication credentials are unacceptable.
IKE security attributes are unacceptable.
IKE Negotiation in progress.
General processing error.
Negotiation timed out.
IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a
valid certificate in the appropriate Certificate Store.
IKE SA deleted by peer before establishment completed.
IKE SA deleted before establishment completed.
Negotiation request sat in Queue too long.
Negotiation request sat in Queue too long.
Negotiation request sat in Queue too long.
Negotiation request sat in Queue too long.
No response from peer.
Negotiation took too long.
Negotiation took too long.
Unknown error occurred.
Certificate Revocation Check failed.
Invalid certificate key usage.
Invalid certificate type.
IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates
require a private key. Contact your Network Security administrator about replacing with a certificate that has a
Simultaneous rekeys were detected.
Failure in Diffie-Hellman computation.
Don’t know how to process critical payload.
No policy configured.
Failed to verify signature.
Failed to authenticate using Kerberos.
Peer’s certificate did not have a public key.
Error processing error payload.
Error processing SA payload.
Error processing Proposal payload.
Error processing Transform payload.
Error processing KE payload.
Error processing ID payload.
Error processing Cert payload.
Error processing Certificate Request payload.
Error processing Hash payload.
Error processing Signature payload.
Error processing Nonce payload.
Error processing Notify payload.
Error processing Delete Payload.
Error processing VendorId payload.
Invalid payload received.
Soft SA loaded.
Soft SA torn down.
Invalid cookie received.
Peer failed to send valid machine certificate.
Certification Revocation check of peer’s certificate failed.
New policy invalidated SAs formed with old policy.
There is no available Main Mode IKE policy.
Failed to enabled TCB privilege.
Failed to load SECURITY.DLL.
Failed to obtain security function table dispatch address from SSPI.
Failed to query Kerberos package to obtain max token size.
Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication
will not function. The most likely reason for this is lack of domain membership. This is normal if your computer
is a member of a workgroup.
Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service
Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the
driver does not have the correct filter. Check your policy to verify the filters.
Given filter is invalid.
Memory allocation failed.
Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation
took too long to complete. If the problem persists, reduce the load on the faulting machine.
Invalid Diffie-Hellman group.
Error encrypting payload.
Error decrypting payload.
Policy match error.
Hash verification failed.
Invalid hash algorithm.
Invalid hash size.
Invalid encryption algorithm.
Invalid authentication algorithm.
Invalid certificate signature.
Deleted via RPC call.
Temporary state created to perform reinitialization. This is not a real failure.
The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum
value. Please fix the policy on the peer machine.
The recipient cannot handle version of IKE specified in the header.
Key length in certificate is too small for configured security requirements.
Max number of established MM SAs to peer exceeded.
IKE received a policy that disables negotiation.
Reached maximum quick mode limit for the main mode. New main mode will be started.
Main mode SA lifetime expired or peer sent a main mode delete.
Main mode SA assumed to be invalid because peer stopped responding.
Certificate doesn’t chain to a trusted root in IPsec policy.
Received unexpected message ID.
Received invalid authentication offers.
Sent DoS cookie notify to initiator.
IKE service is shutting down.
Could not verify binding between CGA address and certificate.
Error processing NatOA payload.
Parameters of the main mode are invalid for this quick mode.
Quick mode SA was expired by IPsec driver.
Too many dynamically added IKEEXT filters were detected.
NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel.
Error in assigning inner IP address to initiator in tunnel mode.
Require configuration payload missing.
A negotiation running as the security principle who issued the connection is in progress.
SA was deleted due to IKEv1/AuthIP co-existence suppress check.
Incoming SA request was dropped due to peer IP address rate limiting.
Peer does not support MOBIKE.
SA establishment is not authorized.
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential.
SA establishment is not authorized. You may need to enter updated or different credentials such as a
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This
might be related to certificate-to-account mapping failure for the SA.
The SPI in the packet does not match a valid IPsec SA.
Packet was received on an IPsec SA whose lifetime has expired.
Packet was received on an IPsec SA that does not match the packet characteristics.
Packet sequence number replay check failed.
IPsec header and/or trailer in the packet is invalid.
IPsec integrity check failed.
IPsec dropped a clear text packet.
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.
IPsec dropped a packet due to DoS throttling.
IPsec DoS Protection matched an explicit block rule.
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.
IPsec DoS Protection received an incorrectly formatted packet.
IPsec DoS Protection failed to look up state.
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by
IPsec DoS Protection has not been enabled.
IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of
queues allowed by policy has been reached.
The requested section was not present in the activation context.
The application has failed to start because its side-by-side configuration is incorrect. Please see the
application event log or use the command-line sxstrace.exe tool for more detail.
The application binding data format is invalid.
The referenced assembly is not installed on your system.
The manifest file does not begin with the required tag and format information.
The manifest file contains one or more syntax errors.
The application attempted to activate a disabled activation context.
The requested lookup key was not found in any active activation context.
A component version required by the application conflicts with another component version already
The type requested activation context section does not match the query API used.
Lack of system resources has required isolated activation to be disabled for the current thread of
An attempt to set the process default activation context failed because the process default activation
context was already set.
The encoding group identifier specified is not recognized.
The encoding requested is not recognized.
The manifest contains a reference to an invalid URI.
The application manifest contains a reference to a dependent assembly which is not installed.
The manifest for an assembly used by the application has a reference to a dependent assembly which is not
The manifest contains an attribute for the assembly identity which is not valid.
The manifest is missing the required default namespace specification on the assembly element.
The manifest has a default namespace specified on the assembly element but its value is not
The private manifest probed has crossed a path with an unsupported reparse point.
Two or more components referenced directly or indirectly by the application manifest have files by the same
Two or more components referenced directly or indirectly by the application manifest have window classes
with the same name.
Two or more components referenced directly or indirectly by the application manifest have the same COM
Two or more components referenced directly or indirectly by the application manifest have proxies for the
same COM interface IIDs.
Two or more components referenced directly or indirectly by the application manifest have the same COM type
Two or more components referenced directly or indirectly by the application manifest have the same COM
Two or more components referenced directly or indirectly by the application manifest are different versions
of the same component which is not permitted.
A component’s file does not match the verification information present in the component manifest.
The policy manifest contains one or more syntax errors.
Manifest Parse Error : A string literal was expected, but no opening quote character was found.
Manifest Parse Error : Incorrect syntax was used in a comment.
Manifest Parse Error : A name was started with an invalid character.
Manifest Parse Error : A name contained an invalid character.
Manifest Parse Error : A string literal contained an invalid character.
Manifest Parse Error : Invalid syntax for an xml declaration.
Manifest Parse Error : An Invalid character was found in text content.
Manifest Parse Error : Required white space was missing.
Manifest Parse Error : The character ‘>’ was expected.
Manifest Parse Error : A semi colon character was expected.
Manifest Parse Error : Unbalanced parentheses.
Manifest Parse Error : Internal error.
Manifest Parse Error : Whitespace is not allowed at this location.
Manifest Parse Error : End of file reached in invalid state for current encoding.
Manifest Parse Error : Missing parenthesis.
Manifest Parse Error : A single or double closing quote character (‘ or “) is missing.
Manifest Parse Error : Multiple colons are not allowed in a name.
Manifest Parse Error : Invalid character for decimal digit.
Manifest Parse Error : Invalid character for hexadecimal digit.
Manifest Parse Error : Invalid unicode character value for this platform.
Manifest Parse Error : Expecting whitespace or ‘?’.
Manifest Parse Error : End tag was not expected at this location.
Manifest Parse Error : The following tags were not closed: %1.
Manifest Parse Error : Duplicate attribute.
Manifest Parse Error : Only one top level element is allowed in an XML document.
Manifest Parse Error : Invalid at the top level of the document.
Manifest Parse Error : Invalid xml declaration.
Manifest Parse Error : XML document must have a top level element.
Manifest Parse Error : Unexpected end of file.
Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal
Manifest Parse Error : Element was not closed.
Manifest Parse Error : End element was missing the character ‘>’.
Manifest Parse Error : A string literal was not closed.
Manifest Parse Error : A comment was not closed.
Manifest Parse Error : A declaration was not closed.
Manifest Parse Error : A CDATA section was not closed.
Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string “xml”.
Manifest Parse Error : System does not support the specified encoding.
Manifest Parse Error : Switch from current encoding to specified encoding not supported.
Manifest Parse Error : The name ‘xml’ is reserved and must be lower case.
Manifest Parse Error : The standalone attribute must have the value ‘yes’ or ‘no’.
Manifest Parse Error : The standalone attribute cannot be used in external entities.
Manifest Parse Error : Invalid version number.
Manifest Parse Error : Missing equals sign between attribute and attribute value.
Assembly Protection Error : Unable to recover the specified assembly.
Assembly Protection Error : The public key for an assembly was too short to be allowed.
Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly’s
An HRESULT could not be translated to a corresponding Win32 error code.
Assembly Protection Error : The catalog for an assembly is missing.
The supplied assembly identity is missing one or more attributes which must be present in this context.
The supplied assembly identity has one or more attribute names that contain characters not permitted in XML
The referenced assembly could not be found.
The activation context activation stack for the running thread of execution is corrupt.
The application isolation metadata for this process or thread has become corrupt.
The activation context being deactivated is not the most recently activated one.
The activation context being deactivated is not active for the current thread of execution.
The activation context being deactivated has already been deactivated.
A component used by the isolation facility has requested to terminate the process.
A kernel mode component is releasing a reference on an activation context.
The activation context of system default assembly could not be generated.
The value of an attribute in an identity is not within the legal range.
The name of an attribute in an identity is not within the legal range.
An identity contains two definitions for the same attribute.
The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes,
missing attribute name or missing attribute value.
A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by
something other than a left parenthesis or another dollar sign or an substitution’s right parenthesis was not
The public key token does not correspond to the public key specified.
A substitution string had no mapping.
The component must be locked before making the request.
The component store has been corrupted.
An advanced installer failed during setup or servicing.
The character encoding in the XML declaration did not match the encoding used in the document.
The identities of the manifests are identical but their contents are different.
The component identities are different.
The assembly is not a deployment.
The file is not a part of the assembly.
The size of the manifest exceeds the maximum allowed.
The setting is not registered.
One or more required members of the transaction are not present.
The SMI primitive installer failed during setup or servicing.
A generic command executable returned a result that indicates failure.
A component is missing file verification information in its manifest.
The specified channel path is invalid.
The specified query is invalid.
The publisher metadata cannot be found in the resource.
The template for an event definition cannot be found in the resource (error = %1).
The specified publisher name is invalid.
The event data raised by the publisher is not compatible with the event template definition in the
The specified channel could not be found. Check channel configuration.
The specified xml text was not well-formed. See Extended Error for more details.
The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel
go directly to a logfile and cannot be subscribed to.
The query result is stale / invalid. This may be due to the log being cleared or rolling over after the
query result was created. Users should handle this code by releasing the query result object and reissuing the
Query result is currently at an invalid position.
Registered MSXML doesn’t support validation.
An expression can only be followed by a change of scope operation if it itself evaluates to a node set and
is not already part of some other change of scope operation.
Can’t perform a step operation from a term that does not represent an element set.
Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand
side arguments must be constants.
A step operation must involve either a node test or, in the case of a predicate, an algebraic expression
against which to test each node in the node set identified by the preceeding node set can be evaluated.
This data type is currently unsupported.
A syntax error occurred at position %1!d!.
This operator is unsupported by this implementation of the filter.
The token encountered was unexpected.
The requested operation cannot be performed over an enabled direct channel. The channel must first be
disabled before performing the requested operation.
Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can’t
be updated or is not supported by this type of channel.
Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range,
can’t be updated or is not supported by this type of publisher.
The channel fails to activate.
The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple
the message resource is present but the message is not found in the string/message table.
The message id for the desired message could not be found.
The substitution string for insert index (%1) could not be found.
The description string for parameter reference (%1) could not be found.
The maximum number of replacements has been reached.
The event definition could not be found for event id (%1).
The locale specific resource for the desired message is not present.
The resource is too old to be compatible.
The resource is too new to be compatible.
The channel at index %1!d! of the query can’t be opened.
The publisher has been disabled and its resource is not avaiable. This usually occurs when the publisher is
in the process of being uninstalled or upgraded.
Attempted to create a numeric type that is outside of its valid range.
The subscription fails to activate.
The log of the subscription is in disabled state, and can not be used to forward events to. The log must
first be enabled before the subscription can be activated.
When forwarding events from local machine to itself, the query of the subscription can’t contain target log
of the subscription.
The credential store that is used to save credentials is full.
The credential used by this subscription can’t be found in credential store.
No active channel is found for the query.
The resource loader failed to find MUI file.
The resource loader failed to load MUI file because the file fail to pass validation.
The RC Manifest is corrupted with garbage data or unsupported version or missing required item.
The RC Manifest has invalid culture name.
The RC Manifest has invalid ultimatefallback name.
The resource loader cache doesn’t have loaded MUI entry.
User stopped resource enumeration.
UI language installation failed.
Locale installation failed.
A resource does not have default or neutral value.
Invalid PRI config file.
Invalid file type.
Invalid qualifier value.
No Candidate found.
The ResourceMap or NamedResource has an item that does not have default or neutral resource..
Invalid ResourceCandidate type.
Duplicate Resource Map.
Invalid Resource Identifier.
Filepath too long.
Unsupported directory type.
Invalid PRI File.
NamedResource Not Found.
ResourceMap Not Found.
Unsupported MRT profile type.
Invalid qualifier operator.
Unable to determine qualifier value or qualifier value has not been set.
Automerge is enabled in the PRI file.
Too many resources defined for package.
The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or
MCCS 2 Revision 1 specification.
The monitor’s VCP Version (0xDF) VCP code returned an invalid version value.
The monitor does not comply with the MCCS specification it claims to support.
The MCCS version in a monitor’s mccs_ver capability does not match the MCCS version the monitor reports when
the VCP Version (0xDF) VCP code is used.
The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0
specification or the MCCS 2.0 Revision 1 specification.
An internal Monitor Configuration API error occurred.
The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor
technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1
The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not
support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
The requested system device cannot be identified due to multiple indistinguishable devices potentially
matching the identification criteria.
The requested system device cannot be found.
Hash generation for the specified hash version and hash type is not enabled on the server.
The hash requested from the server is not available or no longer valid.
The secondary interrupt controller instance that manages the specified interrupt is not registered.
The information supplied by the GPIO client driver is invalid.
The version specified by the GPIO client driver is not supported.
The registration packet supplied by the GPIO client driver is not valid.
The requested operation is not suppported for the specified handle.
The requested connect mode conflicts with an existing mode on one or more of the specified pins.
The interrupt requested to be unmasked is not masked.
The requested run level switch cannot be completed successfully.
The service has an invalid run level setting. The run level for a service must not be higher than the run
level of its dependent services.
The requested run level switch cannot be completed successfully since one or more services will not stop or
restart within the specified timeout.
A run level switch agent did not respond within the specified timeout.
A run level switch is currently in progress.
One or more services failed to start during the service startup phase of a run level switch.
The task stop request cannot be completed immediately since task needs more time to shutdown.
Package could not be opened.
Package was not found.
Package data is invalid.
Package failed updates, dependency or conflict validation.
There is not enough disk space on your computer. Please free up some space and try again.
There was a problem downloading your product.
Package could not be registered.
Package could not be unregistered.
User cancelled the install request.
Install failed. Please contact your software vendor.
Removal failed. Please contact your software vendor.
The provided package is already installed, and reinstallation of the package was blocked. Check the
AppXDeployment-Server event log for details.
The application cannot be started. Try reinstalling the application to fix the problem.
A Prerequisite for an install could not be satisfied.
The package repository is corrupted.
To install this application you need either a Windows developer license or a sideloading-enabled
The application cannot be started because it is currently updating.
The package deployment operation is blocked by policy. Please contact your system administrator.
The package could not be installed because resources it modifies are currently in use.
The package could not be recovered because necessary data for recovery have been corrupted.
The signature is invalid. To register in developer mode, AppxSignature.p7x and
AppxBlockMap.xml must be valid or should not be present.
An error occurred while deleting the package’s previously existing application data.
The package could not be installed because a higher version of this package is already installed.
An error in a system binary was detected. Try refreshing the PC to fix the problem.
A corrupted CLR NGEN binary was detected on the system.
The operation could not be resumed because necessary data for recovery have been corrupted.
The package could not be installed because the Windows Firewall service is not running. Enable the Windows
Firewall service and try again.
The process has no package identity.
The package runtime information is corrupted.
The package identity is corrupted.
The process has no application identity.
Loading the state store failed.
Retrieving the state version for the application failed.
Setting the state version for the application failed.
Resetting the structured state of the application failed.
State Manager failed to open the container.
State Manager failed to create the container.
State Manager failed to delete the container.
State Manager failed to read the setting.
State Manager failed to write the setting.
State Manager failed to delete the setting.
State Manager failed to query the setting.
State Manager failed to read the composite setting.
State Manager failed to write the composite setting.
State Manager failed to enumerate the containers.
State Manager failed to enumerate the settings.
The size of the state manager composite setting value has exceeded the limit.
The size of the state manager setting value has exceeded the limit.
The length of the state manager setting name has exceeded the limit.
The length of the state manager container name has exceeded the limit.
This API cannot be used in the context of the caller’s application type.
If you have additional suggestions regarding the
System Error Codes documentation, given the
constraints enumerated at the top of the page, please click the link labeled
“Send comments about this topic to Microsoft” below. We appreciate the input.
|Minimum supported client||Windows XP [desktop apps only]|
|Minimum supported server||Windows Server 2003 [desktop apps only]|