I'm just curious As explained below you can actually use the Windows Installer Automation api via a VBScript, but it might be calling msiexec.
I would say this question falls within the scope of "a practical, answerable problem that is unique to software development" and should therefore be re-opened. Fully programming related to me. I actually have software who's installers I need to test and also test the uninstallers.
It's worth checking if there is an uninstaller for the application in the program files - even though you installed using an msi it may have extracted an unistaller executable — wunth. Add a comment. Active Oldest Votes. There is also: MSI logging in depth here : msiexec. The below is intended as a "reference": In summary you can uninstall via: msiexec. You can also uninstall via command line as explained in section 3. Select entry and uninstall. Please add comments below if seen.
Try this answer as well General hint : try disabling anti-virus and try again. Several other ways described here registry, local cache folder, etc NB : This supper-hidden folder is now being treated differently in Windows 7 onwards. MSI files are now cached full-size.
Read the linked thread for more details - recommended read for anyone who finds this answer and fiddles with dangerous Windows settings. Avoid these huge cached files by using admin installations. On the topic of disk space: How can I get rid of huge cached MSI files and other disk space cleanup tricks. You can also use PowerShell to show the full path to the locally cached package along with the product name. This is the easiest option in my opinion.
And here is WiX contrasted with other deployment tools commercial - strengths and weaknesses - hopefully as objective as possible. DTF is essentially a. NET jewel - perhaps the easiest-to-use.
NET library I have ever seen. Highly recommended - great even for training students in C. WindowsInstaller is one of the DTF assemblies. See the other assemblies explained here on serverfault. ConfigureProduct productCode, 0, InstallState. Installer" installer. InstallProduct "product. A major upgrade is authored by identifying related products in the MSI's " Upgrade table ". These related setups are then handled as specified in the table.
Generally that means they are uninstalled, but the main setup can also be aborted instead typically used to detect higher versions of your own application present on the box. In my experience these tools feature a lot of "personality" and you need to adapt to their different ways of doing things.
I don't want to make any specific tool recommendations here especially commercial ones , but the well known CCleaner features such an uninstall interface and it has a free version. I should also add that this tool suffered a malware attack recently. I guess we should all remember that even harmless software can be injected with malware in their download locations FTP attack.
I use virustotal. A surprising amount of "gray area" software is usually found with this approach toolbars, smileys, adware, etc And certainly real malware as well. Some usage tips for Process Explorer can be found here - a series of tweets - this Process Explorer tool hooks up to VirusTotal.
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.
Windows process DB: smss. New: Windows dynamic link library DB: cli. Retypes: wxe , rxe , eze , ece , exw , exr , eexe , exxe , exee , nsiexec , ,siexec , maiexec , mdiexec , msuexec , msoexec , msiwxec , msirxec , msiezec , msiecec , msiexwc , msiexrc , msiexex , msiexev , mmsiexec , mssiexec , msiiexec , msieexec , msiexxec , msiexeec , msiexecc , siexec , miexec , msexec , msixec , msieec , msiexc , msiexe , msyexec , mziexec ,.
You should always verify the accuracy of information provided on this page. We pay a big attention to provide you with the correct information. However, many spyware and malware programs use filenames of usual, non-malware processes and DLLs.
If we have included information about msiexec. Also, web links to software and DLL vendors are provided just for your conform, and we cannot guarantee its accuracy nor relevance with DLL or process listed on this page. We are not affiliated with this pages. We are not responsible for misprints on this site or changes occured since this page was published.
The product, software and operating system names mentioned on this web site, can be copyrighted and registered trademarks of their owners. Remove msiexec. Removal guide for software 'msiexec. Tips for getting it away from the hard disk How to permanently delete msiexec.
Restore point will help you to revert changes, if something'll go wrong. Press F3 key to open standard search window. Than type 'msiexec. In couple of minutes, seconds if you're lucky, Windows will find all the copies. Try to locate program, to which the process msiexec.
Than try to uninstall that program in a standard way. Either the package with this ProductCode is not installed or there is a typo. First try to right click on the probably installed.
You will see besides "Install" and "Repair" an Uninstall entry. Click on that. Just google for them. Look there in the table with the name "Property" and search for the string "ProductCode" in the first column. In the second column there is the correct value. You are sure that the product is actually installed! The original install is in fact visible in the current context. It looks as if it might have been a per-user install, and if you are logged in as somebody else now then it won't know about it - you'd need to log in under the same account as the original install.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How to uninstall with msiexec using product id guid without.
Asked 7 years, 11 months ago. Active 1 year, 7 months ago. Viewed k times. The WiX code for the. Improve this question. I don't have a ton of experience with WiX but I was under the impression that what you are doing is correct. What happens if you open up a command prompt and type rundll32 dfshim CleanOnlineAppCache and try again? Add a comment. Active Oldest Votes.
Improve this answer. A final note: you must never hard code a package code in an MSI file for reuse between builds.
0コメント