Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on October 06, 2014, 01:48:08 AM
-
In case this helps any other AVAST user with the same problem... since I updated W7 with SP1, AVAST v7.0.1474 was taking more than two full minutes to boot. (Without AVAST boot time is 42 sec's.) The login screen comes up fast but then the spinning wheel goes on forever even though I have all unnecessary services set to manual and only 3 startup programs.
I disabled COMODO FW wondering if there was a conflict (even though there never was before SP1), but that did not improve boot time.... still over 2 min. I only have three programs in startup: Comodo FW, AVAST and Stickies.
So I turned off the wifi card to stay offline and tried rebooting (with all programs enabled), and boot time was 1:04!
AVAST is obviously grabbing for the network as soon as I login and before the desktop actually comes up... I will look further to see how to delay this behavior until I am fully booted as I don't want to have to remember to get offline every time I shut down, in order to have a fast boot when I start back up next.
And it IS AVAST delaying everything [per Event Viewer] and if I disable AVAST using msconfig I boot fine online or off. But at least I have a clue now to follow up on.
-
No point in trying to troubleshoot an outdated version of avast, doing a clean install of the latest version is recommended.
-
No point in trying to troubleshoot an outdated version of avast, doing a clean install of the latest version is recommended.
No thanks. I want to use v7. (But FTR I DID do a clean install of v10 a few days back and it booted in just over a minute but then left the computer unusable for 2 min while it hogged resources... the same routine I would bet that v7 is doing prior to the DT coming up.)
IAC you obviously haven't read the v7 threads over the last few days here ... some people don't WANT to update. If anyone reading this feels compelled to argue that and not the subject of this thread, please argue it in the v7 threads where that argument is already taking place... or in the "I've had it with AVAST" thread where it is also taking place.
-
I don't have a clue what version 10 you clean installed ???
As I said no point in trying to troubleshoot an outdated version of avast, using outdated versions leaves you in a predicament where you are on your own and will receive no support from avast for issues you may be receiving so essentially you are wasting your effort starting this topic.
You might receive VPS updates for old versions but there is no support for bug fixing internal components "hence" outdated software.
On a side note I have read the other topic mentioned and all I can say/do ::)
-
I don't have a clue what version 10 you clean installed ???
v 2015 10.something or other... don't remember now.
As I said no point in trying to troubleshoot an outdated version of avast,
No point to who? You who doesn't care and doesn't use it, or me and those who do?
using outdated versions leaves you in a predicament where you are on your own and will receive no support from avast for issues you may be receiving
I have never asked for help from AVAST. I was directing my post towards other users... those using v7 specifically. Is that not allowed on this forum? I was under the impression any version could be discussed. Especially a version that continues to be popular.
so essentially you are wasting your effort starting this topic.
Because you are aware of every person who will read my post and you know no one with my problem will see it and perhaps get a clue towards what the problem is... or even just how to circumvent it by booting offline? Or maybe you happen to know not one other person is dealing with this problem? I have no such insights.
You might receive VPS updates for old versions but there is no support for bug fixing internal components "hence" outdated software.
Wasn't planning on AVAST fixing any bugs. Just doing some troubleshooting of my own, got somewhere, and thought I'd share in case it helps someone else.
Feel free to skip my posts, I don't mind, really.
-
It could be AVAST 2015 Beta 3 (10.0.2201)
-
You are a strange group of people, you want to troubleshoot outdated versions and complain when there are conflicts or get infected but you all want to stick with software that has moved on for the better in many ways ( other ways can be removed via custom install ;) )
You can lead a horse to water but can't make it drink is a quote that best suits this occasion ;D
-
You are a strange group of people, you want to troubleshoot outdated versions and complain when there are conflicts or get infected
Please quote one person complaining about getting infected using v7. (Hint, no one did.) As to "complaining" about conflicts with v7, do you characterize every post in this forum about a problem or issue a "complaint" or do you just choose to mischaracterize the posts you don't care for?
What people have complained about is being updated without their permission, leaving their computers (and in at least one case, a slew of corporate computers) virtually useless. People have also complained about configuration choices dwindling in the newer versions and being forced into features or tools they don't want or need. By contrast, people have been PRAISING v7 in the sense they have stuck with it and want to continue to use it and they continue to like it.
The only people complaining aside from those who got SCREWED by the surprise update when they had AVAST config'd to NOT update, are the people here who want everyone to think and do as they do.
You can lead a horse to water but can't make it drink is a quote that best suits this occasion ;D
Maybe stop trying to force feed the koolaid. Not everyone's horse is thirsty. If you are, drink up.
-
Please quote one person complaining about getting infected using v7
Guess you haven't seen that there is a search option on this webboard and/or you don't know how to search.
What people have complained about is being updated without their permission
True, but it happened for a real good reason.
leaving their computers (and in at least one case, a slew of corporate computers) virtually useless.
And who says this wasn't caused by a fault of the admin? After all, he didn't do a fresh install as recommended.
being forced into features or tools they don't want or need.
Totally wrong. No-one is forced to use/install the tools/extra's. It is their own choice. They could have chosen not to install/activate them.
By contrast, people have been PRAISING v7 in the sense they have stuck with it and want to continue to use it and they continue to like it.
Version 7 was good... Back then! Now it is not anymore. New types of threads has risen. Meaning new detection methods are needed which version 7 doesn't have and never will get. It is not only about the vps.
If you don't want the best protection for your system, keep using version 7 (or use something else).
It is very obvious you don't have a clue about computers/software and security.
Please stop whining like a little kid that doesn't get what it wants.
-
It could be AVAST 2015 Beta 3 (10.0.2201)
Yes, that was it. And yes it's a beta whose whole purpose is to work out bugs, (and no, I wasn't willing to continue to use it to help with that effort because it wasn't a version I was interested in sticking with regardless).
-
If you don't want the best protection for your system, keep using version 7 (or use something else).
If YOU want the "best protection" you better switch away from AVAST all together, or maybe you don't review the various lab tests.
I don't need "the best protection" and I've said it many times... v7 is fine with me. I don't know why that bothers the few fanboys here or why you are making my choices your business. My choices are not your business. AVAST supports v7.0.1474... YOU don't need to. And since you don't want to, it's a mystery why you don't have anything better to do but post to threads about v7 bothering the people who want to use it.
It is very obvious you don't have a clue about computers/software and security. Please stop whining like a little kid that doesn't get what it wants.
LOL at THAT projection! You (and the other fanboys here) want everyone to use the newest version and when they aren't interested, you become unglued, rude, hostile and attempt to ridicule them into submission. ...How's that workin' for you?
-
Avast 7:
(http://pixbim.com/wp-content/uploads/2014/07/ww1-gas-mask.JPG)
Avast 2014:
(http://www.iaminthestore.com/media/catalog/product/cache/1/image/dca5dbeb0da86656ca8438b075f39329/D/u/Durable_MO4_Nuclear_War_Crisis_Series_Protector_Gas_Mask_for_Airsoft_Army_Green_OR00106030.jpg)
-
IOW, you got nothin'. I mean, here you are with 11k posts... and you haven't addressed the subject of this thread at all, except to tell me to update to another version. If you don't know anything, just move on. It's ok. Don't be embarrassed that you can't help. I really just wanted to share that v7 boots fine with the network off. That's a good clue going forward. But you can go play with your masks and... whatever else you play with.
-
Sure, keep ignorant and dumb.
Get the clue:
since I updated W7 with SP1
avast didn't change, your OS did.
Here is another clue:
Version 7 was good... Back then! Now it is not anymore. New types of threads has risen. Meaning new detection methods are needed which version 7 doesn't have and never will get. It is not only about the vps.
The question is: Do you want good protection for your system or not? If not, don't use a firewall, don't use malware detectors/removers and other security software.
-
bootsy you're the one who posted here with an issue " that's what forums are for " so expect to get reasoning and advice as to why you are having that issue, if you don't want to listen to common sense then you shouldn't bother forums with your rather pointless and remedial issues.
It is quite obvious you have decided to pester this forum with your presence simply for some lack of attention you aren't receiving elsewhere and are revelling in what you have found here and the disarray you are trying to cause.
Most of your posts are in areas that are really no concern of yours so you are just sticking your nose in for the sake of trolling and when you open a topic such as this one you cant accept others advice on why you have issues so hence my earlier post where I stated you having opened this topic is pointless as know one can help you and more to the truth you "don't want help" so please stop wasting yours and our time and move on if you will.
-
Eddy your picture makes sense 100% true :). Avast 2015 picture will be even stronger and will be more powerful and protect users with even more new and improved features.
Bootsy!!! U have no idea what you are talking about! Listen to me and other advanced users like Craig B and Eddy.
Bootsy here's a hint/clue for you. Buy a new computer/laptop and when you want to install avast 2014/2015 (when it comes out as final) come back here and we will show you how to install Avast properly, you will see a big difference. If you don't want to listen to us and keep using a very old aged version of avast! 7. It's your problem not ours and don't waste our time.
-
I posted a legit thread about a currently supported version of AVAST. I did not ask for your participation since you are not interested in supporting anyone who wants to use v7 of AVAST. And I have gotten nothing but rudeness and flack from you and Eddy as you continue to post here with nothing to say but to stoke an attempted flame war. I reported your last post to the moderator to ask if I am out of line. If they say I am, I will gladly leave. I have no intention of breaking any forum rules. This is a support forum. It supports v7 of AVAST. My post was about v7. It's that simple. If I didn't get a single reply, that's fine too... but the two of you behaving this way makes it unappealing for some posters to join in, if they use v7 too and wanted to comment on my post, as you have made it clear anyone who uses v7 is an idiot and doesn't belong here, in your view.
Again, whatever the moderator decides is fine with me. I was only posting my finding about v7 booting fine with the network off in case it helps another user. How you can misconstrue that as troll like behavior is beyond me, except it's no wonder that came to mind since it's how you are behaving.
-
Bootsy here's a hint/clue for you. [...] If you don't want to listen to us and keep using a very old aged version of avast! 7. It's your problem not ours and don't waste our time.
YOU are the one wasting your time by posting to a thread you have no intention of addressing except to attack the OP, (me). If using v7 "is my problem" then leave me to it. And other v7 users who still LIKE v7. No one is ASKING you to post in this thread, or any other v7 thread!
-
Twist it how you will ::)
As I mentioned earlier VPS updates for some of the old versions are supported, fixing problems are not as development on those old versions has ceased which was also the reasoning behind my saying that unless you are going to update then opening this topic was rather pointless.
The whole of this issue with you having to disable your network card prior to shutting down so it will boot correctly is solely because of using outdated software "AV" not keeping up with the further updates and development of the system, yes you can disable your card as a work around or! you could update the AV as suggested to get better compatibility.
Note that the previous update you performed to the unknowm "10"version was a beta and not a stable release as would be advised.
Another thing you could have done is to set avast to start after everything else which is available within the avast settings, you might also find the slow start is caused by Comodo restricting avasts processes during boot :-\
-
I am not talking about attacking the OP (you) and etc and my intentions is very clear that I don't attack users. This forum is all about helping users solve avast issues (current avast! versions), malware issues, and etc etc). Like me and etc we try to help them upgrade to 2014/2015 (when it gets released). Old avast! version will cause problems to computers "PERIOD". Users with old aged version of avast! with current (supported) Windows OS will cause slowdowns and system freeze/slow downs. All it takes for us to do this keeping our Windows OS up-to-date by installating SP1 (making sure all patches is installed), keeping our avast! version with the latest version, and etc etc. Not keeping our computer systems and resources not updated will cause issues and problems and everything will go downhill from there. I don't post comments on v7 because I don't care about old versions anymore and I have no clue where in this forum talks about old version of avast!
CraigB, Eddy, and etc users like them will agree on me about this!!!
-
Twist it how you will ::)
I am not twisting anything as this thread clearly shows for all to see.
As I mentioned earlier VPS updates for some of the old versions are supported, fixing problems are not as development on those old versions has ceased
I know all this and knew it before I came here. This isn't the issue and no one is asking AVAST to fix bugs in older versions.
which was also the reasoning behind my saying that unless you are going to update then opening this topic was rather pointless.
Not to people who are still using v7 and perhaps having problems. Problems that might be fixed by simply doing a little user-based sleuthing. Or simply sharing their own knowledge and experience. Someone out there might already have this answer.
The whole of this issue with you having to disable your network card prior to shutting down so it will boot correctly is solely because of using outdated software "AV" not keeping up with the further updates and development of the system,
I realize that's the answer one would jump to, but it's not necessarily true. SP1 was officially released in 2011, the same year v7.0.1474 came out, so it should be pretty compatible with it as SP1 is just a collection (mostly) of all the prior patches, and in fact v7 it works fine on many W764SP1 machines.
yes you can disable your card as a work around
...until the problem is identified and fixed (by me).
or! you could update the AV as suggested to get better compatibility.
I won't repeat for the 20th time why I don't want to use the newest version and am sticking with v7. And I am not alone.
Note that the previous update you performed to the unknowm "10"version was a beta and not a stable release as would be advised.
I started building computers for corporate clients in 1988. I have been online for 26 years, before the Internet when you had to join private services or go on local BB boards. I know all about beta trials. I wanted to see what v10 was like in case I was interested in going that route. I knew I did not like v8 or v9. I liked v10 even less. Regardless of how it might perform once out of beta.
Another thing you could have done is to set avast to start after everything else which is available within the avast settings, you might also find the slow start is caused by Comodo restricting avasts processes during boot
While I don't want AVAST to start after the other services because that cripples it effectiveness, I did try that when this first arose for the sole purpose of seeing if it would make a difference. It did not. I also eliminated Comodo as a possible conflicting problem by completely closing it and disabling all processes in msconfig (no diff) and also by adding all AVAST processes to its Trusted Files. Also, Comodo FW and AVAST v7 have been happily existing side by side for several years now. It was only after the SP1 update the problem started. So it isn't likely Comodo.
The other thing is, v7 AVAST works fine on many W764 machines with SP1, so it isn't incompatible with SP1 per se. IOW, where there is a will, there's a way. It will just take more sleuthing.
Thank you for returning to the thread's subject.
-
Old avast! version will cause problems to computers "PERIOD". Users with old aged version of avast! with current (supported) Windows OS will cause slowdowns and system freeze/slow downs.
You are making a sweeping statement that just isn't true. Fact is, v7 is still working fine on many W764 SP1 machines.
Furthermore, W7 is at its end of life. There won't be updates that much longer. SP1 was released the same year as v7.0.1474. And while there have been patches since then, (about 109 so far), they must not affect AVAST or it wouldn't still be flawlessly running on so many machines.
In the context of this thread, the problem lies in AVAST processes trying to grab the network at boot. I might try disabling the Network shield (which I don't need with Comodo FW and the FW built into the router anyway...) see what more tweaking does.
If I discover anything I will post it here for other v7 users.
-
Actually Win7 is supported until 2020 I think if my memory serves me right, Staticguy is correct in saying that older versions of avast will cause more problems/conflicts in windows software as win7 still has changes within it software taking place every month and the old versions of avast wont be remedied to alleviate any problems that occur, your choice/your risk/your problem so good luck to you.
-
bootsy the issues/problems you are facing from the "cause of slow boot narrowed down with v7.0.1474" and etc. issues or problems you may have faced just submit a ticket via avast support ticket. I can say to you this right now that they will ask you to install the latest version of 2014.9.0.2021.
Okay, let me tell you something serious as in the content of malware. Compare malware from many years i.e. 1990-present. How malware has evolved from all those previous years? How has antivirus products has improve from all those previous years? What security measures and precautions did all the security companies and experts from all those previous years come up with? Compare all of these from present?
-
Bootsy, what, specifically, has you so convinced that you need to use an old version?
Keep in mind this is a network-integrated product whose major selling feature is that it keeps itself up to date even by the minute. Yes, Avast 7 continues to get virus database updates, but rest assured it cannot detect all forms of modern malware. Malware writers didn't just stop inventing new ways to infect you 3 years ago. Beyond that, old versions may fall more and more out of date with the operating systems they run on, which are still getting Windows Updates.
There are good reasons new versions are created. Let us not forget that you are here with a problem.
You claim to know what you want, but your statement that you only installed the latest beta version and didn't like it implies you're not yet armed with all the information you need to make an informed decision how to move forward. That's probably why you got critical comments.
Did you try to install the current RELEASE (version 9.0.2021)? If so, what does it do that you don't like? Plenty of folks, I'm sure, would be willing to help you diagnose and debug problems with that, because it's current.
You seem to be upset that folks won't help you diagnose problems with (very) outdated software. Your choice to run such software is certainly yours, but... The phrase "when you break from the pack you're on your own" seems to apply. That's just what happens when you hold back from the mainstream - you get less and less support because you're not longer where the action is.
By the way, in another thread you wrote:
And an AV is only a safety net to a savvy user, not their primary security. Primary security is always user-minimized risk.
Absolutely true. I agree completely. You clearly know what you're doing. My question to you above about why you've chosen to eschew 9.0 is serious, not a criticism of your choices. I'd genuinely like to know why you've decided the current version is not your best choice.
-Noel
-
Whilst an old program version is supported, that is essentially limited to receipt of virus definitions.
Unfortunately since there is no further program development, if this were a startup problem with that program version, it is highly unlikely that program versions of that age are going to be updated. That after all is the likely reason why some people found that their program update was automatically updated despite their program setting, to get around a program problem/bug/feature in some of the old program version/s.
I don't know how your problem might be resolved.
Short of using the latest version, which still receives program development and customising the avast installation (not installing elements that you don't want) I don't really know how your matter can be resolved.
That said the only thing that would be going on close to boot is likely to be avast checking for virus definition updates (VPS), so there could be a possibility to delay the auto VPS update. That is a stab in the dark as there is no way to know for sure if that is the cause.
####
Delay Auto Update - Not sure if this is the same for avast7, but this was in avast8, you need to edit (using notepad) avast5.ini the [InetWD] section of the, C:\ProgramData\AVAST Software\Avast\avast5.ini. Win7, location, this folder may be hidden, you may also have to run notepad.exe as administrator to prevent UAC intervention.
- Broadband connections, add this line:
AlwaysConnectedWaitSeconds=120 and
AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD]
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=120
When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes. You can extend this duration if required.
-
That said the only thing that would be going on close to boot is likely to be avast checking for virus definition updates (VPS), so there could be a possibility to delay the auto VPS update. That is a stab in the dark as there is no way to know for sure if that is the cause.
####
Delay Auto Update - Not sure if this is the same for avast7, but this was in avast8, you need to edit (using notepad) avast5.ini the [InetWD] section of the, C:\ProgramData\AVAST Software\Avast\avast5.ini. Win7, location, this folder may be hidden, you may also have to run notepad.exe as administrator to prevent UAC intervention.
- Broadband connections, add this line:
AlwaysConnectedWaitSeconds=120 and
AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD]
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=120
When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes. You can extend this duration if required.
Thanks for this, David. I considered this might be the problem too. Your nifty little config edit did shave some time off. And also things improved on their own over the next couple days [after I started this thread], as if the SP1 update just needed a few more reboots to square itself away, which sometimes happens.
So boot time is now about 1min to desktop appearing and 1:15 to having everything up in the sys tray, which is livable. Delaying viral updates with your suggestion improved this time by about 20 seconds. Good enough! :) Thanks again.
-
You're welcome - you can of course increase the delay and see if that makes any more difference, but I suspect it wouldn't be much given your new boot times.
-
You're welcome - you can of course increase the delay and see if that makes any more difference, but I suspect it wouldn't be much given your new boot times.
Actually I put 180 to begin with to give my system a little more time as it's an older (2008) laptop with 4GB RAM and a 2gHz CPU ... mediocre specs by today's standards. I'm sure 120 would have been plenty but I don't mind AVAST waiting a few min. It's a great little tip and I made a note of it for future use. :) (BTW would have clicked on a rep icon for you but from what I can tell they don't use those here? If I am wrong let me know how I can give you credit for your help.)
-
SP1 was officially released in 2011, the same year v7.0.1474 came out
Eh no. Release date of 7.0.1474 is 2012-10-31
Source: http://www.avast.com/release-history
-
SP1 was officially released in 2011, the same year v7.0.1474 came out
Eh no. Release date of 7.0.1474 is 2012-10-31
Source: http://www.avast.com/release-history
I guess it was v7 that came out in 2011, but that's even better... that 7.0.1474 is newer than I thought, and was released a year after SP1 came out. That means it's even more compliant.
-
You're welcome - you can of course increase the delay and see if that makes any more difference, but I suspect it wouldn't be much given your new boot times.
Actually I put 180 to begin with to give my system a little more time as it's an older (2008) laptop with 4GB RAM and a 2gHz CPU ... mediocre specs by today's standards. I'm sure 120 would have been plenty but I don't mind AVAST waiting a few min. It's a great little tip and I made a note of it for future use. :) (BTW would have clicked on a rep icon for you but from what I can tell they don't use those here? If I am wrong let me know how I can give you credit for your help.)
A very long time ago I changed mine when I was on dial-up and I didn't want the update check happening if I had just jumped on line to check email, etc. and get back off.
There is no Rep function in the forum software.
-
A very long time ago I changed mine when I was on dial-up and I didn't want the update check happening if I had just jumped on line to check email, etc. and get back off.
I hear that. I actually made mine 180 because the first thing I do at boot is open TBird to check mail, and then FF, and they are process-heavy the first time they are initiated each day. So I lengthened the time to 180 for the same reason, basically. ;D Have a great weekend, David.
-
That said the only thing that would be going on close to boot is likely to be avast checking for virus definition updates (VPS), so there could be a possibility to delay the auto VPS update.
####
Delay Auto Update - Not sure if this is the same for avast7, but this was in avast8, you need to edit (using notepad) avast5.ini the [InetWD] section of the, C:\ProgramData\AVAST Software\Avast\avast5.ini. Win7, location, this folder may be hidden, you may also have to run notepad.exe as administrator to prevent UAC intervention.
- Broadband connections, add this line:
AlwaysConnectedWaitSeconds=120 and
AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD]
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=120
When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes. You can extend this duration if required.
DavidR.....nice trick and great suggestion......nice feature to have for any system I would think ?
Any chance Avast would put this feature as selection in Settings in future V9+ releases ?
It'd be nice to have a 90 to 180+ second delay configurable setting.
-
I believe it had been suggested in the past to delay the update check, so that people didn't have to do the manual edit. It used to be really early now I think it is around the 30 seconds, but without specialist software it would be hard to get the exact time.
A lot really depends on how many people suffer during boot, when you are looking at 200+ million users to shove it back for everyone. Personally I feel it should be an option in the User Interface to delay it by 3-5 minutes avoiding having to do a manual edit of the ini file.
-
Personally I feel it should be an option in the User Interface to delay it by 3-5 minutes avoiding having to do a manual edit of the ini file.
I totally agree.....I think "in general" PCS boot too slow and too much is trying to happen from PW entry to Desktop settling.
I have a SMART software that they added this because they were polling....I think a lot of software "phones home" on login.
Since VBS can be large....depending on factors....it would be nice to have a delay.
I agree perhaps they set a default and this user setting is option in SETTING...perhaps a slider bar of selection range.
I don't know how to suggest new features to Avast...perhaps in the 2015 thread ?
-
Personally I feel it should be an option in the User Interface to delay it by 3-5 minutes avoiding having to do a manual edit of the ini file.
I totally agree.....I think "in general" PCS boot too slow and too much is trying to happen from PW entry to Desktop settling.
I have a SMART software that they added this because they were polling....I think a lot of software "phones home" on login.
Since VBS can be large....depending on factors....it would be nice to have a delay.
I agree perhaps they set a default and this user setting is option in SETTING...perhaps a slider bar of selection range.
I don't know how to suggest new features to Avast...perhaps in the 2015 thread ?
I would think the suggested new features for avast 2015 is too far down the tracks for changing the UI and underlying coding to complete the task. There used to be an avast feedback separate from the forums I think, not sure if that is still available.
-
Personally I feel it should be an option in the User Interface to delay it by 3-5 minutes avoiding having to do a manual edit of the ini file.
I totally agree.....I think "in general" PCS boot too slow and too much is trying to happen from PW entry to Desktop settling.
I have a SMART software that they added this because they were polling....I think a lot of software "phones home" on login.
Since VBS can be large....depending on factors....it would be nice to have a delay.
I agree perhaps they set a default and this user setting is option in SETTING...perhaps a slider bar of selection range.
I don't know how to suggest new features to Avast...perhaps in the 2015 thread ?
I would think the suggested new features for avast 2015 is too far down the tracks for changing the UI and underlying coding to complete the task. There used to be an avast feedback separate from the forums I think, not sure if that is still available.
Too bad......I would think fairly simple adder in the UI......would be helpful feature.
I posted on the 2015 thread....maybe Avast Team will see it.
https://forum.avast.com/index.php?topic=146141.msg1133978#msg1133978