Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Otherwise you'll need to wait for the official fix. This is NOT an issue caused by Bohemia so they have no input into it's resolution.
Avast just checked the ArmA III fingerprint against it's database and found a threat identified with this and triggered a warning. You then have to apply your own experience and decide whether you trust Avast or the BI devs more... Avast has triggered false positives before; BI (ArmA) devs have never distributed a virus... and make a decision on whether to allow the process through or wait.
It worked when i added the location as exception, thanks
Who, for example, gives you the assurance that the new build was not hacked either on BI servers, or somewhere along the way between BI and Steam, or Steam itself? Are we supposed to believe these actors are invulnerable? Because they are not.
The proper way to avoid situations like that is for the developers to run their builds against the common AV suits and see if it checks out. If there is a false positive, then it MUST BE PART of the beta test process to clear the false positive in correspondence with the AV developer. Only then should it be released into the wild. Anything else is carelessness and can easily end up one day in a huge major fu*k up, exactly when malevolent actors recognize that carelessness for the attack vector that it is and fu*k your whole $hit up.
it is extremely unlikely, but what if someone had added harmful code into the .exe and the warning was legit?