CS:GO VAC error, Steam Repair tool not working

Tüm Tartışmalar > Steam Forumları > Help and Tips > Konu Detayları

Bu konu kilitlenmiştir.

RipFuel 20 Tem 2015 @ 0:33

CS:GO VAC error, Steam Repair tool not working

I keep getting an error from CS:GO saying: "An issue with your computer is blocking the VAC system. You cannot play on secure servers."
I run through the steam page on how to fix this, use the run command to
"C:\Program Files (x86)\Steam\bin\SteamService.exe" /repair"

This brings up a steam client service box and it never resolves itself.

Need help thanks.

Ps. Running Comodo firewall & Avast antivirus.

< >

39 yorumdan 31 ile 39 arası gösteriliyor

ReBoot 20 Tem 2015 @ 5:21

İlk olarak RipFuel tarafından gönderildi:
I'm also assuming that the trigger is malware. (reasonable assumption?)

Maybe, maybe not. First see id the option gets turned on again at all.

#31

RipFuel 20 Tem 2015 @ 5:28

If I run the command prompt as adminsitrator I can turn debugging off. (Windows 7).

#32

ReBoot 20 Tem 2015 @ 5:55

İlk olarak RipFuel tarafından gönderildi:
If I run the command prompt as adminsitrator I can turn debugging off. (Windows 7).

Again? This indeed means that something's turning it on again.

#33

RipFuel 20 Tem 2015 @ 5:56

Only as an administrator can debugging be turned off.

#34

RipFuel 20 Tem 2015 @ 5:57

'Run as administrator'

#35

ReBoot 20 Tem 2015 @ 7:36

İlk olarak RipFuel tarafından gönderildi:
Only as an administrator can debugging be turned off.

This is not the question. The question is whether you can turn it off once or every time you reboot.

#36

RipFuel 20 Tem 2015 @ 7:39

Everytime.

#37

ReBoot 20 Tem 2015 @ 7:50

İlk olarak RipFuel tarafından gönderildi:
Everytime.

Then something keeps turning it off again. First, get rid of all the software you don't absolutely surely really need. Especially stuff that hooks the system. Because ringing out a virus alert right from the start would be paranoid, there are actually legit programs that do that nonsense. Unless it is a kernel debugger you installed, it needs the option to work at all.

#38