Stub installers: convenient because the binary being distributed to client never changes.I think there are only three install types we need to cover: I think removing SilentSetup.exe would be just fine □ Most folks wanting a silent install (ex: MSI) want to distribute / install the package themselves so they can avoid multiple machines fetching the same data / eating up network Hence my question whether this installer is really needed :-) I can only think of hacky not-nice workarounds to prevent SilentSetup from opening a browser window. In this hard-coded response, it is possible to supply -do-not-launch-chrome. The reason why StandaloneSilentSetup works is that this binary is created by essentially hard-coding a server response. So it can either never open a browser window (also for normal, non-silent installations), or always. But the update server doesn't know whether the installation is to be performed silently. Specifically, the server would have to respond "invoke the internal Brave installer with argument -do-not-launch-chrome". The reason why my technique won't work is that the update server determines whether the installer launches a browser window. Some technical detail: The difference between SilentSetup.exe and StandaloneSilentSetup.exe is that the former is just a small 1 MB online installer that downloads the latest version of Brave from the update server. Can I pose the radical question and ask whether we can simply no longer offer SilentSetup.exe? I'm wondering if SilentSetup.exe is required at all if StandaloneSilentSetup.exe is available. The technique I'm using won't work to fix SilentSetup.exe and I don't see an easy way to fix SilentSetup.exe. Also, this way of installing Brave does not set up Brave's auto-update my PRs above fix StandaloneSilentSetup.exe but not SilentSetup.exe. They happen to work at the moment, but are currently not officially supported. People looking for a workaround can follow the instructions here. My suspicion is that it's not Omaha that opens the window but Brave's own installer. I don't see an easy way how this could be used to suppress the opening of a window. BraveUpdate.exe is Omaha's binary that installs and uninstalls apps and Omaha. So /foo invokes BraveUpdate.exe /foo "appguid=.&silent&.". With arguments, it passes those into the command line instead of /silent /install. Specifically: Without any arguments, the installer invokes BraveUpdate.exe /silent /install "appguid=&.". The reason for this seems to be the following: The silent standalone installer passes its command line arguments on to Brave's auto-update framework Omaha. In particular, /silent, /silent /install and -silent all produce errors. There also do not seem to be command-line arguments that can be passed to BraveBrowserStandaloneSilentNightlySetup.exe to prevent the browser window from opening. Is the issue reproducible on the latest version of Chrome?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |