Alois Kraus


  Home  |   Contact  |   Syndication    |   Login
  133 Posts | 8 Stories | 366 Comments | 162 Trackbacks



Post Categories


Hopefully nothing. But if you have to do more than simple XCopy deployment and you need to support updates, upgrades and perhaps side by side scenarios there is no way around MSI. You can create Msi files with a Visual Studio Setup project which is severely limited or you can use the Windows Installer Toolset. I cannot talk about WIX with my German colleagues because WIX has a very special meaning. It is funny to always use the long name when I talk about deployment possibilities. Alternatively you can buy commercial tools which help you to author Msi files but I am not sure how good they are. Given enough pain with existing solutions you can also learn the MSI Apis and create your own packaging solution. If I were you I would use either a commercial visual tool when you do easy deployments or use the free Windows Installer Toolset. Once you know the WIX schema you can create well formed wix xml files easily with any editor. Then you can “compile” from the wxs files your Msi package.

Recently I had the “pleasure” to get my hands dirty with C++ (again) and the MSI technology. Installation is a complex topic but after several month of digging into arcane MSI issues I can safely say that there should exist an easier way to install and update files as today. I am not alone with this statement as John Robbins (creator of the cool tool Paraffin) states: “.. It's a brittle and scary API in Windows …”. To help other people struggling with installation issues I present you the advice I (and others) found useful and what will happen if you ignore this advice.

What is a MSI file?

A MSI file is basically a database with tables which reference each other to control how your un/installation should work. The basic idea is that you declare via these tables what you want to install and MSI controls the how to get your stuff onto or off your machine.

Your “stuff” consists usually of files, registry keys, shortcuts and environment variables. Therefore the most important tables are File, Registry, Environment and Shortcut table which define what will be un/installed. The key to master MSI is that every resource (file, registry key ,…) is associated with a MSI component.

The actual payload consists of compressed files in the CAB format which can either be embedded into the MSI file or reside beside the MSI file or in a subdirectory below it. To examine MSI files you need Orca a free MSI editor provided by MS. There is also another free editor called Super Orca which does support diffs between MSI and it does not lock the MSI files. But since Orca comes with a shell extension I tend to use only Orca because it is so easy to right click on a MSI file and open it with this tool.

How Do I Install It?

Double click it. This does work for fresh installations as well as major upgrades. Updates need to be installed via the command line via

msiexec /i <msi> REINSTALL=ALL REINSTALLMODE=vomus


This tells the installer to reinstall all already installed features (new features will NOT be installed). The reinstallmode letters do force an overwrite of the old cached package in the %WINDIR%\Installer folder. All files, shortcuts and registry keys are redeployed if they are missing or need to be replaced with a newer version. When things did go really wrong and you want to overwrite everything unconditionally use REINSTALLMODE=vamus.

How To Enable MSI Logs?

You can download a MSI from Microsoft which installs some registry keys to enable full MSI logging. The log files can be found in your %TEMP% folder and are called MSIxxxx.log. Alternatively you can add to your msiexec command line the option

msiexec …. /l*vx <LogFileName>

Personally I find it rather strange that * does not mean full logging. To really get all logs I need to add v and x which is documented in the msiexec help but I still find this behavior unintuitive.

What are MSI components?

The whole MSI logic is bound to the concept of MSI components. Nearly every msi table has a Component column which binds an installable resource to a component. Below are the screenshots of the FeatureComponents and Component table of an example MSI.




The Feature table defines basically the feature hierarchy.  To find out what belongs to a feature you need to look at the FeatureComponents table where for each feature the components are listed which will be installed when a feature is installed. The MSI components are defined in the  Component table. This table has as first column the component name and as second column the component id which is a GUID. All resources you want to install belong to a MSI component. Therefore nearly all MSI tables have a Component_ column which contains the component name.

If you look e.g. a the File table you see that every file belongs to a component which is true for all other tables which install resources.


The component table is the glue between all other tables which contain the resources you want to install. So far so easy. Why is MSI then so complex? Most MSI problems arise from the fact that you did violate a MSI component rule in one or the other way.

When you install a feature the reference count for all components belonging to this feature will increase by one. If your component is installed by more than one feature it will get a higher refcount. When you uninstall a feature its refcount will drop by one.

Interesting things happen if the component reference count reaches zero: Then all associated resources will be deleted. That looks like a reasonable thing and it is. What it makes complex are the strange component rules you have to follow. Below are some important component rules from the Tao of the Windows Installer

Rule 16: Follow Component Rules

