Still, after months of FP against PrevxEdge, Nod32 is still give FP's against PrevxEdge & zapping the Prevx software causing a reinstallation of Prevx along with Prevx licencing issues for the customer (Nod causing multiple installations). What is Nod playing at with this? Example: Last night, a good customer (Vista, Nod32, PrevxEdge) had a red icon with their Nod32 v3. The error seemed to be that Nod32 was not loading a service correctly & this was not fixed by a reboot. So I remotely logged in, uninstalled Nod32, rebooted, installed a freshly downloaded Nod32 v4. Before Nod32 had time to update, it immediately zapped PrevxEdge - not giving me any chance to restore from Quarantine. (Has Quarantine broken under v4?). So I had to download a new Prevx to install, then contact Prevx to get them to reinstate the licence before I was able to get everything back up & running for the customer. Thankfully Prevx support was online & I got it fixed very quickly... no thanks to Nod.