Uninstall with Product Code Feature you are trying to use is on a network resource that is unavailable Post by gsaunders » Fri Apr 07, pm We installed product from the installaware setup exe file. BUT I would have sworn we ahve done this with other applications and they have uninstalled properly.
Thanks in advance for your feedback. I haven't messed with installers for a while so fresh back into it and just getting back up to speed. A copy of the setup package gets Always stored under the pre-defined setup cache directory of the target system. When it's told to, yes. You seem to be assreting that it does so on a whim which, again, is something I've never experienced as a long-term WPS user.
Oh no. I think we have a misunderstanding here. I don't want to say that WPS is generating on-the-fly a new productcode. Never mind. But I'm curious what application is doing such weird things.
I cant find the application that did this to confirm, however something in the back of my mind "labview version 6" springs to mind as the culprit. Completely agree, extracting the MSI when repackaging the installer would likely prevent this issue. Mistakes happen, just got to find a way to deal with it. I work for a university, sadly we get a lot of really random applications to package.
Sometimes made by fred bloggs in his shed in the back garden and they love do completely random illogical things especially when they try to make up their own little "security" measures to counter piracy. On one package this month i've even been asked to provide details back to the developer so that they could HARD CODE keys and file paths into their app! Posted by: pjgeutjens 10 years ago. As an educational institute we often get software free or at a significant discount.
Therefore the baseball bat is not always the best option : A friendly suggestion that it is not "enterprise friendly" if often the most we can do.
Finally I believe PowerShell can be disabled or locked by various system policies and privileges. If this is the case, you can try a few other ways to retrieve product codes. My preferred alternative is VBScript - it is fast and flexible but can also be locked on certain machines, and scripting is always a little more involved than using tools.
I can't think of any further general purpose options to retrieve product codes at the moment, please add if you know of any. Just edit inline rather than adding too many comments please. Or even use WMI queries from within your application like you do in the samples above using PowerShell , wbemtest. If what you want to do is to uninstall the MSI package you found the product code for, you can do this as follows using an elevated command prompt search for cmd.
Option 1 : Basic, interactive uninstall without logging quick and easy :. You can also enable verbose logging and run in silent mode if you want to, leading us to option Option 2 : Silent uninstall with verbose logging better for batch files :.
There is a plethora of different ways to uninstall. If you are writing a batch file, please have a look at section 3 in the above, linked answer for a few common and standard uninstall command line variants. And a quick link to msiexec. And the Technet version as well. For installed packages this is much more reliable.
If the package is not installed, you still need to look in the MSI file or the source file used to compile the MSI to find the upgrade code. Leaving in older section below:. Then you look in the " Property table " for UpgradeCode it is possible for the UpgradeCode to be redefined in a transform - to be sure you get the right value you need to retrieve the code programatically from the system - I will provide a script for this shortly.
To open the cached MSI files, use Orca or another packaging tool. Here is a discussion of different tools any of them will do : What installation product to use? If you don't have such a tool installed, your fastest bet might be to try Super Orca it is simple to use, but not extensively tested by me.
Then find Orca in the start menu. Go time in no time If you don't have Visual Studio installed , perhaps you know someone who does? Just have them search for this MSI and send you it is a tiny half mb file - should take them seconds. If not, you can always download the Windows SDK it is free, but it is big - and everything you install will slow down your PC. If you do, please just edit and add details here. If you have too many installers to find what you are looking for easily, here is some powershell to provide a filter and narrow it down a little by display name.
I don't have enough Rep points to reply to Stein Asmul directly, maybe someone can message him, but here is a powershell one-liner I adapted from the VBScript solution which I found to be more reliable than the existing powershell one-liner, particularly when running as a non-admin, and it's much faster. Pro-tip: Change the 7 to a 3 to find programs lurking as per-user installs rather than machine wide.
There is also a very helpful GUI tool called Product Browser which appears to be made by Microsoft or at least an employee of Microsoft. It can be found on Github here Product Browser. You may take a look at MSI Finder. It lets you search for products or components by name, GUID or location, view their properties, as well as repair or uninstall individual products.
Disclaimer: I was looking for a similar solution, but couldn't find anything reliable or easy to use. So, I developed this tool. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Press F3 key and search for your product name. However, the GUID could conceivably rarely be overridden by a transform applied at install time and hence not match the GUID the product is registered under approach 1 and 2 above will report the real product code - that is registered with Windows - in such rare scenarios. You need a tool to view MSI files. See towards the bottom of the following answer for a list of free tools you can download or see quick option below : How can I compare the content of two or more MSI files?
For convenience and need for speed, you can download SuperOrca without delay and fuss from this direct-download hotlink - the tool is good enough to get the job done - install, open MSI and go straight to the Property table and find the ProductCode row please always virus check a direct-download hotlink - obviously - you can use virustotal.
Fire up Powershell hold down the Windows key, tap R , release the Windows key, type in " powershell " and press OK and run the command below to get a list of installed MSI package product codes along with the local cache package path and the product name maximize the PowerShell window to avoid truncated names.
Before running this command line, please read the disclaimer below nothing dangerous, just some potential nuisances. If you are trying to uninstall a package there is a section below with some sample msiexec.
So in other words, in the picture above the IdentifyingNumber is the ProductCode. Besides being quite slow, this can in rare cases trigger an MSI self-repair.
This can be a small package or something huge - like Visual Studio.
0コメント