Components are a very important part of the Installer technology. They are the means whereby the Installer manages the resources that make up your application. The SDK provides the following guidelines for creating components in your package:

  • Never create two components that install a resource under the same name and target location. If a resource must be duplicated in multiple components, change its name or target location in each component. This rule should be applied across applications, products, product versions, and companies.
  • Two components must not have the same key path file. This is a consequence of the previous rule. The key path value points to a particular file or folder belonging to the component that the installer uses to detect the component. If two components had the same key path file, the installer would be unable to distinguish which component is installed. Two components however may share a key path folder.
  • Do not create a version of a component that is incompatible with all previous versions of the component. This rule should be applied across applications, products, product versions, and companies.
  • Do not create components containing resources that will need to be installed into more than one directory on the user’s system. The installer installs all of the resources in a component into the same directory. It is not possible to install some resources into subdirectories.
  • Do not include more than one COM server per component. If a component contains a COM server, this must be the key path for the component.
  • Do not specify more than one file per component as a target for the Start menu or a Desktop shortcut.

And these rules do not even talk about component ids, update packages and upgrades which you need to understand as well. Lets suppose you install two MSIs (MSI1 and MSI2) which have the same ComponentId but different component names. Both do install the same file. What will happen when you uninstall MSI2?



Hm the file should stay there. But the component names are different. Yes and yes. But MSI uses not use the component name as key for the refcount. Instead the ComponentId column of the Component table which contains a GUID is used as identifier under which the refcount is stored. The components Comp1 and Comp2 are identical from the MSI perspective. After the installation of both MSIs the Component with the Id {100000….} has a refcount of two. After uninstallation of one MSI there is still a refcount of one which drops to zero just as expected when we uninstall the last msi. Then the file which was the same for both MSIs is deleted.

You should remember that MSI keeps a refcount across MSIs for components with the same component id.

MSI does manage components not the resources you did install. The resources associated with a component are then and only then deleted when the refcount of the component reaches zero.


The dependencies between features, components and resources can be described as relations. m,k are numbers >= 1, n can be 0. Inside a MSI the following relations are valid


   1  –> n Components


   1 –> m Features


   1  –>  k Resources

These relations express that one feature can install several components and features can share components between them. Every (meaningful) component will install at least one resource which means that its name (primary key to stay in database speak) does occur in some other table in the Component column as value which installs some resource.

Lets make it clear with an example. We want to install with the feature MainFeature some files a registry key and a shortcut. We can then create components Comp1..3 which are referenced by the resources defined in the corresponding tables.


Feature Component Registry File Shortcuts
MainFeature Comp1 RegistryKey1    
MainFeature Comp2   File.txt  
MainFeature Comp3   File2.txt Shortcut to File2.txt


It is illegal that the same resource is part of more than one component since this would break the refcount mechanism. Lets illustrate this:





Reference Count









The installation part works well but what happens when you uninstall Feature2? Component {20000…} gets a refcount of zero where MSI deletes all resources belonging to this component.

In this case File1.txt will be deleted. But Feature1 still has another component {10000…} with a refcount of one which means that the file was deleted too early. You just have ruined your installation. To fix it you then need to click on the Repair button under Add/Remove Programs to let MSI reinstall any missing registry keys, files or shortcuts.

The vigilant reader might has noticed that there is more in the Component table. Beside its name and GUID it has also an installation directory, attributes and a KeyPath. The KeyPath is a reference to a file or registry key which is used to detect if the component is already installed. This becomes important when you repair or uninstall a component. To find out if the component is already installed MSI checks if the registry key or file referenced by the KeyPath property does exist. When it does not exist it assumes that it was either already uninstalled (can lead to problems during uninstall) or that it is already installed and all is fine.

Why is this detail so important? Lets put all files into one component. The KeyPath should be then one of the files of your component to check if it was installed or not. When your installation becomes corrupt

because a file was deleted you cannot repair it with the Repair button under Add/Remove Programs because MSI checks the component integrity via the Resource referenced by its KeyPath. As long as you did not delete the KeyPath file MSI thinks all resources with your component are installed and never executes any repair action.

You get even more trouble when you try to remove files during an upgrade (you cannot remove files during an update) from your super component which contains all files. The only way out and therefore

best practice is to assign for every resource you want to install an extra component. This ensures painless updatability and repairs and you have much less effort to remove specific files during an upgrade.

In effect you get this best practice relation


1  –> n Components


1  –>  1 Resources

MSI Component Rules

Rule 1 – One component per resource

Every resource you want to install (file, registry key, value, environment value, shortcut, directory, …) must get its own component which does never change between versions as long as the install location is the same.


If you add more than one resources to a component you will break the repair capability of MSI because the KeyPath is used to check if the component needs repair.

MSI ComponentId Files
MSI 1.0 {1000} File1-5
MSI 2.0 {2000} File2-5

You want to remove File1 in version 2.0 of your MSI. Since you want to keep the other files you create a new component and add them there. MSI will delete all files if the component refcount of {1000} drops to zero. The files you want to keep are added to the new component {2000}. Ok that does work if your upgrade does uninstall the old MSI first. This will cause the refcount of all previously installed components to reach zero which means that all files present in version 1.0 are deleted.

But there is a faster way to perform your upgrade by first installing your new MSI and then remove the old one.  If you choose this upgrade path then you will loose File1-5 after your upgrade and not only File1 as intended by your new component design.


Rule 2 – Only add, never remove resources from a component

