NEW Version: 19.2.2364

[Sugram22]

@ Sugram22
Please read Posts #121 and #130 in this thread. There are many users experiencing this issue. A reboot usually clears the problem temporarily.

As Asyn directed, please send your logs to help Avast resolve this issue.

win 8.1 in some days it works fine so after reboot it works hole day and if it works fine on pc boot it works hole day, if id doesn't work it doesn't work hole day

does avast restart from service also help temporarily? or can it do harm, cause problems?

i tried i used 7z to compress all the logs and it says error, it mite be 2large or..., i don't know how then and i don't know how to make smaller, don't know how the 7z option works

so can't attach file to post

You aren't supposed to attach them here. follow the directions posted here: https://forum.avast.com/index.php?topic=224848.msg1492655#msg1492655

ok i send from outlook site to petr.blatny@avast.com, i don't have mail software on pc, cause i can do same trough browser by opening the site and login in, THX

[3ogdy]

Just updated to this version. (free)
Windows 10 Enterprise LTSC 1809 (17763.316)

Bugs I've found:

I can't seem to be able to find and reopen a targeted scan that I started from Windows Explorer. Went to PC-> right clicked on the drive I wanted to scan -> "Scan selected items for viruses". All good. The window showed up, avast started scanning & showing progress.
Then I did the exact same thing for a different partition while the first scan was running. I got to see the progress for the second scan, but the first scan was nowhere to be found anymore.

I waited for the 2nd scan to finish. It had found 61 issues so I clicked on "Resolve all", waited until I was told that everything was done and closed the window. Avast showed a pop-up in the lower right corner telling me 61 issues were found (this was AFTER everything had been supposedly resolved).
I clicked to view the issues and was told there were no issues. Closed the window and avast kept telling me 61 issues had been found.

Then, I started looking for the first scan I'd initialized...and it was nowhere to be found. With all the GUI upgrades...and I couldn't find a simple way to reopen a scan I'd started from Explorer. What on Earth?
I knew the scan was still running because the partition I started the scan for was being used heavily by AvastSvc.exe in Task Manager and Resource Monitor.
The scan is still running as of this post...and I can't reopen the window to check the scan progress out.
I went to Protection->Virus scans. Custom scans has a "1" in the top right corner of the button, right above the magnifying glass, but selecting that opens the "Custom scans" window and allows me to create a new scan...still cannot check out the progress of that first scan I'd started from Windows Explorer.
I went to "Scan history", assuming it could be some kind of report that would at least let me know which scans were launched, when AND let me see the ones that were still running. All I got was a list with "Scan name" and "Launch" (date). No option whatsoever to check the scan that was running.

Very, very annoying and counterintuitive.
Next time you release versions like these, think about this: some people fix others' computers and we sometimes use your software - imagine spending hours at someone's place working on their PC only to find out you can no longer see the scan, or even tell how long it's gonna take.

[Asyn]

