Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Not really something game devs can do much about (outside just not using stupid invasive DRM measures, which I don't think AtS does).
As far as a business level software goes, those are also generally a lot more strict in general, so I would actually expect this behaviour for a lot of games, and according to that message it saw Steam doing something suspicious. Maybe the direct X check/upgrade it normally does the first time you launch a game.
What is the solution? Is it positively safe to tell Sophos to ignore this detection?
In general, is it possible to run the games in my library standalone (without oversight by Steam)? In this case, the game is URU and it is not clear exactly which file in its local files directory I would double-click on in order to run the game.
Any assistance or tips will be appreciated.
Maybe you could find some useful information elsewhere online, like the Sophos website or related forums.
They also have further information on what to do to allow the games to run without triggering the alert, which is just to exclude them from scanning.
Source: https://support.home.sophos.com/hc/en-us/articles/360053083431-Allowing-games-to-run-along-with-Sophos-Home