Forum Discussion
Hi,
Can you describe your use case with more details? msiexec is Windows installer process and indeed there are 2+ msiexec processes in the system when some piece of software is been installed.
The actual concern is: do you *really* need to interact with the installer's UI? Is it your actual task to go through the UI while installing the software? If you need just to install the software, this can be done unattended from the command line and without the necessity to interact with installer's UI. (And the latter is the recommended and more preferable approach when you do not do verification of the installer's UI.)
Hi Alex,
Sorry for the very late reply. Have been busy with a lot of stuffs lately.
so answering your questions, yes i need to interact with the installer's UI. There are settings on installer UI that I particularly need to automate.
We already have a base version, say version v1, which is installed through the command line parameters. And then we try to install the latest version say, version v2.
This needs to automated, mainly because we want to automate the way the normal user would do.