Behavior Shield not running at startup

On my Windows 7 SP1 machine (all Microsoft updates installed), running Avast free 17.6.2310 since day it was released.

About half the time my machine starts up the Behavior Shield is not running and has to be manually started via the UI. This never happened with 17.5. This is happening to other people I do computer support for, also starting with 17.6 release.

I have tried running a repair, and even uninstalling (avastclear.exe) and installing new. No other virus software has ever been installed on my machine.

Any ideas? I thought this was supposed to be fixed in 17.6, not broken.

Hi priestlucas123,

please send me the content of the log directory via PM. I’ll try to check it.

Thanks,
PDI

@ priestlucas123,
The problem was solved in 17.6 for those of us on Windows 10 because I submitted the requested information.
If you’re willing to help those that use Windows 7, please follow the request from Avast and sent the requested information.
If you need additional help, send a PM to PDI. He’s very helpful and will guide you through the process if you need the help.

Could someone please let me know where the log directory is, and I am not familiar with PM.

Thanks

The most common path is c:\ProgramData\AVAST Software\Avast\log\ but it depends if your system is located on C: drive.

Regards,
PDI

PM is easy. Click on PDI’s logo

http://screencast-o-matic.com/screenshots/u/Lh/1504793796008-18326.png

Now simply select send PM

http://screencast-o-matic.com/screenshots/u/Lh/1504793898586-29555.png

Unfortunately there is no means of attaching a file/s to a PM. So another method is required and email perhaps.

One alternative is to upload the file to google drive or another place and simply enclose the link to
that file in the reply.

I am having this same issue on only one of my Windows 7 laptops using AIS. Sometimes only Ransomware Shield won’t start and other times both it and Behavoir Shield won’t automatically start on powerup. I can start them both via Avast tray icon | Right click | Avast shield control. This has persisted for the past few updates. I’ve tried repairing and also a clean reinstall. The other two laptops have essentially the same third party software as this one, with the exception of manufacturer’s drivers (all three different) and this one has Quicken on it. I have the log directory zipped. It should be alright to upload to Avast FTP server.

Provided you let PDI know about it and, supply him with the information needed to retrieve it from the FTP server. :slight_smile:

Zipped log directory is uploaded to Avast FTP. Filename is GopherJohnLog.zip and is not protected by a password.

Hi Gopher John,

thank you for the data. I checked it and I need to see your debug level logs.

Could you please turn on the debug logging and provide the logs again?

Thanks a lot,
PDI

Hi all,

we’d release small fix in the upcoming beta.
Could you please try the new beta once it’s available and report if the issue persists? The beta should be released on Friday.

Regards,
PDI

It hasn’t been fixed. It was suggested I upload the contents of the log directory. However, my installation has no log directory!

That is because you are looking in the wrong location, try the C:\ProgramData\AVAST Software\Avast\log folder.

bob3160, following your PM instruction doesn’t work for me…I get “Error you are not allowed to access this section”.

I wasn’t aware that Avast has put a restriction on the PM function.
I’ve reported it. We’ll need to wait for an answer from Avast.

I replied in your other topic, https://forum.avast.com/index.php?topic=209685.msg1425440#msg1425440, what you are doing is trying to access his Profile not the PM function.

I am using Avast internet security (paid), with windows 7 pro. This seems to be a bug for a long time now.
With all due respect to these nice fellows here, it shouldn’t be the clients’ job to search for log file and provide it for the developer. Avast should find and fix its bugs, otherwise I will just use the free version.

Rant over.

Absolutely completely correct. If they can’t fix this…and so far they’ve been unable to, tad worrying that they are looking after our protection but there’s a bug in the product.