Provide your logs..!! (https://forum.avast.com/index.php?msg=1492655)

[rocksteady]

...software updater tells me All program are updated, CCleaner version 5.52. But i have installed 5.53!

True. Software updater is not seeing latest version of CCleaner that is available to download.
Well, not yet anyway.

Fixed now.

@Asyn, thanks for notifying software updater is fixed.

[sj.vegetto]

unsecapp.exe is still being triggered and ran when behavior shield is isntalled, Behavior shield does not need unsecapp.exe to run or work. and I would appricated if avast fixes behavior shield from trigger unsecapp.exe from running,  that running has other implications I rather not be open too

Then again the slow image loading on  GUI is still issue 2 years later  it just not as bad as it use to be on SSD, on HDD it still is

[sj.vegetto]

hello I found something in this new version after a clean install:
1/ unsecapp.exe is constantly running (since v19 was released) although Browser clean up tool is not installed (unsecapp is required for it to function according to avast dev long time ago)

Behavior shield started triggering  now in recent build , last time Avast had this problem  of trigger it was like you said when browser clean up tool was installed ( which is not isntalled and never has been cause it trigger "unsecapp.exe"). You can safely terminate the process the behavior shield will work fine, or you can just rename the  process to keep it from  even starting, which more trouble then it worth. or go back to build of avast that didnt trigger this which i no longer sure which builds dont trigger it.

I normally just terminate the process upon boot when i remember it.
Behavior sheild  might trigger unsecapp.exe to run but dont use it according to process monitor so not sure why it even triggering it run.

[DavidR]

hello I found something in this new version after a clean install:
1/ unsecapp.exe is constantly running (since v19 was released) although Browser clean up tool is not installed (unsecapp is required for it to function according to avast dev long time ago)

Behavior shield started triggering  now in recent build , last time Avast had this problem  of trigger it was like you said when browser clean up tool was installed ( which is not isntalled and never has been cause it trigger "unsecapp.exe"). You can safely terminate the process the behavior shield will work fine, or you can just rename the  process to keep it from  even starting, which more trouble then it worth. or go back to build of avast that didnt trigger this which i no longer sure which builds dont trigger it.

I normally just terminate the process upon boot when i remember it.
Behavior sheild  might trigger unsecapp.exe to run but dont use it according to process monitor so not sure why it even triggering it run.

It happened much earlier than 19.1.xxxx, something changed in 18.6.xxxx and unsecapp.exe was launched by the behaviour shield.  It had CPU consequences, certainly for XP users as 18.8.xxxx and the final version for XP/Vista had that in in meaning many can't use that version. 

I had to go back to 18.5.xxxx to be rid of it and get my PC back to some semblance of normal CPU activity and usage. Others also report this in the End of support for Windows XP/Vista topic.

[sj.vegetto]

I know I was in that thread too along with other thread i could find that  referenced unsecapp.exe.

Like said I orginal knew the browser cleanup tool being installed was what caused it which why I never installed it after finding out, and when unsecapp.exe starting popping u again I check to see if, Browser Cleanup was install again. it wasnt that is when I  that is when I started removing shields till I found out it was Behavior shield. it been like this now what 6+  months probably longer.

unsecapp.exe has other consquence for running cpu consequences.

Avast devs need to fix this, I have report this to them multiple times too

[DavidR]

I know I was in that thread too along with other thread i could find that  referenced unsecapp.exe.

Like said I orginal knew the browser cleanup tool being installed was what caused it which why I never installed it after finding out, and when unsecapp.exe starting popping u again I check to see if, Browser Cleanup was install again. it wasnt that is when I  that is when I started removing shields till I found out it was Behavior shield. it been like this now what 6+  months probably longer.

unsecapp.exe has other consquence for running cpu consequences.

Avast devs need to fix this, I have report this to them multiple times too

Well I never installed Browser Cleanup or a whole slew of other components, basically I do a minimal install, so the main shields, plus the Mail Shield and Software Updater.  I never ever install/ed the browser cleanup function, yet unsecapp.exe, so it was pinned down to the behaviour shield.

This leaves the quandary, do I/we deselect to what is essentially a major part of security to progress beyond 18.5.xxxx or do we stick with an older version.  Neither of these options are good and this is made worse when you consider, it has been mentioned that Avast may provide one or two security based updated to what is meant to be the final avast version.

[TheOwner]

Is here any reason why detection dialog button changed from run smart scan to upgrade Avast?

[bob3160]

Is here any reason why detection dialog button changed from run smart scan to upgrade Avast?

Screenshot?

[MartinZ]

Is here any reason why detection dialog button changed from run smart scan to upgrade Avast?

Yes we are testing different approaches in this case.

[fishswimthesea]

Avast Free Antivirus: Installing additional definitions... for the boot-time scan has been running for two hours. In previous versions it took 10 - 20 minutes. I need to use my computer, so I gave up waiting and closed the software. See attachment.

[Asyn]

Avast Free Antivirus: Installing additional definitions... for the boot-time scan has been running for two hours. In previous versions it took 10 - 20 minutes. I need to use my computer, so I gave up waiting and closed the software. See attachment.

-> https://forum.avast.com/index.php?topic=225321.0

[fishswimthesea]

Avast Free Antivirus: Installing additional definitions... for the boot-time scan has been running for two hours. In previous versions it took 10 - 20 minutes. I need to use my computer, so I gave up waiting and closed the software. See attachment.

-> https://forum.avast.com/index.php?topic=225321.0

Thank you for the informative link.