You also can't send it whilst it is in the chest, you need to export it not restore to the original location.
Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the Standard Shield, Customize, Advanced, Add, type (or copy and paste) C:\Suspect\* That will stop the standard shield scanning any file you put in that folder. You should now be able to export any file in the chest to this folder and upload it to VirusTotal without avast alerting.
Also see, http://www.pando.com/phpbb/viewtopic.php?f=3&t=7898.
Hello,
Checked with our devs, and P4SRCSP.EXE is NOT part of the pando package.
Many thanks for the info. Finally, I succeded to submit the file to VT, which returned me some
positive detections : here follows an abtract (manually done) :
Antivir : ADSPY/Mywebsearch.86016
Avast : Win32:Adware-gen
F-Prot : W32/Mywebsearch.A.gen!Eldorado
Fortinet : Adware/MyWebSearch
GdData : Win32:Adware-gen
Ikarus : not-a-virus:AdTool.Win32.MyWebSearch.aw
Kaspery : not-a-virus:AdTool.Win32.MyWebSearch.aw
NOD*32v2 : a variant of Win32/Adinstaller
Panda : Suspicious file
Sunbelt : MyWebSearchToolbar
TheHacker : Aplication/MyWebSearch.aw
VBA32 : suspected of Trojan-Dropper.Delf.36 (paranoid heuristic)
Webmaster-Gateway : Ad-Spyware.Mywebsearch.86016
So at least, this file looks hightly suspicious to me ...
As during this Pando update, a new toolbar came up, perhaps it would be wise
not to use this bar ... What do you think about it ?
TIA.