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
To Fix I had to restore the file after it was quarantined "While" the download was happening for it to recognise the file was still there. So it didn't make a new iteration of it, which would instantly be quarantined preventing the complete update. . . This was a pain in the ass. . .
Once the Update is done the file that caused the issue is irrelevant
Saber in a rush much?
"SymStore (symstore.exe) is a tool for creating symbol stores. It is included in the Debugging Tools for Windows package."
Saber Interactive is the company that made SM2. "Saber" is added likely so Windows can tell the difference between the native version of Symstore and The Saber Interactive version.
The only fix I can think of is figuring out how you can add the file to an exceptions list in your AV. If you're using AVG or avast as AV, I've heard they're prone to flagging false positives, mainly things that modify an .exe. Frankly Windows Defender is quite adequate now a days. I'm a little paranoid so I also use Malwarebytes as a double check scan.