This is why I want initial quickscan optional

[jvidal]

The attached screenshot was taken After avast had finished installing, db was updated and I had already registered. As you can see, the ashquick.exe process continues to run for several minutes, despite I had cancelled it as soon as it started and the AV had finished installing.
I can't understand why this process keeps running after one has pressed the "cancel" button.

PLEASE PLEASE PLEASE, make it optional!

[Mr.Agent]

If you wait some mins does its going to normal ? Or it isnt ?

[jvidal]

yes, but that's not the point.
1) ashquick SHOULD NOT continue to run after Pressing the "cancel" button. Cancel means CANCEL, it does not mean "continue to run for several mins, eating up huge amounts of RAM and 99% of CPU time".
Pressing the cancel button should stop the process immediately and then finish the installation process.
2)I just want to avoid it. Like I said in other post, for me, it's useless most of time, since I install avast on PCs feshly built and SO freshly installed (both by me), so I know FOR A FACT that they're clean.I'm not talking about PCs bought in stores with pre-installed crap.

An option during the customized install to de-select "run a quick scan after installation" is all I'm asking for.

[Nesivos]

In Quick Scan-----Performance lower it to one bar.

Also Un-check "Store Data........."

Also under Settings------Trouble Shooting uncheck "Enable Rootkit Scan At Startup"

See if that helps

[jvidal]

I'm talking about the quick scan that is ran in the last stage of installation.

[Para-Noid]

I personally prefer the initial scan as it might catch something that a previous anti-virus missed. 

[ady4um]

I personally prefer the initial scan as it might catch something that a previous anti-virus missed. 

In the situation described, there is no point. There is no previous AV, no malware, "nada".

That's why the OP is asking if there is any command line parameter or any other method so to skip the first quick scan right after the initial install.

Maybe some of the "silent" options? I don't really know if there is such an option, but the request seems rational/logic for the described case.

[Para-Noid]

In the situation described, there is no point. There is no previous AV, no malware, "nada".

That's why the OP is asking if there is any command line parameter or any other method so to skip the first quick scan right after the initial install.


[/quote]The OP didn't indicate whether or not he had any previous av. I will admit "if" the OP already had avast up and running any update should not have caused an initial scan. 

[jvidal]

please read carefully, I said FRESHLY BUILT PC, FRESHLY INSTALLED OS.
And even if it's not, I just want to skip it. If somebody wants it, they don't have to do anything, it's ran by default.
But, for people like me, who do not want it, I think an option should be added to the customized installation, to make it optional. That's ALL I'M ASKING FOR.

[Asyn]

May I ask, why you ask for that..??
How often do you install on a freshly installed OS..?

[Lisandro]

I think Asyn is fully right.
There is no option to cancel the initial scanning which takes less than a minute.
Can you cancel that? How?

[Para-Noid]

I think Asyn is fully right.
There is no option to cancel the initial scanning which takes less than a minute.
Can you cancel that? How?

The OP states the initial scan continues to run several minutes even after cancelling.
I didn't know you could even cancel it. 

[spg SCOTT]

From the original thread:

I would tend to agree with the OP...it shouldn't be forced on users. If they know that it is clean, then they wont want to waste the time...
I know that I was slightly annoyed at it, when I last installed avast on a machine...

Maybe a command line switch?

It is all about personal preference...I think, it would be better to ask the user first, but that is just me...

[Lisandro]

If the computer is infected, the avast installation could fail.
It's avast duty to make its own installation work.
The initial scanning is a security feature that must be kept there imho.

[spg SCOTT]

I agree with that...but the scan takes place at the end of the installation, doesn't that make it a little redundant in preventing the install being messed up? (The install would already have failed at that point wouldn't it?)