MZ@ !L!This program cannot be run in DOS mode. $թթթԩթԩԩRichթPEdW"  -` .rdatap@@.rsrc @@W T.rdataT.rdata$zzzdbg .rsrc$01!H.rsrc$02x8P h ( 8 H X hhb@ "!@( h} WEVT_TEMPLATE/8008 0 0tPPp(p  ef8D:;   ̏lqrvlYY<AO|)#2#l4#4#''*+l..X2266::>>iBtBQFVF9J:J$BJCJ0JJKK eKhKL#KK`&-L.L,YM]M-!N"N1NN4 R R7UU:YY<]]=$>Startup Shutdown Logon Logoff API ,Component Startup $Client Common Catalog Publishing 0Embedded Scripting 0Virtual File System ,Virtual Services Settings 4Dynamic Configuration ,Client Management Subsystems 0Client Co-existence ,Virtual Registry Streaming 0Client Streaming UX @Virtual Application Launch (Virtual Object Reporting 0Publishing Refresh Integration $Side by Side @AppManagementConfiguration Info Start Stop Send Critical Error Warning Information (Client Startup (Client Shutdown User Logon User Logoff DDynamic Configuration Change API Request DImpersonation/Deimpersonation ,Configure Package (Publish Package ,Unpublish Package (Remove Package hConfigure Virtual Application Connection Group dPublish Virtual Application Connection Group hUnpublish Virtual Application Connection Group `Remove Virtual Application Connection Group <Execute Embedded Scripts HVirtual File System Redirection @Configure Virtual Services (Setting Changes LParse Dynamic Configuration File ,PowerShell Invoke ,Subsystem Startup 0Application Launch <Virtual Environment Start 0User State Deletion 4Background Streaming @PSObject Get Property Value 8PSObject Invoke Method HConnect to AppV Client Service 0Powershell Process 4Create Reporting Data 4Upload Reporting Data Streaming (Repair Package `Repair Virtual Application Connection Group 0Publishing Refresh LStop Package or Connection Group Integration $Side by Side 0Enable/Disable Appv Admin Operational 4Virtual Applications SLAPI check failed because of failure to read license info. {error: %1} \The Client service started successfully. DThe Client service shut down. A required component (%1) cannot be loaded. Please repair your installation. {error: %2} The Client service could not get the list of currently logged-on users. If users experience any issues running virtual applications, please logoff and logon again, or restart the service. {error: %1} The Client could not register a logged-on user. The user will not be able to access any App-V services, including running virtual applications. Please have the user logoff and logon again. {error: %1-%2} @The Client could not unregister a user that logged off. If other users experience any issues logging on, please restart the Client service. {error: %1-%2} The Client could not determine the identity of a caller on a public request, and the request was denied. {error: %1} 8The Client could not register a caller, or verify the registration status of a caller, on a public request, and the request was denied. {error: %1-%2} A public request to the Client was initiated by a caller which granted the Client the authority for %1, whereas the Client requires at a minimum RPC_C_IMP_LEVEL_IMPERSONATE in order to satisfy a request on the caller's behalf. The calling application will need to modify its security settings for outbound calls in order to successfully access the Client API. The access to the client was denied. The caller didn't have required permission for this operation. The Client failed to register for power notifications. {error: %1-%2}. The Client failed to unregister for power notifications. {error: %1-%2}. The Client service cannot be started due to reboot required. The Client service cannot be started due AppV being disabled. PIAppVClient::%1 COM method entered. TIAppVClient::%1 COM method exited. %2 Active processing could not be shut down, this may lead to delays or hangs for Client shutdown. {error: %1-%2} Package %1 version %2 was successfully configured in folder '%3'. Package %1 version %2 was successfully published for the user. Package %1 version %2 was successfully published for all users. pPackage %1 version %2 was unpublished for the user. tPackage %1 version %2 was unpublished for all users. PPackage %1 version %2 was removed. Package %1 version %2 failed configuration in folder '%3' with error %4-%5. Virtual application connection group %1 version %2 was successfully configured. Virtual application connection group %1 version %2 failed configuration with error %3-%4. Virtual application connection group %1 version %2 was successfully published for the user. Virtual application connection group %1 version %2 was successfully published for all users. Virtual application connection group %1 version %2 was unpublished for the user. Virtual application connection group %1 version %2 was unpublished for all users. Virtual application connection group %1 version %2 was removed. Failed to unpublish package %1 version %2 because the package is published as part of one or more connection groups. Unpublish all connection groups that reference this package and try again. Failed to remove package %1 version %2 because the package is configured as part of one or more connection groups. Remove all connection groups that reference this package and try again. A package could not be unpublished for the user because it is currently in use by the user. Shut down all applications in the package, and try again.%nPackage %1%nVersion %2%nActivity #%3 A package could not be globally unpublished because it is currently in use. Make sure all users have shut down all applications in the package, and try again.%nPackage %1%nVersion %2%nActivity #%3 |A package could not be removed because it is currently in use. Make sure all users have shut down all applications in the package, and try again.%nPackage %1%nVersion %2%nActivity #%3 An app connection group could not be unpublished for the user because it is currently in use by the user. Shut down all applications in the group, and try again.%nConnection Group %1%nVersion %2%nActivity #%3 An app connection group could not be globally unpublished because it is currently in use. Make sure all users have shut down all applications in the group, and try again.%nConnection Group %1%nVersion %2%nActivity #%3 An app connection group could not be removed because it is currently in use. Make sure all users have shut down all applications in the group, and try again.%nConnection Group %1%nVersion %2%nActivity #%3 LThe package %1 version %2 could not be reconfigured because it is not configured on the system. Ensure the package ID and version ID are correct and try again. The package %1 version %2 could not be configured because it can only be used with 64-bit versions of Windows. The package %1 version %2 could not be configured because it is not compatible with this version of Windows. LThe package %1 version %2 could not be configured becaused the Deployment Configuration file '%3' could not be found. Ensure the path is correct and try again. LThe package %1 version %2 could not be configured because the Deployment Configuration file '%3' is not valid. Verify that the document is valid and try again. The package %1 version %2 could not be configured because the Deployment Configuration file does not match the the specified package. Ensure the GUIDs in the Deployment Configuration file match those of the package and try again. The package %1 version %2 could not be configured because the user account does not have administrative privileges. The package %1 version %2 could not be published globally because the user account does not have administrative privileges. ,The package %1 version %2 could not be published because the package has not been configured on the system. Configure the package and try again. <The package %1 version %2 could not be published becaused the User Configuration file '%3' could not be found. Ensure the path is correct and try again. <The package %1 version %2 could not be published because the User Configuration file '%3' is not valid. Verify that the document is valid and try again. The package %1 version %2 could not be published because the User Configuration file does not match the the specified package. Ensure the GUIDs in the User Configuration file match those of the package and try again. The package %1 version %2 could not be published globally because a User Configuration file was specified. Either publish the package for the user with the User Configuration file specified or do not supply a User Configuration. The package %1 version %2 could not be unpublished globally because the user account does not have administrative privileges. The package %1 version %2 could not be unpublished because it is not published to the target of the unpublish operation. The package %1 version %2 could not be removed because the package is not configured on the system. The package %1 version %2 could not be removed because the user account does not have administrative privileges. The package %1 version %2 cannot be repaired because the package is not configured on the system. HThe package %1 version %2 was repaired successfully, but the package is published in one or more Virtual Application Connection Groups. Settings are associated with the group, so you may need to clear settings for the Virtual Application Connection Groups associated with this package. PThe app connection group %1 version %2 could not be added because the app connection group file '%3' could not be found. Ensure the path is correct and try again. PThe app connection group %1 version %2 could not be added because the package %3 version %4 is not configured on the system. Configure the package and try again. TThe app connection group %1 version %2 could not be added because the app connection group file '%3' is not valid. Verify that the document is valid and try again. The app connection group %1 version %2 could not be added because the user account does not have administrative privileges. `The app connection group %1 version %2 could not be enabled because the app connection group has not been added on the system. Add the app connection group and try again. pThe app connection group %1 version %2 could not be enabled because the package %3 version %4 is not published to the target of the operation. Publish the package and try again. The app connection group %1 version %2 could not be enabled globally because the user account does not have administrative privileges. The app connection group %1 version %2 could not be disabled because it is not enabled for the target of the disable operation. The app connection group %1 version %2 could not be disabled globally because the user account does not have administrative privileges. The app connection group %1 version %2 could not be removed because the package it has not been added on the system. The app connection group %1 version %2 could not be removed because the user account does not have administrative privileges. The app connection group %1 version %2 cannot be repaired because the app connection group has not been added on the system. pA package could not be unpublished for the user because it is currently in use by the user. The package will be unpublished at a later time.%nPackage %1%nVersion %2%nActivity #%3 PA package could not be globally unpublished because it is currently in use. The package will be unpublished at a later time.%nPackage %1%nVersion %2%nActivity #%3 The package %1 version %2 was detected to have a pending global Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the package or stop the package. The app connection group %1 version %2 was detected to have a pending global Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the app connection group or stop the app connection group. The package %1 version %2 was detected to have a pending user Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the package or stop the package. The app connection group %1 version %2 was detected to have a pending user Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the app connection group or stop the app connection group. A connection group could not be unpublished for the user because it is currently in use by the user. The connection group will be unpublished at a later time.%nConnection Group %1%nVersion %2%nActivity #%3 A connection group could not be globally unpublished because it is currently in use. The connection group will be unpublished at a later time.%nConnection Group %1%nVersion %2%nActivity #%3 A package could not be published for the user because it is currently in use by the user. Shut down all applications in the package, and try again.%nPackage %1%nVersion %2%nActivity #%3 A package could not be globally published because it is currently in use. Make sure all users have shut down all applications in the package, and try again.%nPackage %1%nVersion %2%nActivity #%3 An app connection group could not be published for the user because it is currently in use by the user. Shut down all applications in the group, and try again.%nConnection Group %1%nVersion %2%nActivity #%3 An app connection group could not be globally published because it is currently in use. Make sure all users have shut down all applications in the group, and try again.%nConnection Group %1%nVersion %2%nActivity #%3 hA package could not be published for the user because it is currently in use by the user. The package will be published at a later time.%nPackage %1%nVersion %2%nActivity #%3 HA package could not be globally published because it is currently in use. The package will be published at a later time.%nPackage %1%nVersion %2%nActivity #%3 A connection group could not be published for the user because it is currently in use by the user. The connection group will be published at a later time.%nConnection Group %1%nVersion %2%nActivity #%3 A connection group could not be globally published because it is currently in use. The connection group will be published at a later time.%nConnection Group %1%nVersion %2%nActivity #%3 |The package %1 version %2 was detected to have an upgrading task. The App-V Client cannot start the virtual environment. Please try again in several minutes once the update is complete. The application connection group %1 version %2 was detected to have an upgrading task. The App-V Client cannot start the virtual environment. Please try again in several minutes once the update is complete. The pending publish operation for package %1 version %2 was not performed because network connectivity is not available. The package %1 version %2 was detected to have a pending publish or unpublish operation. The App-V Client cannot remove the package. Pending user operations are processed at logon, and pending global operations are processed at startup. Please try again when any related pending operations are complete. Activity #%3 The app connection group %1 version %2 was detected to have a pending task. The App-V Client cannot remove the app connection group. Pending user operations are processed at logon, and pending global operations are processed at startup. Please try again when any related pending operations are complete. Activity #%3 4The UserSID value %1 is not valid. Please ensure it is a valid SID and that the associated user is logged in when you run the cmdlet. {error: %2-%3} While publishing package %1 version %2 an error occurred when obtaining the integration settings for each of the connection groups that the package belongs to {error %3 - %4}.%nThe package has not been published. Package %1 version %2 was user published while belonging to globally published Connection Group %3 version %4.%nTherefore, although the package will be published to the user, it will not be assocated with the Connection Group until it is also published globally. hThe App-V driver mappings were not successfully updated when Package %1 version %2 was added (error: %3-%4).%nConnection Groups containing this package may not work correctly. The App-V driver mappings were not successfully updated when Package %1 version %2 was removed (error: %3-%4).%nConnection Groups previously containing this package may not work correctly. The App-V driver mappings were not successfully updated when Package %1 version %2 was published (error: %3-%4).%nConnection Groups previously containing this package may not work correctly. The App-V driver mappings were not successfully updated when Package %1 version %2 was unpublished (error: %3-%4).%nConnection Groups previously containing this package may not work correctly. Failed to move Catalog folder  %1 to new required location  %2 . {error: %3} XCatalog folder  %1 was migrated to new required location  %2 , but the old location could not be removed. The Catalog will be used from the new location. {error: %3} Catalog folder  %1 was migrated to new required location  %2 , but the new location previously existed. Failed due to could not get catalog folder. {error: %1-%2} The package %1 version %2 was detected to be in an irreconcilable state and has been removed. Please manually remove any remaining data (by default under %ProgramData%\App-V\) when re-adding the package. The app connection group %1 version %2 was detected to be in an irreconcilable state and has been removed. Please manually remove any remaining data (by default under %ProgramData%\App-V\) when re-adding the app connection group. The Client service has encountered a critical security issue and must shut down immediately. {error %1-%2} PThe App-V client failed to create a process for %1 script event %2 with command line: '%3'. Windows error: %4. The path must be a Windows application (.exe file). The App-V client waited for the designated Timeout of %1 seconds for %2 script event %3 with executable: '%4' to complete. Because the Timeout was reached, the script process was terminated. Since RollbackOnError is set to true in script definition, the current AppV Client operation was rolled back due to script timeout. Running %1 script defined in package %2 for event %3. Script execution was initiated by User Account: '%4'; command line: '%5'. A %1 script is defined in package %2 for event %3 but will not be run because embedded scripting is disabled for this client. Parsing of Embedded Script XML in package Manifest failed. Package: %1; event name: %2; XML parsing error: %3-%4. Please ensure that the XML script section in the package manifest for event %2 is well formed. An error was encountered while reading the setting to enable scripts. Error code: %1-%2. The App-V client waited for the designated Timeout of %1 seconds for %2 script event %3 with executable: '%4' to complete. Because the Timeout was reached, the script process was terminated. Since RollbackOnError is set to false in script definition, the timeout is ignored and current AppV Client operation will continue. %1 script for event %2 with command line: '%3' exited with failure error code: %4. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back. %1 script for event %2 with command line: '%3' exited with failure error code: %4. Because Rollback is set to false in the script definition, the script process failure is ignored and the current AppV Client operation will continue. XAppv Client Scripting Component failed to acquire a proper token before querying Appv Client settings for Scripting, the query of the settings for Scripting may fail. hThe move/rename of a directory was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory. `The delete of a directory was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory. dThe delete of directory '%1' was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory. Failed to get Virtual Service information from manifest.%n Package: %1%n Version: %2%n Error: %3-%4 Virtual Service startup type %1 is not supported. The only supported configuration values are Automatic, Manual and Disabled. `Service %1 failed to start due to error %2. tDependentService %1 failed to start due to error %2. Service %1 failed while handling a control message due to error %2. tCould not acquire service start lock due to error %1. HStarting automatic service %1. LService %1 could not be stopped. `Automatic service %1 could not be started. Request to change the service configuration is rejected. Currently, changing service configuration during runtime is not supported. Request to delete a virtual service is rejected. Currently, deleting a service during runtime is not supported. Service %1 is created as a native service instead of a virtual service. Creating virtual service during runtime is not supported. Request to set virtual service security is rejected. Currently, changing service security during runtime is not supported. @The client service has encountered an error monitoring settings. Changes to some settings will not take effect until the service is restarted. {error: %1} Failed to load provided xml.%nDOM Error: %1%nReason: %2%nLine: %3%nColumn: %4%nOffset: %5 Failed to validate provided xml.%nDOM Error: %1%nReason: %2 (Invalid connection group document format. There are no packages specified in the connection group document for connection group %1, version %2. \Invalid connection group XML document format. There needs to be at least one mandatory package in the connection group XML document for connection group %1, version %2. Failed to update the connection groups for user %1. Some virtualized applications may fail to execute properly. Error: %2 All of the package groups associated with the publishing of package %1, version %2 were not successfully refreshed. Error: %3 All of the package groups associated with the unpublishing of package %1, version %2 were not successfully refreshed. Error: %3 All of the package groups associated with the adding of package %1, version %2 were not successfully refreshed. Error: %3 Failed to get the package groups associated with the removal of package %1, version %2. Error: %3. All of the package groups associated with the removal of package %1, version %2 were not successfully refreshed. Error: %3 Package group %1, version %2 was not successfully refreshed. Error: %3 8Mandatory package %3, version %4 specified in connection group %1, version %2 has not been added to the computer or has not been entitled to the user. hError %3-%4 occurred while attempting to delete the user publishing data associated with group %1, version %2 for user %5. The publishing data may need to be removed manually. PError %3-%4 occurred while attempting to unpublish group %1, version %2 for user %5. This error should correct itself on the next publishing refresh for the user. Failed to get the package groups associated with the unpublish of package %1, version %2. Error: %3. xError encountered while executing command %1. Error: %2 xWarning raised while executing command %1. Warning: %2 Error encountered when accessing a property value of an App-V Publishing Server. This Publishing Server has been skipped. Error encountered when accessing a property value of an App-V Client Connection Group. This Connection Group has been skipped. Error encountered when accessing a property value of an App-V Client Package. This Package has been skipped. Error encountered when accessing a property value of an App-V Client Application. This Application has been skipped. $Error encountered when attempting to access the packages of an App-V Client Connection Group. This Connection Group will display no Packages. Error encountered when attempting to access the applications of an App-V Client Package. This Package will display no Applications. Error encountered during Powershell process startup or exit while executing command '%1'. Error encountered while executing command '%1'. Please refer to the AppV Client log for error details. Error encountered when accessing a property value of an App-V Client Configuration. Process %1 failed to start due to %4 subsystem failure. Package ID %2. Version ID %3. Error: %5-%6 Unable to inject into a non-virtual process with PID %1. This process will not be able to use virtual components. Could not takeover extension points ownership from legacy package %1. Error: %2 Could not give extension points ownership back to legacy package %1. Error: %2 0MigrationMode is enabled but legacy App-V Client is not installed on the machine. Managing Authority policy will not be applied for the package %1. |Taking over extension points ownership using command: %1 xGive back extension points ownership using command: %1 Failed reading Managing Authority policy for package %1. Error: %2-%3 Failed reading old Managing Authority policy for package %1. Error: %2-%3 LError '%2' waitig for command: %1 LTimed out waitig for command: %1 dError '%2' getting exit code for command: %1 LCommand '%1' exited with code: %2 A conflict was detected in the user configuration setting for enabling the virtual registry in virtual application connection group %1 version %2. The virtual application could not be started. dUser VFS COW state deleted for package ID %1. User VFS COW state deletion failed for package ID %1, error %2-%3. %1 application from package ID %2 failed to launch. process ID %3, error %4-%5. User VFS COW folder validation failed for source: %1, target: %2. lFailed to publish roaming packages, error %1-%2. hFailed to publish roaming groups, error %1-%2. Security information for VFS directory %1 has changed from its previous value. App-V client is relying on a mobile network connection to stream packages. Background streaming has been suspended due to the mobile network approaching/exceeding the data limit or roaming. HApp-V client has detected an unrestricted network connection or a mobile connection with sufficient remaining data capacity. Background streaming has resumed. App-V client has detected that you are trying to launch a new application on a mobile network connection. The launch has been blocked due to the mobile network approaching/exceeding the data limit or roaming. XUnexepected error. The App-V client was unable to register for the network cost callback and will be unable to suspend background loads if the network cost increases. 8Unexpected error %1-%2. The App-V client was unable to start the background load queue. Packages will not be loaded in the background automatically. xUnexpected error. The App-V client was unable to start the background load queue properly. Package information is not available to determine if background loads are local or remote. App-V client has entered connected standby mode. Background streaming has been suspended. App-V client has exited connected standby mode. Background streaming has resumed. App-V client has detected an HTTP error 502 while attempting to stream a package. This can be the result of a proxy server not being configured to allow a high enough rate of requests from the client to the package server. The package %1 version %2 could not be configured because the path %3 could not be reached. Ensure the path is correct and try again. 8The package %1 version %2 could not be configured because the package is corrupt. Ensure that the package file is a valid App-V package and try again. The package %1 version %2 could not be configured because the package store location is not on a valid NTFS file system. Ensure that the package store location is a valid NTFS file system and try again. The package %1 version %2 could not be configured due to low disk space. Ensure that there is enough disk space and try again. The package %1 version %2 could not be configured because the specified URL is not valid. Ensure that the URL is valid and try again. 4The package %1 version %2 could not be configured because the target location %3 already exists. Ensure that this location is removed and try again. DThe package %1 version %2 could not be mounted because the network connection has been lost or is unavailable. Check your network connection and try again. dThe package %1 version %2 could not be mounted. The operation failed with HRESULT %3, probably due to low disk space. Ensure that there is enough disk space and try again. The package %1 version %2 could not be mounted due to the network connection timing out. Check your network connection and try again. The package %1 version %2 full mount was suspended because the user who initiated the operation has logged off. The package %1 version %2 failed to be configured because the package is not valid for the current CPU architecture. Content required by an application could not be retrieved from the network. A request for file %2 from package version %1 failed with error %3. Check your network connection and try again. hThe App-V Client failed to initialize properly. The Streaming Mini-Filter failed to initialize with error code %1. Please verify that the App-V Client is installed properly. A request for the file %1 from process %2 is being processed as SYSTEM since no suitable user token could be found. A request for the file %1 from process %2 is being processed as an alternate user %3. 4App-V client has detected that the system has exited idle state. Background streaming has been suspended due to the system coming out of idle state. App-V client has detected that the system has entered idle state. Background streaming has resumed. xApp-V client failed to create the idle state detector. |App-V client failed to register for idle state callback. dThe AppVStreamingUX application experienced an AppV error while attempting to connect to the AppVClient service. The AppVStreamingUX process will now exit. AppV Error: %1-%2 TThe AppVStreamingUX application experienced a COM error while attempting to connect to the AppVClient service. The AppVStreamingUX process will now exit. HResult: %1 xThe AppVStreamingUX application experienced an AppV error while attempting to stop a package or connection group. Running Virtual Environment ID: %1, Version: %2, AppV Error: %3 - %4 A conflict was detected in the configuration settings for Virtual Object exclusions in virtual application connection group %1 version %2. The virtual application could not be started. Verify that the settings are correct and try again. A conflict was detected in the 'enabled' setting for Virtual Object subsystem in virtual application connection group %1 version %2. The virtual application could not be started. Verify that the settings are correct and try again. The connection group %1 version %2 could not be published because the virtual objects settings of the individual packages conflict. Verify that the virtual objects settings are the same for all member packages and try again.%nError code: %3 - %4 Failed to publish package %1 version %2 because its virtual objects settings do not match those of other packages in connection group %3 version %4.%nVerify that the virtual objects settings are the same for all member packages and try again.%nError code: %5 - %6 Failed to save last report data cache file path %1 to the registry due to error %2. If there is a Client failure before the next save attempt, and the report data must be loaded from the cache, some records may be missing. Reporting data cache could not be loaded from %1 due to error %2-%3. A new report data cache file will be generated and saved separately. Any report data from the previous cache file will be lost. 0Reporting data manager queue worker thread is exiting on unexpected wait condition %1, error code %2. No further report records will be processed. Reporting data cache could not be saved to disk after adding new records (rc = %1-%2); those records may be lost if the Client shuts down before the next attempt to save or transmit the cache. tReporting data cache has exceeded the maximum cache size, and older records will be discarded to make room for new records until the cache can be transmitted to a Reporting Server. Reporting data cache could not be sent to Reporting Server. (rc = %1-%2). ,Failed to add application launch data to the reporting queue. This application launch will not be reported to the reporting server. (rc = %1-%2). 4Failed to add application shutdown data to the reporting queue. This application shutdown will not be reported to the reporting server. (rc = %1-%2). LFailed to add virtual environment created data for the launching application. The application launch will not be reported to the reporting server. (rc = %1-%2). XFailed to add virtual environment terminated data for the terminating application. The application shutdown will not be reported to the reporting server. (rc = %1-%2). `Failed to save updated cached file after upload due to error %1-%2; duplicate records may be sent to the server if the cache must be reloaded before the next save attempt. lFailed to add virtual process launch failure information for the terminating process. The application launch failure will not be reported to the reporting server. (rc = %1-%2). DA virtual application could not be launched from package '%1' because the App-V Client Service is not running. Start the App-V Client Service and try again. The virtual application '%1' could not be launched because the user is not entitled to the package to which it belongs. Either publish the package to the user or globally and try again. The virtual application '%1' could not be launched because the App-V Client could not determine which environment to use. Provide a priority to the app connection group for the package and try again. The virtual application '%1' could not be launched because the service '%2' could not be started. The virtual application '%1' could not be started because the App-V Subsystem '%2' could not be initialized. {error: %3-%4} XThe virtual environment for connection group %1 version %2 could not be created because the package %3 version %4 is not published. Publish the package and try again. pPublishing Refresh started.%n URL: %1%n Global: %2 Publishing Refresh stopped.%n URL: %1%n Global: %2%n Return code: %3 - %4 XSettings synced.%n Return code: %1 - %2 `Settings sync failed.%n Error code: %1 - %2 |Getting client information failed.%n Error code: %1 - %2 Getting server publishing data failed.%n URL: %1%n Error code: %2 - %3 Getting client published data failed.%n Error code: %1 - %2 tPart or all packages publish failed.%n published: %1%n failed: %2 %nPlease check the error events of 'Configure/Publish Package' before this message for the details of the failure. pPart or all packages un-publish failed.%n un-published: %1%n failed: %2 %nPlease check the error events of 'Unpublish Package' before this message for the details of the failure. Part or all groups publish failed.%n published: %1%n failed: %2 %nPlease check the error events of 'Configure/Publish Virtual Application Connection Group' before this message for the details of the failure. Part or all groups un-publish failed.%n un-published: %1%n failed: %2 %nPlease check the error events of 'Unpublish Virtual Application Connection Group' before this message for the details of the failure. Failed to publish group due to the failure of the package.%n Group GUID: %1%n Group Version GUID: %2%n Package GUID: %3 dUnknown protocol for package URI.%n input: %1 HttpRequest initialize failed.%n URL: %1%n Error code: %2 - %3 HttpRequest sendRequest failed.%n URL: %1%n Error code: %2 - %3 xThe content could not be coverted to unicode.%n URL: %1 The content from server is not valid XML for publishing.%n URL: %1%n Error code: %2 - %3 Failed to create default machine policy document.%n Package: %1, %2%n Error code: %3 - %4 Failed to create machine policy document from string.%n Package: %1, %2%n Error code: %3 - %4 Failed to create user policy document from string.%n Package: %1, %2%n Error code: %3 - %4 Failed to create package group descriptor document from string.%n Group: %1, %2%n Error code: %3 - %4 Failed to get publishing server record from registry.%n Server ID: %1%n Error code: %2 - %3 The URL has already been used by other publishing server.%n Server ID: %1%n URL: %2 No URL was supplied for the publishing server.%n Server ID: %1 The ID for the publishing server is out of the range.%n Server ID: %1%n Valid Range: [1~5] The interval of hours for the publishing server is out of the range.%n Server ID: %1%n Interval: %2%n Valid Range: [0~23] The interval of days for the publishing server is out of the range.%n Server ID: %1%n Interval: %2%n Valid Range: [0~365] The interval unint for the publishing server is not valid.%n Server ID: %1%n Interval Unit: %2%n Valid Values: 0/Hour, 1/Day The stored URL %1 for the server %2 is incorrectly formatted. xSyncAppvPublishingServer completed successfully: '%1'. SyncAppvPublishingServer failed due to a PowerShell error.%nError: '%1' \Deimpersonation failed.%n Error: %1 - %2. Read policy identities failed.%n URL: %1%n Global: %2%n For deployment configuration: %3%n Error: %4 - %5. Write policy identities failed.%n URL: %1%n Global: %2%n For deployment configuration: %3%n Error: %4 - %5. File type associations, shell extensions, and shortcuts updated. Failed to update file type associations, shell extensions, and shortcuts.%n Error: %1 - %2. The connection group %1 version %2 could not be published because the virtual COM settings of the individual packages conflict. Verify that the virtual COM settings are the same for all member packages and try again.%nError code: %3 - %4 Package %1 version %2 could not be published because its virtual COM settings conflict with those of other packages in connection group %3-%4. Verify that the virtual COM settings are the same for all member packages and try again.%nError code: %5 - %6 Package %1 version %2 could not be published because its virtual file system settings conflict with other packages in connection group %3-%4. Verify that the virtual COM settings are the same for all member packages and try again.%nError code: %5 - %6 An error was encountered while reading the setting to enable or disable Dynamic Virtualization. Dynamic Virtualization is enabled by default and can be modified using the Set-AppvClientConfiguration Powershell cmdlet. Error code: %1-%2. Dynamic Virtualization is currently disabled. Publishing will not take effect for shell extensions, browser plugins, or ActiveX controls. To modify this setting, use the Set-AppVClientConfiguration Powershell cmdlet. |The SxS assembly '%1' could not be installed because its payload file '%2' is not part of the package. Please ensure this assembly is installed natively to ensure package functionality. lA timeout occurred while streaming an application, which may have prevented the application from running. The application should start successfully the next time it is launched. LEnable Appv failed with error %1. PDisable Appv failed with error %1. Controller ,StreamingManager (CatalogManager 4VirtualizationManager 0IntegrationManager ,PublishingManager 0SubsystemController $ScriptManager ,ReportingManager <RPC_C_IMP_LEVEL_ANONYMOUS <RPC_C_IMP_LEVEL_IDENTIFY @RPC_C_IMP_LEVEL_IMPERSONATE <RPC_C_IMP_LEVEL_DELEGATE user machine CRIMpZ[Nʞ[E$WEVT$]]x^ imCHANL<Microsoft-AppV-Client/AdminHMicrosoft-AppV-Client/Operational\Microsoft-AppV-Client/Virtual ApplicationsMAPSLPVMAP\t  VMAP4    VMAP$ ComponentType4EmbeddedScriptingScope,ImpersonationLevelTTBL0Z:TEMP( FTۃn'BVD EventDataA5oDataKNameError ErrorTEMP<.ɥV\"^j1VD EventDataA5oDataKNameError  PErrorTEMPAQ[U#d=VTD EventDataA3oDataKNameItem ItemTEMPm/N/,Q؀ŻrED EventDataA3oDataKNameName A9oData!KNameHResult  NameHResultTEMP"kP] ?D EventDataA5oDataKNameItem1 A5oDataKNameItem2  Item1Item2TEMP,1R@8ZUV D EventDataA=oData%KName ErrorHigh A;oData#KNameErrorLow ,DErrorHighErrorLowTEMPx sBz]l??;BD EventDataAAoData)KName StringParam A=oData%KName ErrorHigh A;oData#KNameErrorLow    StringParamErrorHighErrorLowTEMP(h i|1,]ec6-4D EventDataACoData+KName StringParam1 ACoData+KName StringParam2 A=oData%KName ErrorHigh A;oData#KNameErrorLow     StringParam1 StringParam2ErrorHighErrorLowTEMP  ɌtʕQ3,)bDD EventDataA3oDataKNameItem A5oDataKNameError  $ ItemErrorTEMP^IcQ(4)*D EventDataAAoData)KName ScriptScope A=oData%KName EventType AAoData)KName CommandLine A5oDataKNameError P4ScriptScopeEventTypeCommandLineErrorTEMP`sODW*GD EventDataAAoData)KName ScriptScope A9oData!KNamePackage A=oData%KName EventType PScriptScopePackageEventTypeTEMP6 ݜS\|5TMnD EventDataAAoData)KName ScriptScope A9oData!KNamePackage A=oData%KName EventType A9oData!KNameUserSid AAoData)KName CommandLine P4HScriptScopePackageEventTypeUserSidCommandLineTEMPVv>Ry|'V.D EventDataA9oData!KNameTimeout AAoData)KName ScriptScope A=oData%KName EventType AAoData)KName CommandLine  P,H`TimeoutScriptScopeEventTypeCommandLineTEMP4T х\UTÉD EventDataA?oData'KName LastFolder A=oData%KName ReqFolder |LastFolderReqFolderTEMP<܋7VT@&pD EventDataA?oData'KName LastFolder A=oData%KName ReqFolder A5oDataKNameError 4LastFolderReqFolderErrorTEMPP$(WmpD EventDataA9oData!KNamePackage A9oData!KNameVersion A7oDataKNameFolder PackageVersionFolderTEMPd\l|z_^D EventDataA9oData!KNamePackage A9oData!KNameVersion A7oDataKNameFolder A=oData%KName ErrorHigh A;oData#KNameErrorLow PackageVersionFolderErrorHighErrorLowTEMP 0KLW:xR9'D EventDataA9oData!KNamePackage A9oData!KNameVersion $8PackageVersionTEMP`eD6tVe@紧D EventDataA9oData!KNamePackage A=oData%KName ErrorHigh A;oData#KNameErrorLow PackageErrorHighErrorLowTEMPSٯ[ٶ$!~D EventDataA]oDataEKNameCurrentImpersonationLevel 8CurrentImpersonationLevelTEMP4 ?VL9ｇD EventDataACoData+KName PackageGroup A9oData!KNameVersion  ! PackageGroupVersionTEMPt"JB;D EventDataAIoData1KNameConnectionGroup A9oData!KNameVersion A?oData'KName ActivityID  =8= L=$ConnectionGroupVersionActivityIDTEMP 8>0KLW:xR9'D EventDataA9oData!KNamePackage A9oData!KNameVersion `>t>PackageVersionTEMP?/][;EJ[ D EventDataA9oData!KNamePackage A9oData!KNameVersion A=oData%KName ErrorHigh A;oData#KNameErrorLow ,@@@T@l@PackageVersionErrorHighErrorLowTEMPDA71]\t!3 BD EventDataAIoData1KNameConnectionGroup ACoData+KName GroupVersion A9oData!KNamePackage AGoData/KNamePackageVersion LBpBBB$ConnectionGroup GroupVersionPackage$PackageVersionTEMPC)FS: ( D EventDataA7oDataKNameString A3oDataKNameFlag  C CStringFlagTEMPhD6LPTk'@=h VD EventDataA5oDataKNameValue |DValueTEMPXEq}М]"Po$:!=D EventDataA7oDataKNameValue1 A7oDataKNameValue2 EEValue1Value2TEMPpFn1@TqL2)D EventDataA5oDataKNameValue A7oDataKNameString FFValueStringTEMPGZ'Yr=Y=D EventDataA5oDataKNameValue A=oData%KName ErrorHigh A;oData#KNameErrorLow HH0HValueErrorHighErrorLowTEMPpLI'kӌP=I<D EventDataA5oDataKNameGuid1 A5oDataKNameGuid2 A5oDataKNameGuid3 IIIGuid1Guid2Guid3TEMPKRn$U- yD EventDataA7oDataKNameString A3oDataKNameFlag  A=oData%KName ErrorHigh A;oData#KNameErrorLow TK hKxKKStringFlagErrorHighErrorLowTEMPT4Mf t PVD EventDataA7oDataKNameString A5oDataKNameFlag1  A5oDataKNameFlag2  A=oData%KName ErrorHigh A;oData#KNameErrorLow M M MMMStringFlag1Flag2ErrorHighErrorLowTEMPlN,c/ZЫqD EventDataA/oDataKNameId A9oData!KNameVersion A3oDataKNamePath 8ODOXO IdVersionPathTEMPtP=8\ho=D EventDataA5oDataKNametGuid A9oData!KNametString A9oData!KNameHResult PP PtGuidtStringHResultTEMPQz%Uf[^:?D EventDataA3oDataKNameFile A1oDataKNamePid QQFile PidTEMP\RtV`VValoD EventDataA3oDataKNameFile A1oDataKNamePid A1oDataKNameSid  S0S0]]d_6 6X0]]d_77>0]]H_8 8>0]]_: :>0]]d_; ;>0]]_0]]^ģ0]]^У|0]]^ܣ00]]h=0]]^h=0]]^ @ 0H]],_ @ 0H]],_4 0]](`d0]](` @0]](`@D0]](`\$0]](`00]](`d0]](` 4 0]](`$4 0]](`(0]](`, 0]]D`0 0]]D`4 `0]]D`8q@q>0]]``<r@r`0]]``@v@v 0]]``Dw@w 0]]``Hx@x 0]]``Ly@y0]]``Pz@z`0]]``T{@{`0]]``X|@|`0]]``\}@}0]]```~@~0]]``d@`0]]``h@0]]``lYY0]]|`pA AP&0]]`tB B(0]]`xC C30]]_|D D30]]_E E\0]]_F F>0]]_G G>0]]_H H>0]]_I I>0]]_J J>0]]_K K>0]]_L L@0]]_M M70]]_N N70]]_O O>0]]H_)#@)#)0]]`*#@*#)0]]`+#@+#0]]\a,#@,#0]]\a-#@-#0]]\a.#@.#0]]\aĤ/#@/#0]]xaȤ0#@0#0]]xa̤1#@1#`0]]aФ2#@2#`0]]aԤ4#@4#0]]\aؤ''*0]]`ܤ''C0]]^* *( 0]]d_* *( 0]]_* *.0]]d_* @*`0]]d_* @*`0]]_* *L0]]d_+ +L0]]d_+ +( 0]]d_+ +`0]]d_+ +( 0]]d_+ @+( 0]]d_ ..(#<]]a2@2.0]]$a2@2L0]]$a2@2`10]]`2@2 0]]H_ 2 @200]]d_$2 @200]]_(22`0]]`,6@60]]@a06@60]]@a4660]]@a8660]]@a<66|/0]]@a@660]]@aD6@60]]@aH6@60]]@aL6!60]]bP66D0]]H_T6630]]H_X6630]]H_\6630]]H_`6630]]H_d66D0]]H_h6!630]]bl6!640]]bp6!630]]bt6!630]]bx6630]]H_|6!6hO0]]b6!60]]b6!@6P0]]b6!@6Q0]]b6@60]]@a6@60]]@a6@60]]@a6@60]]@a::|/0]]a::00]]a:%:HS0]]tb> >(#0]]a> >(#0]]a> >!0]]_> >U0]]d_iB @iB( 0]]ajB @jB\0]]akB@kB00]]aĥlB@lB00]]aȥmB@@mB0]]ḁnB @nB00]]aХoB@oB00]]aԥpB@pB00]]aإqB@qB00]]aܥrB@rB00]]asB @sB00]]atB@tB00]]aQFQF`0]]`RFRF`0]]`SFSF`0]]`TFTF 0]]`UF UF 0]]`VFVF@0]]`9J$@9JB0]]Xb:J$@:JI0]]XbBJ$@BJ|/0]]Xb CJ$CJ|/0]]XbJ$J|/0]]XbJ$J\0]]XbJ$J|/0]]XbJ$JD0]]Xb J$JD0]]Xb$J$JD0]]Xb(J$JD0]]Xb,J$JHH0]]Xb0K$K`0]]Xb4K$K\0]]Xb8K$K\0]]Xb<K$K`0]]Xb@K$K\0]]XbDeK$eK>0]]XbHfK$fK>0]]XbLgK$gK>0]]XbPhK$hK>0]]XbTK$KF0]]XbXK$KE0]]Xb\K$KC0]]Xb`K$KC0]]XbdK$KD0]]XbhK$KD0]]XblK$KD0]]XbpK$@K 0]]Xbt-L$@-L`0]]Xbx.L$.L`0]]Xb|YM$YM|/0]]XbZM$ZMK0]]Xb[M$[MK0]]Xb\M$@\M0]]Xb]M$@]M|/0]]Xb!N !N!0]]_"N "NU0]]d_N NU0]]d_ R&@ R00]]b R&@ R0]]bU'U 0]]bY!@Y0]]b](@]0]]b](@]0]]b,i ProductVersion10.0.14393.0DVarFileInfo$Translation =Size of data streamed to disk for each package on the system.$AppV Client Streamed Data Percentage$AppV Client Streamed Data PercentageHThe percentage of data streamed from the primary feature of the package.Primary Feature % StreamedPrimary Feature % Streamed