Argument to pass in "Specify Installer Argument" field to have silent installation?

%3CLINGO-SUB%20id%3D%22lingo-sub-1142555%22%20slang%3D%22en-US%22%3EArgument%20to%20pass%20in%20%22Specify%20Installer%20Argument%22%20field%20to%20have%20silent%20installation%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1142555%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Team%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20using%20MSIX%20Pcakaging%20Tool%20to%20convert%20some%20exes%20and%20msi%20installers%20to%20MSIX%20package.%26nbsp%3B%3CBR%20%2F%3EI%20want%20to%20have%20silent%20installation%20of%20these%20installers%20at%20STEP%205%20(Installation)%20-%20that%20is%20no%20GUI%20to%20be%20popped%20up%20and%20default%2Ftypical%20installation%20to%20be%20continued%20(no%20need%20to%20click%20next%20next).%20The%20installation%20should%20take%20place%20in%20background%2C%20unless%20there%20is%20something%20that%20user%20needs%20to%20enter.%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20archiving%20this%2C%20what%20argument%20can%20be%20passed%20in%20Step%203%20(Select%20installer)%20-%26nbsp%3B%20%22Specify%20Installer%20Argument%22%20field%3F%26nbsp%3B%3CBR%20%2F%3EI%20have%20tried%20-%20'%2Fqn'%20%2C%20'%2Fs'%20and%20'%2Fqb'%2C%20but%20none%20of%20these%20worked.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3CBR%20%2F%3EPriyanka%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1144487%22%20slang%3D%22en-US%22%3ERe%3A%20Argument%20to%20pass%20in%20%22Specify%20Installer%20Argument%22%20field%20to%20have%20silent%20installation%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1144487%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F258183%22%20target%3D%22_blank%22%3E%40Priyanka_Aggarwal%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThose%20installer%20arguments%20should%20work%2C%20we%20simply%20pass%20them%20to%20the%20installer%20through%20the%20tool.%20Its%20generally%20specific%20to%20the%20installer%2C%20so%20could%20you%20verify%20that%20those%20installer%20arguments%20work%20when%20you%20aren't%20installing%20through%20the%20tool%3F%20In%20my%20experience%2C%20there%20are%20some%20exe's%20that%20I've%20encountered%20that%20need%20'%2FS'%20instead%20of%20'%2Fs'%20for%20example.%20If%20you%20are%20still%20having%20an%20issue%20with%20passing%20the%20arguments%2C%20please%20let%20me%20know%20and%20I%20can%20follow%20up.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3ESharla%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158419%22%20slang%3D%22en-US%22%3ERe%3A%20Argument%20to%20pass%20in%20%22Specify%20Installer%20Argument%22%20field%20to%20have%20silent%20installation%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158419%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F258183%22%20target%3D%22_blank%22%3E%40Priyanka_Aggarwal%3C%2FA%3E%26nbsp%3BThe%20starting%20folder%20of%20the%20process%20would%20be%20System32%20I%20belive%2C%20which%20may%20cause%20some%20exe%20installers%20to%20break.%20Also%20MSIs%20are%20handled%20by%20msiexec.exe%2C%20so%20it%20depends%20on%20how%20the%20tool%20is%20launching%20the%20process%20whether%20or%20not%20the%20switch%20would%20be%20passed%20on.%3CBR%20%2F%3E%3CBR%20%2F%3EMost%20reliable%20way%20I've%20found%20is%20to%20use%20an%20install.cmd%20file%2C%20and%20specify%20the%20startup%20exe%20and%20args%20as%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EPath%3A%20C%3A%5CWindows%5CSystem32%5Ccmd.exe%0AArgs%3A%20%2Fc%20%22Path%5CInstall.cmd%22%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3EThen%20make%20sure%20your%20cmd%20file%20plays%20nicely%20with%20an%20unknown%20current%20working%20dir%20by%20either%20starting%20with%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3Epushd%20%22%25~dp0%22%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3EOr%20putting%20%25~dp0%20in%20each%20command%2C%20e.g%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3Emsiexec%20%2Fi%20%22%25~dp0Setup.msi%22%20%2Fqb%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hi Team,

I am using MSIX Pcakaging Tool to convert some exes and msi installers to MSIX package. 
I want to have silent installation of these installers at STEP 5 (Installation) - that is no GUI to be popped up and default/typical installation to be continued (no need to click next next). The installation should take place in background, unless there is something that user needs to enter.

For archiving this, what argument can be passed in Step 3 (Select installer) -  "Specify Installer Argument" field? 
I have tried - '/qn' , '/s' and '/qb', but none of these worked.

Thanks
Priyanka

2 Replies

Hi @Priyanka_Aggarwal,

 

Those installer arguments should work, we simply pass them to the installer through the tool. Its generally specific to the installer, so could you verify that those installer arguments work when you aren't installing through the tool? In my experience, there are some exe's that I've encountered that need '/S' instead of '/s' for example. If you are still having an issue with passing the arguments, please let me know and I can follow up. 

 

Best,

Sharla 

 

 

 

@Priyanka_Aggarwal The starting folder of the process would be System32 I belive, which may cause some exe installers to break. Also MSIs are handled by msiexec.exe, so it depends on how the tool is launching the process whether or not the switch would be passed on.

Most reliable way I've found is to use an install.cmd file, and specify the startup exe and args as:

Path: C:\Windows\System32\cmd.exe
Args: /c "Path\Install.cmd"


Then make sure your cmd file plays nicely with an unknown current working dir by either starting with:

 

pushd "%~dp0"


Or putting %~dp0 in each command, e.g:

msiexec /i "%~dp0Setup.msi" /qb