Page 42 of 67

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:21 pm
by Yaliskah
uh??? Oo

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:22 pm
by wargrimnir
Bozzax wrote: Sun Jul 01, 2018 2:10 pm Also get the
Could not download file from server. (WAR-64.exe) and pulled the zip from news


It contains a Trojan though so I won't use it (Trojan:Win32/Fuery.B!cl)
Trojan:Win32/Fuery.B!cl is a heuristic detection designed to generically detect a Trojan. It's not actually a virus. We've explained this before.

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:32 pm
by Hargrim
Bozzax wrote: Sun Jul 01, 2018 2:10 pm Also get the
Could not download file from server. (WAR-64.exe) and pulled the zip from news


It flags as a Trojan (Trojan:Win32/Fuery.B!cl) though so I won't use it
Spoiler:
Trojan: Win32/Fuery.B!cl is a newly detected Trojan horse virus which is was released at the end of year 2016. It seems that the malware is actively used by the criminal hackers. In majority of cases, this Trojan is used for gaining the access onto the infected computer and then stealing user’s banking or financial related information. While seeking this deceptive aim, the virus can not only start capturing your keystrokes, but also start download other noxious computer threats and update itself constantly. Also, the malware can display a bogus bank login screen onto your system’s screen and try to trick you entering your login credentials and other confidential informations.

Yes, you detected our master plan that come to fruition after 5 years. Well done.

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:33 pm
by Yaliskah

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:43 pm
by daemon2611
"The launcher is a trojan / malware!
The mechanism used in order to launch the client is picked up by anti-malware heuristics. Nothing we can do about that.
You can do something about it. Exclude the entire WAR folder in your anti-virus software, Windows Firewall/Defender, or whatever other software you have that would do something like this. How to do this is up to you to figure out, each bit of software is going to have its own procedure.
warpatch.exe doesn't work!
warpatch.exe is not used on this server. We have our own launcher for the server, and you will need to use this launcher in order to connect."

The Malware is announced in this thread: "Technical Support Sticky - Launcher and Installation FAQ"

Unfortunately, i can't pass the "could not download file from server (patchui.dll)" error... any thoughts? :)
thanks in advance!

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 2:59 pm
by Bozzax
Yaliskah wrote: Sun Jul 01, 2018 2:33 pm https://www.virustotal.com/fr/
Spoiler:
Image
Nod downloaded .zip and scanned it on my mac (ok) but when I copied over to my PC Windows Defender still flags/block file: RoRLauncher.exe. (note: Defender also blocked download directly to the pc)

Using the other files from .zip and my own old RoRLauncher.exe worked though and now "connect" is lit up.

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 4:30 pm
by Razac
- Newbie

Image

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 4:43 pm
by MaxHayman
Anyone with 'could not download file from server' it should be working now.

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 4:49 pm
by daemon2611
Thank you very much!!! Cheers!

Re: New Launcher Issues

Posted: Sun Jul 01, 2018 5:30 pm
by Glorian
Bozzax wrote: Sun Jul 01, 2018 2:59 pm
Yaliskah wrote: Sun Jul 01, 2018 2:33 pm https://www.virustotal.com/fr/
Spoiler:
Image
Nod downloaded .zip and scanned it on my mac (ok) but when I copied over to my PC Windows Defender still flags/block file: RoRLauncher.exe. (note: Defender also blocked download directly to the pc)

Using the other files from .zip and my own old RoRLauncher.exe worked though and now "connect" is lit up.
I had just a simmilliar thing.
My RoRlauncher was deleted and I could copy a new one into the Gamefolder.

Reason was after I tried it 3 times that my AntiVir detected it as malware. So went into Antivir and put it on reestablish file and get it on the exception list.
Now Working Again.