I’ve had some developments with this, but last night right when I then had to go to bed and couldn’t post.
I did find and go through the ‘old settings’ a few days ago (I’ve only been running Avast - Premier - for a couple of weeks), but I keep forgetting about them. When I did remember late last night, I found they do fit exactly (at least with respect to the Smart Scan) everything I found in the Avast online Help that I was complaining about not being there in my Avast in my post above. Clearly Avast need to re-do the Help pages either to refer to what is in the now default ‘modern’ settings, or to add in the need to open the ‘old settings’ to then find what some of the Help pages refer to.
That Viruses & Malware.txt file you mentioned and I said I didn’t have is, I see, a report, by default switched off, but which one can turn on in the ‘old settings’ Smart Scan options, specifically for reports for the virus and malware scan part of a Smart Scan. I don’t have the file because the option to turn it on was set to off in those old settings, and I missed it when going through all the settings, new and old, and turning on the report options for the other scans which ARE in the new settings. BUT it only covers the Malware scan step of the Smart Scan, not the other parts of the Smart Scan, so it wouldn’t have helped in this case even if turned on.
But something unexpected happened when I decided to run another Smart Scan just to check on something just before I went to bed last night, which has made me pretty sure I actually ran into a bug with the scheduled Smart Scan I posted about in this thread rather than the deliberate poor design I assumed and complained about in the posts above. I haven’t understood exactly what that final ‘advanced issues’ part of the scan actually covers, and was wondering if some text popped up during that part of the scan saying what was being checked each moment, like it does with the Viruses and Malware part, and I just hadn’t noticed, so I ran another Smart Scan to see - and found it doesn’t. But what was really unexpected was that it found an issue again - unexpected because it hadn’t found anything on any other Smart Scan over the last two weeks since installation before last night’s scheduled Smart scan, and supposedly that Smart Scan fixed the whatever-the-unkown issue was it found, so I wasn’t expecting it to find anything. But on this manually started Smart Scan, at the end of the ‘Advanced Issues’ part I got the same alert type page as on the scheduled smart scan, and the same line about having found an ‘open door’ to a more advanced threat. But whereas on the scheduled Smart Scan there had been nothing below that other than the ‘resolve’ and ‘ignore’ buttons, THIS time there was a box specifying exactly what the issue was. It had found a file (which it named) it thought had sensitive data in that wasn’t set to be covered by the Sensitive Data shield. And whereas it still did not say what ‘resolve’ would do, pretty obviously it would add it to the covered list in the Sensitive Data Shield - which it duly did after I clicked ‘resolve’.
So, clearly it is NOT the case that Smart Scan ‘advanced issue’ scans do not, by design, tell me what found problems actually are as I had assumed after the scheduled Smart Scan and its completely uninformative warning. Instead, I now conclude that what happened at the end of the scheduled Smart Scan was I encountered a bug in the Smart Scan. Unfortunately the lack of a Smart Scan report or log leaves me unable to choose between two possibilities for the bug. Either (a) the first, scheduled Smart Scan found the SAME problem as the second on demand one - the unprotected sensitive document - but a bug prevented it from completing the result page with the part specifying the problem, and the ‘resolve’ action then actually failed without saying so; or (b) the first, scheduled Smart Scan found a DIFFERENT problem than the second on demand one, but a bug prevented it from specifying that problem in the result page. I’m inclined to guess it’s the former, and it’s also possible the bug only manifests in scheduled Smart Scans, not on demand ones. But that is only a guess on the current evidence.
Either way, there’s a bug; and the lack of an option to produce Smart Scan reports for all the scan phases other than the virus and malware check makes it hard to diagnose. Avast really SHOULD add options to generate reports for every Smart Scan phase.
Hm. I suppose that if I remove that document from the Sensitive Data Shield protected document list, then change the schedule for the Smart Scan to get another scheduled scan, I might be able to see if I can replicate the results. If I can, it would show that the scheduled Smart Scan advanced issue found is the same unprotected document as found by the on demand scan, and that the bug is specifically with scheduled Smart Scans. I’ll try that a bit later, and if I can replicate the problem I’ll switch to reporting it in the thread about the latest release.