App-V 5.0 SP2 Client and the pain to upgrade

December 6, 2013 - App-V

Microsoft released the long awaited SP2 for the App-V 5.0 client. With new features like better integration with the local OS (shell extensions!), the possibility to sequence some dependencies like MsXML and Visual C++ run times. A welcome change with this release is that the volume license editions of Office 2013 Standard and Professional, Visio 2013 Std & Pro and Prject 2013 Std & Pro are supported! Many customers will look at App-V 5.0 again!

It’s time to deploy the new App-V client to workstations!

As I’m always trying to get my hands on the MSI’s to deploy software, the first thing I did was getting and extracting the sources. Once I had played arround with the MSI’s I decided to take a walk to consider things and throw the MSI’s gently in the bin and install the EXE wrapper instead!! The next step was to find the required confguration parameters and finally deploy to workstations.

Prepare the sources

Get the App-V Client 5.0 SP2 binaries from the MDP ISO and extract the contents from it.

APPV_CLIENT_SETUP.EXE /Layout /LayoutDir=c:\temp

This will extract all the MSI’s from the EXE. The result is the App-V Client MSI and the all language pack(s) available.


I’m only interested in the English version, I will install only one language pack.


Install the App-V client (MSI) and language packs

Command-line to install the App-V client:

msiexec /i appv_client_MSI_x64.msi /qn /NORESTART AcceptEULA=1 /L*v “LogPath\appv5SP2_client_MSI_x64.log”

English Language Pack:

msiexec /i “appv_client_LP_enus_x64.msi” /qn /NORESTART AcceptEULA=1 /L*v “LogPath\appv5SP2_appv_client_LP_enus_x64.log”

So far so good!

Issue’s with upgrading SP1 to SP2

A clean SP2 client installation works fine by using the MSI’s, but upgrading a previous version gave nothing but errors.


Sync-AppvPublishingServer : CoCreateInstance() failed

 Get-AppvClientPackage : CoCreateInstance() failed. The Microsoft Application Virtualization Service may not have been started. Please verify that the service is running.

It’s clear that the AppV service wasn’t running, but I wasn’t able to get it up and running again.

Reinstalling the AppV Client solved this issue, using the EXE wrapper!  … Then I decided to use the default EXE wrapper instead.

Install the App-V client (EXE)

I’m using these setup paramaters against the AppV client installer.






/Log “<myLogPath>\appv5SP2_client_EXE_x64.log”

Don’t forget the /AcceptEULA paramater, apart from the information in the log file “Initializing string variable ‘ACCEPTEULA’ to value ‘0’” you will get an meaningless error;

Exit code: 0x68e

But this silent install gave the same error when upgrading an SP1 App-V Client!

All things considered, I gave up and ended up with a manual installation of APPV_CLIENT_SETUP.EXE :-S

Luckily I had only some POC workstations with AppV client 5.0 SP1 installed! For new installations the MSI’s did the job.


With the deployment of the SP1 client, I used a Powershell script to configure the client. There are also ADMX templates avalaible to deploy with GPO’s and the MSI/EXE installers accept switches to configure the client.


My intention was to blog about the deployment of the App-V Client 5.0 SP2 using the MSI installer. But it became a total failure, I’m publishing this post just to start a discussion and maybe to find a solution over time.




11 thoughts on “App-V 5.0 SP2 Client and the pain to upgrade

Chetan Kumar Tammala

Hi Ben,

I really appreciate your efforts in helping others and sharing the knowledge. We are actually in the plan of upgrading our App-V clients, which are running with client v5.0, to v5.0 SP2. I just tested the upgrade manually and the upgrade went fine. However, post the upgrade I don’t see the App-V system tray icon and the shortcut in start menu, which were there in App-V 5.0 client. Not sure if this is an expected behavior.

Also, I am not quite sure about the upgrade path from v5.0 to 5.2.


Ben De Vriese

That is normal behavior. Since App-V 5.0 SP2 the client UI isn’t a part of the App-V client anymore.

Starting from SP2 the client UI is a separate download. You can choose to install the client UI native (MSI) or get the .appv package and distribute it with App-V 5.

Get the Microsoft Application Virtualization 5.0 Client UI Application from Microsoft:

Chetan Kumar Tammala

Thank you for the details, Ben. I got the details. BTW, I don’t see a switch to suppress the machine restart. When I upgrade my client from 5.0 to 5.0 SP2, it automatically restarting the computer. I tried using “/noreboot” but that didn’t help.


Chetan Kumar Tammala

Hi Ben,

Nevermind, I got the switch to suppress the reboot. Using “/REBOOT=ReallySuppress” did the trick. Thank you!

Bucky Badger

Ben, did you ever find a work around for the SP1 to SP2 upgrade?

Ben De Vriese

No I didn’t looked into it.
The workaround with The EXE installer was fine for my needs.

Ben De Vriese

Hotfix Package 1 for Microsoft Application Virtualization 5.0 Service Pack 2 should fix this issue.

Jonas Berends


Hotfix 1 (KB2921362) also had upgrade issues and has been replaced by hotfix 2 (KB2934349 – see

Cliff Steinman

Have to set it to true

Jonas Berends

Hi Ben,

I got similar issues with “my” MSI-installers when trying to update SP1 to SP2 with hotfix 4 recently (App-V service wouldn’t start after the update). Turned out I missed VC++ 2013 in my installation script, which is a prereq for hotfix 4 (and my script originally only installed the VC++ redistributables up to 2012). After adding VC++ 2013 redist, the service started up fine again.


Cory G

The problem I’ve run into using the EXE is there is no control over what language packs are installed – it installs all of them. The MSIs are the only way to be granular with the LPs. Have you found a workaround for this?

The MSIs worked if SP1 was completely uninstalled from the system and reboot occurs prior to installing SP2 client.

Note this was also on an RDS server so I was using the RDS components.

Comments are closed.