Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
Follow this tutorial on how to create an exclusion area with Kaspersky:
http://www.slitherine.com/forum/viewtopic.php?f=234&t=45519
If it starts with HEU. then it's the heuristic scan which fails.
Didn't work for me. Kaspersky keeps finding it afterwards.
It often gives false-positives. This is a problem with Kaspesky here, not Distant Worlds.
You can safely add the exception.
I've seen posts that updates to the previous Shadows expansion got detected (false positive) by Kaspersky, so it's not the first time either.
http://support.kaspersky.com/10017
They shouldn't have to.
Most antivirus publisher prefer automated reporting and won't listen to the users.