sxs.dll

Associated Error Codes

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

CodeFound inDescription
0xc101000178.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple top-level ASSEMBLY elements found.
0xc101000278.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000378.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000478.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000578.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000678.11011MSG_SXS_ABANDONED167
0xc101000778.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000878.11011MSG_SXS_ABANDONED182
0xc101000978.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest file root element must be assembly.
0xc101000a78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The application config file root element must be configuration.
0xc101000b78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest assembly element is missing the required manifestVersion attribute.
0xc101000c78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The value specified for the manifest assembly element manifestVersion attribute is not currently supported.
0xc101000d78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000e78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101000f78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101001078.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Call to installation callback failed; %1
0xc101001178.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101001278.11011Invalid disposition returned from file copy callback: %1
0xc101001378.11011The %1 hash of file %2 does not match the manifest
0xc101001478.11011MSG_SXS_ABANDONED283
0xc101001578.11011The manifest %1 does not match its source catalog or the catalog is missing.
0xc101001678.11011Dll redirector contributor unable to assign assembly path; %1
0xc101001778.11011The manifest store for assembly %1 is missing
0xc101001878.11011Activation context generation failed for "%11". Dll redirector contributor unable to add file map entry for file %1; %2
0xc101001978.11011%1() called with unhandled reason %2
0xc101001a78.11011MSG_SXS_ABANDONED331
0xc101001b78.11011MSG_SXS_ABANDONED338
0xc101001c78.11011MSG_SXS_ABANDONED345
0xc101001d78.11011MSG_SXS_ABANDONED352
0xc101001e78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101001f78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101002078.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13.
0xc101002178.11011Activation context generation failed for "%11". Dependent Assembly %1 could not be found. Please use sxstrace.exe for detailed diagnosis.
0xc101002278.11011Activation context generation failed for "%11". The application failed to launch because of an invalid manifest.
0xc101002378.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Component identity found in manifest does not match the identity of the component requested. Reference is %1. Definition is %2. Please use sxstrace.exe for detailed diagnosis.
0xc101002478.11011The assembly %1 contained one or more invalid files but has been sucessfully restored.
0xc101002578.11011The assembly %1 has missing or invalid files; recovery of this assembly failed.
0xc101002678.11011The assembly %1 was moved to %2 because it was detected to be invalid.
0xc101002778.11011The assembly %1 was not able to be moved because of the error %2.
0xc101002878.11011The file %1 is not a member of the assembly %2 but it was not able to be removed.
0xc101002978.11011The file %1 is not a member of the assembly %2 so it was deleted.
0xc101002a78.11011A System File Protection validation request could not be queued for the directory %1.
0xc101002b78.11011MSG_SXS_ABANDONED481
0xc101002c78.11011MSG_SXS_ABANDONED489
0xc101002d78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest contains a non-empty tag.
0xc101002e78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest contains a non-empty tag.
0xc101002f78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest contains multiple tags; it must have zero or one.
0xc101003078.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The policy contains a tag, but only manifests may have these.
0xc101003178.11011MSG_SXS_ABANDONED534
0xc101003278.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The bindingRedirect element is only permitted in component configuration manifests.
0xc101003378.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The bindingRedirect element requires both oldVersion and newVersion attributes.
0xc101003478.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. A component configuration manifest contains more than one dependentAssembly element.
0xc101003578.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. An application configuration manifest contains more than one dependentAssembly element for configuring the same assembly identity.
0xc101003678.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. An application configuration manifest contains a dependentAssembly element which is missing its assemblyIdentity subelement.
0xc101003778.11011Installing the assembly %1 into the public side-by-side store requires it to have a catalog.
0xc101003878.11011The signer %1 of the assembly %2 was too short - minimal key length is 2048 bits.
0xc101003978.11011The signing key for catalog %1 does not match the assembly publisher %2`s public key token %3.
0xc101003a78.11011Win32 Error Message : %1
0xc101003b78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Invalid Xml syntax.
0xc101003c78.11011%1 failed for %2.
0xc101003d78.11011Assembly under %1 could not be installed because manifest is missing.
0xc101003e78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The required attribute %2 is missing from element %1.
0xc101003f78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The value "%3" of attribute "%2" in element "%1" is invalid.
0xc101004078.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The attribute %2 is not permitted in this context on element %1.
0xc101004178.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The root or application manifest contains the noInherit element but the dependent assembly manifest does not contain the noInheritable element. Application manifests which contain the noInherit element may only depend on assemblies which are noInheritable.
0xc101004278.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest contains multiple noInheritable elements.
0xc101004378.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The manifest defines multiple identities for this assembly or application.
0xc101004478.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. In element %1 the value of attribute %2 must either be yes or no.
0xc101004578.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple dependentAssembly elements within one dependency element.
0xc101004678.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple assemblyIdentity elements within one dependentAssembly element.
0xc101004778.11011Activation context generation failed for "%11". Version overlap with previous version redirection while parsing policy file %1 where oldVersion is %2 and newVersion is %3.
0xc101004878.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The element %1 appears as a child of element %2 which is not supported by this version of Windows.
0xc101004978.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The element %1 may only appear before the %2 element.
0xc101004a78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The requestedPrivileges element is not allowed in component manifest.
0xc101004b78.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple requestedPrivileges elements are not allowed in manifest.
0xc101004c8.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The application element is not allowed in component manifest.
0xc101004d8.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Assemblies that require branch version logic can not be privately deployed.
0xc101004e8.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: %1. Component 2: %2.
0xc101004f8.11011Activation context generation failed for "%11". The setting %1 is not registered.
0xc10100508.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Application configuration specified an invalid private-assembly probing path. The invalid probing path was part of %1.
0xc10100518.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The element %1 appears as a child of element %2 which is not supported except in desktop applications.
0xc10100528.11011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The attribute %1 is not permitted except in desktop applications on element %2.
0xc10100538.11011Activation context generation failed for "%11". Dependent Assembly %1 could not be found. Centrally-installed dependencies are not processed except in desktop applications. Please use sxstrace.exe for detailed diagnosis.
0xc10100541011Activation context generation failed for "%11". The COM class threadingModel must be specified in this type of application and cannot be set to 'Single'.
0xc10100551011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The msix element is not allowed in component manifest.
0xc10100561011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple msix elements are not allowed in manifest.
0xc10100571011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The msix publisher must be valid according to MSIX packaging rules.
0xc10100581011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The msix packageName must be valid according to MSIX packaging rules.
0xc10100591011Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The msix applicationId must be valid according to MSIX packaging rules.
0xc101005a11Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The msix optionalIdentityPolicy must be 'defaultEnabled'; 'defaultDisabled'; or unspecified; and is not supported below 'urn:schemas-microsoft-com:msix.v2'.
0xc101004c7Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The compatibilityInfo element is not allowed in component manifest.
0xc101004d7Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Multiple compatibilityInfo elements are not allowed in manifest.
0xc101004e7Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. The application element is not allowed in component manifest.
0xc101004f7Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Assemblies that require branch version logic can not be privately deployed.
0xc10100507Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: %1. Component 2: %2.
0xc10100517Activation context generation failed for "%11". The setting %1 is not registered.
0xc10100527Activation context generation failed for "%11".Error in manifest or policy file "%12" on line %13. Application configuration specified an invalid private-assembly probing path. The invalid probing path was part of %1.
0xc10100548.1Activation context generation failed for "%11". The COM class threadingModel must be specified in this type of application, and cannot be set to 'Single'.
98 entries