????
Your IP : 216.73.216.152
| Current Path : C:/Windows/System32/en-US/ |
|
|
| Current File : C:/Windows/System32/en-US/AppXDeploymentServer.dll.mui |
MZ� �� � @ � � � �!�L�!This program cannot be run in DOS mode.
$ ��<߱�R���R���R�U�����R�U�P���R�Rich��R� PE L � ! �
� ۸ @ � 8 .rdata � @ @.rsrc � � @ @ �|�
T 8 8 �|� $ � � 8 .rdata 8 x .rdata$zzzdbg @ .rsrc$01 @! � .rsrc$02 4�+S���7�>�&X��5si&�F�ۋ�|� 0 �0 � H � ` � x � � � � � � � � � � 8! � � �! � � �# T� � 8� � � M U I ��� � ϱ�L �[!bt�
$ .�W�,����G � � � M U I e n - U S ! A p p X D e p l o y m e n t S e r v i c e ( A p p X S V C ) � P r o v i d e s i n f r a s t r u c t u r e s u p p o r t f o r d e p l o y i n g S t o r e a p p l i c a t i o n s . T h i s s e r v i c e i s s t a r t e d o n d e m a n d a n d i f d i s a b l e d S t o r e a p p l i c a t i o n s w i l l n o t b e d e p l o y e d t o t h e s y s t e m , a n d m a y n o t f u n c t i o n p r o p e r l y . � , 1 1 � 0 0� P P� � � , �, �$ . �/ �t 1 �2 �P 6 �< �T > �D �x M �O �@ T �V �@ � �� �T � �� ��( � �� �+ � �� �</ � �� ��3 � �� ��5 � �� �= � �� ��> � �� �`? � � �B � ��H
�
�`I �) ��I 0 �2 �<O 5 �= �(P X �] ��R _ �m ��U o �v ��Z x �� �4_ � �� ��m � �� ��n � �& ��~ + �- � � / �6 �� 8 �: ��� < �> �� @ �D �Р F �d ��� � �� �H� � �� ��� � �� �D� � �� �� � � �� � �ص � ��� � �� �0� � �� �̼ � �� �x� � ��� � �� �x� � �� �ؾ � �� ��� � �� �$� � �� �p� � �� ��� � �� ��� � �� �x� � �� ��� � �� � � P �o ��� q �� �p� � �� ��� � �� ��� � �� �T� � ��� � ��� % �' �� ) �) ��� | � �l� � �� �d� � �� �x� � �� ��� 9 �E �� G �K �� M �W �� d �i �L � �� �X � �� �� � �� �P Y �Z �D ] �] �| ` �` �( b �s �� u �u �� � �� �8 � �8' R �R ��' � �� ��' � �� �0) � �� ��+ L �M ��- � �� �X. � �|/ F �G ��3 � �� ��4 � �� ��5 � �� �l6 � �t7 " �% �8 , �/ ��9 @ �A ��; � �� �<< � �t>
� ��? & �& ��@ : �; �`A l �l �4B � �� ��B � �� �xD ! �! ��D 5! �5! �E 7! �7! ��E q! �u! �F �! ��! �dG " �" ��G 9" �9" �HH )# �E# ��H J# �N# ��Z �# ��# ��] $ �$ ��] �$ ��$ ��_ �$ ��$ � ` �$ ��$ �|` &% �(% �Db 1% �1% �<c E% �G% �xc �% ��% �He �% ��% �h �% ��% �@h �% ��% �tk \& �\& ��k �& ��& ��k ' �' ��l �* ��* ��o \+ �\+ ��p �+ ��+ �8q �. ��. ��u �. ��. �v �. ��. ��v X/ �X/ �<w �/ ��/ ��w �/ ��/ �dx �/ ��/ � � 40 �40 �l� Ђ м� �@ � $ AppXDeploymentServer Keyword
0 VisualElements Extension Handler Keyword
OSIM Keyword
( State Extension Handler Keyword
, AutoPlay Extension Handler Keyword
4 CollectorExtension Extension Handler Keyword
, PackagedCom Extension Handler Keyword
, FileType Extension Handler Keyword
( Trust Extension Handler Keyword
, Licensing Extension Handler Keyword
4 Data Package Host Extension Handler Keyword
0 Certificates Extension Handler Keyword
, AppX Base Extension Handler Keyword
, Protocol Extension Handler Keyword
( MoCOM Extension Handler Keyword
( Runtime Extension Handler Keyword
0 BackgroundTasks Extension Handler Keyword
, Download Extension Handler Keyword
( AppXDeploymentServerPerf Keyword
$ Mrt Extension Handler Keyword
$ DSM Extension Handler Keyword
, Package Runtime Information Keyword
4 RestrictedLaunch Extension Handler Keyword
0 DeviceAccess Extension Handler Keyword
, IndexedDB Extension Handler Keyword
0 MSAC SignOut Extension Handler Keyword
0 SearchIndexer Extension Handler Keyword
( AppSync Extension Handler Keyword
, Apply Data Extension Handler Keyword
( Alarm Extension Handler Keyword
, Geolocation Extension Handler Keyword
8 PreInstalledConfigTask Extension Handler Keyword
4 UpdateMigrationTask Extension Handler Keyword
4 WebAccountProvider Extension Handler Keyword
, AppService Extension Handler Keyword
0 UserDataAccess Extension Handler Keyword
0 DialProtocol Extension Handler Keyword
( AoW App Extension Handler Keyword
D CommunicationBlockingAppProvider Extension Handler Keyword
8 PhoneCallOriginProvider Extension Handler Keyword
, WmiProvider Extension Handler Keyword
8 Local Experience Pack Extension Handler Keyword
0 Server Common Extension Handler Keyword
Response Time
Info
Start
Stop
Error
Warning
Information
Verbose
0 Microsoft-Windows-AppXDeployment-Server
8 Microsoft-Windows-AppXDeploymentServer/Diagnostic
< Microsoft-Windows-AppXDeploymentServer/Operational
4 Microsoft-Windows-AppXDeploymentServer/Debug
8 Microsoft-Windows-AppXDeploymentServer/Restricted
P error %3: Cannot register the %1 package due to the following error: %2.
T 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.
L Injected a failure on evaluate due to the following error: %2 (%1).
H 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.
� error %3: Cannot register the %1 package because the following error was encountered while determining the level of trust for the package: %2.
� error %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.
T error %1: Failed to load the extension DLL due to the following error: %2.
@ %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.
D %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.
X Registration has successfully created the following extensions on Package %2: %1.
d Cannot open manifest file for package %1 (%2). Using manifest from StateRepository instead.
X The current impersonation for %1(RunAsSystem:%2) is invalid, we will correct it.
d Deployment %1 operation with target volume %4 on Package %2 from: %3 finished successfully.
� Deployment %1 operation with target volume %5 on Package %2 from: %3 failed with error %4. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
L error %2: Reading manifest from location: %1 failed with error: %3.
8 error %2: Failure to get staging session for: %1.
x AppX Deployment operation failed for package %2 with error %3. The specific error text for this failure is: %1
H 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.
� Another 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.
D error %2: Deployment of package %1 was blocked by AppLocker.
, Deployment of package %1 with package origin %2 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.
X Checking whether deployment is in developer mode because package %1 is unsigned.
D The check for the origin of package %1 returned %2 origin.
T The check for enterprise qualifications to approve package %1 returned %2.
L 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.
T error %2: Unable to install because the following apps need to be closed %1.
� 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.
� Windows 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.
x Windows cannot remove non-qualified resource package %1 because package(s)%2 currently depends on the package.
� Windows 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.
� Windows cannot install the bundle because the resource Id of the resource package %1 is invalid as it is the same as the resource id of the main package %2.
` Package %1 with %2 origin cannot be sideloaded or installed using developer mode option.
t The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy.
� Deployment of package %1 to volume %2 failed because deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps to non-system volumes" policy.
d Failed to initialize a MRT resource manager for the inbox application: %1 and file path: %2 .
\ Failed to initialize a MRT resource manager for the package: %1 and file path: %2 .
@ Merging resource PRIs failed with error %2 for paths: %1.
� Writing registry key for user %1 returned %4. User had outdated package %3, which will be updated to %2. User was online: %5.
L Package dependency %1 could not be found in the repository database.
H Skipping some operations for remove of package %1 due to repair.
< Can't complete the applocker check for %2 because %1
8 Package %1 is blocked by a platform policy: %2.
\ User %1 had outdated package %3, which will be updated to %2. User was online: %5.
p Removed registry for package %2 for user %1. This package will be installed for the user on next logon.
� Deployment of package %1 to volume %2 failed because deployments to non-system volumes are blocked for this package's package family.
| Deployment of package %1 to volume %2 failed because deployments to non-system volumes are blocked on this machine.
� Error %4: Deployment of package %3 failed becuase user %1 with package %2 is logged in. Packages with singleton components will fail if other users are logged in and have the package installed.
4 error %2: Creating DataSource to %1 failed.
, error %2: Creating folder %1 failed.
, error %2: Creating file %1 failed.
< Writing to file %1 at offset %2 of size %3 failed.
0 error %2: Hard linking to file %1 failed.
@ error %2: Opening the package from location %1 failed.
D error %2: Creating the package metadata directory %1 failed.
T error %2: Setting file attributes for package metadata directory %1 failed.
4 error %2: Failed to set access rights to %1.
H Integrity check failed for file %1. The integrity state is: %2.
D error %3: Package update failed for %1. Re-stage package %2.
, error %2: Deleting file %1 failed.
4 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.
4 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.
L 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.
< Hard linking file %1 to %2 failed with HRESULT %3.
D error %2: Creating the system metadata directory %1 failed.
D error %2: Deleting the system metadata directory %1 failed.
H error %2: Opening the loose file package from location %1 failed.
H error %3: Package volume operation %1 for %2 failed at line %4.
H error %3: Package volume state update for %1 failed for user %2.
\ error %3: No package table row %1 associated with visibility table row for user %2.
D AppX Deployment operation failed with error %2 from API %1
4 Removing directory %2 failed with error %1
X Error %1: Could not mount volume with Single Instance Store %2 and Media ID %4.
T Notification to setting monitor of the change to %1 failed with error: %2.
d Found partially downloaded file to resume. File path: %1, resume offset: %2, file size: %3.
@ Resume requires full block hash validation for package %1
T There were %2 additional files that failed to be deleted under the folder %1.
D There were %1 additional files that failed to be hardlinked.
8 %2 in MsixvcStagingSession failed with error %1.
< Invalid footprint file %2 for package %3, error %1.
� Error %2: Opening the Msixvc package from location %1 failed. Please check whether the Msixvc support services are installed.
L MSIXVC data source called to remove package %1 root %2 successfully.
8 Removing mounted package folder %2. Result: %1.
\ Framework package %1 download failed, file write size is %2, actual file size is %3
4 error %3: Failed to delete %2 for package %1.
0 Successfully 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.
X Error %1: Failed to Scavenge Application Data from volume %2 with media ID %3.
d Error %1: Failed to Scavenge Application Data for User %4 from volume %2 with media ID %3.
p Error %1: Failed to Scavenge Application Data for User %4 and Package %5 from volume %2 with media ID %3.
l Succeeded to Scavenge Application Data for User %4 and Package %5 from volume %2 with media ID %3.
< Removing orphan package in path %2. Result code: %1
x Finished scanning and cleaning up orphan packages. Setting last cleanup time to registry returned result code: %1
8 Successfully Removed orphan backup manifest %1.
D Removing orphan backup manifest %1 failed. Result code: %2
t Staging session streaming data source prefetch canceled, session key %1, data source prefetch canceled %2.
� error %1: Windows cannot process a deployment operation because the package repository database encountered an unrecoverable error. Use the Reset Your PC feature to recover your PC.
@ error %2: Failed to create package repository folder %1.
L Started bytecode generation for package %1 on %2-bit architecture.
L Finished bytecode generation for package %1 on %2-bit architecture.
P %3: Failed to generate bytecode for package %1 on %2-bit architecture.
X Failed to generate bytecode for %3 JS files in package %1 on %2-bit architecture.
d File %2 in package %1 is missing the UTF-8 BOM. Skipping bytecode generation for this file.
t 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.
P ByteCodeGenerator process terminated with exit code %2 for package %1.
h %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.
x 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.
h Valid bytecode file %2 is already present for package %1; so bytecode generation is unnecessary.
� Staging failed with error code %1 because package folder %2 does not have the correct ACLs applied. Please use the official tool to create package folders for app attach.
@ Staging roaming data for package %2 failed with error %1.
\ Not staging roaming data for package %1. The application state is already present.
P Establishing the sync relationship for package %2 failed with error %1.
@ Alternate staging location was cleared for package %1.
@ Acquiring roaming data for already registered package %1.
` Performed deferred roaming data acquirisition for registered package %2 with error %1.
T Deferring staging of roaming data for package %1 without blocking app launch.
` Deferring staging of roaming data for package %1, will block app launch for roaming data.
P Failed to get or set roaming data status for package %2 with error %1.
@ First user logon Started before installing package %1.
< First user logon ended before installing package %1.
H Setting Sync Enabled status, package family name %1, enabled %2.
\ 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.
P Identified %1 request(s) in the Queue Store for potential restoration.
� Started deployment %1 operation on a package with main parameter %2 and Options %3 and %4. 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 and %5. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
l The last successful state reached was %1. Failure occurred before reaching the next state %2. hr: %3
` Deployment %1 operation on package %2 has been de-queued and is running for user SID %3.
T Unable to recover package %1 because it does not have any .recovery files.
h Recovering DeploymentRequest from file %4 for %1 Operation on Package %2. Resuming from state %3.
D error %2: Recovering DeploymentRequest from file %1 failed.
8 Failed flushing deployment data with result: %1.
l Could not contact Process Lifetime Management to ensure that no apps are running during servicing.
H Performance summary of Deployment %1 operation on Package %2: %3
, Bundle Uri %1 contains packages: %2.
P Deployment %1 operation on package %2 has been cancelled by the caller.
8 Relaunching app %1 after the app was serviced.
L Successfully updated the status for package %1 (Clear=%2, Set=%3).
P error %5: Unable to update the status for package %1 (Clear=%2, Set=%3).
h error %3: Unable to change application state for package %1 (BiApplicationStateTransition=%2).
X error %3: Unable to set package status for dependents of package %1 (context=%2).
X error %3: Unable to reset package status for dependencies of package %1 (key=%2).
X error %3: Unable to reset package status for dependencies of package %1 (key=%2).
� Started deployment %1 operation on all applications with Options %3 and %4. Exempt applications: %2. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
H The package deployment operation is now paused for package: %1
P Deployment %1 operation on package %2 has been requeued for user SID %3.
� Windows 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 package %1 because this package depends on a framework that could not be found. Provide the framework "%2" published by "%3", with neutral or %4 processor architecture and minimum version %5, along with this package to install. The frameworks with name "%2" currently installed are: %6
� No applicable cross-architecture framework was found for package %1. The package will be installed with matching-architecture framework only.
| For PreRegisterPackage, unable to determine visibility state to set for package %2 with error: %1, default to Staged
t Deployment request for %1 operation on package %2 was cancelled because it cannot be resumed from state %3.
0 PreRegisterPackage %1, IsInstalled=%2.
p OnDemandRegisterPackage %1, unable to find the package from StateRepository, we will register it later.
D ServerSideRPCPreRegisterPackage %1, Option: %2, Result:%3.
< ServerSideRPCPreRegisterAllInboxPackages result:%1.
� Running apps were shut down to allow packages to be updated. Running apps: {%1}, Directly serviced packages: {%2}, Indirectly serviced packages: {%3}, Number of previous attempts: %4, Is user session locked: %5
� Packages were not updated because affected apps are still running. Running apps: {%1}, Directly serviced packages: {%2}, Indirectly serviced packages: {%3}, Number of previous attempts: %4, Is user session locked: %5
8 ServerSideRPCCleanupWCIReparsePoints result:%1.
< ServerSideEnsurePackageFamilyIsRegistered result:%1.
$ OnDemandRegisterPackage %1
l OnDemandRegisterPackage found existing package %1, set PACKAGE_STATUS_REGISTRATION_REQUIRED_BLOCKING
T OnDemandRegisterPackage %1 add PackageUser row, Bundle:%2, AppDataVolume:%3
@ OnDemandRegisterPackage %1, update Staged to Installed
( OnDemandRegisterPackage error %1.
D The running app %2 was shut down for servicing (Priority=%1).
@ Removing registrations for DownlevelInstalled package %1.
� The last successful state reached was %1. Failure occurred in the early preparatory steps of the request or before reaching the next state %2. hr: %3
0 Deployment %1 operation on Package %2: %3
� Error processing appinstaller at resolved path %1. UpdateSettings for OnLaunch require ShowPrompt to be true when UpdateBlocksActivation is true.
D Appinstaller operation failed with error code %1. Detail: %2
� Error processing appinstaller at resolved path %1. The appinstaller file or one of its referenced files does not exist.
� The package full name returned from the AppxManifest (%1) does not match the name generated from the AppInstaller (%2). Please ensure that the package attributes specified in the .appinstaller file match the package attributes referenced in %3.
` The appinstaller file referenced at %1 is invalid. Please see event log for more details.
P OnDemandRegisterPackage %1, failed to create or update tiles. Error: %2
@ Skipping OnDemandRegisterPackage %1 because it is Paused.
8 ServerSideRemovePackageFromContainer result %1.
T Marking package {%2} for deferred registration because {%1} is still running.
` Skipping add of {%1} from the provided URI because it is already installed on the system.
� Deployment will return success to the caller instead of {%1} because DeferRegistrationWhenPackagesAreInUse was passed for the register operation when packages were in use.
� Windows cannot install package %2 because this package depends on a device driver that could not be found. One of the following device drivers must be installed: %3
The package to be staged has already been staged before with a different StageInPlace option. Please destage the existing package then try again. Package full name: %1. Current request has StageInPlace option: %2. Existing package was staged with StageInPlace option: %3.
� The package that is being deprovisioned should be destaged, but the destaging operation was unable to be enqueued. Package full name: %1.
P Error %1: The request cannot be processed because package %2 is in use.
X For repair of package %1: starting %2 operation on package %3 (step %4 of %5).
d For repair of package %1: %2 operation on package %3 finished with result %6 (step %4 of %5).
$ %1:%2 failed with error %3
� Unable to install %1 because the same package %2 is specified multiple times. Each package specified needs to be unique.
x Unable to install %1 because %2 dependencies were specified. The maximum number of allowed dependencies is %3.
� Windows cannot install %1 because this package has multiple dependencies on the same package %2. Remove all redundant dependency declarations.
d 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.
@ error %2: Windows cannot access deployment target at %1.
8 error %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.
� Deployment %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.
� Rejecting 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.
� Windows 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.
� Windows 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.
t 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.
0 Failed to initialize PLM with error %1.
< Deployment was cancelled after failure with error %1.
l Failed with error %1 to reset machine register state in the State Repository database for package %2.
� The specified package full name %1 is not eligible for a StageUserDataAsync call. The operation cannot be performed on an installed package.
d StageUserDataAsync cannot be called for package %1 which was deployed in development mode.
8 Windows 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.
L Windows cannot find the main package manifest in the bundle file: %1.
P Windows cannot find the resource package manifest in the bundle file: %1.
H error %2: Unable to relaunch app %1 after the app was serviced.
T 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.
< The check for how %1 applies to user %2 returned %3.
@ The check for how %1 applies to user %2 failed with %3.
, Invalid dependencies were specified.
\ Package Manager aborted the %1 operation because an invalid argument was passed: %2.
P Windows cannot move package %1 because it is a development mode package.
� Windows cannot move package %1 because it is a resource package. Specify the main package or bundle package to move, and the associated resource packages will also move.
H Windows cannot move package %1 because it is part of the system.
P Windows cannot move package %1 because it needs to be reinstalled first.
d Windows cannot move package %1 because the current user does not have the package installed.
t Windows cannot move package %1 because a more recent version of the family is staged for the user to update.
l Windows cannot move package %1 because other versions of the family are installed for other users.
@ Windows cannot move package %1 because it is a framework.
L Package %1 is already on the target volume, so it will not be moved.
t Windows cannot install package %1 because another package in the family is installed on a different volume.
h Windows cannot install package %1 to volume %2 with media ID %3 because the volume is offline.
� Windows cannot install package %1 to volume %2 with media ID %3 because framework packages can only be installed to the system volume.
d Windows cannot move package %1 to volume %2 with media ID %3 because the volume is offline.
d Windows cannot move package %1 from volume %2 with media ID %3 because the volume is offline.
� Volume %2 with media ID %3 is offline. Although Windows can remove package %1 from the device, it cannot remove the package from the offline volume.
l Windows failed to undo changes with error code %1 to package %2. The package needs to be reinstalled.
� Windows failed to update the mounted folder of package %1. Updating the mounted folder to path %2 failed with error %3.
� Windows failed to move package %1 to the MovedPackages location. Updating the mounted folder to path %2 failed with error %3.
h Windows failed to create a mounted folder for package %1 to location %2. Failed with error %3.
t Windows cannot install app data for package %1 to volume %2 with media ID %3 because the volume is offline.
� Windows cannot install app data for package %1 to volume %2 with media ID %3 because it is already installed to volume %4 with media ID %5.
P Windows cannot move package %1 because it is in an invalid XAP state: %2.
� Windows cannot install package %1, because this operating system only supports apps built using the Windows 10 and greater universal application platform.
@ Failed creating preview tiles for package %1. Error: %2
H Failed creating the canonical PRI file for package %1. Error: %2
, Preview tiles created for package %1.
4 Windows cannot move this type of package %1.
� Windows cannot install package %1 because the package is currently paused. The package must be Staged in order to proceed.
T Windows cannot install package %1 because it is missing a phone product ID.
x Windows cannot install package %1 to volume %2 with media ID %3 because it is not supported on this filesystem.
X Failed to create PackageInUseHelper. Error code: %1, main package family name: %2
� Failed to set optional package in used by deployment. Error code: %1, main package family name: %2, optional package full name: %3
P Failed committing %1 transaction for preview tile generation. Error: %2
D Could not update related set %2 because %1 is missing in %3.
d Invalid bundle %1 contains multiple main or optional packages %2, %3 registered for a user.
D Could not find the path %1 in the State Repository database.
Re-indexing package %1.
X Setting status for package %1, so that it is re-registered before next launch.
x Marking paused package %1 as staged in the State Repository database, since its payload was found to be complete.
P Related set %2 is not ready for registration because %1 is missing in %3.
h Windows failed to cleanup path %2 for package %1 with error %3. Marking package for remediation
� Windows cannot install package %1 because this package is not compatible with the device. The package can only be installed on the following device families: %2
� Windows cannot install package %1 because this package is not compatible with the device. The package requires OS version %3.%4.%5.%6 or higher on the %2 device family. The device is currently running OS version %7.%8.%9.%10.
� Windows cannot install non-preinstalled package %1 to volume %2 with media ID %3 because the volume is the Preinstalled Apps volume.
| Windows cannot move package %1 from volume %2 with media ID %3 because the volume is the Preinstalled Apps volume.
x Windows cannot move package %1 to volume %2 with media ID %3 because the volume is the Preinstalled Apps volume.
� error %4: AppX Deployment %1 operation on package %2 from: %3 failed. Removing this app is blocked by Enterprise policy.
| Windows cannot remove package %1 from volume %2 with media ID %3 because the volume is the Preinstalled Apps volume.
L Failed initializing preview tile generation for user %1. Error: %2
t Failed creating preview tiles for package %1 due to the package not being found in StateRepository. Error: %2
� Appinstaller file %1 has specified UpdateBlocksActivation is true but defined ShowPrompt as false (or did not define ShowPrompt). Setting ShowPrompt = true since UpdateBlocksActivation = true implies ShowPrompt = true.
� Windows cannot remove %1 because the PreserveRoamableApplicationData flag cannot be used together with incompatible options.
$ ContainerDeployment error %1.
X Windows cannot move package %1 because it is staged in place and cannot be moved.
@ Windows cannot move package %1 because it is unsigned.
T Windows cannot install package %1 because it is not a valid unsigned package.
d Windows cannot install package %1 because its publisher %3 is not in the unsigned namespace.
d Windows cannot install package %1 because its publisher %3 is not in the signed namespace.
| Windows cannot install package %1 because it must allow external content to be installed with an external location.
d Windows cannot install package %1 because an unsigned package cannot provide a host runtime.
l Windows cannot install package %1 because an unsigned package cannot include Executable activations.
D Access denied. Windows cannot install unsigned package %1.
\ Windows cannot install package %1 because an unsigned package must be a Main package.
` Windows cannot install package %1 because windows.hostRuntime must be in a Main package.
< Creation of registry key: %1 failed with error: %2.
8 Opening registry key: %1 failed with error: %2.
< Deletion of registry key: %1 failed with error: %2.
D Registry copy of tree for package: %1 failed with error: %2.
P Failed to read the value named %2 from registry key: %1 with error: %3
P Failed to write the value named %2 from registry key: %1 with error: %3.
x Package(s) with the following package full names were not registered due to sideloading policy restrictions: %1
T Unable to determine whether package %2 is an all user package with error: %1
H Unable to update all user store with package %2 with error: %1
< Successfully updated all user store with package %1.
< Creating registry key: %1\\%2 failed with error: %3.
h Failed to write the value named %3 with value %4 in registry key %1\\%2 failed with error: %3.
x Package %1 was moved to the Deleted store after reaching the max number of deployment attempts with error: %2.
H Determining packages to be installed during logon for user: %1.
` The following packages will be installed: %1. The following packages will be removed: %2
P Unable to determine packages to be installed during logon with error: %1.
l During-logon registration of package %2 for user %1 finished with result: %3; updating registry...
D Updating registry for package %2 completed with result: %1.
\ Windows cannot register the package %1 because Modern App can't be updated to Xap.
\ Windows cannot register the package %1 because Appx can't be updated to SL Lightup.
� Windows cannot register the package %1 because there is mismatch in developer status for package registered with same PID
� error %4: AppX Deployment %1 operation on package %2 from: %3 failed. This app cannot be uninstalled on a per-user basis.
4 Could not retrieve decryption key from CLIP
( Move is blocked for package %1
\ The downlevel package repository could not be accessed for package %1 (action=%2).
h The package %1 was removed from the package repository because the package manifests are missing.
< The package repository fix failed with error code %1.
� The optional package %1 can't be installed because its main package dependency %2 is not installed. Install the main package first.
X The optional package %2 with dependency on main package %1 will also be removed.
8 Invalid End of Life package %1 will be ignored.
H Skipping package %2 because its volume is offline or missing: %1.
h The corresponding main package already has the same Application Id %1 as this optional package.
t Failed to Expand the environment strings, while creating the Merged Pri file for package:%2, with error :%1.
L Failed to create the Merged Pri file for package:%2 with error %1.
� The optional package %2 has a FullTrust entry point which requires the main package %1 to have the runFullTrust capability which it does not have.
� The optional package with centennial content %2 is not in a related set and it is required to be in a related set specified by the centennial main package %1.
X Windows can't provision the package %1 because it is an unsupported package type.
` Windows can't provision the package %1 because it is not installed on a system volume.
h Windows can't provision the package %1 because its dependency main package is not provisioned.
@ Package %1 is end of life and can no longer be installed.
p Target user for deployment %1 operation on package %2 was changed to DefaultAccount. Original User: %3.
� Redirection to DefaultAccount was attempted for deployment operation %1 on package %2 and blocked because the user is not a device owner. User: %3. Result: %4.
� Windows can't upgrade to package %1 due to a different architecture when policy for the package requires same-architecture upgrades (on 64-bit Windows).
@ Scheduled task %2 could not be enabled due to error: %1.
� Error %1 in package folding: cannot create hardlinking file in main package folder for file %2, because both package %3 and package %4 have this file.
D Successfully added the following uri(s) to be processed: %1.
L Finished resolving action lists. DeploymentRequest action lists:%1.
D Getting registration status of package family %2 for user %1.
p Getting registration status of package family %2 completed with result: %1.(statusFound: %3, Status: %4)
L Failed to determine the type of current user's profile with error %1.
@ Failed to check for a developer license with error %1.
@ Failed to notify RDS of recovery trigger with error %1.
� The InstallStub option cannot be used with package %2 because it is not a bundle containing a stub. Remove this option or specify a different option.
� The package %2 has a host runtime dependency resolving to package %3 containing full trust content which requires the main package %1 to have the runFullTrust capability which it does not have.
d Orphaned AppDataVolume %1 no longer exists, and is now replaced with the package volume %2.
l The preinstalled app %1 will be destaged because it is not applicable for the region of the device.
4 Path missing for package %1, will be ignored.
` Windows cannot install package %1 because it must be installed with an external location.
l Windows cannot install package %1 because it is already installed with a different external location.
h Windows failed to evaluate the preinstalled apps' region applicability with error %1 at step %2.
t Windows cannot install package %1 because existing app package %2 uses the same mutable package directory %3.
� Evaluation of allow list of package family names for BlockNonAdminUserInstall policy failed for rule %1 with error code %2. %3.
, Started activating the %1 package.
, Finished activating the %1 package.
, Started deactivating the %1 package.
, Finished deactivating the %1 package.
0 Started parsing the %1 package manifest.
0 Finished parsing the %1 package manifest.
P Started conflict resolution on %1 package for extension %2 and %3 key.
P 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.
< Started removing the request for the %1 extension.
< Finished removing the request for the %1 extension.
< Started committing the request for the %1 extension.
< Finished committing the request for the %1 extension.
, Started a call to dependency manager
@ Finished a call from dependency manager with error: %1
L Starting to setup the firewall for the %1 package with %2 binaries.
P Completed setting up the firewall for the %1 package with %2 error code.
l 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.
H Starting to create the AppContainer profile for the %1 package.
\ Completed creating the AppContainer profile for the %1 package with %2 error code.
H Starting to create the repository metadata for the %1 package.
X Completed creating the repository metadata for the %1 package by %2 error code.
0 About to call CreateDataSource with %1
4 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
< Begin range request, file name %1, offset %2, size %3
@ Range request progress: file name %1, offset %2, size %3
@ End range request for file name %1, offset %2, size %3
0 PreAllocateFile Start for file %1 size %2
0 PreAllocateFile End for file %1 size %2
D AppxRequestHandler::Run Start for package %1 staging to %2
@ AppxRequestHandler::Run End for Package %1 staged to %2
4 PreAllocatePackage Start: %1 staging to %2
0 PreAllocatePackage End: %1 staging to %2
d 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
8 Starting to delete the de-staged package files.
8 Deleted de-staged package files with result %1.
H Starting to delete the AppContainer profile for the %1 package.
\ Completed deleting the AppContainer profile for the %1 package with %2 error code.
� Hardlink candidates - Current package %1, target package %2, current file path %3, target file path %4, current file size %5, target file size %6.
0 ApplyAppxSharedFileAclsStart for path %1.
< ApplyAppxSharedFileAclsStop completed with result %1.
@ These hardlinks did not have packages in repository: %1.
@ Msixvc staging session method %2 started for package %1.
@ Msixvc staging session method %2 finished for package %1.
H Starting to delete the de-staged package files in directory %1.
8 Deleted de-staged package files with result %1.
0 Started loading the AppX Extensions DLL.
0 Finished loading the AppX Extensions DLL.
0 Successfully registered the %1 package.
D Initialization of the Visual Elements extension was started.
T Initialization of the visual elements extension was completed with error %1.
H Uninitialization of the Visual Elements extension was started.
T Uninitialization of the Visual Elements extension completed with error %1.
X The Visual Elements extension started to commit the deployment for package %1.
h The Visual Elements extension completed committing the deployment for package %1 with error %2.
H The Visual Elements extension started to revert the deployment.
H The Visual Elements extension completed reverting the deployment.
D The Visual Elements extension started installing package %1.
X The Visual Elements extension completed installation of %1 package with error %2.
\ The Visual Elements extension started updating package %1 over existing package %2.
l The Visual Elements extension completed updates to package %1 over existing package %2 with error %3.
D The Visual Elements extension started removing package %1.
T The Visual Elements extension completed removal of package %1 with error %2.
H The Notifications extension initialized app %1 with settings %2.
d App %1 was not initialized for notifications. No notification capabilities were manifested.
h error %1: The Notifications extension was unable to connect to the Push Notification Platform.
T The Notifications extension started periodic update manifest processing (%1).
T The Notifications extension stopped periodic update manifest processing (%1).
p The Notifications extension found URI %2 with a periodic update recurrence of %3 in the manifest (%1).
X The Notifications extension started periodic update temporary registration (%1).
h The Notifications extension stopped periodic update temporary registration with HRESULT %2 (%1).
P The Notifications extension started periodic update registration (%1).
` The Notifications extension stopped periodic update registration with HRESULT %2 (%1).
� %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.
T %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.
t %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.
< error %1: Adding a tile failed with unexpected error.
X Adding a tile failed because the VisualElements element is missing for app %1.
X Adding a tile failed because element '%1' is defined multiple times for app %2.
P Adding a tile failed because color value '%1' is not valid for app %2.
P Adding a tile failed because there are multiple apps with ID %1 defined.
X Adding a tile failed because the required element '%1' is not defined for app %2.
D Adding a tile failed because the resource '%1' is not valid.
h Adding a tile failed because file '%1' could not be opened which represents the tile for app %2.
x Adding a tile failed because changes could not be committed to file '%1' which represents the tile for app %2.
P 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.
Adding 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.
8 error %1: The Visual Elements extension failed.
x 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.
L error %1: Cannot create registry key or value %2 for the %3 package.
L 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.
4 The system app data folder already exists.
0 The system app data key already exists.
@ The application data local root folder already exists.
@ The application data roaming root folder already exists.
< The application data temp root folder already exists.
< The application data settings store already exists.
H The application data user profile packages folder already exists.
H The application data user profile packages key already exists.
L Creation of the system app data folder failed with error code : %1.
H Creation of the system app data key failed with error code : %1.
X Creation of the application data local root folder failed with error code : %1.
X Creation of the application data roaming root folder failed with error code : %1.
X Creation of the application data temp root folder failed with error code : %1.
T 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.
8 Successfully created the system app data folder.
4 Successfully created the system app data key.
D Successfully created the application data local root folder.
H Successfully created the application data roaming root folder.
D Successfully created the application data temp root folder.
@ Successfully created the application data settings store.
L Successfully created the application data user profile packages key
P Successfully created the application data user profile packages folder
8 Error while deleting file %1. Error Code : %2.
< Error while deleting Directory %1. Error Code : %2.
D Error while deleting system app data key. Error Code : %1.
< Application data remains from a previous uninstall.
@ No application data remains from a previous uninstall.
D Local, Roaming and Temp application data roots already exist.
L Error while deleting the existing application data. Error Code: %1.
< Successfully deleted any existing application data.
X State DEH failed to load existing application data settings store. Error Code: %1
P Creation of the application data root folder failed with error code : %1.
@ Successfully created the application data root folder.
8 The application data root folder already exists.
P Creation of application data settings folder failed with error code : %1.
@ Successfully created application data settings folder.
< The application data settings folder already exist.
l Copying the settings apphive into the application data settings folder failed with error code : %1.
X Successfully copied the settings store into the application data settings folder.
D Access Denied error while deleting the system app data key.
X Trying to reset the ACL's on the system app data key failed with error code : %1.
4 Successfully ACL'ed the system app data key.
4 The system app data folder does not exist.
0 The system app data key does not exist.
\ Creation of the application data synchronization lock failed with error code : %1.
0 The application data lock already exists.
0 The application data lock does not exist.
` Verification of the application data synchronization lock failed with error code : %1.
4 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.
D The application data local cache root folder already exists.
\ Creation of the application data local cache root folder failed with error code : %1.
L Successfully created the application data local cache root folder.
T error %1: Windows failed to signal registration change for the %2 package.
T error %1: Windows failed to persist backup eligibility for the %2 package.
P error %1: Windows failed to unregister the state lock for the %2 package
h error %1: Windows failed to add the marker when unable to unistall the state for the %2 package
, The app data folder already exists.
, The app data folder does not exist.
0 Successfully created the app data folder.
D Creation of the app data folder failed with error code : %1.
$ The AC folder already exists.
$ The AC folder does not exist.
, Successfully created the AC folder.
@ Creation of the AC folder failed with error code : %1.
0 The Publisher Root folder already exists.
L Creation of the Publisher Root folder failed with error code : %1.
8 Successfully created the Publisher Root folder.
8 The %1 Publisher Shared folder already exists.
P Creation of the %1 Publisher Shared folder failed with error code : %2.
< Successfully created the %1 Publisher Shared folder.
, The Publishers folder already exists.
H Creation of the Publishers folder failed with error code : %1.
4 Successfully created the Publishers folder.
T Application data local root folder is a mounted folder that has no target.
T Application data roaming root folder is a mounted folder that has no target.
P Application data temp root folder is a mounted folder that has no target.
X Application data local cache root folder is a mounted folder that has no target.
@ Successfully created the secure system app data folder.
T Creation of the secure system app data folder failed with error code : %1.
8 The secure system app data folder already exists.
8 The secure system app data folder does not exist.
@ Set package status for %2 failed with error code : %1.
< Package AppData for %2 unavailable, error code : %1.
L Fetching of policy data for package %1 failed with error code: %2.
L Clearing of policy data for package %1 failed with error code: %2.
\ Writing Setting %3 (index %5) with value %4 for package %2 failed with error code: %1
� %1(%2,%3): error %4: Cannot register the %5 package because the '%6' file type association is reserved for system use.
p %1: error %2: Error during removal of the %3 package because the '%4' registry key could not be deleted.
� %1(%2,%3): error %4: Cannot register the %5 package because the '%6' content type association is reserved for system use.
p %1(%2,%3): error %4: Cannot register the %5 package because the '%6' protocol is reserved for system use.
T error %2: Windows cannot create the AppContainer profile for the %1 package.
H error %2: Windows cannot set up the firewall for the %1 package.
T 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.
� %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.
T error %2: Windows cannot delete the AppContainer profile for the %1 package.
� 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.
� error %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.
x %1 : error %4 : Cannot register the %5 package because there are no free merge indices for the main package '%6'.
t %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
%1 : %2 : %3
%1 : %2 : err=%3 : %4
D Scheduling roaming sync for package %2 failed with error %1.
d Deferred roaming data acquisition for package %1, will block its activation for roaming data.
d Deferred roaming data acquisition for package %1, will not block activation for roaming data.
0 Roaming data status for package %2 is %1.
x 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.
� error %1: Windows cannot register the package because the %2 ActivatableClassID of the %3 contract is not marked with the ActivateAsPackage attribute.
� error %1: Windows cannot register the package because an ActivatableClassID with the same name already exists: '%2'. Provide a different name and try again.
� error %1: Windows cannot register the package because an ActivatableClassID was previously declared with the same name: '%2'. Provide a different name and try again.
t error %1: Windows cannot register the package because the %2 ActivatableClassID name is empty or too long.
d error %1: Windows cannot register the package because the %2 ActivatableClassID is invalid.
� error %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.
t error %1: Windows cannot register the package because the %2 Windows Runtime server name is empty or too long
l 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.
� error %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.
p error %1: Windows cannot register the package because an attribute on the ActivatableClass is invalid.
x 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.
l error %1: Windows cannot register the package because the %2 contract identifier is empty or too long
L 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.
d error %1: Windows cannot register the %2 package because of an internal error or low memory.
d 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.
P 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.
� error %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.
� error %1: windows.licensing failed to start ClipSvc. Try again and contact the package publisher if the problem persists.
� %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
@ %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.
T 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.
� %1(%2,%3): error %4: Cannot register the %5 package because the following error was encountered while parsing the %7 Extension element: %6. The ResourceGroup attribute for this extension must match the parent application.
4 Version %1 selected for Proxy App package.
� error %3: Cannot register the %1 package because the following error was encountered while creating the %2 package dependency file: %4
� error %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 %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
X 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
L Started creating the Dependency Mini Repository for the %1 package.
L 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
� error %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
T Started creating the Dependency Mini Repository for the %1 incoming package.
T Finished creating the Dependency Mini Repository for the %1 incoming package.
T Started updating the Dependency Mini Repository for the %1 upstream package.
T Finished updating the Dependency Mini Repository for the %1 upstream package.
T Started removing the Dependency Mini Repository for the %1 outgoing package.
T Finished removing the Dependency Mini Repository for the %1 outgoing package.
H %2: Package runtime information %1 failed to load (processid=%3).
� error %2: Cannot process the %1 package because the following error was encountered while retrieving its package status: %3
X Upstream dependency scan for the %1 package found the %2 package (PackageKey=%3)
� error %3: Cannot update the DependencyMiniRepository (DMR) file (.pckgdep) for %1 package due to the following error: %2.
P 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.
h %1(%2,%3): error %4: Cannot register the %5 package because the ServerName attribute is invalid.
h %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 task of this type requires a custom background task host.
� %1(%2,%3): error %4: Cannot register the %5 package because ServerName and ResourceGroup attribute are mutually exclusive.
� %1(%2,%3): error %4: Cannot register the %5 package because Executable cannot be specified when no EntryPoint is specified.
� %1(%2,%3): error %4: Cannot register the %5 package because ResourceGroup must match application ResourceGroup when no EntryPoint is specified.
| error %3: Cannot register the %1 package while processing the default background task due to the following error: %2.
� %1(%2,%3): error %4: Cannot register the %5 package because ResourceGroup must not match application ResourceGroup when SupportsMultipleInstances is true.
� %1(%2,%3): error %4: Cannot register the %5 package because Executable cannot be specified when SupportsMultipleInstances is true.
� %1(%2,%3): error %4: Cannot register the %5 package because EntryPoint must be specified when SupportsMultipleInstances is true.
� %1(%2,%3): error %4: Cannot register the %5 package because StartPage must be specified when SupportsMultipleInstances is true.
P error %3: Cannot register the %1 package due to the following error: %2.
P 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.
� %2: Package runtime information %1 is corrupted (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue.
� %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: Package runtime information %1 contains conflicting data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue.
� %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.
T Package runtime information %1 failed to load because exception %2 occurred.
� %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).
x Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3.
P error %3: Cannot register the %1 package due to the following error: %2.
h %1(%2,%3): error %4: Cannot register the %5 package because the Executable attribute is invalid.
t %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.
t APPX manifest DeviceCapability %6: missing required Device element. Registration of package %1 not affected.
l %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
h %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.
X %2: Cannot register package %1 because of a problem with Device element %7: %9
X %2: Cannot register package %1 because of a problem with Function element %8: %9
l %2: Cannot register package %1 because of an error with DeviceCapability[@Name="%6"]\...\%7[@%8="%9"]
T %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
x 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).
T SearchIndexer extension has failed to connect into Windows Search service: %1
8 SearchIndexer extension started initialization
H SearchIndexer extension has finished initialization with error %1
0 SearchIndexer extension started removal
< SearchIndexer extension has finished removal of %1
0 UserDataAccess extension started removal
P UserDataAccess extension has finished removal of %1 (returned with %2)
� %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.
� Geolocation extension could not invoke the Visual Studio simulator to remove package %1. Close the simulator before re-installing the package (error: %2)
P 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 cannot be specified for a preinstall task.
� %1(%2,%3): error %4: Cannot register the %5 package because the Executable attribute cannot be specified for a preinstall task.
P 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 cannot be specified for an update task.
� %1(%2,%3): error %4: Cannot register the %5 package because the Executable attribute cannot be specified for an update task.
4 AppXSvc service initialization failed : %1.
4 Updating service status to %1 failed with %2.
T Starting validation and setting the Trust Label on package %1 with flags %2.
T Finished validation and setting the Trust Label on package %1 with flags %2.
, Modified file %2 found in package %1.
0 File %2 does not belong to package %1.
L Failed to set the Trust Label on package %1 with flags %2. Error: %3.
D %2 file(s) have been validated from block map for package %1.
4 Package %1 has Trust Label already. Flags: %2
p Illegal non-AppStore or non-AppInstaller package integrity validation attempted for package %1. Flags: %2
X Successfully added volume %2 with name "%3", mountPoint "%4", and media ID "%5".
` Successfully set volume %2 with name "%3", mountPoint "%4", and media ID "%5" offline.
\ Successfully set volume %2 with name "%3", mountPoint "%4", and media ID "%5" online.
\ Successfully removed volume %2 with name "%3", mountPoint "%4", and media ID "%5".
` Error %1: Found a corrupt volume %2 with name "%3", mountPoint "%4", and media ID "%5".
� The path "%1" cannot be added as a package volume. Installing apps on external volumes is not supported on this device.
� %1(%2, %3): error %4: Cannot register the %5 package because the following error was encountered while registering WebAccountProvider extension: %6
P 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.
P error %3: Cannot register the %1 package due to the following error: %2.
@ error %2: AoW App Evaluate Install failed for package %1.
@ error %2: AoW App Evaluate Update failed for package %1.
8 error %2: AoW App Commit failed for package %1.
< error %2: AoW App Revert failed with operation %1.
< error %2: AoW App Uninstall failed for package %1.
` error %2: AoW App failed to find the element PayloadName in the Manifest for package %1.
d error %2: AoW App failed to find the element PayloadVersion in the Manifest for package %1.
P error %3: Cannot remove the %1 package due to the following error: %2.
P error %3: Cannot remove the %1 package due to the following error: %2.
� Compiling mof file %1 has the status information: phase error %2, number of object that is at fault %3, first line number of the object %4, last line number of the object %5.
H The WMI provider is not supported because its HostingModel is %1.
8 Notify PackageStatus change for %1 with error %2.
$ Verify for %1 with error %2.
P RegisterNotification for AppId[%1] AppExtensionName[%2] with error %3.
P UnregisterNotification for AppId[%1] AppExtensionName[%2] with error %3.
P GetNotificationPayload for AppId[%1] AppExtensionName[%2] with error %3.
� Windows cannot install the package because the current user is not a member of Administrators group and creation of server extension failed.
P error %3: Cannot register the %1 package due to the following error: %2.
@ AppExecutionAlias directory missing, error code is %1.
| %1(%2,%3): error %4: Cannot register the %5 package. ComServer element was not found in category windows.comServer.
� %1(%2,%3): error %4: Cannot register the %5 package. ComInterface element was not found in category windows.comInterface.
p %1(%2,%3): error %4: Cannot register the %5 package. ComServer element does not have any child elements.
t %1(%2,%3): error %4: Cannot register the %5 package. ComInterface element does not have any child elements.
t %1(%2,%3): error %4: Cannot register the %5 package. AutoConvertTo attribute value can not be the same as Id.
� %1(%2,%3): error %4: Cannot register the %5 package. Cannot specify attribute InsertableObject = true in the Class element when attribute ProgId is not specified.
� %1(%2,%3): error %4: Cannot register the %5 package. Cannot specify the ProxyStubClsid attribute in the Interface element when attribute UseUniversalMarshaler = true.
� %1(%2,%3): error %4: Cannot register the %5 package. Interface element cannot have both AsynchronousInterface and SynchronousInterface attributes.
� %1(%2,%3): error %4: Cannot register the %5 package. SynchronousInterface attribute requires ProxyStubClsid attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. AsynchronousInterface attribute requires ProxyStubClsid attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. Attribute UseUniveralMarshaler = true requires a TypeLib element under the Interface element.
x %1(%2,%3): error %4: Cannot register the %5 package. LocalId could not be parsed as a hexidecimal/base16 number.
| %1(%2,%3): error %4: Cannot register the %5 package. LibraryFlag could not be parsed as an unsigned decimal integer.
� %1(%2,%3): error %4: Cannot register the %5 package. TypeLib element requires at least one Win32Path or Win64Path child.
� %1(%2,%3): error %4: Cannot register the %5 package. Conversion element requires at least one Readable or ReadWritable.
� %1(%2,%3): error %4: Cannot register the %5 package. Format element requires exactly one FormatName or StandardFormat attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. DataFormats elements requires exactly one DefaultFormatName or DefaultStandardFormat attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. DataFormat element requires exactly one FormatName or StandardFormat attributes.
� %1(%2,%3): error %4: Cannot register the %5 package. Multiple DataFormat elements under a DataFormat element have the same values for all attributes.
X %1(%2,%3): error %4: Cannot register the %5 package. The path %6 was not found.
p %1(%2,%3): error %4: Cannot register the %5 package. The element must be under an Application element.
� %1(%2,%3): error %4: Cannot register the %5 package. The ProgId referenced in the Class element does not refer back to the same Class Id.
� %1(%2,%3): error %4: Cannot register the %5 package. The TypeLib referenced in the Interface element does not have the specified VersionNumber.
� %1(%2,%3): error %4: Cannot register the %5 package. To use the AsynchronousInterface and SynchronousInterface attributes, there must be two Interfaces elements with the same ProxyStubClsid attribute value. One Interface element will be the synchronous interface that must refer to the asynchronous interface via the AsynchronousInterface attribute. The second element is the asynchronous interface that must refer to the synchronous interface via the SynchronousInterface attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. The VersionIndependentProgId referenced in the Class element refers back to a ProgId element without a CurrentVersion attribute.
%1(%2,%3): error %4: Cannot register the %5 package. The VersionIndependentProgId referenced in the Class element refers back to a Class with a different VersionIndependentProgId attribute value. Verify that the ProgId marked as the CurrentVersion refers to the correct Clsid.
%1(%2,%3): error %4: Cannot register the %5 package. The VersionIndependentProgId referenced in the Class element refers back to a Class with no VersionIndependentProgId attribute. Verify that the ProgId marked as the CurrentVersion refers to the correct Clsid.
� %1(%2,%3): error %4: Cannot register the %5 package. There is a circular reference with the ProgIds. Verify the CurrentVersion attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. The ProgId referenced in CurrentVersion attribute value points to a ProgId without Clsid or CurrentVersion attribute.
� %1(%2,%3): error %4: Cannot register the %5 package. SurrogateServer element cannot have both CustomSurrogateExecutable and SystemSurrogate attributes.
� %1(%2,%3): error %4: Cannot register the %5 package. There is a circular reference with the TreatAsClasses. Verify the TreatAs attribute.
l Package COM is not supported on this platform. %1 packaged COM extensions have not been registered.
� %1(%2,%3): error %4: Cannot register the %5 package. The Id referenced in the ClassReference element does not refer to a Class element in the manifest.
� %1(%2,%3): error %4: Cannot register the %5 package. Packages with classic CompatMode packaged COM extensions cannot be registered with a user ExternalLocation.
P error %3: Cannot register the %1 package due to the following error: %2.
x Deleting the shared hardlink for the eventlog dll for package %2 at location %3 during %4 operation, error is %1.
� Extension 'windows.mailProvider' with a <MailProvider> requires CompatMode attribute to be 'classic' to register as inproc MAPI. Package full name: %1.
� Extension 'windows.mailProvider' without a <MailProvider> requires that CompatMode attribute be 'modern' and Scope to be 'user' to register as out-of-proc MAPI. Package full name: %1.
\ Failed to set Desktop AppX metadata for the package. Error code: %1, package name: %2
` Failed to set Desktop AppX metadata for the path. Error code: %1, for move: %3, path: %2
d Failed to create output location for Desktop AppX registry files. Error code: %1, path: %2
P Failed to delete the Desktop AppX registry file. Error code: %1, path: %2
H Desktop AppX registry file was unexpectedly a directory. Path: %1
X Failed to delete the Desktop AppX registry directory. Error code: %1, path: %2
t Failed to process the Desktop AppX registry file. Error code: %1, source path: %2, dest path: %3, flags: %4
` Couldn't install interop asssembly for %1 package because the assembly already exists: %2
h Version downgrade happened for interop asssembly for %1 package, from version %2 to version %3
0 PIA copyfile for %1 package failed, %2
< CC file pattern %1, hresult %2, error %3, index %4
� error %4: Package %1 declares capability %3 but its HostRuntimeDependency %2 does not. The package will be registered without this capability.
� error %4: Package %1 declares custom capability %3 but its HostRuntimeDependency %2 does not. The package will be registered without this capability.
� error %4: Package %1 declares device capability %3 but its HostRuntimeDependency %2 does not. The package will be registered without this capability.
| %1(%2,%3): error %4: Cannot register the %5 package. Administrator privileges required to install packaged service
< %1: PackagedServiceDEH successfully parsed manifests
< %1: PackagedServiceDEH successfully parsed manifests
< %1: PackagedServiceDEH successfully parsed manifests
< %1: PackagedServiceDEH successfully parsed manifests
X %1(%2,%3): PackagedServiceDEH successfully parsed manifest for package %5 install
X %1(%2,%3): PackagedServiceDEH successfully parsed manifest for package %5 removal
P %1(%2,%3): PackagedServiceDEH failed to delete service %6 in package %5
T %1: PackagedServiceDEH PostOsUpgradeEvaluateRequest completed successfully
8 %1: Deployment aborts due to active service %2.
, %1: TerminateApplications successful.
4 %1: AllowUninstall successful for package %2.
@ %1: GetActiveAumidsInPackage successful for package %2.
@ %1: TerminateServicesInPackage successful for package %2.
p %1: TerminateSingleService for uninstall successful for service %3 in package %2, terminateService: %4.
l %1: TerminateSingleService for update successful for service %3 in package %2, terminateService: %4.
8 %1: Cannot terminate service %3 in package %2.
< %1: Succesfully terminated service %3 in package %2.
� %1: Service %3 in package %2 has an error level that is marked either critical or severe. Package cannot be removed in this state.
@ %1: Force terminated service %3 process in package %2.
8 OpenService for service %2 failed with error %1.
4 The shortcut variable '%2' is not supported.
D The ApplicationRegistration variable '%2' is not supported.
� The registry key path must be compatible with the 'windows.classicAppCompatKeys' <Extension>'s scope attribute. e.g. An HKLM key requires 'machine' scope. Package full name: %1.
\ 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.
D Creating Resiliency File %3 for %1 Operation on Package %2.
< Deleting Resiliency File %1 finished with code %2.
� Publishing deployment request status to TDL for package %1 : operation %2 state %3 percentage %4 errorcode %5 impersonating %6
@ Published deployment request status to TDL for package %1
� Failed to read the sideload limit from Software Licensing policy with error %1. Max number of developer sideloaded packages is limited to %2 by default.
p Finished servicing singleton package %1. Setting the singleton package state to enabled returned with %2.
x Failed to install loopback access rule. Error code: %4, PackageSid: %1, PackageFullName: %2, Capabilities: %3.
x Failed to uninstall loopback access rule. Error code: %4, PackageSid: %1, PackageFullName: %2, Capabilities: %3.
� %1(%2,%3) %4: The %5 package cannot be registered because an unexpected error occured while processing the Local Experience Pack extension.
8 PreInstalledVolumeServicing ApplySuccess started
8 PreInstalledVolumeServicing ApplySuccess finished
8 PreInstalledVolumeServicing ResetCleanup started
8 PreInstalledVolumeServicing ResetCleanup finished
H PreInstalledVolumeServicing did not find an upgrade to service
\ PreInstalledVolumeServicing failed to get the PreInstalled AllUserStore with error %1
X PreInstalledVolumeServicing failed to Activate required Instances with error %1
X PreInstalledVolumeServicing failed to get the DefaultAccount Token with error %1
T PreInstalledVolumeServicing failed to Migrate StateRepository with error %1
H PreInstalledVolumeServicing failed to Remove apps with error %1
L PreInstalledVolumeServicing failed to Prepare new apps with error %1
T PreInstalledVolumeServicing failed to Delete the Upgrade Key with error %1
L PreInstalledVolumeServicing failed to Remove package %2 with error %1
P PreInstalledVolumeServicing failed to Upgrade package %2 with error %1
d PreInstalledVolumeServicing failed to get the Applicable Version Upgrade key with error %1
h Extension 'windows.shadowCopyExclude' requires that Scope be 'machine'. Package full name: %1.
� Extension 'windows.systemFileAssociation' requires that CompatMode attribute be 'classic' and Scope to be 'machine'. Package full name: %1.
� Extension 'windows.errorReporting' requires CompatMode attribute to be 'classic' to register a runtime exception module. Package full name: %1.
� Extension 'windows.customControlPanelItem' requires that CompatMode attribute be 'classic' and Scope to be 'machine'. Package full name: %1.
� Extension 'windows.approvedShellExtension' requires that CompatMode attribute be 'classic' and Scope to be 'machine'. Package full name: %1.
� Extension 'windows.eventTracing' requires Scope attribute to be 'machine' and CompatMode attribute to be 'classic' to register a provider. Package full name %2 failed with error %1.
t A Provider element was found to have a duplicate Id attribute %3. Package full name %2 failed with error %1.
x A Provider element was found to have a duplicate Name attribute %3. Package full name %2 failed with error %1.
t A Channel element was found to have a duplicate Name attribute %3. Package full name %2 failed with error %1.
� A Channel element with the Name attribute %3 referenced by an ImportChannel element in Provider with Id %4 was not found. Package full name %2 failed with error %1.
� A circular dependency between Provider elements was detected. See ImportChannel element with Name %3 in Provider with Id %4. Package full name %2 failed with error %1.
� An event tracing provider from package %1 was not registered due to its guid conflicting with another package. Provider guid: %2, provider name: %3, other package name: %4.
� An event tracing provider from package %1 was not registered due to its name conflicting with another package. Provider guid: %2, provider name: %3, other package name: %4.
� An event tracing provider from package %1 was not registered due to a channel name conflicting with another package. Provider guid: %2, provider name: %3, channel name: %4, other package name: %5.
� An event tracing provider from package %1 was not registered due to its dependency provider not being registered. Provider guid: %2, provider name: %3, dependency provider guid: %4.
� An event tracing provider registration from package %1 was overwritten when another package with a conflicting guid was installed. Provider guid: %2, provider name: %3, other package name: %4.
� An event tracing provider registration from package %1 was overwritten when another package with a conflicting name was installed. Provider guid: %2, provider name: %3, other package name: %4.
� An event tracing provider registration from package %1 was overwritten when another package with a conflicting channel name was installed. Provider guid: %2, provider name: %3, channel name: %4, other package name: %5.
An event tracing provider registration from package %1 was overwritten due to its dependency provider being overwritten when another package with a conflicting provider was installed. Provider guid: %2, provider name: %3, dependency provider guid: %4.
l Registering the event tracing provider with Id %4 and Name %3 from package %2 failed with error %1.
l Unregistering the event tracing provider with Id %4 and Name %3 from package %2 failed with error %1.
P error %3: Cannot register the %1 package due to the following error: %2.
P error %3: Cannot register the %1 package due to the following error: %2.
Invalid
Add
Remove
Update
Stage
DeStage
Register
( Get list of registered packages
Fix staged packages
( Delete all files of the package
RegisterByPackageFullName
StageUserData
PreRegisterPackage
MovePackageOperation
AddVolumeOperation
DeleteVolumeOperation
SetVolumeOfflineOperation
SetVolumeOnlineOperation
GetDefaultVolumeOperation
SetDefaultVolumeOperation
$ RegisterByPackageFamilyName
$ GeneratePreviewTilesOperation
$ ResetApplicationDataOperation
0 ResetAllApplicationDataForUserOperation
ResumeOperation
, ResetSingleApplicationDataOperation
OnDemandRegisterOperation
( AddByPackageFamilyNameOperation
ProvisionPackageOperation
$ AddFromAppInstallerOperation
( UpdateUsingAppInstallerOperation
0 RegisterPackageOnLogonForUserOperation
$ DeprovisionPackageOperation
( SetMutablePackagesOnlineOperation
$ StageByAppInstallerOperation
RepairPackageOperation
ResetPackageOperation
Not Validated
Unknown
Windows Store
Windows Component
Unknown
Unsigned
Inbox
Windows Store
Developer Unsigned
Developer Signed
Line Of Business
Queued
De-Queued
SharedAppsRedirect
$ OptionalDependenciesHandled
BundleProcessed
Indexed
Resolved
Approved
BlockDeploymentIfNeeded
DynamicDependenciesInUse
( PreEvaluatePackagesInUseClosed
Evaluated
PrerequisitesChecked
( SqmSetOperationForPackageUpdate
CheckRestoredState
$ PreStagePackagesInUseClosed
Staged
TilesProcessed
MRTDataPopulated
$ MutablePackageDirectoryAdd
MachineRegisterAdd
SystemRegister
StageUserDataProcessed
PackagesInUseClosed
$ ResolvedDeferredRegistrations
SingletonRegisterAdd
RegistrationChanged
$ ProcessHostRuntimePackages
DeployInContainer
VersionSuperceded
SingletonRegisterRemove
MachineRegisterRemove
De-Indexed
Committed
PackagesInUseRestarted
$ MutablePackageDirectoryRemove
MRTDataRemoved
De-Staged
DeStagedUserData
DataFlushed
PreSharedAppsSync
SharedAppsSync
No Error
l Attribute not in required format of type:value, or the format of the type or value portion is invalid
, Type is not supported for this bus
, Value is not supported for this bus
4 Value is blocked, and not allowed on this bus
d Function requires a Device with a specific Id element, and cannot be used with an Id of "any"
NotInstallable
Installable
Installed
RequiresReinstall
Offline
Invalid
Universal
Windows8x
WindowsPhone8x
Desktop
Mobile
Xbox
Team
IoT
IoTHeadless
Server
Holographic
XboxSRA
XboxERA
ServerNano
7067329
Core
x86
x64
ARM
ARM64
Neutral
x86 CHPE on ARM64
� Windows 8 Desktop ARM32 packages are blocked on ARM64 devices, as they will not function properly. To install this package, upgrade it to the Windows 10 Universal Windows Platform.
User
Machine
Not an optional package
Optional Package
Modification Package
DefaultOption
( ForceApplicationShutdownOption
DevelopmentModeOption
RepositoryRecoveryOption
PushButtonResetOption
BackgroundTaskOption
InstallAllResources
, ForceTargetApplicationShutdownOption
( PreserveRoamableApplicationData
RequiredContentGroupOnly
( SkipReregisterIfPackageStatusOk
PackageIsCoServicing
RegisterHighestVersion
PreserveApplicationData
FailIfNeedsRemediation
$ SkipSignatureValidationOption
SkipStagingForMoveOption
PreRegisterApplyTrustAce
ForceUpdateFromAnyVersion
RemoveForAllUsers
ApplyToExistingPackages
RetainFilesOnFailure
StageInPlace
AllowUnsigned
HighPriorityRequest
NormalPriorityRequest
LowPriorityRequest
AppRestoreRequest
ImmediatePriorityRequest
PreRegisterIndexing
$ RepairAppRegistrationOption
FirstLogonInstall
ReIndex
ApplyStagedInPlaceUpdate
FailRemoveIfInUse
DismDeprovision
RequestReputationCheck
, DeferRegistrationWhenPackagesAreInUse
8 StageAdditionalRelatedSetUpdateRequiredPackages
StageFromUpdateAgent
RegisterAsSystem
DisableUninstall
ValidateDependencies
DeleteXapFile
$ MoveWithAllOptionalPackages
$ RemoveForUserProfileDeletion
0 ApplyMutablePackageDirectoryProcessing
4 SkipDeploymentOperationRpcCallerIsAdminCheck
( SkipPausePackageIfRestoreFails
( FailOnRedirectToDefaultAccount
StageInPlaceUpdate
InstallFull
InstallStub
UseCurrentStubPreference
$ ValidateDependenciesForStage
$ MinimalRegisterInContainer
$ DestagePreinstalledPackage
OverrideNonRemovable
( DoNotEnqueueSubsequentRepairSteps
PerformAll
ApplyTrustAce
Indexing
ReIndex
ValidateDependencies
�4 V S _ V E R S I O N _ I N F O ��
l|O
l|O? @ S t r i n g F i l e I n f o 0 4 0 9 0 4 B 0 L C o m p a n y N a m e M i c r o s o f t C o r p o r a t i o n ^ F i l e D e s c r i p t i o n A p p X D e p l o y m e n t S e r v e r D L L n ' F i l e V e r s i o n 1 0 . 0 . 2 0 3 4 8 . 3 6 9 2 ( W i n B u i l d . 1 6 0 1 0 1 . 0 8 0 0 ) R I n t e r n a l N a m e A p p X D e p l o y m e n t S e r v e r . d l l � . L e g a l C o p y r i g h t � M i c r o s o f t C o r p o r a t i o n . A l l r i g h t s r e s e r v e d . b O r i g i n a l F i l e n a m e A p p X D e p l o y m e n t S e r v e r . d l l . m u i j % P r o d u c t N a m e M i c r o s o f t � W i n d o w s � O p e r a t i n g S y s t e m D P r o d u c t V e r s i o n 1 0 . 0 . 2 0 3 4 8 . 3 6 9 2 D V a r F i l e I n f o $ T r a n s l a t i o n �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX