Microsoft Installer command line string parameter not working?











up vote
1
down vote

favorite












So I am trying to run a quite installation, with my msi, and it seems like I can easily pass a number for a parameter that I have, but I can't seem to pass in a string...I tried using single quotes ' and double quotes "



msiexec /i 'My Installer.msi' /quiet JREPATH="c:\BLA BLA"


This and also the single quotes return this :



enter image description here



Now according to this article : https://docs.microsoft.com/en-us/windows/desktop/msi/command-line-options



it should work...




Property values that are literal strings must be enclosed in quotation
marks. Include any white spaces in the string between the marks.



msiexec /i A:Example.msi PROPERTY="Embedded White Space"




There is no problem with the MSI, I assume this because if i pass a number..it works...



msiexec /i 'My Installer.msi' /quiet JREPATH=3


LATER EDIT:



It seems that the problem appears when I have a space in the value of the parameter..for example something like the example below works :



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA"


This however doesn't:



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA a"


LATER EDIT 2:



These commands including spaces in the value work if using a simple cmd instead of PowerShell..










share|improve this question
























  • Is there a reason enclosing the MSI file name with single instead of double quotation marks?
    – Klaus Gütter
    Nov 23 at 5:29










  • @KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
    – Teshte
    Nov 23 at 7:32










  • @Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
    – Stein Åsmul
    Nov 23 at 18:58















up vote
1
down vote

favorite












So I am trying to run a quite installation, with my msi, and it seems like I can easily pass a number for a parameter that I have, but I can't seem to pass in a string...I tried using single quotes ' and double quotes "



msiexec /i 'My Installer.msi' /quiet JREPATH="c:\BLA BLA"


This and also the single quotes return this :



enter image description here



Now according to this article : https://docs.microsoft.com/en-us/windows/desktop/msi/command-line-options



it should work...




Property values that are literal strings must be enclosed in quotation
marks. Include any white spaces in the string between the marks.



msiexec /i A:Example.msi PROPERTY="Embedded White Space"




There is no problem with the MSI, I assume this because if i pass a number..it works...



msiexec /i 'My Installer.msi' /quiet JREPATH=3


LATER EDIT:



It seems that the problem appears when I have a space in the value of the parameter..for example something like the example below works :



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA"


This however doesn't:



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA a"


LATER EDIT 2:



These commands including spaces in the value work if using a simple cmd instead of PowerShell..










share|improve this question
























  • Is there a reason enclosing the MSI file name with single instead of double quotation marks?
    – Klaus Gütter
    Nov 23 at 5:29










  • @KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
    – Teshte
    Nov 23 at 7:32










  • @Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
    – Stein Åsmul
    Nov 23 at 18:58













up vote
1
down vote

favorite









up vote
1
down vote

favorite











So I am trying to run a quite installation, with my msi, and it seems like I can easily pass a number for a parameter that I have, but I can't seem to pass in a string...I tried using single quotes ' and double quotes "



msiexec /i 'My Installer.msi' /quiet JREPATH="c:\BLA BLA"


This and also the single quotes return this :



enter image description here



Now according to this article : https://docs.microsoft.com/en-us/windows/desktop/msi/command-line-options



it should work...




Property values that are literal strings must be enclosed in quotation
marks. Include any white spaces in the string between the marks.



msiexec /i A:Example.msi PROPERTY="Embedded White Space"




There is no problem with the MSI, I assume this because if i pass a number..it works...



msiexec /i 'My Installer.msi' /quiet JREPATH=3


LATER EDIT:



It seems that the problem appears when I have a space in the value of the parameter..for example something like the example below works :



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA"


This however doesn't:



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA a"


LATER EDIT 2:



These commands including spaces in the value work if using a simple cmd instead of PowerShell..










share|improve this question















So I am trying to run a quite installation, with my msi, and it seems like I can easily pass a number for a parameter that I have, but I can't seem to pass in a string...I tried using single quotes ' and double quotes "



msiexec /i 'My Installer.msi' /quiet JREPATH="c:\BLA BLA"


This and also the single quotes return this :



enter image description here



Now according to this article : https://docs.microsoft.com/en-us/windows/desktop/msi/command-line-options



it should work...




Property values that are literal strings must be enclosed in quotation
marks. Include any white spaces in the string between the marks.



msiexec /i A:Example.msi PROPERTY="Embedded White Space"




There is no problem with the MSI, I assume this because if i pass a number..it works...



msiexec /i 'My Installer.msi' /quiet JREPATH=3


LATER EDIT:



It seems that the problem appears when I have a space in the value of the parameter..for example something like the example below works :



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA"


This however doesn't:



msiexec /i "WKFS ReportGenerator.msi" /quiet JREPATH="c:\;;BLA a"


