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
Two possible outcomes:
Over zealous AV (which is not a bad thing).
Some malicious process corrupted that executable (unlikely).
I'd run a quick scan, read any log output and if clean make an exception for that executable.
If you are unsure you can always try services that check files on multiple Virus checking engines. A while back Virustotal was the hype for that, though I don't know the current status for that. I have my own private solution for a comparable use case. ;)
None. Don't know what AV you're packing, so: none.