Advanced Installer 13.3 - fixes MSI launch condition issue in Windows 10 anniversary update 1607

Earlier when trying to install the Advanced Installer created virtual package through MSI format in windows 10 anniversary update 1607, it failed to install with the below error.




This issue is caused because of a launch condition in MSI which has been set to check for App-V client installed as a pre-requisite. Since App-V comes inbox with windows 10 v1607, the pre-req check fails with the above error.

This was a known issue even with App-V created packages and it was reported back to Microsoft.

Meantime I had a chance to talk with the Advanced Installer team about this issue. They quickly reported that they will look into this issue ASAP and come back with a fix. To my wonder they released an update within a short time period. You can have a look on their release note about this bug fix.

http://www.advancedinstaller.com/release-13.3.html

Now using Advanced Installer 13.3 when you create a virtual package and use the MSI to install in windows 10 1607, it installs fine without any issue. I tested with few apps sequenced by Advanced Installer 13.3 and found it to be 100% success.


So I looked into the MSI created after virtualizing and saw that it had the same launch condition but with a different approach. They have used the APPV_5X_CLIENT_INSTALLED property which has been set using AppSearch.




In this case they have used to locate the registry existence (HKLM\Software\Microsoft\AppV\Client).





Since windows 10 has inbuilt App-V, it  has a registry for AppV with version 5.2.0.0 by default.





Now when you install the new Advanced Installer 13.3 created virtual package MSI, the launch condition gets satisfied as there is a registry key with a valid  version and so it gets installed successfully.


For earlier versions, it still fails. For now you can fix it using the below solutions.


Solution - Virtual applications packaged into MSI format doesn’t install on inbox App-V client in Windows 10 Anniversary update 1607


UPDATED LINK -https://technet.microsoft.com/en-us/itpro/windows/manage/appv-release-notes-for-appv-for-windows

TweakAppv - Change PackageID, VersionID, Version to a predefined value

If you want to change the Package Version or VersionID, you can do it by exporting the AppxManifest.xml file from App-v 5.1 sequencer and do the changes. But after importing it back and saving the package, those values changes to some other random values. The version also gets incremented. So how to set them to a predefined value?


Advanced Installer has released a free tool called Tweakappv. It can be downloaded from the below link.It makes things so easy that you can also do a batch conversion for bulk packages.


http://www.advancedinstaller.com/appv-automation.html


Change Version:


Follow the below command to change the version value to a predefined value.





You can note that after publishing the version has been changed to the value 4.0.0.6 which we had set using Tweakappv.





Change VersionID:


Follow the below command to change the VersionID to a predefined value.





Change PackageID:


Follow the below command to change the PackageID to a predefined value.





NOTE - The value you provide for -attributename is case sensitive.

Solution: How to launch two App-V 5.x sequenced different versions of firefox side by side

Recently I came across an issue in TechNet which was quite interesting.

Issue:

I was able to publish two Mozilla Firefox (41.0, 49.0) to a client machine. I've added Desktop Icons with the respective version on it to differentiate one from the other.
If I open them individually, not keeping both opened, I can confirm the version of the browser checking the Help otpion, however if I open one browser say 41.0, keep it opened, then open the second browser version 49.0 , the first browser version 41.0 will take precedensce on the second instance too.This can be checked by opening up help and checking the version. The second window showed 41.0 version even though it was 49.0 version firefox shortcut.

https://social.technet.microsoft.com/Forums/en-US/c364b975-a2e4-425f-8d4c-88fdc7550599/having-two-mozilla-firefox-versions-from-appv-published-to-a-computer-if-i-open-both-versions-one?forum=mdopappv&prof=required

Solution:

Edit the dynamic config file and add the below -no-remote in the <Arguments> tag. -no-remote will tell the FireFox to use a new instance of it while opening, if we don't pass the argument then it will open a new window but it will be the same instance of previously opened FireFox.

<Shortcuts Enabled="true">
        <Extensions>
          <Extension Category="AppV.Shortcut">
            <Shortcut>
              <File>[{Programs}]\Mozilla Firefox.lnk</File>
              <Target>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</Target>
              <Icon>[{Windows}]\Installer\{xxxxxxxxx-0B398xxxxxxF}\Icon_firefox1.exe.0.ico</Icon>
              <Arguments> -no-remote  </Arguments>
              <WorkingDirectory>[{ProgramFilesX86}]\Mozilla Firefox\</WorkingDirectory>
              <ShowCommand>1</ShowCommand>
              <ApplicationId>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</ApplicationId>
            </Shortcut>
          </Extension>
        </Extensions>
      </Shortcuts>


Save the deploymentconfig/user config file and add it while publishing.

Reference - http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile

Solution - Virtual applications packaged into MSI format doesn’t install on inbox App-V client in Windows 10 Anniversary update 1607

We see that the solution provided in the link from Microsoft for the msi (sequenced with App-V 5.1 or earlier) failure in windows 10 v1607 doesn't seem to fix the issue.


https://technet.microsoft.com/en-us/itpro/windows/manage/appv-release-notes-for-appv-for-windows

We see the below Msidb.exe not found error running the command as said in the link.





When checked for Msidb.exe, it was found in c:\program files(x86)\windows kits\10\bin. Changed the -msidbpath to c:\program files(x86)\windows kits\10\bin and tested. It fails too. Changed it to c:\program files(x86)\windows kits\10\bin\msidb.exe. It fails too.




The update-AppvMsiPackage.ps1 from C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer seems to look for the location c:\program files(x86)\windows kits\10\bin\msidb.exe which is not located after installing the windows 10 sdk. The actual path where the msidb.exe is located after installing windows 10 sdk is c:\program files(x86)\windows kits\10\bin\x86\msidb.exe



 


The above highlighted code needs to be changed to $msidbExe = Join-Path -Path $msSdkPath -ChildPath "Bin\x86\MsiDb.exe"

Save the modified code and run the command. Now the solution works fine and the MSI gets updated.


App-V 5.1 sequencer and earlier doesn't work on windows 10 version 1607

When trying to install App-V 5.1 and earlier version of sequencer in windows 10 version 1607, it fails with the below error.




Solution: You would need to download the latest SDK for windows 10 version 1607 which has sequencer along with it. Using this sequencer you can proceed virtualizing apps.


https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit