App-V: Troubleshooting WinSxS errors encountered when doing a package upgrade

When sequencing an application, libraries/assemblies that’re normally registered and stored in the \windows\winsxs folder’re instead copied into the package, and’re in the same folder as the executable that uses them . For some applications, when doing a package upgrade, this can cause your setup program to fail because it’s trying to update those assemblies at […]
When sequencing an application, libraries/assemblies that’re normally registered and stored in the \windows\winsxs folder’re instead copied into the package, and’re in the same folder as the executable that uses them . For some applications, when doing a package upgrade, this can cause your setup program to fail because it’s trying to update those assemblies at \windows\winsxs but they don’t exist at that location in the package. If you receive an error message while doing a package upgrade related to Side by Side (WinSxS) you can first try removing HKLM\Components from the virtual registry and then performing the package upgrade. This has the effect of telling the TrustedInstaller service that the component does not exist in \windows\winsxs and it should attempt to reinstall it.  Most of the time that’ll allow the package upgrade to now succeed.