Can't play with Avast

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    Dear players,

    please read >> here <<.

    Thank you for being a part of this!

    • Hello @Yudo,

      we are aware of this error. Unfortunately, the error does not appear to be caused by our side.

      Please contact Avast Support. We had a similar problem months ago with bitdefender. bitdefender has released a patch for the user, which has solved the compatibility problems.

      Since the "wermgr.exe" is a part of Windows, it is possible that a Windows Update can solve the problem.

      Greetings Firelli
      Quality Assurance Specialist für Metin2.

      Meine Aufgabe ist es Metin2 auf Probleme und Fehler zu prüfen, bzw. gemeldete Fehler zu reproduzieren.

      Habt Ihr dazu eine Frage, schaut hier vorbei und fragt mich.
    • I can confirm this, I am Bitdefender Gold Partner and I was raising this issue to Bitdefender several months ago. There was a new module called Advanced Threat Defence introduced along with Bitdefender 2018 suite that was giving the issue. Till that was solved, only option was to deactivate the module before launching Metin2.

      Another option is to exclude the game from the AV but that's a tricky thing to do...for ex in Bitdefender this is not possible . Why? Because the main game file is not an executable, it has a .bin extension and Bitdefender only allows to exclude applications (that is files with an .exe or .com extension). Excluding the launcher that has an .exe extension does not solve the problem because not the launcher should be excluded but the game client itself. If this is the same with Avast or other antiviruses, you might not be able to exclude the game from a certain AV module. You should be able to exclude the "metin2client.bin" file not the "metin2launch.exe" or the entire game folder and this depends on your AV suite.

      "werfault errors" and "wermgr.exe" are given by the Windows Error Reporting system and even if disabling the service (which is NOT recommended for other reasons except trobleshooting), you will still get the errors. Only way is to either report the issue to Avast and hope for a fix...or switch to another more troublefree AV