Hi everyone, my name is Keshav and I’m an App-V support engineer here at Microsoft. I recently came across an interesting issue where the App-V 4.6 SP3 client fails to install so I thought I would share what we found with you here. It’s a rare problem but at least with this you’ll know how to fix it in case you ever happen to run across it.

512 = Detects the range of versions including the value in VersionMax.

2

Detects products and applications but does not remove.

What this all means is that if the installer finds any App-V product with an upgrade code of {515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} and a version less than “4.6.3.24870” then the installer tries to migrate the existing product installed on the machine to the recent version (which we are trying to install).

Cause

So based on the information above, we can see that App-V 4.6 SP3 is trying to migrate the features of App-V 4.6 SP1 ({342C9BB8-65A0-46DE-AB7A-8031E151AF69}) and App-V 4.6 SP2 ({5D80483C-D297-4E04-9EDF-DD58521E9565}.

Since this is a migration, the installer for App-V 4.6 SP3 needs the cached installer files for the previous version. Generally these files are cached under C:\windows\installer or the ccm cache, however in this scenario these installer files seem to be missing:

If you tried to repair the App-V 4.6 SP2, you would probably get the error below. Here as well, the App-V 4.6 SP2 installer is trying to find the locally cached installer.

The Resolution

In a case like this, we simply need to remove the installed version of the client (App-V 4.6 SP2 or APP-V 4.6 SP1) before installing APP-V 4.6 SP3. The uninstall command line for these products are below:

Product

Version

Command line:

Microsoft Application Virtualization Desktop Client.

4.6.1.20870

Msiexec /x {342C9BB8-65A0-46DE-AB7A-8031E151AF69}

Microsoft Application Virtualization Desktop Client

4.6.2.24020

Msiexec /x {5D80483C-D297-4E04-9EDF-DD58521E9565}

NOTE: If uninstalling the old client fails for whatever reason, you can usually fix that with our utility here: