Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Using MsiInv to gather information about what is installed on a computer

Using MsiInv to gather information about what is installed on a computer

Rate This
  • Comments 72

As I was reading one of the posts on Quan To's new blog, I noticed that someone posted a link to a tool named msiinv.exe on their tools page.  This tool (which stands for MSI Inventory) wraps some of the publicly documented MSI APIs to provide information about the state of all Windows Installer products, features and components that Windows Installer thinks are installed on your computer.  I say "thinks are installed" because there are some rare cases where the actual installation state of a given product can get out of sync with the information Windows Installer has stored in its internal data structures, which can cause confusion for setup packages.

I use this tool nearly every day as one of the first troubleshooting tools for setup problems because it allows me to get a baseline snapshot of what the current state is for a machine before I start trying to make changes to fix any problems a customer might be having.

Example usage of msiinv.exe

One of the common uses of msiinv.exe is if someone is trying to install one of the recent beta builds of VS 2005 or .NET Framework 2.0 and the setup UI states that you are not allowed to install because a previous beta version of <insert product name here> is on the machine and you must uninstall that first.  Sometimes after receiving this error message, a user will look in Add/Remove Programs and the product that setup is complaining about is nowhere to be found, or there is an Add/Remove Programs entry for that product but trying to remove it claims that the product is not on the computer and asks if you would like to remove the entry from the Add/Remove Programs list.

In these cases, you can use the following steps:

  1. Download msiinv.zip from the following location:

  2. Extract the contents of msiinv.zip to the folder c:\msiinv on your system
  3. Click on the Start menu, choose Run, type cmd and click OK
  4. Type this command:  c:\msiinv\msiinv.exe -p > c:\msiinv\msiinv_output.txt

    Note: This command must be run from a cmd prompt or it will not create a log file as expected.

These steps will create a text file named c:\msiinv\msiinv_output.txt with a list of each product that Windows Installer thinks is installed on the system.  Then you can open the text file in any text editor and search the list of products for the name of the product that setup told you to uninstall.  The output will look something like this (I am using an example from a machine that has .NET Framework 2.0 beta 2 installed):

Microsoft .NET Framework 2.0 Beta 2
 Product code: {7A1ADD0C-17F3-47B8-B033-A06E189C835D}
 Product state: (5) Installed.
 Package code: {856D48D2-6F94-466D-9732-534DB5854FB3}
 Version: 2.0.50215
<note: there is more info after this but I am omitting it because it isn't useful to the rest of my example>

Now we have the Windows Installer product code and we can use that to uninstall the product by running msiexec /x <product code> (make sure that you include the curly braces in this command line).  If the product is actually installed on your system you will see a progress screen and uninstall will complete, and from there you should be able to re-run VS or .NET Framework setup and successfully install.

If Windows Installer thinks that the product is installed but it really isn't, then running msiexec /x <product code> will give you an error stating that this command is only valid for installed products.  If this happens, you will need to perform an extra step to remove the data that causes Windows Installer to think this product is installed.  You can download the Windows Installer Cleanup Utility and install and run it on your machine to fix this.  In the list of applications that this tool displays, choose the one that matches the product name displayed when you first ran VS or .NET Framework setup and choose to remove it.  After this removal completes, you should be able to re-run VS or .NET Framework setup and successfully install.

Advanced usage of msiinv.exe

The msiinv.exe tool has several command line parameters that you can see by running it with the /? switch.  A couple of the more interesting options are the following:

  • msiinv.exe -v - This option will list all feature GUIDs and component GUIDs for each Windows Installer product that is installed on the machine.  This can be useful to see which products share components (which can help track down why running uninstall for one product leaves behind some files and/or registry).  If you have a lot of products installed on the machine, running with the verbose switch will take a long time.
  • msiinv.exe -x - This option will list Windows Installer components that are installed on the machine that do not have any products that hold reference counts on them anymore.  In most cases, this is caused by one or more setup being installed on the machine at some point in the past that violated the MSI component rules. (more info about component rules can be found here and here if you are interested)

