F-Prot 6.4 begins an immediate scan after installing and rebooting. That is inexcusable as you have no chance to configure the AV first. It kills procguard.exe before it loads in the systray claiming that it is a virus. It quarantines it. When I went to get it out of quarantine, I was able to do that. I had already adjusted the settings in F-Prot as it is set to automatically delete files that it thinks are viruses but put a copy in quarantine. I set it to ask what to do instead. (It is inexcusable that any AV would run like this before allowing the user to adjust settings. I'm very disappointed Frisk...they have been around long enough to know better). Then I tried to start PG from Start/Programs. F-Prot quarantined the file again WITHOUT ASKING FIRST!!! When I looked in quarantine to retrieve it again the file was not there and F-Prot reported nothing in quarantine! That meant F-Prot deleted it even though I set it to ask first and then didn't put it in quarantine the second time. I had to resort to System restore to get PG back with all its settings. I couldn't find the F-Prot quarantine folder to doublecheck that F-Prot had actually deleted the file the second time instead of putting a copy in quarantine. I read the F-Prot help and it doesn't say where that folder is...I assumed C:\Documents and Settings\All Users but I didn't see it there. I, of course, am not happy that PG succumbed so easily to F-Prot ....but that was just the GUI. PG was running I just couldn't interact with it. Plus, in fairness to PG, I want to remind anyone reading that I am using 3.15 which doesn't protect itself as well as 3.4.