THIS DOESN'T WORK ANYMORE So there's been a discussion about renaming Honorbuddy. Some say it matters, others say it doesn't. Personally, I don't know and don't care but it doesn't hurt to try. NOTE: This has to be done every time HB Updates. Questions -Why not simply rename honorbuddy.exe to something else? It will hide name but the description remains the same. Assuming Blizzard scans for processes they could see chrome.exe is in fact a disguised Honorbuddy. How-to: Requirements: You have to download this so you can edit the description: Resource Hacker It's totally safe, you can find mirrors on trusted websites if you don't trust my link. This is a re-assembler basically. Steps: Go to your Honorbuddy folder, find honorbuddy.exe and rename it to chrome.exe (you can rename it to something else but you'll then need to find the other exe's description). Open ResHacker. Go to File > Open... Find your honorbuddy that has been renamed to chrome.exe and click open or accept. You will see 4 folders on the left of the ResHacker screen, expand the one that says version info, it pops up a folder named "1", expand again. There you'll find a file, click once on it. On the right side scroll down a little bit, until you see these lines: Code: BLOCK "StringFileInfo" { BLOCK "000004B0" { Now, the code after that until you reach the closing } symbol. Where you deleted the code, paste this (it's Google Chrome actual description): Code: VALUE "CompanyName", "Google Inc." VALUE "FileDescription", "Google Chrome" VALUE "FileVersion", "30.0.1599.101" VALUE "InternalName", "chrome_exe" VALUE "LegalCopyright", "Copyright 2012 Google Inc. All rights reserved." VALUE "OriginalFilename", "chrome.exe" VALUE "ProductName", "Google Chrome" VALUE "ProductVersion", "30.0.1599.101" VALUE "CompanyShortName", "Google" VALUE "ProductShortName", "Chrome" VALUE "LastChange", "227552" VALUE "Official Build", "1" Click compile script, then File > Save You should be all set, like this: Author notes: As I said previously: I don't care if you care or not about renaming it Neither do I care if you care about me caring about renaming it Nor will I care if you care about me not caring about you caring about me caring about renaming it. Use it if you want it, ask for help if you need it. Try to troll and I won't go with it. Cya.
Good work zon. This is what I used to change mine, same method. Whether or not it actually made things safer, well that's another issue. As you seen in my ban thread I had mine changed and well you know the rest. Regardless, botting is a risk and I accepted the risk many years ago Does that stop me from finding ways to out think the bot snoopers at Blizzard? Nope. Nice guide, sure some folks will find it helpful!
Is this still possible? I had this working in HB version 702 but after updating to 704 and using the same steps, HB now crashes with a Greymagic.dll error. Any advice? Problem signature: Problem Event Name: APPCRASH Application Name: Ventrilo.exe Application Version: 2.5.8529.704 Application Timestamp: 527c1794 Fault Module Name: GreyMagic.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 527c16e1 Exception Code: c0000005 Exception Offset: 00014359 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: a94c Additional Information 2: a94c4e478052b81162aeabc213a0a0b6 Additional Information 3: 7d4a Additional Information 4: 7d4a089f6644915e2a9f79b2670cf7c7 Problem signature: Problem Event Name: BEX Application Name: Ventrilo.exe Application Version: 2.5.8529.704 Application Timestamp: 527c1794 Fault Module Name: StackHash_4c4a Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 4c4a Additional Information 2: 4c4ad7529a34983b6293625c48169922 Additional Information 3: 4c4a Additional Information 4: 4c4ad7529a34983b6293625c48169922
Hello Dude, nice guide. But there is always an error message... Because of the 704er version. And your tutorial was written for the 702er version. Can you please help?
changing it isnt hard it will hang tho, every time hacker resource does the same, you can change the name, but not the description. And until those devs get off theyre asses and get this part of the code ( description part ) un-protected in their software, we will never be able to. So, they dont care, they say its not needed, so we are ... ye, indeed. Looks like every attempt to make this bot safer wich is not implemented by them gets a not needed, no reply or wont change anything answer. If blizz makes snapshots, it will improve security, it will be better, cant understand they dont care.
It was completely working until HB was updated to the newest release, for some reason editing the description causes errors with GreyMagic.dll, I'm still looking into it. My guess is version mismatch
Waiting for the new form! A Gm say me, "You banned because honorbuddy appear in your process" Blizzard can see process... and a gm in live can see your process and banhammer for botting!!! :S
How it looks with the new version of Rename Honor Buddy? Is there a new guide? For the new 704er version? I do not want to be recognized by Blizzard...
It's really odd, this had been working for every version and now that I posted this guide it suddenly can't be done. It's almost as if HB Developers wanted to take all hope away from us. Paranoia aside, I'm still investigating and trying, haven't had any success with it yet.
i always rename to aim.exe because of aol instant messenger, i have been rename every time HB update without no problem for like 2 years now and no banned or suspend at all.
Oh dear another one of these threads -posted with good intentions but rhetoric nonetheless -and worse still is that it's out of date and posted without context. ResourceHacker and its modifications made to the HonorBuddy executable therein has often caused hangs and crashes; this applied to many releases back not just the current one! Your CPU processes and RAM -outside of Wow -have been available by law (you agreed to the terms) since August and November 2012 in both EU and USA. If you want to avoid detection then bot in the safest conditions and do not AFK.
Oh dear another of these condescending replies. The purpose of this thread is to alter the description of HB in the process list, nothing more. It's not a discussion on having agreed to the TOS and why Blizzard can view processes, or even how to bot safely. The info was posted a week ago and worked with the previous version so it's not grossly outdated. I guess the OP said it best himself: