Unsolved Scripted Installation parameters
-
Hey there. I'm the maintainer of the Vivaldi package on Chocolatey.
Looks like for 5.x the installation parameters have changed from what I used in the past (
--vivaldi-silent --do-not-launch-chrome --vivaldi-update
). What are the parameters for silent and standalone installations now? Do we have documentation on these anywhere?It also seems like the .exe simply kicks off another process and exits before installation is actually finished. Is there a
--wait
parameter now as well, or something like it?Thank you.
-
I'm not sure if there has been any more progress on this since the original question, but I figured out some details for Vivaldi 5.5.2805.35 because I'm working on silent standalone installations for automated testing:
- Installations can be made silent with
--vivaldi-silent --do-not-launch-chrome
- Installations can be in three modes:
- Install for all users (
--system-level
) - Install per user (default, no argument added)
- Install standalone (
--vivaldi-standalone
)
- Install for all users (
- The installation directory can be specified with
--vivaldi-install-dir="C:\path\to\vivaldi"
For the process hierarchy, the downloaded
Vivaldi.*.exe
installer does fork two child processes. Both children aresetup.exe
, extracted to the temporary./CR_*.tmp/
sibling directory. The first execution is the installer wizard UI, and the second one is the installer logic that extracts Vivaldi to disk.Luckily, the parent
Vivaldi.*.exe
does not actually exit before its children. Therefore, to wait for the entire installation to be done, all you have to do is wait for the parent process to exit. I did this with PowerShell'sStart-Process -Wait
, and you can probably use Command Prompt'sstart /wait
as well.I figured out most of this by running the installer interactively, providing the options I wanted, installing, and then inspecting
%TEMP%\vivaldi_installer.log
. Not only does this show you the arguments passed tosetup.exe
(which you could also get using Process Monitor), but it shows you error messages when required arguments are missing. For example, the original question's arguments do not include--vivaldi-install-dir
, which triggers the helpful log error[1011/154021.967:ERROR:vivaldi_setup_util.cc(491)] Vivaldi silent standalone install requires --vivaldi-install-dir option
All together, I am waiting for a silent, standalone installation with
Start-Process -FilePath .\Vivaldi.5.5.2805.35.x64.exe -ArgumentList @('--vivaldi-silent', '--vivaldi-standalone', '--vivaldi-install-dir="C:\Users\Administrator\Desktop\vivaldi"', '--do-not-launch-chrome') -Wait
- Installations can be made silent with
-
Following your indications, I can't install vivaldi for all users. here is the command I use:
choco install vivaldi --system-level
On my 2 laptops this command seems identical to :
choco install vivaldi
and installs vivaldi for USER1 only (to "C:\Users\USER1\AppData\LocalVivaldi\Application")
USER2 and USER3 are neglected. What did I forget ?EDIT : I think I have solved my problem. This command:
cinst vivaldi --ia="--system-level" -y
installs vivaldi on this path: %PROGRAMFILES%\Vivaldi and not under %LOCALAPPDATA%\Vivaldi\Application
This is perfect for all users!!!
I have the intuition that to avoid a mess during an upgrade, it is better to uncheck the internal update setting of Vivaldi (Ctrl+F12)...