-->
A.NET application crashes after installing the Microsoft Server Application Virtualization client Symptoms. A natively installed.NET application may crash after the Microsoft Server Application Virtualization (Server App-V) client agent is installed on a computer. How To Install Application Virtualization Client. Microsoft Application Virtualization Desktop Client or MS App-V allows applications to be deployed to the client from a virtual application server. It removes the need for traditional local installation of applications. MS App-V supports the virtualization and streaming of an application.
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.0 client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer.
What to do before you start
Review and install the software prerequisites:
Install the prerequisite software that corresponds to the version of App-V that you are installing:
App-V 5.0 SP1 and App-V 5.0 SP2 – no new prerequisites in these versions
Review the client coexistence and unsupported scenarios, as applicable to your installation:
Deploying coexisting App-V clients Planning for the App-V 5.0 Sequencer and Client Deployment Unsupported or limited installation scenarios App-V 5.0 Supported Configurations
- Review the locations for client registry, log, and troubleshooting information:
Client registry information
- By default, after you install the App-V 5.0 client, the client information is stored in the registry in the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMICROSOFTAPPVCLIENT
- When you deploy a virtualized package to a computer that is running the App-V client, the associated package data is stored in the following location:
C:ProgramDataApp-V
However, you can reconfigure this location with the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMICROSOFTSOFTWAREMICROSOFTAPPVCLIENTSTREAMINGPACKAGEINSTALLATIONROOT
Client log files
- For log file information that is associated with the App-V 5.0 Client, search in the following log:
Event logs/Applications and Services Logs/Microsoft/AppV
- In App-V 5.0 SP3, some logs have been consolidated and moved to the following location:
Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog
For a list of the moved logs, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-event-logs-moved).
- Packages that are currently stored on computers that run the App-V 5.0 Client are saved to the following location:
C:ProgramDataApp-V<package id><version id>
Client installation troubleshooting information
- See the error log in the %temp% folder.
- To review the log files, click Start, type %temp%, and then look for the appv_ log.
To install the App-V 5.0 Client
Copy the App-V 5.0 client installation file to the computer on which it will be installed.
Choose from the following client types:
Client type File to use Standard version of the client appv_client_setup.exe Remote Desktop Services version of the client appv_client_setup_rds.exe
Double-click the installation file, and click Install. Before the installation begins, the installer checks the computer for any missing App-V 5.0 Prerequisites.
Review and accept the Software License Terms, choose whether to use Microsoft Update and whether to participate in the Microsoft Customer Experience Improvement Program, and click Install.
On the Setup completed successfully page, click Close.
The installation creates the following entries for the App-V client in Programs:
.exe
.msi
language pack
Note
After the installation, only the .exe file can be uninstalled.
Application Virtualization Client Disabled
To install the App-V 5.0 client using a script
Install all of the required prerequisite software on the target computers. See What to do before you start. If you install the client by using an .msi file, the installation will fail if any prerequisites are missing.
To use a script to install the App-V 5.0 client, use the following parameters with appv_client_setup.exe.
Note
The client Windows Installer (.msi) supports the same set of switches, except for the /LOG parameter.
/INSTALLDIR Specifies the installation directory. Example usage: /INSTALLDIR=C:Program FilesAppV Client
/CEIPOPTIN Enables participation in the Customer Experience Improvement Program. Example usage: /CEIPOPTIN=[0|1]
/MUOPTIN Enables Microsoft Update. Example usage: /MUOPTIN=[0|1]
/PACKAGEINSTALLATIONROOT Specifies the directory in which to install all new applications and updates. Example usage: /PACKAGEINSTALLATIONROOT='C:App-V Packages'
/PACKAGESOURCEROOT Overrides the source location for downloading package content. Example usage: /PACKAGESOURCEROOT='http://packageStore'
/AUTOLOAD Specifies how new packages will be loaded by App-V 5.0 on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0]. Example usage: /AUTOLOAD=[0|1|2]
/SHAREDCONTENTSTOREMODE Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: /SHAREDCONTENTSTOREMODE=[0|1]
/MIGRATIONMODE Allows the App-V 5.0 client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage: /MIGRATIONMODE=[0|1]
/ENABLEPACKAGESCRIPTS Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage: /ENABLEPACKAGESCRIPTS=[0|1]
/ROAMINGREGISTRYEXCLUSIONS Specifies the registry paths that will not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=softwareclasses;softwareclients
/ROAMINGFILEEXCLUSIONS Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS 'desktop;my pictures'
/S[1-5]PUBLISHINGSERVERNAME Displays the name of the publishing server. Example usage: /S2PUBLISHINGSERVERNAME=MyPublishingServer
/S[1-5]PUBLISHINGSERVERURL Displays the URL of the publishing server. Example usage: /S2PUBLISHINGSERVERURL=pubserver
/S[1-5]GLOBALREFRESHENABLED Enables a global publishing refresh. Example usage: /S2GLOBALREFRESHENABLED=[0|1]
/S[1-5]GLOBALREFRESHONLOGON Initiates a global publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1]
/S[1-5]GLOBALREFRESHINTERVAL Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] /S[1-5]GLOBALREFRESHINTERVALUNIT Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2GLOBALREFRESHINTERVALUNIT=[0|1]
/S[1-5]USERREFRESHENABLED Enables user publishing refresh. Example usage: /S2USERREFRESHENABLED=[0|1] /S[1-5]USERREFRESHONLOGON Initiates a user publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1]
/S[1-5]USERREFRESHINTERVAL Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] /S[1-5]USERREFRESHINTERVALUNIT Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2USERREFRESHINTERVALUNIT=[0|1]
/Log Specifies a location where the log information is saved. The default location is %Temp%. Example usage: /log C:logslog.log
/q Specifies an unattended installation. /REPAIR Repairs a previous client installation. /NORESTART Prevents the computer from rebooting after the client installation. The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V 5.0 SPX and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V.
/UNINSTALL Uninstalls the client. /ACCEPTEULA Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1
/LAYOUT Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.0. No value is expected. /LAYOUTDIR Specifies the layout directory. Requires a string value. Example usage: /LAYOUTDIR=”C:Application Virtualization Client”
/?, /h, /help Requests help about the previous installation parameters.
To install the App-V 5.0 client by using the Windows Installer (.msi) file
Install the required prerequisites on the target computers. See What to do before you start. If any prerequisites are not met, the installation will fail.
Ensure that the target computers do not have any pending restarts before you install the client using the App-V 5.0 Windows Installer (.msi) files. The Windows Installer files do not flag a pending restart.
Deploy one of the following Windows Installer files to the target computer. The file that you specify must match the configuration of the target computer.
Type of deployment Deploy this file Computer is running a 32-bit Microsoft Windows operating system appv_client_MSI_x86.msi Computer is running a 64-bit Microsoft Windows operating system appv_client_MSI_x64.msi You are deploying the App-V 5.0 Remote Desktop Services client appv_client_rds_MSI_x64.msi
Using the information in the following table, select the appropriate language pack .msi to install, based on the desired language for the target computer. The xxxx in the table refers to the target locale of the language pack.
What to know before you start:
The language packs are common to both the standard App-V 5.0 client and the Remote Desktop Services version of the App-V 5.0 client.
If you install the App-V 5.0 client using the .exe, the installer will deploy only the language pack that matches the operating system running on the target computer.
To deploy additional language packs on a target computer, use the procedure To install the App-V 5.0 client by using Windows Installer (.msi) file.
Type of deployment Deploy this file Computer is running a 32-bit Microsoft Windows operating system appv_client_LP_xxxx_ x86.msi Computer is running a 64-bit Microsoft Windows operating system appv_client_LP_xxxx_ x64.msi
Got a suggestion for App-V? Add or vote on suggestions.
Got an App-V issue? Use the App-V TechNet Forum.
Microsoft Application Virtualization Client Install
Related topics
-->You can use the procedures in this section to configure and manage the Microsoft Application Virtualization (App-V) Client. Procedures are provided for manual interaction with the App-V Client by using the App-V Client Management Console and also by using the command line.
Application Virtualization Client Error
In This Section
How to Use the Desktop Notification Area for Application Virtualization Client Management
Includes information about using the features and commands that are available from the Windows desktop notification area.
How to Manage Virtual Applications Manually
Provides information about how to manage the virtual applications by using the App-V Client Management Console.
Microsoft Application Virtualization Client
How to Configure the Application Virtualization Client Settings Manually
Provides a set of procedures that you can use to configure App-V Client settings by using the App-V Client Management Console.
How to Manage Virtual Applications by Using the Command Line
Provides important procedures you can use to manage virtual applications and packages by using the SFTMIME command-line language.
How to Configure the App-V Client Registry Settings by Using the Command Line
Provides a set of procedures you can use to change the configuration of the App-V Client.
Troubleshooting Information for the Application Virtualization Client
Provides information about troubleshooting the App-V Client.
Application Virtualization Client Reference
Contains detailed technical reference material related to installing and managing system components.