[CLIENT] - 5.5 Patcher Not Working + Discussion

Redesignated·3/13/2015, 2:07:43 AM·2 votes·2,922 views

EDIT: Disabling avast!'s shields until the patch had finished downloaded allowed it to go through without issue. I would recommend doing this if you're experiencing issues.


I've been trying to patch to 5.5 since noon (roughly nine hours ago now), and have gone through 10+ attempts at it. Every time, it gets to 6k–10k files scanned during the "calculating differences" stage, and then stalls with an unspecified error. I did a little tech work (i.e. randomly turning things on and off while listening to "Volare" by Gipsy Kings for moral support), and it seems to be an issue rising from avast! Anti-Virus detecting a specific Web address used during the patching process as a malicious location. The location in question: IP address 52.10.72.221.

http://www.infobyip.com/ip-52.20.72.221.html http://www.infobyip.com/ipwhois-52.20.72.221.html

The address is currently registered to Amazon Web Services, which is a reputable service. However, the address itself is identified as hostile, potentially due to services that specific sub-host for AWS has been used for recently: http://whatmyip.co/info/whois/52.10.72.221

If anybody else is having this issue, have you been able to fix it? Are you using avast!, or something else? Are you experiencing entirely different problems with patching? I'm going to try a hard reset on my PC (was doing work earlier while trying to patch, so I didn't really have the opportunity) and see if that helps anything.

7 Comments

Psychiatric3/13/2015, 2:48:04 AM1 votes

Watching a sports video, I randomly heard my AV go off (Avast). It detected lolclient.exe with an address of 52.10.72.221 .

It was awfully random, though I had closed my client a few minutes before it had happened, so maybe that triggered it?

I didn't have any issues patching my client earlier today and I had actually played a few games. Not sure why this happened.

kazenokiseki3/13/2015, 2:56:55 AM1 votes

The patch was completed for me, though AV went off after a game...(same issue as 52.10.72.221 being malicious).

Redesignated3/13/2015, 2:58:39 AM1 votes

Just attempted a hard reset, avast! is fully up-to-date, bug is still happening. Going to try patching with shields temporarily disabled and see if that helps.

{quoted}

Watching a sports video, I randomly heard my AV go off (Avast). It detected lolclient.exe with an address of 52.10.72.221 .

It was awfully random, though I had closed my client a few minutes before it had happened, so maybe that triggered it?

I didn't have any issues patching my client earlier today and I had actually played a few games. Not sure why this happened.

Some file called "m.gif" or similar is being hosted and called from that domain periodically. Not sure what it's used for though.

SIushy3/13/2015, 2:58:40 AM1 votes

Same thing has happened to me, I currently do not know what to do...

Redesignated3/13/2015, 3:57:13 AM1 votes

Disabling avast!'s shields until the patch had finished downloaded allowed it to go through without issue. I would recommend doing this if you're experiencing issues.

Argent Argonaut3/13/2015, 9:21:48 AM1 votes

Mine keeps reporting a malicious message from the same address as well. it keeps popping up multiple times randomly when I'm logged into client

Sir Yamazuki3/14/2015, 6:46:37 AM1 votes

I am also getting the notification rather often while using boards, client, or pather. I reported it to Avast, so just waiting for an answer.