If it stays “Executing” indefinitely, it generally means that it did not actually run “quietly” and instead it is waiting for user input of some kind. However, since it runs hidden, of course no user input can be provided.
I would suggest that you test this syntax manually at the command prompt WITHOUT using BatchPatch. Get your syntax working manually at the command prompt without it requiring any user interaction. Once you have the syntax figured out at the command prompt, then you can easily port it into BatchPatch.
Assuming your parameters and syntax work at the command prompt without requiring any user interaction, then when you enter the command into the BatchPatch deployment the “Command to execute” field would look something like this:
msiexec.exe /p "YourFileName.msp" REINSTALLMODE=omus REINSTALL=ALL BB_DEFAULTVIEWER=0 BB_DESKSHORTCUT=0 IGNORE_RBT=1 DISABLE_WELCOME=0 /qn
NOT like this:
msiexec.exe /p "C:SomeFolderYourFileName.msp" REINSTALLMODE=omus REINSTALL=ALL BB_DEFAULTVIEWER=0 BB_DESKSHORTCUT=0 IGNORE_RBT=1 DISABLE_WELCOME=0 /qn