Welcome to TechNet Blogs Sign in | Join | Help

News

  • Dislaimer: All postings are provided "AS IS" with no warranties, and confer no rights. This weblog does not represent the thoughts, intentions, plans or strategies of Microsoft. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.

    Locations of visitors to this page

    Computers Blogs - Blog Top Sites
A tip for troubleshooting WinSxS errors encountered when doing a package upgrade

fixWhen sequencing an application, libraries/assemblies that are normally registered and stored in the \windows\winsxs folder are instead copied into the package, and are 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 do not 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 will allow the package upgrade to now succeed.

Jason Hu | Microsoft App-V Software Development Engineer

Posted: Thursday, August 20, 2009 3:07 PM by jchornbe

Comments

bradler said:

If you Virtualise IE7, is your system still exploitable by IE7 vulnerabilities? Is it necessary to patch or re-sequence an app such as IE7 with it's new updates?

# August 21, 2009 5:37 AM
Anonymous comments are disabled
Page view tracker