You're welcome.
It was my reading between the lines when you mentioned the file system shield (which deals with on-access scans), so perhaps that was an error on my part.
I have never seen one that you cannot exclude an area from being scanned in real-time via File System Shield as Avast names it and not still be capable of manually starting a scan.
The problem as I see it (as an avast user, I don't work for avast), in having an exclusion that encompass on-access and on-demand scans. There may well be a case that you want to exclude a folder from on-demand scans (I have my samples folder excluded and by back-up images folder excluded, etc.). But in excluding a folder you are effectively putting a hole in your security if anything malicious was placed there you wouldn't want it to be run either intentionally or accidentally.
What I do know is that avast are very wary in regard to user security on exclusions, a point in case many advanced users wanted a button to click on the alert window so they could a) exclude a file from scans and b) allow it to run if considered an FP.
Avast felt that is too dangerous to have a single click option to ignore/exclude/run a malicious file by accident and that exclusion had to be a deliberate act; so it looks like this is further extended into the on-demand and on-access exclusion settings. If it was done in that single exclusions way the right click scan would be unable to scan any folder you had excluded and return the 0 files and 0 time window which is possibly more misleading.
I have been using avast for almost six and a half years now and have got used to this 'quirky' exclusion setup, it just took a little time at first
I might have missed it, but if you have a 64bit OS the behaviour shield although running doesn't have any rules at this point, but they will be developed as required.
A belated welcome to the forums.