neumi5694: 1. do you know any GOG installers that may do something like that? I know some run scripts for registry entries (Tales of Monkey Island being an example). Most of the time we complain about the GOG installers
not installing the necessary runtimes.
2. The 'on access' scan would trigger then when programs are being executed, so protection is active.
3. do you know any scanner that would be able to find a problem like that before the chunks were unpacked? Because then I agree, then it would make sense.
Well, it's the runtimes which I was referring. If you've got dotNet redists included in the installer and they get launched without prompting the user, then if they contained anything malicious (not saying it's likely, but let's just use this as an example) then the execution has already occurred. Yes, good AV packages scan in progress and nab stuff as they happen. As for detecting the segments of code prior to unpacking ... no, probably not... depending on how it's packaged/compressed. I don't know nearly enough about how they work to say so definitively.
It's just, well, your advice sounded ambiguous/absolute, and when dealing with users of much lower knowledge base here they might take it as verbatim that it's OK to, say, turn off their AV to install and just turn it back on later to scan the install directory. Which, don't laugh, some may actually do because they have had issues in the past with false positives or think it'll significantly speed up the install process.