Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
Part of the update was massively upgrading the Unity engine version (from a 2018 version to the 2021 version), so this is likely the reason that this is triggering now.
From some quick research it seems like this is a pretty widespread false positive that affects many games & programs.
Unfortunately I may not be able to do much about this, but I'll do some more research to see if there is a fix. For now the only solution is to whitelist the .exe or add an exclusion to your antivirus. There also may be ways to report false positives depending on the antivirus.
- Kevin
I've got the same info when looking around but not everyone is keen on whitelisting something without 100% certainty.
Best regards