F-Secure continues to persecute a file after I excluded it.
F-Secure customer here (loving it), but also an avid gamer and a continued windows XP user. I've run into a little problem with the F-Sec problem that I have not been able to fix. Maybe you nice people could help me out, because I'm about to turn the program off in despair.
The newest and latest games, have all taken to excluding windows XP from their line of support. This includes X-COM: enemy unknown. This game simply wouldn't start on Windows XP.
Luckily, the community surrounding it has come up with an elegant solution!
The jest of it is that friendly modders have created their own DLL files with 32-bit WinXP code and have shown us a way to use a XVI32 to force the game to use these files!
So happy! Game runs perfectly and I trust that person enough to use these files.
Heavy stuff. Problem is, F-Secure agrees and zealously destroys my newly patched files whenever I try to run them.
It comes up with a "Gen:Variant.Barys.508" error and eliminates my newly modded exe, corrupting the game and preventing me from playing.
I've already tried to exclude both the files and the Steam Directory in which they are present through the options, but F-Secure doesn't seem to listen to me.
For now, my only solution is turning off F-Sec whenever I want to play XCOM and unplugging the Internet cable for good measure. It's such an inelegant solution however, so if someone could show me a way to actually make F-Sec respect my decision to exclude certain files, I'm stuck with a customer unfriendly virus scanner