It's indeed very strange. Maybe it's Wise Package studio!? That application is also generating new productcode's. 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! A growing number of software companies also recognize the need to provide silencing information about their installation packages. A second alternative is to find a software repackaging solution that handles much of this work for you.
These solutions incorporate a range of tactics to gather the necessary silencing and customization information with the goal of presenting it in meaningful ways. MSI packaging solutions can be found by many third-party companies with a range of price points and feature sets. One final element of MSI installations merits discussion. This element consolidates a series of property changes and other MSI reconfigurations into a single file. An MST, or transforms file, is commonly used when an MSI's configuration database requires large scale changes to prepare itself for installation.
Rather than requiring you to enter a long list of alterations at the command line, a transforms file consolidates changes into a single file that is invoked at the command line. Creating your own transforms typically requires the use of a software.
At the end of the day, getting a software installation packaged for silent installation is only the first step. It can also be arguably the most difficult step. One packaged, you'll need a software deployment solution to execute the command you've created on entire groups of computers at once. Or, since this is a command line, you can keep walking the halls. Except this time you're not clicking Next, Next, Finish; you're typing long command strings into each computer's Run prompt.
To perform the uninstall, which AFAIK should be silent it has been in my experience, but try it before you bet the farm on that. Installation and Uninstallation of MSU in silent mode.
File silently without reboot with the following command line. Below command to uninstall the MSU from. That syntax looks generally like this: msiexec.
So, for example, if you wanted to install the Adobe Flash Player to your desktop and had the correct MSI available, you might do so with the following syntax: msiexec. Sleuthing for Custom Properties As I mentioned earlier, each MSI has its own custom name and value pairs that answer questions the installation requires.
Msi Silent Uninstall Command Line Free Just about any property you see in this table can be adjusted at the command line as you execute msiexec to kick off an installation.
NET Framework 4. Once downloaded, install the SDK's debugging tools. Double-click this file to install it to your management desktop. Once within Orca, you can open an MSI and peer around to locate its custom settings. Remember that MSIs are above all big databases of content and configurations that apply files to disk drives and keys and values to registries.
Orca exposes these databases for what they really are. Inside every MSI is a table called Property. That table identifies all the properties that are tagged to an installation. The name and value pairs discussed above are in fact properties along with their values as seen in Orca. Its value defaults to Yes. For this one, change its value to No. Just about any property you see in this table can be adjusted at the command line as you execute msiexec to kick off an installation.
While this method is the comprehensive approach, it is also the time-consuming approach. Another alternative is to simply search the Internet for clues that others have found. A popular website that contains installation hints for many common software packages is www. A growing number of software companies also recognize the need to provide silencing information about their installation packages.
A second alternative is to find a software repackaging solution that handles much of this work for you. These solutions incorporate a range of tactics to gather the necessary silencing and customization information with the goal of presenting it in meaningful ways. MSI packaging solutions can be found by many third-party companies with a range of price points and feature sets. One final element of MSI installations merits discussion.
This element consolidates a series of property changes and other MSI reconfigurations into a single file.
An MST, or transforms file, is commonly used when an MSI's configuration database requires large scale changes to prepare itself for installation.
Rather than requiring you to enter a long list of alterations at the command line, a transforms file consolidates changes into a single file that is invoked at the command line. Creating your own transforms typically requires the use of a software. At the end of the day, getting a software installation packaged for silent installation is only the first step. It can also be arguably the most difficult step. One packaged, you'll need a software deployment solution to execute the command you've created on entire groups of computers at once.
You need a regular security tool for interactive, online heuristic protection. For what it is worth, I think some security software border on causing more false-positive problems than malware does damage. Famous last words in the era of ransom-ware That is a large enough digression - I just don't want to see people download malware. Do your virustotal. Uninstalling like this should work OK. I think these tools mess with too many things when you try their "cleanup features" though.
Use with caution. If you only use the uninstall feature, you should be OK. It should not be used on any newer Windows versions This command line tool msizap. Both tools are deprectated. The intended use of these tools was to clean out failing uninstalls : Generally for the rare case when the cached MSI with the random name is erroneously missing and uninstall fails for this reason whilst asking for the original MSI.
This is a rare problem, but I have seen it myself. Just a few potential causes: Moved to this answer. Key words: system restore interference, bad cleanup apps, msiexec. It could also be used to zap any MSI installation, though that is obviously not advisable. More information: Why does MSI require the original. This newer support tool this tool is now also deprecated can be tried on recent Windows versions if you have defunct MSI packages needing uninstall. Some have suggested to use the tool linked to here by saschabeaumont: Uninstall without an MSI file.
If you try it and it works, please be sure to let us know. If you have access to the original MSI that was actually used to install the product, you can use this to run the uninstall. It must be the exact MSI that was used, and not just a similar one.
Restoring via a restore point brings the system back to a previous installation state you can find video demos of this on YouTube or a similar site. Note that the feature can be disabled entirely or partly - it is possible to disable permanently for the whole machine, or adhoc per install.
I have seen new, unsolvable installation problems resulting from a system restore, but normally it works OK. Obviously don't use the feature for fun. It's a last resort and is best used for rollback of new drivers or setups that have just been installed and are found to cause immediate problems bluescreen , reboots, instability, etc The longer you go back the more rework you will create for yourself, and the higher the risk will be. Most systems feature only a few restore points, and most of them stretch back just a month or two I believe.
Be aware that system restore might affect Windows Updates that must then be re-applied - as well as many other system settings. Beyond pure annoyances, this can also cause security issues to resurface and you might want to run a specific security check on the target box es using Microsoft Baseline Security Analyzer or similar tools. This feature has nothing to do with uninstall or system restore, but it is the last boot configuration that worked or resulted in a running system.
It can be used to get your system running again if it bluescreens or halts during booting. This often happens after driver installs. Copy and paste the above code into your main CPP file replacing whatever is there. That should be it to be able to run the code.
Maybe set a breakpoint, build and run. Beware of changes to the default templates in VS, and the weird errors that can result: There are too many errors for the IntelliSense engine to function correctly.
I no longer see the above issue. The MSDN link in the code lists the possible error messages returned from msiexec. Improve this answer. In case you want a simpler way to deal with the complicated msiexec. Can you update your answer with a new link?
There are certainly further possible causes. Show 4 more comments.
0コメント