I have just run some tests just now and I was able to reproduce the same behavior as you. It looks like this is an issue on our side for which I already create a ticket with the maximum priority so it can be addressed as soon as possible.
I have a Main EXE package with 3 chained MSI packages. The last MSI in the chain should execute some custom actions of type "Launch file". The Main EXE is deployed with parameters "/exenoui /qn" via SCCM.
Unfortunately the actions are often not executed. But not always. Sometimes it works ...
Unfortunately, uninstalling as a custom action no longer works. I have no idea at the moment.
I have defined the custom action "Launch EXE with working directory". As file = msiexec.exe and SystemFolder as working directory and as command line parameter "/x {product id}". This works when it ...
does it also work in my case? I need to uninstall another MSI package when my application is installed . I mean I tried it already with custom action or on prerequisites page als .BAT scheduled "After the Main Package" but it doesn't work. The .BAT contains "msiexec.exe /x {GUID} /qn ...
I have an installer with 3 chained MSI packages. After all chained packages are installed an other software should be uninstalled (if present on computer). The software for uninstall is also MSI based. I have the MSI file too.
thank you. I defined all sub packages as Feature-based and the installation runs fine now. But the problem is now on uninstall of main setup. I defined the uninstall command line for some Feature-based sub packages but these will not be uninstalled.
Hi, I'm using chained installation with 3 MSI packages. Now, the vendor provide EXE instead of MSI. How to rebuild my project with dependency as follows?
1. NET Framework vX.X must be installed 2. Visual C++ vX.X must be installed 3. installation of one third party MSI package (32 or 64 bit based ...
your suggestion will not help me. In case of uninstall the folder with this file will be deleted. I will copy this file to another location on the disk before removal. After re-install this file can be copied back to the profile folder.