![]() ![]() ![]() Like I wrote, the quarantined file, uTorrent.exe, was from install folder, it was not downloaded, nor it was auto-updated by uTorrent. Which finally brings us back to the real issue in this topic: The user comments in that article does not paint a pretty picture.Īlso, from the article: "Once it identifies something really fishy, it stops the action and reports the behavior to you, before any damage can be done." What's with that?ĮDIT2: Currently running uTorrent and downloading, Avast doesn't seem to mind it anymore? Weird. While at the same time, scanning in the Virus Chest always produces the IDP.Generic result. It's a properly signed file (BitTorrent Inc, sha256RSA) so I don't think that there's anything wrong with it.Īlso ran Avast explorer scan on the restored file and it doesn't find anything wrong with the file. So at least 50% of the shield settings do not work, dunno about the exclusions whether those work or not.ĮDIT: I restored the file from the Virus Chest and ran VirusTotal scan, here's the analysis. The reason I chose to try out the new Behavior Shield is that it offered an "always ask" setting. I've set the "Please define how you would like to deal with suspicious program behavior" to "always ask".ġ) So why was uTorrent.exe silently quarantined?Ģ) Is it normal that a file that was quarantined is left in the file system as empty/0 bytes? I gather that the IDP refers to the Behavior Shield. BUT, there it was, uTorrent.exe in Virus Chest, added on 23.4., with IDP.Generic as the cause. without my consent (I have only File System & Behavior Shields installed). I kind of panicked at what was going on in my computer, faulty HD, malware, etc.? Few minutes went and I remembered to check the Avast Virus Chest, though nothing should be there because I have set the Avast settings so that nothing gets cleaned/quarantined/etc. ![]() I checked the install folder (%APPDATA%\uTorrent\) and the uTorrent.exe file was 0 bytes. torrent file and it didn't open uTorrent client at all. Psychosopher: We/I have answer from Support and it's official enough I am quoting it here:Įdit: thank you.Today I tried to open a. Ideally, you should also report this false positive to the anti-virus software manufacturer customer service, if it isn't an inconvenience to you. I also scanned the entire game installation folder using Malwarebytes software. I checked the game.exe file(OPUS The Day We Found Earth.exe) using VirusTotal. If this isn't possible, you should disable the scanner for the duration of the installation - disconnecting/unplugging your internet connection before disabling your anti-virus software would be a good idea, for security reasons. You should disregard the scanner's error messages, if possible. If the results are inconsistent (as in, different scanners show different results), this practically proves that it's a false positive. Please disregard this warning, or use to have the file scanned by 60+ known, well-established anti-virus scanners. This happens when an anti-virus/anti-malware heuristic scanner (or “smart scanner”) checks a file and finds parts of code that resemble a virus. Our games are thoroughly checked for viruses before launch, therefore we are confident that any warning your software displays is just a “false positive”. We/I have answer from Support and it's official enough I am quoting it here: So all alleged virus reports must be investigated vigorously, even if it will turn out to be a false positive. We can't rely on principles like "GOG wouldn't be foolhardy enough to put viruses on their game" or "a lot of alleged virus reports are false positives." Whilst those points are both true, generally & usually, mistakes can always happen. Rather, my point is that the only wise thing to do is for all GOG customers always to remain very vigilant about this subject. I'm not saying the game mentioned in the OP does have a virus. Darvond: But do you think GOG would be foolhardy enough to not only risk getting sued, but their own data and property? There is a difference between "being foolhardy" and making honest mistakes, and the latter of which does happen sometimes.įor example, there have been a few cases where GOG removed manuals off of GOG games, and also out of everyone's GOG library even if they'd already purchased those games, because GOG had honestly believed that they had the right to include those manuals as a part of the game.īut then they got cease & desist letters from the owners of the intellectual property that comprises those manuals, and so GOG removed them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |