Or maybe the software is older software created before a newer version of the operating system existed i.e. ST2 SEEC Administrator on Windows 2008 R2:
Blocked installs because of operating system version can be quite easily overcome by using Orca, a free Microsoft tool that allows you to quickly and easily modify and edit the .msi installer files.
Microsoft provides a KB article on using Orca but it specifically doesn’t specifically address how to override and remove operating system version restrictions.
First you must download and install Orca. Unfortunately Microsoft does not provide a direct download of Orca. In order to get Orca you must download and install the Microsoft Windows SDK which includes Orca.
Or to save yourself some time you can search the interweb for a standalone copy of Orca someone has already extracted from the Microsoft SDK for you.
However you end up getting Orca, once installed, you are then ready to begin modifying the software .msi installer file.
Back up the software .msi installer file:
Launch Orca:
Select File -> Open ->Browse to the software .msi installer file ->Open:
In the Tables column on the left-hand side locate the “LaunchCondition” table:
In the Condition column on the right-hand side select the condition that is blocking the software from installing. Typically this will be a condition containing the string “Version” in it somewhere:
You can then either double-click on the condition and manually edit the condition or right-click and select “Drop Row” to delete the condition all together. I typically drop the row to bypass *all* OS version checking:
File -> Save the modified .msi file and exit out of Orca:
You should now be able to launch the software .msi installer and successfully install the software to the previously blocked operating system:
As an added bonus, once you’ve downloaded Orca, it runs standalone so you can add it to your portable software toolbox. (As an administrator you do have a set of portable tools, don’t you? If not check out two of my fav portable application toolsets, PortableApps and LiberKey).
Just remember that when you install software onto unsupported platforms you cannot typically expect support or help from product support (GTAC?) with resolving problems with software on unsupported platforms ;-)
Thank you for posting this.
ReplyDeleteYou are welcome. Glad to be of help and thanks for the feedback and reading.
DeleteThis just helped me out a lot. I'm using BrekIT UacAA in the automated testing of my installers, but the 32-bit MSI refused to install on Vista. I fixed the LaunchCondition entry to say "VersionNT >= 600" and now I can install. Thank you!
ReplyDeleteMichael,
DeleteThanks for reading and your feedback. Glad to be of help.
-Dave
You're the man.
ReplyDeleteSaved me a lot of time and nerves.
Thanks :)
Thanks for reading and your feedback. Glad to have been of help!
DeleteThis is possibly one of the most useful tools and tutorial that i have ever seen for windows
ReplyDeleteThanks for reading and the positive feedback. Always appreciated!
DeleteWill this work to change installation behaviour on Windows system installations?
ReplyDeleteFor example, when using Windows system install disc from within Windows, the wizard starts and shows two options, "Upgrade Install" and "Clean Install", but Upgrade Install is greyed out. Can this technique change that behavior so that an Upgrade Install can be performed?
IsaLandr,
DeleteHonestly I have no idea. If the Windows system install file is an msi file that can be edited by Orca and you can find the condition that is blocking or greying out the Upgrade Install then I would say yes.
Regardless I would be leary of attempting to override a Windows OS install behaviour. One thing to hack on secondary software installs but the primary OS install...
Thanks for stopping by and reading.
Good post, I tried to install Solid Edge ST6 on windows XP, but is the same, any advice you could give me??
ReplyDeleteCharly,
DeleteYou can get ST6 to successfully install onto XP. However, just because you can successfully install does *not* mean the software will successfully run.
With ST6 there are Windows dll files required that simply do not exist on XP. I know because I have tried and was able to get ST6 installed but it would not run. I even went so far as to identify the needed Win7 .dll files and installing those manually onto XP as I came across issues. I made progress but the effort far outweighed the results.
Sorry to be the bearer of bad news! Thank you for reading and your feedback.
Big thanks for this tip. It worked great.
ReplyDelete