Is there nothing you can do against the 132 wow error? Its not my computer thats bad, I only get the error when I start wow with ARelog...
Since 4.3.3, pretty much each time the game goes all black after the character selection and nothing happens.
For some reason ARelog stopped detecting WoW disconnects - not sure its my PC's problem, or something that happened during WoW realm restarts, will update if I learn more.
I get this eror, and it tries to launch Launcher.exe insted of wow.exe, and all reloger just stops working.
I get the problem with launcher.exe too...but it only seems to happen if I use "Start All" and not if i start every account alone
Arelog has been realy buggy lately. The launcher error, wont relog after DC'ing and it doesn't recognize that the char has been logged on and just waits for it to log on even though its already online... All of these bugs happends completely randomly so I realy dont know whats wrong. And there's all of us, just not one so its something with the program.
Same for me. I have set up several tasks and have ticked the loop option, but it will just stop after one task has been completed, or if WoW has disconnected nothing is done. It also only detects when HB has closed, not when it has been stopped.
View attachment 37643 Same error like Beshanas and I will try Bioern's workaround today. Sometimes Arelog runs fine a day then error comes up after 3 or 4 hours. Running 6 Accounts.
i have looked around this forum for an answer but i think i am getting a different kind of error, i have wow in windowed mode, set as running admin, i have reinstalled arelog, and i have arelog set as admin any ideas?
