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
Might want to report this issue to the FC or any devs of the game, you can go to their discord (if they dont ban you because of the controversy) and report them about this, and then check your computer and just use windows defender from now on. But i recommend you just wait for another patch update and don't touch the game until then.
Or maybe its just a corrupted file, maybe bitdefender is having a stroke, or maybe is just steam having a bad day, dont know, i haven't downloaded the patch yet. But i don't think there's a virus inside the game, that would be stupid.
If it was really a virus infected executable, by now it would have been picked up by other anti-virus engines and ofc by Valve's own security measures. But one can never be 100% certain, so I personally decided to report it and wait.
Lastly, to address the "Disk Write Error" notifications that people are getting, these are caused by the BitDefender av-engine, which has determined the file infected and has either quarantined it or locked access to it (pending on global rulesets, thus the file privileges missing or content file locked errors).
If you really want to bypass this security notification, then at your own risk, you can manually exclude the executable from the BD scanner and then - and only then - restore the file from quarantine (Protection > Antivirus > Settings > Manage Exceptions > Add Exception), but I would advise to wait until the devs have gone through the official procedure and cleared it up or release another patch that rectifies the issue.
For more information, you can check the patch releases here: https://steamdb.info/app/245170/patchnotes/
Then again 50/50 it could just be incompetence. Mike was the only one who really knew how the code worked and he's gone now.