Right, 12 hours ago I went to start up my bots and received the Warden Check false positive. I waited roughly 30 minutes before trying again and it still did not work. I tried roughly 10 times over a 3 hour period last night and each time it did not work. I left it until this morning in the end but I have been getting the same errors all morning. I restarted my system, reinstalled my HB and GB folders and then proceeded to wait 20 minutes for the Warden check to pass. Unfortunately this still did not work and I am now ultimately unable to log in. I would post logs but obviously if the bot does not load no logs are produced. Any further advice/suggestions before I go ahead and start to hunt down this registry key I have heard about?
My best guess would be to go hunting, see what i can dig up. I am not coming up with anything very easily, will wait for Ski, Main, or Tony to hop in and give you some help.
I am using BigSister.exe, and there is no warden problem. Nevertheless, I have a problem of disconnections but it's different, but 3 days without warden checks ! Try it
Previous start was attempted roughly one hour ago, running on a fresh bot install. Just loaded a farmer and then loaded GB, GB threw up the warden check html file before loading the actual bot. Seeing as the bot never actually loaded no logs were written. EDIT; Also the bot load was attempted on a clean Warcraft install. Beginning to wonder whether the bot creates perhaps a temporary file somewhere on my system that is being called and subsequently flagging a Warden check on each load.
You know what... I have just noticed it and yes it is indeed messed up. Time is set to 10:24 when it should be 12:20. Not sure what has caused that so I guess it is time I formatted. Thanks for your help Hawker.
I probably sound like a bit of a noob here, but i get the same issue, especially around 11 - 3 in at night if im not already logged in, it will come up with warden checker. What is it :S ? Could someone explain?
But what is it? I'm guessing its a blizz thing? I thought it meant that a Blizz computer somewhere is watching my action's atm, and my Hb can feel a change in the force so decides to quit for a while
It probably set a time in the past for the 15 minute window to be over, which is why it never went away. If you're still having the issue, send me a PM.
I believe the problem was caused with some files I installed yesterday afternoon, I have since formatted and resolved this issue.
If you want to blatantly ignore the message, you can also do the following to make it run instantly: Run the following: Start -> Run -> Regedit -> HKEY_CURRENT_USER/Software There will be a key with a numeric name, and a subkey called "LastUpdate". If you ignore the numeric or uint key entirely, HB and GB will start without the Warden check stuff. As Hawker will undoubtedly say, not recommended. But if you can tell a false positive from a "real" update, you're free to do this at your own risk. (I think HB/GB ignore the key if the "LastUpdate" value is greater than 15 minutes from the current time)
Just want to add a disclaimer here in big letters: ---- MESSING WITH YOUR REGISTRY CAN DESTROY YOUR PC IF YOU DO IT WRONG ---- ---- THIS IS NOT SUPPORTED BY HB/GB, DO SO AT YOUR OWN RISK ---- ---- IF YOU DESTROY YOUR PC OR THE ENTIRE PLANET, WE CANNOT HELP YOU ----
