Based on what I've observed on client computers and comments to this list, my guess is that this is an issue with current definition files and not the version of the scanning engine. I've been seeing the previous version (10.0.2.2020) detecting Trojan.Dropper as well, so I don't think the new version upgrade announced last week (10.1.0.401) is to blame. -JLT -------------------------------------------------------------------------- Jonathan L. Trigaux CIT Client Services | Rubenstein School of Environment & Natural Resources 111 Waterman | 342 Aiken University of Vermont Burlington, VT 05405