[Mobhack]

My antivirus is like that with new executables that it does not yet know - it freezes the first attempt as it scans it, then terminates. Usually it then lets it run after it puts a pop-up message, but not if you have pop-up messages disabled (gaming mode or something similar it's called in Avast).

It gets so &*^% irritating in the development environment where every new compile is a "new" EXE to it that I finally read the help file and figured out how to tell Avast which folders not to run its behaviour shield feature in..