MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  ݵ@.rsrc@@00H `x     8̫MUIQb#DJve˦=[`> MUI en-US!AppX Deployment Service (AppXSVC)Provides infrastructure support for deploying Store applications. This service is started on demand and if disabled Store applications will not be deployed to the system, and may not function properly.N   11L 00p PP  ,,./12D6D<MOd"P(E O4UV ` c d(i02 sXhtL &ԡ+6 h( TP<@P $'D))|9EGK,MW2 ,=dh`B\GLLQY`\bqe0t  xz{}LM(FG8xx<@A|@''d.м DAppXDeploymentServer Keyword \VisualElements Extension Handler Keyword $OSIM Keyword HState Extension Handler Keyword PAutoPlay Extension Handler Keyword dCollectorExtension Extension Handler Keyword `ActivatableClass Extension Handler Keyword HGame Extension Handler Keyword PFileType Extension Handler Keyword HTrust Extension Handler Keyword PLicensing Extension Handler Keyword XCertificates Extension Handler Keyword PAppX Base Extension Handler Keyword PProtocol Extension Handler Keyword HMoCOM Extension Handler Keyword LRuntime Extension Handler Keyword \BackgroundTasks Extension Handler Keyword PDownload Extension Handler Keyword LAppXDeploymentServerPerf Keyword DMrt Extension Handler Keyword DDSM Extension Handler Keyword PPackage Runtime Information Keyword `RestrictedLaunch Extension Handler Keyword XDeviceAccess Extension Handler Keyword PIndexedDB Extension Handler Keyword XMSAC SignOut Extension Handler Keyword XSearchIndexer Extension Handler Keyword LAppSync Extension Handler Keyword TApply Data Extension Handler Keyword HAlarm Extension Handler Keyword TGeolocation Extension Handler Keyword $Response Time Info Start Stop Error Warning Information XMicrosoft-Windows-AppXDeployment-Server lMicrosoft-Windows-AppXDeploymentServer/Diagnostic pMicrosoft-Windows-AppXDeploymentServer/Operational dMicrosoft-Windows-AppXDeploymentServer/Debug lMicrosoft-Windows-AppXDeploymentServer/Restricted error %3: Cannot register the %1 package due to the following error: %2. error %3: Cannot de-register the %1 package due to the following error: %2. error %1: While preparing to process the request, the system failed to register the %3 extension due to the following error: %2. %1: While preparing to register the request, the system failed to register the %3 extension due to the following error: %2. error %1: While processing the request, the system failed to register the %3 extension due to the following error: %2. error %1: Cannot register the request because the following error was encountered while initializing the %3 extension: %2. error %1 : Cannot register the request because the following error was encountered while creating the %3 extension: %2. Injected a failure on evaluate due to the following error: %2 (%1). Injected a failure on commit due to the following error: %2 (%1). error %1: While removing the request, the system failed to de-register the %3 extension due to the following error: %2. error %1: While reverting the request, the system failed to de-register the %3 extension due to the following error: %2. error %1: Cannot register the request because the following error was encountered during the registration of the %3 extension: %2. %1(%2,%3): warning: The '%5' extension category in the %4 package is unrecognized. (error %3: Cannot register the %1 package because the following error was encountered while determining the level of trust for the package: %2. Lerror %3: Cannot register the %1 package because the following error was encountered: %2. Verify that the package's 'resources.pri' file in the package is valid. ,error %3: Cannot register the %1 package because the following error was encountered while determining whether the package identity is valid: %2. error %3: Cannot register the %1 package because the following error was encountered while determining the package's root location: %2. error %3: Cannot register the %1 package because the following error was encountered while trying to read the package: %2. error %3: Cannot register the %1 package because the following error was encountered while reading the package repository: %2. error %1: Failed to load the extension DLL due to the following error: %2. x%1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while determining whether the %7 string resource could be localized: %6. Check that the string resource is defined and that there is at least one instance defined in the resources.pri file contained in this package. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while determining whether the %7 file resource could be localized: %6. Check sure that the file resource is defined and that there exists at least one instance defined in the resources.pri file contained in this package. error %1: An unexpected error occurred while refreshing the shell after a fileType association or protocol change. Deployment %1 operation on Package %2 from: %3 finished successfully. LDeployment %1 operation on Package %2 from: %3 failed with error %4. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. error %2: Reading manifest from location: %1 failed with error: %3. lerror %2: Failure to get staging session for: %1. error %2: AppX Deployment operation failed. The specific error text for this failure is: %1 error %2: Opening file from location: %1 failed with error: %3. Windows cannot register the package %1 because the specified value from the DeploymentOptions enumeration is DevelopmentMode. DevelopmentMode is not allowed when registering framework or resource packages. If this is meant to be an app package, remove the framework or resource attribute from the properties element in the AppXManifest.xml. Otherwise, do not specify DevelopmentMode. `The current user has already installed an unpackaged version of this app. A packaged version cannot replace this. The conflicting package is %1 and it was published by %2. Another user has already installed an unpackaged version of this app. The current user cannot replace this with a packaged version. The conflicting package is %1 and it was published by %2. `The current user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is %1 and it was published by %2. XAnother user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is %1 and it was published by %2. Windows cannot install package %1 because this package requires a higher Windows version. The package requested Windows version %2.%3 with AppModel version %4, while the current Windows version is %5.%6 with AppModel version %7. error %2: Deployment of package %1 was blocked by AppLocker. $Deployment of package %1 failed because no valid license or sideloading policy could be applied. A developer license (http://go.microsoft.com/fwlink/?LinkId=233074) or enterprise sideloading configuration (http://go.microsoft.com/fwlink/?LinkId=231020) may be required. Checking whether deployment is in developer mode because package %1 is unsigned. The check for the origin of package %1 returned %2 origin. The check for enterprise qualifications to approve package %1 returned %2. The check for a developer license to approve package %1 returned %2. error %2: The package %1 being removed cannot be automatically closed; some part of the package may exist temporarily. error %2: Unable to install because the following apps need to be closed %1. Windows cannot install package %1 because this package depends on another package that could not be found. This package requires minimum version %4 of framework %2 published by %3 to install. Provide the framework along with this package. Package %1 requires minimum version %4 of framework %2 published by %3 to install. The cross-architecture framework was not found. Windows cannot install framework %1 because it declares a dependency. Frameworks are not allowed to declare any dependencies. Remove the dependency element in order to install the framework. Windows cannot register package %1 because it is in development mode and the package is already installed. Increment the version number of the package to be registered, or remove the old package for every user on the system before registering this package. pWindows cannot remove framework %1 because package(s)%2 currently depends on the framework. Removing all packages that depend on the framework automatically removes the framework. Windows cannot install package %1 because it has version %2. A higher version %3 of this package is already installed. Windows cannot install package %1 because package %2 was provided but not used. This could be because package %1 does not depend on %2. Only the packages that package %1 depends on can be installed. (Windows cannot install package %1 because a different package %2 with the same name is already installed. Remove package %2 before installing. Windows cannot update package %1 because the previous version is not installed. Install package %1 instead of updating it. |Windows cannot install package %1 because it depends on another package with the same name. Ensure that the package has a name that is different from all frameworks that it depends on. Windows cannot install package %1 because the package requires architecture %2, but this computer has architecture %3. hWindows cannot install package %1 because this package depends on another package that couldn't be found. This package requires minimum version %4 of framework %2 published by %3 to install; the frameworks with name %2 available to the user are %5. Provide the correct framework along with this package. Package %1 requires minimum version %4 of framework %2 published by %3 to install. The cross-architecture framework was not found. The frameworks with name %2 available to the user are %5. Package %1 requires minimum version %4 of framework %2 published by %3 to install. The cross-architecture framework was not found. No frameworks with the name %2 are available to the user. pWindows cannot install resource package %1 because the app package it requires could not be found. Ensure that the app package is installed before installing the resource package Framework %1 is no longer explicitly installed but remains implicitly installed because packages still depend on it. Windows will automatically remove the framework when no other packages depend on it. Package %1 with %2 origin cannot be installed using developer mode option. The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy. `error %2: Creating DataSource to %1 failed. Terror %2: Creating folder %1 failed. Perror %2: Creating file %1 failed. pWriting to file %1 at offset %2 of size %3 failed. \error %2: Hard linking to file %1 failed. xerror %2: Opening the package from location %1 failed. error %2: Creating the package metadata directory %1 failed. error %2: Setting file attributes for package metadata directory %1 failed. derror %2: Failed to set access rights to %1. Integrity check failed for file %1. The integrity state is: %2. error %3: Package update failed for %1. Re-stage package %2. Perror %2: Deleting file %1 failed. `Moving package folder %1 to %2. Result: %3. |Failed to read signature of already-installed package %2 with error %1; installation is assumed to be corrupted. Deployment will proceed with a full restage using the provided package. `Deployment of package %1 was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package. Service is being shut down forcefully while still executing a deployment request. Please cancel all pending and running deployment requests before shutting down the service or before rebooting a machine. Executing deployment request count: %1. Request queue length: %2. LazyFlush queue length: %3. IdleTasksInProgress: %4. pHard linking file %1 to %2 failed with HRESULT %3. derror %3: Failed to delete %2 for package %1. XSuccessfully deleted %2 for package %1. The file system entries for package %1 could not be cleaned up after reboot. The package is removed from the purge list. error %1: Windows cannot process a deployment operation because the package repository database encountered an ESENT error. Use the Reset Your PC feature to recover your PC. See the Application event log for messages with ESENT as the event source for more details. (error %1: ESENT error reported. The repository database could not be found. Package Manager will create a new repository. This event can be ignored, unless a repository was previously present, in which case you should use the Refresh Your PC feature to recover your apps. |error %2: Failed to create package repository folder %1. Started bytecode generation for package %1 on %2-bit architecture. Finished bytecode generation for package %1 on %2-bit architecture. %3: Failed to generate bytecode for package %1 on %2-bit architecture. Failed to generate bytecode for %3 JS files in package %1 on %2-bit architecture. File %2 in package %1 is missing the UTF-8 BOM. Skipping bytecode generation for this file. Script error occurred in file %2 in package %1 at line: %5 column: %6. ErrorText: %3. ErrorDescription: %4. File %2 in package %1 could not be validated from the package blockmap. Skipping bytecode generation for this file. ByteCodeGenerator process terminated with exit code %2 for package %1. %3: Failed to generate bytecode for %2 in package %1. Skipping bytecode generation for this file. Bytecode for file %2 in package %1 can only be generated at runtime. Skipping the file. Bytecode generation for package %1 on %2-bit architecture got cancelled because of a new deployment operation. ByteCodeGenerator process for package %1 did not shutdown in time. Wait Result :%2. Valid bytecode file %2 is already present for package %1; so bytecode generation is unnecessary. |Staging roaming data for package %2 failed with error %1. Not staging roaming data for package %1. The application state is already present. Establishing the sync relationship for package %2 failed with error %1. The package %1 was installed for the current user. This package will be recovered. error %3: Unable to recover this package %1 for the current user. Reading file %2 failed. Identified %1 request(s) in the Queue Store for potential restoration. pStarted deployment %1 operation on a package with main parameter: %2 and Options: %3. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. Started deployment %1 operation on a package with main parameter: %2, dependency parameters: %3 and Options: %4. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. The last successful state reached was %1. Failure occurred before reaching the next state %2. `error %2: Unable to write recovery file %1. Deployment %1 operation on package %2 has been de-queued and is running for user %3\%4. Unable to recover package %1 because it does not have any .recovery files. Recovering DeploymentRequest from file %4 for %1 Operation on Package %2. Resuming from state %3. error %2: Recovering DeploymentRequest from file %1 failed. lFailed flushing deployment data with result: %1. Could not contact Process Lifetime Management to ensure that no apps are running during servicing. PAdding uri to the list of Uris: %1. TBundle Uri %1 contains packages: %2. Deployment %1 operation on package %2 has been cancelled by the caller. hRelaunching app %1 after the app was serviced. Unable to install %1 because the same package %2 is specified multiple times. Each package specified needs to be unique. Unable to install %1 because %2 dependencies were specified. The maximum number of allowed dependencies is %3. 0Windows cannot remove %1 because the current user does not have that package installed. Use Get-AppxPackage to see the list of packages installed. (Windows cannot install %1 because this package has multiple dependencies on the same package %2. Remove all redundant dependency declarations. Unable to install because of an unknown error %1 in determining which apps need to be closed. Windows cannot deploy to path %1 of file system type %2. The path must be located on an NTFS volume. |error %2: Windows cannot access deployment target at %1. herror %4: AppX Deployment %1 operation on package %2 from: %3 failed. This app is part of Windows and cannot be uninstalled on a per-user basis. An administrator can attempt to remove the app from the computer using Turn Windows Features on or off. However, it may not be possible to uninstall the app. 0Deployment %1 operation rejected on package %2 from: %3 install request because the Local System account is not allowed to perform this operation. Rejecting a request to register from %1 because the manifest is not in the package root. |The AppModel version could not be read from the registry. 8Rejecting a request to register from %1 because the files are on a network share. Copy the files to the local computer before registering the package. 8Windows cannot perform the %1 operation because it could not find %2 in the repository. Make sure %2 has been staged or was installed by another user. Windows cannot register %1 because this bundle was passed in as dependency package. Bundles must be specified in the main package argument. tWindows cannot register the bundle %1 because the specified value from the DeploymentOptions enumeration is DevelopmentMode. DevelopmentMode is not allowed when registering bundles. Windows cannot install from %1 because the AllResources DeploymentOption has been set and this package is not a bundle. The AllResources option is only meaningful for bundles and does not make sense in the context of a package. Unable to install bundle %2 because it does not have an appropriate application package for %1 architecture. Windows cannot remove %1 because the PreserveApplicationData flag can only be used on a package that was deployed in development mode. XFailed to initialize PLM with error %1. tDeployment was cancelled after failure with error %1. $The specified package full name %1 is not eligible for a StageUserDataAsync call. The operation cannot be performed on an installed package. StageUserDataAsync cannot be called for package %1 which was deployed in development mode. hWindows cannot install package %1 because this package declares mismatched Windows versions. The requested mininimum and maximum version tested must be identical. The package requested Windows version %2.%3 with AppModel version %4, with the max tested Windows version is %5.%6 with AppModel version %7. Windows cannot install package %1 because this package declares invalid Windows versions. The package requested Windows version %2.%3 with AppModel version %4, but the max tested Windows version is %5.%6 with AppModel version %7. Windows cannot find the main package manifest in the bundle file: %1. Windows cannot find the resource package manifest in the bundle file: %1. error %2: Unable to relaunch app %1 after the app was serviced. error %2: Unable to notify pre-launch service for app %1 install/uninstall. Unable to install %1 because %2 framework dependencies were specified. The maximum number of allowed framework dependencies is %3. Unable to install %1 because %2 resource dependencies were specified. The maximum number of allowed resource dependencies is %3. tThe check for how %1 applies to user %2 returned %3. xThe check for how %1 applies to user %2 failed with %3. TInvalid dependencies were specified. Package Manager aborted the %1 operation because an invalid argument was passed: %2. pCreation of registry key: %1 failed with error: %2. hOpening registry key: %1 failed with error: %2. pDeletion of registry key: %1 failed with error: %2. Registry copy of tree for package: %1 failed with error: %2. Failed to read the value named %2 from registry key: %1 with error: %3 Failed to write the value named %2 from registry key: %1 with error: %3. Package(s) with the following package full names were not registered due to sideloading policy restrictions: %1 Unable to determine whether package %2 is an all user package with error: %1 Unable to update all user store with package %2 with error: %1 tSuccessfully updated all user store with package %1. pOpening registry key: %1\\%2 failed with error: %3. tCreating registry key: %1\\%2 failed with error: %3. Failed to write the value named %3 with value %4 in registry key %1\\%2 failed with error: %3. Package %1 was moved to the Deleted store after reaching the max number of deployment attempts with error: %2. Determining packages to be installed during logon for user: %1. The following packages will be installed: %1. The following packages will be removed: %2 Unable to determine packages to be installed during logon with error: %1. During-logon registration of package %2 for user %1 finished with result: %3; updating registry... Updating registry for package %2 completed with result: %1. PStarted activating the %1 package. PFinished activating the %1 package. TStarted deactivating the %1 package. TFinished deactivating the %1 package. \Started parsing the %1 package manifest. \Finished parsing the %1 package manifest. Started conflict resolution on %1 package for extension %2 and %3 key. Finished conflict resolution on %1 package for extension %2 and %3 key. |Started an evaluate of the request for the %1 extension. |Finished an evaluate of the request for the %1 extension. pStarted removing the request for the %1 extension. pFinished removing the request for the %1 extension. tStarted committing the request for the %1 extension. tFinished committing the request for the %1 extension. TStarted a call to dependency manager xFinished a call from dependency manager with error: %1 Starting to setup the firewall for the %1 package with %2 binaries. Completed setting up the firewall for the %1 package with %2 error code. Starting to setup device capabilities for the %1 package with %2 friendly-name device capabilities. Completed setting up the device capabilities for the %1 package with %2 error code. Starting to create the AppContainer profile for the %1 package. Completed creating the AppContainer profile for the %1 package with %2 error code. Starting to create the repository metadata for the %1 package. Completed creating the repository metadata for the %1 package by %2 error code. XAbout to call CreateDataSource with %1 `Finished call from CreateDataSource for %1 Begin delta diff calculation for package update: %1 staging to %2 with base package in %3 End delta diff calculation for package update: %1 staging to %2 with base package in %3 tBegin range request, file name %1, offset %2, size %3 |Range request progress: file name %1, offset %2, size %3 xEnd range request for file name %1, offset %2, size %3 \PreAllocateFile Start for file %1 size %2 XPreAllocateFile End for file %1 size %2 AppxRequestHandler::Run Start for package %1 staging to %2 xAppxRequestHandler::Run End for Package %1 staged to %2 `PreAllocatePackage Start: %1 staging to %2 \PreAllocatePackage End: %1 staging to %2 AppxRequestHandler::Run Start for package update: %1 staging to %2 with base package in %3 AppxRequestHandler::Run End for package update: %1 staging to %2 with base package in %3 PreAllocatePackage Start for package update: %1 staging to %2 with base package in %3 PreAllocatePackage End for package update: %1 staging to %2 with base package in %3 hStarting to delete the de-staged package files. hDeleted de-staged package files with result %1. Starting to delete the AppContainer profile for the %1 package. Completed deleting the AppContainer profile for the %1 package with %2 error code. \Started loading the AppX Extensions DLL. \Finished loading the AppX Extensions DLL. XSuccessfully registered the %1 package. Initialization of the Visual Elements extension was started. Initialization of the visual elements extension was completed with error %1. Uninitialization of the Visual Elements extension was started. Uninitialization of the Visual Elements extension completed with error %1. The Visual Elements extension started to commit the deployment. The Visual Elements extension completed committing the deployment with error %1. The Visual Elements extension started to revert the deployment. The Visual Elements extension completed reverting the deployment. The Visual Elements extension started installing package %1. The Visual Elements extension completed installation of %1 package with error %2. The Visual Elements extension started updating package %1 over existing package %2. The Visual Elements extension completed updates to package %1 over existing package %2 with error %3. The Visual Elements extension started removing package %1. The Visual Elements extension completed removal of package %1 with error %2. The Notifications extension initialized app %1 with settings %2. App %1 was not initialized for notifications. No notification capabilities were manifested. error %1: The Notifications extension was unable to connect to the Push Notification Platform. The Notifications extension started periodic update manifest processing (%1). The Notifications extension stopped periodic update manifest processing (%1). The Notifications extension found URI %2 with a periodic update recurrence of %3 in the manifest (%1). The Notifications extension started periodic update temporary registration (%1). The Notifications extension stopped periodic update temporary registration with HRESULT %2 (%1). The Notifications extension started periodic update registration (%1). The Notifications extension stopped periodic update registration with HRESULT %2 (%1). h%1: Cannot delete splash screen information from the registry for package %2. The registry keys may be in use or the system may not have adequate permissions to delete them. %1: Cannot install or update package %2 because the splash screen information could not be written to the registry. The system may not have adequate permissions to write to the registry or the registry keys may be in use. %1(%2,%3): error %4: Cannot install, update, or uninstall package %5 because the splash screen element could not be parsed from the package's manifest. Verify that the splash screen element in the package manifest is valid. %1(%2,%3): error %4: Cannot install or update package %5 because the splash screen image [%6] cannot be located. Verify that the package contains an image that can be used as a splash screen for the application, and that the package manifest points to the correct location in the package where this splash screen image can be found. %1(%2,%3): error %4: Cannot install or update package %5 because a splash screen image for the current application context cannot be identified. The application context could include a specific language, DPI, contrast, or other special circumstance. Add a splash screen image to be used as a default if a context-specific splash screen image cannot be identified. terror %1: Adding a tile failed with unexpected error. Adding a tile failed because the VisualElements element is missing for app %1. Adding a tile failed because element '%1' is defined multiple times for app %2. Adding a tile failed because color value '%1' is not valid for app %2. Adding a tile failed because there are multiple apps with ID %1 defined. Adding a tile failed because the required element '%1' is not defined for app %2. Adding a tile failed because the resource '%1' is not valid. Adding a tile failed because file '%1' could not be opened which represents the tile for app %2. Adding a tile failed because changes could not be committed to file '%1' which represents the tile for app %2. Removing a tile failed because file '%1' could not be deleted for app %2. Adding a tile failed because app %1 is defined to provide tile notifications on lock screen but does not have a WideLogo attribute defined. 4Adding a tile failed because app %1 is defined to provide either notifications on the lockscreen or background tasks, but not both. Verify that the manifest either contains entries for both lockscreen notifications and background tasks, or does not contain entries for either. herror %1: The Visual Elements extension failed. error %1: The Visual Elements extension failed while processing the SplashScreen element in the package manifest. error %1: The Visual Elements extension failed while processing the Notification element. error %1: Cannot create registry key or value %2 for the %3 package. error %1: Cannot delete registry key or value %2 for the %3 package. %1(%2,%3): error: Cannot register the %4 package because the %5 verb occurs more than once. Remove or rename the additional verb(s). %1(%2,%3): error: Cannot register the %4 package because the open verb is reserved for use with file type association. %1(%2,%3): error: Cannot register the %4 package because this app handles AutoPlay events that require the removable-storage capability. `The system app data folder already exists. XThe system app data key already exists. xThe application data local root folder already exists. |The application data roaming root folder already exists. tThe application data temp root folder already exists. pThe application data settings store already exists. The application data user profile packages folder already exists. The application data user profile packages key already exists. Creation of the system app data folder failed with error code : %1. Creation of the system app data key failed with error code : %1. Creation of the application data local root folder failed with error code : %1. Creation of the application data roaming root folder failed with error code : %1. Creation of the application data temp root folder failed with error code : %1. Creation of the application data settings store failed with error code : %1. Creation of the application data user profile packages key failed with error code: %1. Creation of the application data user profile packages folder failed with error code: %1. lSuccessfully created the system app data folder. dSuccessfully created the system app data key. Successfully created the application data local root folder. Successfully created the application data roaming root folder. Successfully created the application data temp root folder. |Successfully created the application data settings store. Successfully created the application data user profile packages key Successfully created the application data user profile packages folder hError while deleting file %1. Error Code : %2. pError while deleting Directory %1. Error Code : %2. Error while deleting system app data key. Error Code : %1. pApplication data remains from a previous uninstall. xNo application data remains from a previous uninstall. Local, Roaming and Temp application data roots already exist. Error while deleting the existing application data. Error Code: %1. pSuccessfully deleted any existing application data. tError while acquiring roaming mutex. Error Code: %1. State DEH failed to load existing application data settings store. Error Code: %1 Creation of the application data root folder failed with error code : %1. xSuccessfully created the application data root folder. lThe application data root folder already exists. Creation of application data settings folder failed with error code : %1. xSuccessfully created application data settings folder. pThe application data settings folder already exist. Copying the settings apphive into the application data settings folder failed with error code : %1. Successfully copied the settings store into the application data settings folder. Access Denied error while deleting the system app data key. Trying to reset the ACL's on the system app data key failed with error code : %1. dSuccessfully ACL'ed the system app data key. `The system app data folder does not exist. XThe system app data key does not exist. Creation of the application data synchronization lock failed with error code : %1. \The application data lock already exists. \The application data lock does not exist. Verification of the application data synchronization lock failed with error code : %1. `Successfully created application data lock. An internal error occurred with error %1. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. The application data local cache root folder already exists. Creation of the application data local cache root folder failed with error code : %1. Successfully created the application data local cache root folder. error %1: Windows failed to signal registration change for the %2 package. error %1: Windows failed to persist backup eligibility for the %2 package. %1(%2,%3): error %4: Cannot register the %5 package because the '%6' file type association is reserved for system use. %1(%2,%3): error %4: Cannot register the %5 package because the '%6' content type association is reserved for system use. %1(%2,%3): error %4: Cannot register the %5 package because the '%6' protocol is reserved for system use. error %2: Windows cannot create the AppContainer profile for the %1 package. error %2: Windows cannot set up the firewall for the %1 package. error %2: Windows cannot set up the device capabilities for the %1 package. error %3: Windows cannot create the repository metadata for the %1 package with %2 apps. 0%1(%2,%3): error %4: Cannot map the %6 well-known device name to a device interface GUID for the %5 package. Check that the device name is correct. error %2: Windows cannot delete the AppContainer profile for the %1 package. %1(%2,%3): error %4: The OSMaxVersionTested element must be greater than or equal to the OSMinVersion element for package %5. $error %2: Failed to install package %1 because the firewall service is not running. Ensure that the firewall service is enabled and started. error %2: Failed to remove package %1 because the firewall service is not running. Ensure that the firewall service is enabled and started. error %2: Failed to update package %1 because the firewall service is not running. Ensure that the firewall service is enabled and started. Perror %2: Unable to install the framework package %1 because its manifest contains capabilities. The manifest for a framework package cannot specify capabilities. %1 : error %4 : Cannot register the %5 package because the specified resource language '%6' is not a valid language. %1 : error %4 : Cannot register the %5 package because there are no free merge indices for the main package '%6'. %1 : error %4 : Cannot register the %5 package because there was a merge failure with the following file: %6 %1 : error %4 : Cannot register the %5 package family because there was a failure setting permissions on the ResourceConfig registry key error %1: Windows cannot register the package because the %2 ActivatableClassID of the %3 contract was not found. error %1: Windows cannot register the package because the logo file name is missing. Provide a logo file name and try again. error %1: Windows cannot register the package because the %2 ActivatableClassID of the %3 contract is not an exe server. 8error %1: Windows cannot register the package because the %2 ActivatableClassID of the %3 contract is not marked with the ActivateAsPackage attribute. Derror %1: Windows cannot register the package because an ActivatableClassID with the same name already exists: '%2'. Provide a different name and try again. Terror %1: Windows cannot register the package because an ActivatableClassID was previously declared with the same name: '%2'. Provide a different name and try again. error %1: Windows cannot register the package because the %2 ActivatableClassID name is empty or too long. error %1: Windows cannot register the package because the %2 ActivatableClassID is invalid. Herror %1: Windows cannot register the package because a Windows Runtime server with the same name already exists: '%2'. Provide a different name and try again. \error %1: Windows cannot register the package because a Windows Runtime server with the same name was previously declared: '%2'. Provide a different name and try again. error %1: Windows cannot register the package because the %2 Windows Runtime server name is empty or too long error %1: Windows cannot register the package because the %2 Windows Runtime server name is invalid. error %1: Windows cannot register the package because an error occured when registering the %2 Windows Runtime server. error %1: Windows cannot register the %2 package because the Activatable Class %3 does not contain a valid DllPath. The DllPath must point to a DLL in the package or to an OS-provided hosting binary. Correct the DllPath and try again. error %1: Windows cannot register the %2 package because the Activatable Class %3 does not have a valid Threading Model. herror %1: Windows cannot register the package because two or more attributes share the name '%2'. Attribute names must be unique. Rename at least one attribute and try again. error %1: Windows cannot register the package because an attribute on the ActivatableClass is invalid. error %1: Windows cannot register the package because an attribute on the ActivatableClass is empty or too long error %1: Windows cannot register the package because the ProxyStub CLSID %2 is defined in two or more DLLs. A ProxyStub CLSID can be defined only once. Correct the definitions and try again. error %1: Windows cannot register the package because a ProxyStub CLSID is already associated with interface %2. Only one ProxyStub CLSID can be associated with an interface. Correct the registrations and try again. error %1: Windows cannot register the package because the publisher name is missing. Provide a publisher name and try again. error %1: Windows cannot register the package because the display name is mising. Provide a display name and try again. error %1: Windows cannot register the package because the description is missing. Provide a description and try again. error %1: Windows cannot register the package because the %2 contract identifier is empty or too long error %1: Windows cannot register the package because of low memory. error %1: Windows cannot register the package because of an internal error or low memory. error %1: Windows cannot register the %2 package because of an internal error or low memory. error %1: Windows cannot register the %2 package because of an internal error or low memory. error %1: Windows cannot register the package because of an internal error or low memory. Terror %1: Failed to install Game %3. herror %1: Failed to create Internal Game State. Perror %1: Failed to remove Game %3. xThe extension content from the package manifest is %1. pThe game definition file container file path is %1. |error %1: game definition file container file not found. herror %1: Failed to validate extension content. Xerror %1: Game %3 is already installed. Perror %1: Game %3 is not installed. lerror %1: Could not create a GameExplorer object. herror %1: Failed to validate input parameters. Lerror %1: Internal state not set. error %1: Invalid Access. This game cannot be installed for the user. error %1: windows.licensing was unable to validate the input parameters. error %1: windows.licensing was unable to properly elevate. Try again and contact the package publisher if the problem persists. error %1: windows.licensing failed to start WSService. Try again and contact the package publisher if the problem persists. error %2: windows.licensing failed to update critical data for %1. Try again and contact the package publisher if the problem persists. 8error %2: windows.licensing failed to update critical data for %1. You must uninstall one or more apps before you can install or update any new apps. `%1(%2,%3): error %4: Cannot register %5 package because the following error was encountered while trying to open and evaluate the %6 certificate to add to the %7 store: %8 x%1(%2,%3): warning: While registering %4 package, a SelectionCriteria element without attributes was found. You should specify HardwareOnly or AutoSelect as SelectionCriteria attributes. If you don't need to specify any attributes for SelectionCriteria, exclude the SelectionCriteria element from the manifest. %1(%2,%3): error %4: Cannot register %5 package because the following error was encountered while parsing the Certificates element: %6 %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 extension: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while registering the %7 extension: %6. Try again and contact the package publisher if the problem persists. Cannot restore the %1 extension because it was not found in the %2 package. error %4: The following error occured while preparing the %1 extension in the %2 package for update or removal: %3. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the package: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 Extension element: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 application: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while registering the %7 activatable class: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while registering the %7 contract ID: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 Action element: %6. Try again and contact the package publisher if the problem persists. %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 service ID: %6. Try again and contact the package publisher if the problem persists. error %3: Cannot register the %1 package because the following error was encountered while creating the %2 package dependency file: %4 Lerror %3: Cannot register the %1 package because the following error was encountered while removing the %2 package dependency file (queued for later removal): %4 (error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\%3 package family registry key: %5 $error %4: Cannot register the %1 package because the following error was encountered while removing the %2\%3 package family registry key: %5 Perror %3: Failed to enqueue a request for deferred file deletion for %1 package because the following error was encountered for the %2 package dependency file: %4 <error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_CURRENT_USER_LOCAL_SETTINGS registry key: %3 @error %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\%3 package family registry key: %5 Upstream dependency scan for the %1 package found the %2 package (PackageKey=%3) <error %3: Cannot register the %1 package because file error was encountered while removing the %2 package dependency file (queued for later removal): %4 error %2: Cannot process the %1 package because the following error was encountered while retrieving its package state: %3 Started creating the Dependency Mini Repository for the %1 package. Finished creating the Dependency Mini Repository for the %1 package. error %6: Cannot process the %1 package because the following error was encountered while retrieving the %3 property for the value '%4': %7 Lerror %7: Cannot process the %2 application in the %1 package because the following error was encountered while retrieving the %4 property for the value '%5': %8 error %3: Cannot retrieve file usage for the %2 package dependency file in the %1 package because the following error was encountered: %4 `error %3: Failure processing %1 package because %2 package dependency file is in use by %6 processes. Process[%5] = processid %7 (error retrieving process information): %4 error %3: Failure processing %1 package because %2 package dependency file is in use by %6 processes. Process[%5] = processid %7, application %8, package %9, executable %10, user %11 username %12/%13, session %14: %4 Started creating the Dependency Mini Repository for the %1 incoming package. Finished creating the Dependency Mini Repository for the %1 incoming package. Started updating the Dependency Mini Repository for the %1 upstream package. Finished updating the Dependency Mini Repository for the %1 upstream package. Started removing the Dependency Mini Repository for the %1 outgoing package. Finished removing the Dependency Mini Repository for the %1 outgoing package. %2: Package runtime information %1 failed to load (processid=%3). error %3: Cannot register the %1 package due to the following error: %2. %1(%2,%3): error %4: Cannot register the %5 package because the extension is missing an EntryPoint or StartPage attribute. %1(%2,%3): error %4: Cannot register the %5 package because the ServerName attribute is invalid. %1(%2,%3): error %4: Cannot register the %5 package because the Executable attribute is invalid. %1(%2,%3): error %4: Cannot register the %5 package because ServerName and Executable attribute are mutually exclusive. $%1(%2,%3): error %4: Cannot register the %5 package because a custom background task host cannot be specified for this background task type. %1(%2,%3): error %4: Cannot register the %5 package because a task of this type requires a custom background task host. error %3: Cannot register the %1 package due to the following error: %2. %1 : Failed to fire WNF notification for Device Setup for the package %2 after uninstall. %1 : Failed to fire WNF notification for Device Setup for the package %2 after install. (%1 : Failed to switch to system context before firing the WNF notification(s) for Device Setup for incoming package %2 and outgoing package %3. 4%2: Package runtime information %1 is corrupted (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. 4%2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. L%2: Package runtime information %1 contains conflicting data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. L%2: Package runtime information %1 contains unexpected data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. Package runtime information %1 failed to load because exception %2 occurred. 4%2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. %2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5). error %3: Cannot register the %1 package due to the following error: %2. %1(%2,%3): error %4: Cannot register the %5 package because the Executable attribute is invalid. %1 : Failed to load the object that will clean up the association between the current user and package %2. \%1 : Failed to complete cleaning up the association between the current user and package %2. See Winevt\Logs\Microsoft-Windows-LiveId/Operational.evtx for more details. %2: Cannot register package %1 because of an error in DeviceCapability %6: missing required Device element %2: Cannot register package %1 because of an error in DeviceCapability %6: %6 is not a supported Name %2: Cannot register package %1 because of an error in DeviceCapability %6: Device %7 missing required Function element %2: Cannot register package %1 becuase the handler for DeviceCapability %6 could not be loaded. $%2: Cannot register package %1 because the handler for DeviceCapability %6 is missing a required registry parameter (%8) and cannot be used. %2: Cannot register package %1 because of a problem with Device element %7: %9 %2: Cannot register package %1 because of a problem with Function element %8: %9 %2: Cannot register package %1 because of an error with DeviceCapability[@Name="%6"]\...\%7[@%8="%9"] %2: Cannot register package %1 because of an error in %6 (attribute %7): %9 %2: Cannot register package %1 because element %6 is missing required attribute %7 warning %2: The following error occurred while performing Indexed DB cleanup when removing the package: %1 (%3). warning %2: The following error occurred while getting deployment options during Indexed DB cleanup when removing the package: %1 (%3). XAppSync DEH invoke (%1) on package=%2. SearchIndexer extension has failed to connect into Windows Search service: %1 hSearchIndexer extension started initialization SearchIndexer extension has finished initialization with error %1 XSearchIndexer extension started removal pSearchIndexer extension has finished removal of %1 %1(%2,%3) %4: The %5 package cannot be registered because an unexpected error occured while processing the alarm extension. %1(%2,%3) %4: The %5 package cannot register an alarm extension because it does not have the required lock screen capability. HGeolocation extension could not invoke the Location Framework Service to remove package %1. A reboot may be needed before re-installing the package (error: %2) <Geolocation extension could not invoke the Visual Studio simulator to remove package %1. Close the simulator before re-installing the package (error: %2) `AppXSvc service initialization failed : %1. dUpdating service status to %1 failed with %2. Starting validation and setting the Trust Label on package %1 with flags %2. Finished validation and setting the Trust Label on package %1 with flags %2. TModified file %2 found in package %1. XFile %2 does not belong to package %1. Failed to set the Trust Label on package %1 with flags %2. Error: %3. %2 file(s) have been validated from block map for package %1. dPackage %1 has Trust Label already. Flags: %2 Illegal non-AppStore package integrity validation attempted for package %1. Flags: %2 About to service package %1. Setting the package state to disabled returned with %2. Finished servicing package %1. Setting the package state to enabled returned with %2. Creating Resiliency File %3 for %1 Operation on Package %2. pDeleting Resiliency File %1 finished with code %2. Invalid Add Remove Update Stage DeStage Register HGet list of registered packages 0Fix staged packages HDelete all files of the package <RegisterByPackageFullName $StageUserData 0PreRegisterPackage x86 x64 ARM Neutral $Not Validated Unknown $Windows Store ,Windows Component Queued De-Queued (BundleProcessed Indexed Resolved Approved Evaluated 4PrerequisitesChecked Staged 8StageUserDataProcessed 0PackagesInUseClosed 0RegistrationChanged 8PackagesInUseRestarted De-Indexed De-Staged No Error Attribute not in required format of type:value, or the format of the type or value portion is invalid PType is not supported for this bus PValue is not supported for this bus dValue is blocked, and not allowed on this bus Function requires a Device with a specific Id element, and cannot be used with an Id of "any" (NotInstallable Installable Installed ,RequiresReinstall $DefaultOption HForceApplicationShutdownOption 4DevelopmentModeOption <RepositoryRecoveryOption 4PushButtonResetOption 4BackgroundTaskOption 0InstallAllResources 8PreserveApplicationData 8RegisterProvisionedApp 4VS_VERSION_INFOB%B%?BStringFileInfo040904B0LCompanyNameMicrosoft Corporation^FileDescriptionAppX Deployment Server DLLr)FileVersion6.3.9600.17031 (winblue_gdr.140221-1952)RInternalNameAppXDeploymentServer.dll.LegalCopyright Microsoft Corporation. All rights reserved.bOriginalFilenameAppXDeploymentServer.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.17031DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD