Microsoft’s recent Security Updates for Visual Studio break Windows Installer Updates


Taken from Stefan Kruger’s Blog- This problem was brought up in a question on the InstallSite Forum and is also mentioned in a blog post by Gauravb (who appears to be a Microsoft employee).

The typical symptom is missing or not updated files after you install a Small or Minor Update to your application (Major Upgrades are not affected). In the installer log file you’ll notice that some features have been switched to “advertised” state and instead of being installed locally. The actual cause is noted in the SELMGR error message in the log similar to this:

SELMGR: ComponentId ‘{-GUID-}’ is registered to feature ‘-Feature-Name-‘, but is not present in the Component table. Removal of components from a feature is not supported!

This happens if your setup includes a merge module like Microsoft_VC80_CRT_x86.msm and you rebuilt your setup package after installingsecurity updates 971090 and 973673 for Visual Studio 2005 SP1 or 971092 and 973675 for Visual Studio 2008 SP1. These security updates install newer versions of merge modules.

Apparently a component that existed in the original version of the merge module has been removed in the updated msm. Removing a component is a violation of Windows Installer’s rules for Small and Minor Updates.

To read more on the MergeModules which are affected and the WorkArounds – check this link – http://msmvps.com/blogs/installsite/archive/2009/09/12/microsoft-s-recent-security-updates-for-visual-studio-break-windows-installer-updates.aspx