Configuring Network License Manager [lmtools.exe] for more than one product
Fatal error: Unhandled access violation writing 0x006c exception at f3256d5ah

Installation Framework: Using Orca to get a GUID (Product Code)

OrcaFor advanced users that deploy our software in the USA, this is going to be a Thanksgiving treat for you. We have had occasional requests to assist in uninstalling our software via a command line.  This is unsupported because there are a lot of variables in your corporate network and complexity with various other software installed via pre-requisites etc.

This tip is really about getting the GUID (Product Code) for our products.

1.  Download Orca.  Use this tool with EXTREME caution!  If you edit, modify or save a change in a .msi or .mst file with this tool, you render your software (via Setup.exe) inoperable.

Danger, Will Robertson!


2.  Search for the .msi files in our installer.  In our example, we are trying to find the GUID (Product Codes) for Product Design Suite Premium 2013.



3. Use Orca and open the .msi file.

  • Under Tables > Go to Property
  • In the second column, under click on Property, so that the items will be in alphbetical order.
  • Go to  Product Code and select/copy the Value.

A video demo is here:  Orca-productcode-guid.mp4

Now, you can check out this post to see what we did with the GUID (Product Code):

Thanks to Hashim Mundol for sharing this workflow with the community. Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime.

NOTE:  Product Support does not support Orca. It is a developer tool so please do NOT log a case for product support to troubleshoot this tool/workflow. The only 'supported' method that we will 'officially' endorse is to use a user interface via the Control Panel, Microsoft Fix it, or the 2014 Uninstall Tool.


Feed You can follow this conversation by subscribing to the comment feed for this post.

Constantin Gherasim

Hi David,

If you don't mind, I would add some more information on this subject.

Another method for getting the GUID is to search the Windows registry for the product you want to uninstall.

For 32-bit applications running on a 64-bit version of Windows:

For 64-bit applications running on a 64-bit version of Windows:

For instance, if I am going to search for some 2014 product, the search sequence will pause on each key of a product which contains 2014 in the name.

Obviously, it's very possible that there are more installed products than the one you are looking for, but using the F3 key (Windows standard for next instance when searching for something) you will be able to navigate very fast to the right product.

On the left pane of the registry editor the product GUID is highlighted, and then if you look in the right pane of the registry editor, you will see some info concerning that product.

Among others, you will see the "Display Name" which will confirm that you are looking at the right product and there's also the "Uninstall String", which can be used to uninstall the product.

Sometimes the original Autodesk product Setup.exe is used for uninstalling the product, but most of the time the MSIEXEC utility is used (the MSIEXEC approach can be substituted to the Setup approach).

For instance, if we take AutoCAD 2014, the uninstall string from the registry is:
C:\Program Files\Autodesk\AutoCAD 2014\Setup\en-us\Setup\Setup.exe /P {5783F2D7-D001-0000-0102-0060B0CE6BBA} /M ACAD /language en-US

But it could be replaced with the MsiExec approach:
MsiExec.exe /X{5783F2D7-D001-0000-0102-0060B0CE6BBA} /q

Int the same vein, if we take Revit (One box) 2014, the uninstall string from the registry is:
C:\Program Files\Autodesk\Revit 2014\Setup\en-US\Setup\Setup.exe /P {7346B4A0-1400-0510-0000-705C0D862004} /M RVT2014 /LANG en-US

But again, it could be replaced with the MsiExec approach:
MsiExec.exe /X{7346B4A0-1400-0510-0000-705C0D862004} /q

If you want to know more about the MsiExec switches, here is an useful link:

For a similar topic you can read the following post:

And last but not least, I would like to mention another MSI editor called InstEdit, which in my opinion is a better product than Orca:

I hope this some other people will find this usefull.


Constantin Gherasim

David Lau

Thanks a lot for this long comment and sharing your knowledge with the community.

The comments to this entry are closed.