LATER EDIT 2:



These commands including spaces in the value work if using a simple cmd instead of PowerShell..







wix windows-installer






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 at 9:05

























asked Nov 22 at 15:26









Teshte

3781523




3781523












  • Is there a reason enclosing the MSI file name with single instead of double quotation marks?
    – Klaus Gütter
    Nov 23 at 5:29










  • @KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
    – Teshte
    Nov 23 at 7:32










  • @Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
    – Stein Åsmul
    Nov 23 at 18:58


















  • Is there a reason enclosing the MSI file name with single instead of double quotation marks?
    – Klaus Gütter
    Nov 23 at 5:29










  • @KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
    – Teshte
    Nov 23 at 7:32










  • @Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
    – Stein Åsmul
    Nov 23 at 18:58
















Is there a reason enclosing the MSI file name with single instead of double quotation marks?
– Klaus Gütter
Nov 23 at 5:29




Is there a reason enclosing the MSI file name with single instead of double quotation marks?
– Klaus Gütter
Nov 23 at 5:29












@KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
– Teshte
Nov 23 at 7:32




@KlausGütter Not really...I am using PowerShell, and from my observations it doesn't make any difference if single or double quotation marks are used..
– Teshte
Nov 23 at 7:32












@Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
– Stein Åsmul
Nov 23 at 18:58




@Teshte Updated my answer below with some information on Heath Stewart's PowerShell Modules for MSI.
– Stein Åsmul
Nov 23 at 18:58












2 Answers
2






active

oldest

votes

















up vote
1
down vote



accepted










If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:



& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:BLA BLA`"





share|improve this answer























  • adding & does not change anything :(
    – Teshte
    Nov 23 at 8:51






  • 1




    You may need to escape the quotes with backtick characters. I updated my answer accordingly.
    – Klaus Gütter
    Nov 23 at 13:25










  • yeah...this fixed it :)
    – Teshte
    Nov 23 at 13:31










  • Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
    – Stein Åsmul
    Nov 24 at 11:15


















up vote
0
down vote














UPDATE: Since this was related to PowerShell. See Windows Installer PowerShell Module on github.com (scroll down for description, use releases tab for download). I haven't really tested it much, but it is from Heath
Stewart - Microsoft Senior Software Engineer (github).



Brief, inline sample:



install-msiproduct .example.msi -destination (join-path $env:ProgramFiles Example)



  • How can I use powershell to run through an installer?

  • Get the Windows Installer PowerShell Module easier with WMF 5.0






The below was written before I realized that this was related to PowerShell.





Quick Suggestion: Maybe try this command line:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log" JREPATH="c:MyPath"


Get rid of the double \ in the path you specify (could be enough), and use the old style /QN switch instead of the /quiet switch. Some elaboration and details below.





Silent Installation: What installer is this? Is it a vendor package? Some sort of Java application I presume? This is how to install a normal MSI file silently:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log"


Quick explanation:



/L*V "C:Tempmsilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence




msiexec.exe: There are two types of switches for msiexec.exe - the old fashioned ones such as /QN (Command-Line Options) for silent installation which matches the newer /quiet that you are using (Standard Installer Command-Line Options).



To add properties you do as you have already done, add it to the command line:



msiexec.exe /i myinstaller.msi ADDLOCAL="Program,Dictionaries" SERIALKEY="1234-1234" /qn




Some Further Links:





  • How to make better use of MSI files (On how to deploy MSI files silently with or without transforms applied. First section only. The last section goes into a lot of details on other topics)


  • Batch script to install MSI (similar answer)






share|improve this answer























  • ...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
    – Teshte
    Nov 23 at 7:49










  • also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
    – Teshte
    Nov 23 at 7:51











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434089%2fmicrosoft-installer-command-line-string-parameter-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:



& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:BLA BLA`"





share|improve this answer























  • adding & does not change anything :(
    – Teshte
    Nov 23 at 8:51






  • 1




    You may need to escape the quotes with backtick characters. I updated my answer accordingly.
    – Klaus Gütter
    Nov 23 at 13:25










  • yeah...this fixed it :)
    – Teshte
    Nov 23 at 13:31










  • Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
    – Stein Åsmul
    Nov 24 at 11:15















up vote
1
down vote



accepted










If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:



& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:BLA BLA`"





share|improve this answer























  • adding & does not change anything :(
    – Teshte
    Nov 23 at 8:51






  • 1




    You may need to escape the quotes with backtick characters. I updated my answer accordingly.
    – Klaus Gütter
    Nov 23 at 13:25










  • yeah...this fixed it :)
    – Teshte
    Nov 23 at 13:31










  • Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
    – Stein Åsmul
    Nov 24 at 11:15













up vote
1
down vote



accepted







up vote
1
down vote



accepted






If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:



& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:BLA BLA`"





