![]() ![]() As a result, real-time scanning should not detect it (but "manual" scan, probably, still will detect it). Then (after the restart), you can to 'restore' item and to exclude it (or folders). But more sounds as a technical limitation. So, even if file is restored - at restart - removal action is anyway proceed. Perhaps, it is uncompleted removal and only after the restart - removal is done (quarantine?! in fact). I think it should not undo the restart removal. Is this normal? Should it not nullify the restart removal? When I restarted it still removed the file and I had to reinstall the product again. What surprised me was that even though I restored the quarantined file it did not undo the restart removal. Maybe there is something like on-going redesign (for except real maintenance, of course). Sounds that their "F-Secure SAS" is indeed under maintenance (quite rare situation for notice). I tried to submit a sample but that part of the F Secure site is down for maintenance. I am also only an F-Secure user (their home solutions). ![]() I can't submit a support request as a home products like F Secure Safe don't appear to be listed. I've rarely had a problem with F Secure Safe doing this so my experience is limited but I added product directory to exclude list (after a couple of attempts) and realizing it was multiple installs hanging around (thank you F Secure for making me realize this). This included the same dll in an old directory of the same product so I knew this is false. I recently upgraded to the newest version when prompted for this software but F Secure flagged it as a suspect trojan. Just to advise the community and ask a question. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |