- #Chrome remote desktop avast .exe#
- #Chrome remote desktop avast install#
- #Chrome remote desktop avast pro#
- #Chrome remote desktop avast free#
refers to the filename of the "Main" installer ( in my case avast_free_antivirus_setup) refers to the directory where the Main installer was located. refers to the directory the "Main" installer extracted files to (in my case %temp%\_av_sfx.tm~). I then had a look at the switches the "Main" installer was launching the "Real" installer ( tup) with, and found it was using these switches:Ĭode: /sfx /sfxstorage "" /GetEdition:free /brandcode "A" /srcpath "" /sfxname ""
#Chrome remote desktop avast .exe#
exe file extension) called tup, I confirmed what it was doing using Process Monitor, which also showed me that the installer was extracting some files (including the tup file) to a temporary directory (located inside %temp%). Using Process Explorer, I could clearly see that the installer was executing an otherwise non-executable file(due to it missing the.
#Chrome remote desktop avast pro#
My main method was to analyze the installer using Process Explorer, Process Monitor, and to some minor extent IDA Pro and Olly Debug - the last two to examine what switches where handled by the executables.
#Chrome remote desktop avast install#
Therefore I decided to come up with a better solution (in my opinion at least), and I started by looking at how the installer handles the install (what switches, files, etc. I started by reading up on the web for known switches/solutions to the problem, but all I could find was to either let Chrome install then uninstall it, OR kill the Chrome installer when it launches and delete any files it created - none of which in my opinion is a really proper solution. However, today I decided to remedy the problem.
#Chrome remote desktop avast free#
Hope it helps for anybody needing to automate this setup without installing Chrome.Īlright, I'll start of saying that on previous installs I've done of the free version of Avast I've ran it with the /silent switch and let it install Chrome and then uninstalled it afterwards(or just left it, depending on user preferences).
![chrome remote desktop avast chrome remote desktop avast](https://img.informer.com/pa/AFA-v21.4-main-window-display.png)
If you have other Google products installed that use GoogleUpdate.exe, this might not be a good solution for you. The TP.bat script will kill any instances of GoogleUpdate.exe that are already running or start during the Avast install (say about a 60s period on a Pentium 2.6GHZ). I would prefer to prevent GoogleUpdate.exe from running through command-line switches but cannot find any that work with this install. The start /wait prefixing the setup file are not necessary in a batch file but I put them in so that you can try this at the command prompt without scratching your head wondering why the behaviour is different.Īs I've said the solution is not elegant. This is usually about a minute into the Avast Setup, at which point TP.bat will kill GoogleUpdate.exe and exit. Tp.bat will run first and wait for GoogleUpdate.exe to start. Start /wait Avast_setup_free /silent /noreboot The script lines that I use to do the whole install look like.Ĭall TP.bat /exit /waittostart /force GoogleUpdate.bat Rem %OutputDevice% echo Timed out waiting for %TPTarget%, or not instructed to wait. If %TPCounter% LSS %TPTimeout% goto NextIteration If Errorlevel 2 (%OutputDevice% TaskKill /F /PID %%c) If "%TPCounter%" = "1" (echo Waiting %TPTimeout%s for %TPTarget% to start, so me can kill it^^!) >%TFile% echo This is a temporary file created by %~nx0 and may be deleted. Rem Find an unused tempfile name and then create empty file.
![chrome remote desktop avast chrome remote desktop avast](https://fossbytes.com/wp-content/uploads/2021/09/avast-antivirus-service-stopped.jpg)
Set /p TPTarget=What is the name or process id of the task that you wish to terminate? The script I call to kill GoogleUpdate.exe is called TP.bat and looks off
![chrome remote desktop avast chrome remote desktop avast](https://3ddroid.ru/wp-content/uploads/2018/0ctransg810d3.jpg)
At the same time I run the Avast Setup using the Start /wait command so that when it returns to the calling script, Avast has finished installing and there are (hopefully) no timing issues for any installs you have scripted after this. The method I use to install Avast silently without downloading Chrome involves first spawning a script (as a separate process) that lurks in the background waiting for GoogleUpdate.exe to run, then kills it.
![chrome remote desktop avast chrome remote desktop avast](https://relate13.com/wp-content/uploads/2021/09/Avest-Online-Security-Extension-2.jpg)
Ok if you want it, not so ok if you don't want it. From, the setup is downloading and installing Chrome as part of a silent install. For those who haven't read the rest of this thread, versions of Chrome up to this build have by default installed silently (eg Avast_setup_free /silent) without Chrome. Today I decided to put elegance aside and use a blunt instrument to install Avast silently without Chrome. I'm going to put this down to wishful thinking. I thought that I was able to install Avast silently without Chrome using the switches /VERYSILENT /NORESTART /SP- but cannot repeat this today. I might just be talking to myself but in case somebody does reference this thread sometime I must have had my rosetinted glasses on yesterday.