share|improve this answer














If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:



& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:BLA BLA`"






share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 23 at 13:24

























answered Nov 23 at 8:13









Klaus Gütter

1,587912




1,587912












  • adding & does not change anything :(
    – Teshte
    Nov 23 at 8:51






  • 1




    You may need to escape the quotes with backtick characters. I updated my answer accordingly.
    – Klaus Gütter
    Nov 23 at 13:25










  • yeah...this fixed it :)
    – Teshte
    Nov 23 at 13:31










  • Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
    – Stein Åsmul
    Nov 24 at 11:15


















  • adding & does not change anything :(
    – Teshte
    Nov 23 at 8:51






  • 1




    You may need to escape the quotes with backtick characters. I updated my answer accordingly.
    – Klaus Gütter
    Nov 23 at 13:25










  • yeah...this fixed it :)
    – Teshte
    Nov 23 at 13:31










  • Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
    – Stein Åsmul
    Nov 24 at 11:15
















adding & does not change anything :(
– Teshte
Nov 23 at 8:51




adding & does not change anything :(
– Teshte
Nov 23 at 8:51




1




1




You may need to escape the quotes with backtick characters. I updated my answer accordingly.
– Klaus Gütter
Nov 23 at 13:25




You may need to escape the quotes with backtick characters. I updated my answer accordingly.
– Klaus Gütter
Nov 23 at 13:25












yeah...this fixed it :)
– Teshte
Nov 23 at 13:31




yeah...this fixed it :)
– Teshte
Nov 23 at 13:31












Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
– Stein Åsmul
Nov 24 at 11:15




Hi Klaus, I want to alert you to the availability of the Windows Installer PowerShell Module. See my answer. Not sure if it is any good, but might be good to know about.
– Stein Åsmul
Nov 24 at 11:15












up vote
0
down vote














UPDATE: Since this was related to PowerShell. See Windows Installer PowerShell Module on github.com (scroll down for description, use releases tab for download). I haven't really tested it much, but it is from Heath
Stewart - Microsoft Senior Software Engineer (github).



Brief, inline sample:



install-msiproduct .example.msi -destination (join-path $env:ProgramFiles Example)



  • How can I use powershell to run through an installer?

  • Get the Windows Installer PowerShell Module easier with WMF 5.0






The below was written before I realized that this was related to PowerShell.





Quick Suggestion: Maybe try this command line:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log" JREPATH="c:MyPath"


Get rid of the double \ in the path you specify (could be enough), and use the old style /QN switch instead of the /quiet switch. Some elaboration and details below.





Silent Installation: What installer is this? Is it a vendor package? Some sort of Java application I presume? This is how to install a normal MSI file silently:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log"


Quick explanation:



/L*V "C:Tempmsilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence




msiexec.exe: There are two types of switches for msiexec.exe - the old fashioned ones such as /QN (Command-Line Options) for silent installation which matches the newer /quiet that you are using (Standard Installer Command-Line Options).



To add properties you do as you have already done, add it to the command line:



msiexec.exe /i myinstaller.msi ADDLOCAL="Program,Dictionaries" SERIALKEY="1234-1234" /qn




Some Further Links:





  • How to make better use of MSI files (On how to deploy MSI files silently with or without transforms applied. First section only. The last section goes into a lot of details on other topics)


  • Batch script to install MSI (similar answer)






share|improve this answer























  • ...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
    – Teshte
    Nov 23 at 7:49










  • also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
    – Teshte
    Nov 23 at 7:51















up vote
0
down vote














UPDATE: Since this was related to PowerShell. See Windows Installer PowerShell Module on github.com (scroll down for description, use releases tab for download). I haven't really tested it much, but it is from Heath
Stewart - Microsoft Senior Software Engineer (github).



Brief, inline sample:



install-msiproduct .example.msi -destination (join-path $env:ProgramFiles Example)



  • How can I use powershell to run through an installer?

  • Get the Windows Installer PowerShell Module easier with WMF 5.0






The below was written before I realized that this was related to PowerShell.





Quick Suggestion: Maybe try this command line:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log" JREPATH="c:MyPath"


Get rid of the double \ in the path you specify (could be enough), and use the old style /QN switch instead of the /quiet switch. Some elaboration and details below.





Silent Installation: What installer is this? Is it a vendor package? Some sort of Java application I presume? This is how to install a normal MSI file silently:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log"


Quick explanation:



/L*V "C:Tempmsilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence




msiexec.exe: There are two types of switches for msiexec.exe - the old fashioned ones such as /QN (Command-Line Options) for silent installation which matches the newer /quiet that you are using (Standard Installer Command-Line Options).



To add properties you do as you have already done, add it to the command line:



msiexec.exe /i myinstaller.msi ADDLOCAL="Program,Dictionaries" SERIALKEY="1234-1234" /qn




Some Further Links:





  • How to make better use of MSI files (On how to deploy MSI files silently with or without transforms applied. First section only. The last section goes into a lot of details on other topics)


  • Batch script to install MSI (similar answer)






share|improve this answer























  • ...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
    – Teshte
    Nov 23 at 7:49










  • also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
    – Teshte
    Nov 23 at 7:51













up vote
0
down vote










up vote
0
down vote










UPDATE: Since this was related to PowerShell. See Windows Installer PowerShell Module on github.com (scroll down for description, use releases tab for download). I haven't really tested it much, but it is from Heath
Stewart - Microsoft Senior Software Engineer (github).



Brief, inline sample:



install-msiproduct .example.msi -destination (join-path $env:ProgramFiles Example)



  • How can I use powershell to run through an installer?

  • Get the Windows Installer PowerShell Module easier with WMF 5.0






The below was written before I realized that this was related to PowerShell.





Quick Suggestion: Maybe try this command line:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log" JREPATH="c:MyPath"


Get rid of the double \ in the path you specify (could be enough), and use the old style /QN switch instead of the /quiet switch. Some elaboration and details below.





Silent Installation: What installer is this? Is it a vendor package? Some sort of Java application I presume? This is how to install a normal MSI file silently:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log"


Quick explanation:



/L*V "C:Tempmsilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence




msiexec.exe: There are two types of switches for msiexec.exe - the old fashioned ones such as /QN (Command-Line Options) for silent installation which matches the newer /quiet that you are using (Standard Installer Command-Line Options).



To add properties you do as you have already done, add it to the command line:



msiexec.exe /i myinstaller.msi ADDLOCAL="Program,Dictionaries" SERIALKEY="1234-1234" /qn




Some Further Links:





  • How to make better use of MSI files (On how to deploy MSI files silently with or without transforms applied. First section only. The last section goes into a lot of details on other topics)


  • Batch script to install MSI (similar answer)






share|improve this answer















UPDATE: Since this was related to PowerShell. See Windows Installer PowerShell Module on github.com (scroll down for description, use releases tab for download). I haven't really tested it much, but it is from Heath
Stewart - Microsoft Senior Software Engineer (github).



Brief, inline sample:



install-msiproduct .example.msi -destination (join-path $env:ProgramFiles Example)



  • How can I use powershell to run through an installer?

  • Get the Windows Installer PowerShell Module easier with WMF 5.0






The below was written before I realized that this was related to PowerShell.





Quick Suggestion: Maybe try this command line:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log" JREPATH="c:MyPath"


Get rid of the double \ in the path you specify (could be enough), and use the old style /QN switch instead of the /quiet switch. Some elaboration and details below.





Silent Installation: What installer is this? Is it a vendor package? Some sort of Java application I presume? This is how to install a normal MSI file silently:



msiexec.exe /i c:setup.msi /QN /L*V "C:Tempmsilog.log"


Quick explanation:



/L*V "C:Tempmsilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence




msiexec.exe: There are two types of switches for msiexec.exe - the old fashioned ones such as /QN (Command-Line Options) for silent installation which matches the newer /quiet that you are using (Standard Installer Command-Line Options).



To add properties you do as you have already done, add it to the command line:



msiexec.exe /i myinstaller.msi ADDLOCAL="Program,Dictionaries" SERIALKEY="1234-1234" /qn




Some Further Links:





  • How to make better use of MSI files (On how to deploy MSI files silently with or without transforms applied. First section only. The last section goes into a lot of details on other topics)


  • Batch script to install MSI (similar answer)







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 23 at 18:59

























answered Nov 22 at 18:57









Stein Åsmul

20.7k1354113




20.7k1354113












  • ...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
    – Teshte
    Nov 23 at 7:49










  • also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
    – Teshte
    Nov 23 at 7:51


















  • ...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
    – Teshte
    Nov 23 at 7:49










  • also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
    – Teshte
    Nov 23 at 7:51
















...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
– Teshte
Nov 23 at 7:49




...See my updated question..It seems like the problem appears when I have a space in the value of the parameter...I also tried with /qn and the same issue appears..
– Teshte
Nov 23 at 7:49












also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
– Teshte
Nov 23 at 7:51




also, the logging file is not generated when that window from the question appears..so there is no extra information that I can use from the logs..:(
– Teshte
Nov 23 at 7:51


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434089%2fmicrosoft-installer-command-line-string-parameter-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

What visual should I use to simply compare current year value vs last year in Power BI desktop

How to ignore python UserWarning in pytest?

Alexandru Averescu