If you did follow rule 1 you will not need Rule 2. You can add in a patch more resources to one component. That is ok. But you can never remove anything from it. There are tricky ways around that but I do not want to encourage bad component design.


Lets assume you have 2 MSI files which install under the same component one file




{1000} - ComponentId

{1000} – ComponentId




When you install and uninstall both MSIs you will end up with an installation where either File1 or File2 will be left. Why? It seems that MSI does not store the resources associated with each component in its internal database. Instead Windows will simply query the MSI that is currently uninstalled for all resources belonging to this component. Since it will find only one file and not two it will only uninstall one file. That is the main reason why you never can remove resources from a component!


Rule 3 Never Remove A Component From an Update MSI.

This is the same as if you change the GUID of a component by accident for your new update package. The resulting update package will not contain all components from the previously installed package.


When you remove a component from a feature MSI will set the feature state during update to Advertised and log a warning message into its log file when you did enable MSI logging.

SELMGR: ComponentId '{2DCEA1BA-3E27-E222-484C-D0D66AEA4F62}' is registered to feature 'xxxxxxx, but is not present in the Component table.  Removal of components from a feature is not supported!

MSI (c) (24:44) [07:53:13:436]: SELMGR: Removal of a component from a feature is not supported

Advertised means that MSI treats all components of this feature as not installed. As a consequence during uninstall nothing will be removed since it is not installed! This is not only bad because uninstall does no longer work but this feature will also not get the required patches. All other features which have followed component versioning rules for update packages will be updated but the one faulty feature will not. This results in very hard to find bugs why an update was only partially successful.

Things got better with Windows Installer 4.5 but you cannot rely on that nobody will use an older installer. It is a good idea to add to your update msiexec call MSIENFORCEUPGRADECOMPONENTRULES=1 which will abort the installation if you did violate this rule.

posted on Friday, June 17, 2011 11:07 AM


# re: What Every Developer Should Know About MSI Components 7/25/2011 3:54 PM mano
Excellent article

# re: What Every Developer Should Know About MSI Components 11/3/2011 6:01 AM sreeginsen
Nice should Include more details

# re: What Every Developer Should Know About MSI Components 11/23/2011 6:07 PM Kavs

Not sure if I am implying to Rule 2.
I have 2 MSIs, msi 1 and msi2 both having versions 1.0.
Now, I need to upgrade both these msi's to versions 2.0.


msi1 v1.0 installs file1.txt at a location.
msi2 v1.0 also installs file1.txt at the same location. (This was done as a mistake).

Later, we have removed the instance of file1.txt from the wxs file of the msi2.

And so, msi2 v2.0, does not have the file1.txt.

But when a user tries to upgrade from v1.0 to v2.0,

file1.txt is missing from the respective location.

Install sequence is msi1 and then msi2

Can you suggest a solution to this problem? Any fix needs to be done in the v2.0 msi only.


# re: What Every Developer Should Know About MSI Components 11/25/2011 9:15 AM Alois Kraus
If both msis have for the same file the same component id it should work. If not you will uninstall the file in every msi and it will depend on the install sequence if after an install file1.txt is there again. A guess would be that it should work if you first upgrade msi2 and then msi1. But to be sure I would need to see the component ids of all msis for this file.

# re: What Every Developer Should Know About MSI Components 6/14/2012 2:32 AM Calum James
Hi Alois,

I just wanted to thank you for this great, well-written, informative article. It provided me with a lot of vital information when I was creating MSI packages for my work.

Thanks again!


# re: What Every Developer Should Know About MSI Components 5/14/2017 8:56 AM Jeremy
The information in this article is gold! Grreat job!!

# Online Tech support Service Provider 8/16/2017 10:42 AM Stephen
very Good and Informative artical sir..

# re: What Every Developer Should Know About MSI Components 9/4/2017 12:07 PM Ron
Ok, great, but what if this happens:

I found that when my nifty installer was run on a windows 10 32 bit machine here, upon launching the installed program, the msi would always go into autoheal mode. That is the "Please wait while Windows configures <such n' such a program>". I found out why, and fixed it by deleting KeyPath entries with orca and applying the fixit transform to the msi. - Good.

So I thought, well I better do the same to my 64 bit version of the nifty program. But first it would be good to make sure it fails in the same way first so I know when I fix it that I really did.

So I took a virgin 64bit installer (no transform applied) and installed it on a windows 10 x64 box. To my surprise, when I launched the program it did not autoheal as the 32 bit one did. So I went and deleted one of the deployed files to see if it would then fix itself. And no, it does not!

I tried the same on my wife's w10 x64 laptop and no auto-heal there either no matter how much I abuse the installed group of files!

So vs2008 x64 setup projects won't autoheal? - Right.

# re: What Every Developer Should Know About MSI Components 9/5/2017 5:17 PM Alois Kraus
@Ron: This is hard to tell what exactly went wrong. I am sure there are other ways to break some arcane MSI rule. Advertised usually means that somehow the components got messed up by an update or an x64/x86 installer fight which share the same component locations.

Post A Comment