All you need to do is update to the latest version: https://forum.avast.com/index.php?topic=219889.0
You certainly don’t need to go to a third party website recommended by someone brand new to this form.
I still see this problem occurring, even though I am using Avast Free 18.5.2342 on Windows 7 SP1.
Unfortunately Avast isn’t addressing this problem until a memory dump is sent, but when I tried this with a connection with over 100Mbps upload speed it still was going to take over 12 hours to send a 600MB file. I tried uploading same file to somewhere else and it took less than a minute, so the problem must have been the Avast server, and I wasn’t going to leave it running for that long.
Memory dump files can be zipped up to reduce the size before uploading.
Are you sending this to the avast ftp location ?
The 600MB file is zipped; original over 4GB but no matter how fast upload speed I have it takes too long
One thing noticed is when it fails, I find the following two events in EventViewer
“The aswbIDSAgent service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.”
“A timeout was reached (30000 milliseconds) while waiting for the aswbIDSAgent service to connect.”
I tried changing the “Startup type” from Manual to Automatic as some have suggested, but I only get message “Access denied” even if I start the Services window as an administrator.
‘Access Denied’ error is very likely caused by Avast Self-Defense. Ensure you are in an Administrative account. Temporarily turn this off in Settings, make your changes to Startup Type, click apply then re-enable Self-Defense. Reboot when done to ensure changes are loaded.
same problem, I have version 18.8.2356 (build 18.8.4084.4090)
The issue of Behaviour Shield being an uncertain starter has existed as long as has Behaviour Shield. Since Avast know what shields are required by the user to run and what shields are actually running, why is there no mechanism to check on this and to automatically restart or start any shields which should be running but are detected not to be?
I guess that this must only require a fairly trivial bit of programming compared with the really awesome stuff inside Avast. It would better ensure protection if it could be ensured that shields are actually running. One shield not running is one shield providing less protection and Behaviour Shield does protect against zero-day hazards. Behaviour Shield must have been a reason (among others) why Avast acquired AVG.
The yellow alert flag (with an exclamation mark?) on the Avast icon in the system tray is not the most conspicuous thing on the screen so it is easily missed and all the while Behaviour Shield is not protecting.
I have a hunch that Avast 19.1.2360 has cured this issue. The simplication of ceasing support of XP and Vista might be relevant?
A problem I have not experienced on Windows 10 in many, many months.
I have not had this problem recently on either XPSP3 or Win10, both running 18.8.2356.
I realise v19 has been released today and that update will not apply to XP or Vista.
Ed
bob3160, my hardware is almost pre-historic. The new Avast 19 has made a huge difference to its responsiveness. Avast is now without peer in the anti-malware field as far as I am concerned.
If it can make an ancient AMD Sempron 3000+ single core 1.8Gz powered Windows 7 (x64) system actually sprightly, it must be good. I do like a gentler pace of web page loading. It gives me time to think.