False Positive Detection with a Glitch [Maybe Solved]

Viruses and worms
1

Alright so I know the drill with your average False Positive file. Send it in using the site and wait for the email telling you bad or good or fixed. But this is a special case that’s only been happening with the last two false flags. Last time it got fixed in a jiffy and I had a file I could send in, so you can guess why I’m here this time. I get the message this time while updating League of Legends and it blocks two things in the same message window. First I tell it to flag it as a false positive and send it in, works great. Then I tell it to move the two files to the chest so I can move them to a place with an exception so I can upload them to virus total and check them myself. The message goes away only to re-appear a moment later same message I chose the same option and it keeps coming back up. The only way to get it to stop is to outright log off and log back on to refresh windows. So now I’m sitting at a total of 23 False Positive detection’s in the monthly with no way to send the files in myself and no way to refresh the count without waiting 30 days so if a real detection comes in I’ll know about it. What do I do to fix the glitch? Is there a way to reset the 30 day counter without waiting 30 days?

[After digging for an hour I finally found where the logs are stored. This is what the message showed and said.]

  • avast! Real-time Shield Scan Report
  • This file is generated automatically
  • Started on: Thursday, September 25, 2014 10:03:41 PM

9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
9/25/2014 11:38:06 PM C:\Riot Games\League of Legends\RADS\projects\lol_patcher\releases\0.0.0.7\deploy\jpatch.exe [L] Win32:Evo-gen [Susp] (0)
While moving file to chest, error occurred: Access is denied
While moving file to chest, error occurred: Access is denied
While moving file to chest, error occurred: Access is denied
While moving file to chest, error occurred: Access is denied
While moving file to chest, error occurred: Access is denied

Fox

2

Always give info on what the avast message say … or attach a screenshot

3

Done. Check the edit.

4

Alright. I don’t know how. I don’t know why and I’m very unsure what to do next but the detection quite literally fixed itself when I tried to replicate it again to get a picture. Maybe !Avast updated before I logged off the last time I checked I don’t know. If you want me to post logs to make sure this wasn’t real, feel free. I just finished two scans, one with MBAM and !Avast both came up completely clean. I trust Riot enough to say that this was likely a FP and because I was literally doing nothing besides updating when the message appeared to allow for a coincidence.

Fox.