<update date="12/1/2008"> Updated the link to msiinv.zip because the old location was no longer available. </update>

<update date="2/12/2009"> Updated command line for running msiinv.exe so it will work on Windows Vista and Windows Server 2008. </update>

<update date="4/1/2009"> Removed broken link to msiinv.exe tool </update>

<update date="10/11/2012"> Embedded new SkyDrive link to msiinv.exe tool </update>


  • Hi Searcher54 - The error 1605 is a Windows Installer error code that means "This action is only valid for products that are currently installed."  Likely this means that one of the installed products on your system is in a bad/inconsistent state, and that is confusing msiinv and the WIndows Installer Cleanup Utility.  I'm not sure how to narrow down exactly what product is causing that error though.  It might help to use the -v (verbose) switch on msiinv.  If you want, you can run msiinv in verbose mode and zip and send me the log file so I can see if I can figure out anything about the root cause.  You can send the log file to Aaron.Stebner (at) microsoft (dot) com.

  • I previously wrote about a log collection tool that will automatically gather and cab up Visual Studio

  • I previously wrote about a log collection tool that will automatically gather and cab up Visual Studio

  • Visual Studio 2008 - Install Problem Solved

  • This week with the RTM of VS2008 I made the move from the Beta 2 version of VS2008 to the RTM version.

  • Since XNA Game Studio 2.0 shipped back in December, we've heard of a few installation issues from customers

  • Since XNA Game Studio 2.0 shipped back in December, we&#39;ve heard of a few installation issues from

  • Hi, do you know of an alternate source of msiinv.zip?  The website for it appears to be gone or down.

    Thank you!

  • Hi Dkwright - I've sent out mail to ask the owner of that site whether this is a temporary or permanent outage.  In the meantime, I've posted this file for download at the following alternate locations:



  • Thank you.  I really appreciate it!

  • I just tried running this on my laptop with Vista SP1 installed and I get "Unexpected Error: 1605 <>" repeated 3 times in the command prompt window and no output file. Any thoughts?

  • Hi Dasharp - I've seen these 1605 errors in the past on some systems.  They usually mean that there is some incorrect Windows Installer data somewhere in your registry.  However, I also looked at the code for this MsiInv tool and it should continue even after hitting errors like that and continue to list installed MSI-based products.  Are you sure it didn't list anything in the log file?  Are you looking in the right location on your file system for the log file to be produced?

  • I forgot to put the folder in output redirect. I found the file.


  • Hi,

    msiinv -x gives me many orphaned Components whose ProductCode is {00000000-0000-0000-0000-000000000000}.

    Those components seems to come from various appli:

    Component {89476830-4393-4DB3-8330-773401C4EE50} has no parent product (permanent)

    Product Code: {00000000-0000-0000-0000-000000000000}

    Permanent Product placeholder.

    Component path: C:\Program Files\MEGA\MEGA 2009\Demonstration\

    File or directory not found.


    Component {A44402F0-AE37-45ED-9498-1094455D934B} has no parent product (permanent)

    Product Code: {00000000-0000-0000-0000-000000000000}

    Permanent Product placeholder.

    Component path: C:\Program Files\palmOne\PhotoDesktop\ui\DGUI\img_Dialogs_vw.ui

    File or directory not found.


    How can I remove those orphaned Components?

    I haven't dare to use MsiZapA.exe TW{00000000-0000-0000-000000000000}

    I fear it removes too many things.

    Any suggestions?

    Thanks in advance

  • Hi Boivin - Those orphaned components are from products that you had installed that had components that were marked as permanent (meaning they would not be removed during an uninstall).  My systems all have some components like that.  You should just leave them as is - if the product marked the components as permanent, they intended for them to be left behind on the system even after uninstalling the product.

Page 4 of 5 (72 items) 12345
Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post