Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: priestlucas123 on September 05, 2017, 12:14:56 AM
-
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
-
Could someone please let me know where the log directory is, and I am not familiar with PM.
Thanks
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)
-
Could someone please let me know where the log directory is, and I am not familiar with PM.
Thanks
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. :)
-
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".
-
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.
-
bob3160, following your PM instruction doesn't work for me.....I get "Error you are not allowed to access this section".
I replied in your other topic, https://forum.avast.com/index.php?topic=209685.msg1425440#msg1425440 (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.
-
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.
-> https://forum.avast.com/index.php?topic=201143.msg1431155#msg1431155
-
@ 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.
The problem was not solved on Windows 10. I am on Windows 10 with Avast v17.9.2322. Couple of days ago Avast decided to permanently turn off Behaviour shield. I can turn it back on in the standard Status screen, (at least that is implied on the Avast window), but the taskbar Avast icon still shows a little red x. When I exit from the Avast window and then come back in again, the shield is once again turned off.
I've uninstalled and then reinstalled Avast, but that made no difference.
Can someone out there please advise.
-
@ 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.
The problem was not solved on Windows 10. I am on Windows 10 with Avast v17.9.2322. Couple of days ago Avast decided to permanently turn off Behaviour shield. I can turn it back on in the standard Status screen, (at least that is implied on the Avast window), but the taskbar Avast icon still shows a little red x. When I exit from the Avast window and then come back in again, the shield is once again turned off.
I've uninstalled and then reinstalled Avast, but that made no difference.
Can someone out there please advise.
Have you tried a Clean Install of Avast:
https://goo.gl/4Ptzkf
-
Hello again Bob. When I click on PDI's logo it states that I am not allowed to access it???
-
Hello again Bob. When I click on PDI's logo it states that I am not allowed to access it???
What are you trying to find out ??? You may not have enough posts to have access to forum members information.
Are you able to access my information ???
-
I read everywhere in the forum that this issue has been taken care of and I started seeing this issue for the first time on my machine (Windows 10) since last night when I updated my Avast to Version 18.2.2328 (build 17.5.3559.0).
Could someone please confirm if this known issue has been really fixed by Avast?
Thanks!
-
I read everywhere in the forum that this issue has been taken care of and I started seeing this issue for the first time on my machine (Windows 10) since last night when I updated my Avast to Version 18.2.2328 (build 17.5.3559.0).
Could someone please confirm if this known issue has been really fixed by Avast?
Thanks!
Update to the latest version.
(https://screencast-o-matic.com/screenshots/u/Lh/1520032133163-41784.png)
-
I read everywhere in the forum that this issue has been taken care of and I started seeing this issue for the first time on my machine (Windows 10) since last night when I updated my Avast to Version 18.2.2328 (build 17.5.3559.0).
Could someone please confirm if this known issue has been really fixed by Avast?
Thanks!
Update to the latest version.
(https://screencast-o-matic.com/screenshots/u/Lh/1520032133163-41784.png)
The update didn't work. So, I had to uninstall and re-install for it to work. Thanks for taking time to post the details.
-
You're welcome. :)