Smart scan components differ from those selected

[bob3160]

Reported to Avast.

[DougCuk]

This problem has now been going on since at least May 2018 - but for some reason the fixes never last - and this is getting really annoying. I am constantly getting calls from my customers asking what they need to do about these "Unprotected Sensitive Documents" that Avast is warning them about.

Initially I had some success in deactivating this rogue setting - as detailed earlier in this thread. But this no longer seems to work - the setting just reactivated again on my system (must be the 4th or 5th time now) and it resists all attempts to clear the rogue setting.

On one occasion a Virus Definitions Update appeared to remove the rogue Smart Scan option. So I have to assume that it can also be reinstated by this route. So it would appear that updates from Avast are causing this rogue Smart Scan item to toggle on and off - depending on who builds the update package. Maybe Avast should make sure that all staff are using the same set of rules when building Avast Free updates.   

[Asyn]

Hi guys, you could try the latest beta: https://forum.avast.com/index.php?board=15

[Asyn]

Info from MartinZ: It will be solved different way in new settings. no option to configure smart scan but option to create a new custom scan based on smart scan.

[DavidR]

Info from MartinZ: It will be solved different way in new settings. no option to configure smart scan but option to create a new custom scan based on smart scan.

For me the easiest resolution isn't to run a Smart Scan.

[rocksteady]

For me the easiest resolution isn't to run a Smart Scan.
[/quote]

@DavidR: True, can just avoid the big attractive "Run Smart Scan" button, but that is not the point. I reported this bug months back, but so far no fix. Hope by Bob notifying Avast of user disgruntlement something now gets done.
PS. @Asyn: I will not be trying the Beta version.

Ed 

[bob3160]

For me the easiest resolution isn't to run a Smart Scan.

@DavidR: True, can just avoid the big attractive "Run Smart Scan" button, but that is not the point. I reported this bug months back, but so far no fix. Hope by Bob notifying Avast of user disgruntlement something now gets done.
PS. @Asyn: I will not be trying the Beta version.

Ed
Best I've been able to find out is that there will be a custom scan based on the smart scan.

[rocksteady]

For what it is worth, new version 18.7.2354 still exhibits this problem. Otherwise it installed fine on our Win10 and WinXPSP3 devices.
Ed

[avant-guvnor]

This problem has now been going on since at least May 2018 - but for some reason the fixes never last - and this is getting really annoying. I am constantly getting calls from my customers asking what they need to do about these "Unprotected Sensitive Documents" that Avast is warning them about.

Earlier than May 2018, as I reported this issue in reply no. 51 on 14 November 2017 here:
https://forum.avast.com/index.php?topic=210678.msg1430863#msg1430863

After waiting months for a fix or an explanation from Avast and neither is forthcoming, I suspect this feature is now meant to annoy free users.

Finally, regarding the fix e.g. create a new custom scan based on smart scan, it isn't clear how to set this up. I can create new scans, but I can't see where to create a new scan, based on Smart Scan.

[Asyn]

New settings are planned for V18.8, let's see...

[avant-guvnor]

New settings are planned for V18.8, let's see...

Although I would welcome new settings, I've been hearing that for months.

[Asyn]

New settings are planned for V18.8, let's see...

Although I would welcome new settings, I've been hearing that for months.

Well, that's all I know, but feel free to wait for MartinZ.

[rocksteady]

I have just incurred reocurrance of "sensitive data" scan within Smart Scan.
I know Smart Scan is prone to these failings and I should not use it, but seemed to be cured of this bad behaviour recently.
This occurred on my WinXP SP3 rig with Avast Free 18.8.2356. Even with all Smart Scan components switched off, it still persists. Did Repair of Avast and Reboot to no beneficial effect.
I have also just checked my Win10 rig and same happens with Smart Scan there. The fault must be something recent, as I did a Smart Scan on that without it doing a bogus "sensitive data" scan on that machine just a day or so ago.
Can this be fixed again by devs please. Perhaps a more permanant fix.
Ed

[DougCuk]

The Sensitive Data scan had been showing in my Smart Scan for many weeks - and even a full reinstall failed to remove it. It was still there early yesterday - but now it is gone. There was a Definitions update that was collected at startup today (version 181213-2 dated 13-Dec) which I assume changed the Smart Scan config. This did happen once before as a result of complaints in this thread - but it did not last.

I'm not really sure how a definitions update can change the config of the Smart Scan elements - but it appears that it is possible (having happened twice now). And in fact checking the Config.def file (in the Avast program folder, Setup subfolder) the Sensitive Data item has been removed from the "SmartScanItems" config line. I had tried making this change manually (with the self defense module "paused") and it did work but Avast reinstated it at next reboot. The inclusion of a Sensitive Data scan was obviously coded as a default action somewhere within Avast and was reinstated at reboot if found to be missing.

The current fixed state does survive a reboot - so looking good so far.

[Pondus]

I'm not really sure how a definitions update can change the config of the Smart Scan elements

VPS updates can also containe minor program changes

Signatures also arrive as stream updates evry 5-15minutes  >>  https://press.avast.com/avast-software-streaming-updates-for-all-with-the-newa-avast-7