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.

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.

No comments:

Post a Comment