[guide] generating new unique id

[ObscuR]

[guide] generating new hardware and client unique id

hello all,

if you wanna generate a new hardware / unique id for your botting machine do this.

Generating a new client id :

1: remove HKEY_CURRENT_USER\Software\Blizzard Entertainment from your registry
2: restart diablo
3: voila

Generating a new hardware id :

1: Change all your HHD drives volume ID with VolumeID
2: Change your mac addresses Change Your MAC address in Windows 7 - YouTube
3: Lunch sysprep from \Windows\System32\sysprep.
Select OOBE Out-Of-Box and check the generate check box.
Press Ok . you computer should restart as a new install your it should generate a new windows ID.


Warning: Running sysprep can BRICK your Windows installation permanently with no way to reverse the damage, other than a clean installation!

thx and have fun

 

[Kabomi]

Will this help from botting on 1 account on 1 pc? around 12 hours +? or is it only helpfull for multiple botters?

 

[johnwoo]

It's very simple OMFG !!!

You can launch X Diablo 3 on 1 unique computer. In fact, Buzzard, identify you by 1 unique ID in your registry when you loggon, one time logged, you can change this unique ID and lauch another Diablo 3.

1 loggon = 1 unique ID so don't care about VM, MacAdress or any Hardware ID.
X loggon = X unique ID

Enjoy and thanks Obscur for this trick.

 

[Rayariime]

Thanks, but what's the goal of this?

 

[Gusgus]

Thanks, but what's the goal of this?

Some people need to change the Hardware ID, so Obscur made a guide.

Thx Obscur for that

 

[Aion]

ObscuR, do we need to re-activate our Windows copy, after changing the SID with sysprep? Havent ran it in the last several years

 

[ObscuR]

ObscuR, do we need to re-activate our Windows copy, after changing the SID with sysprep? Havent ran it in the last several years

yea you have to reactivate it

 

[coffeeortea]

Thanks for the heads up! Just wondering though, as I am still fairly new to all this terminology and tech stuff, my question is how often should this change be done? Once every week?

Thanks

 

[elucid]

yea you have to reactivate it

So this eats up an install on that copy of windows?

 

[axazol]

VolumeID not the same as Hardware ID.
And since Blizz looks at subnet/IP more often than MAC (in case what MAC is easily changeable), then it's may bring more trouble with internet provider than profit.

 

[mephuser1000]

3: Lunch sysprep from \Windows\System32\sysprep.
Select OOBE Out-Of-Box and check the generate check box.
Press Ok . you computer should restart as a new install your it should generate a new windows ID.


thx and have fun

Warning: Running sysprep can BRICK your Windows installation permanently with no way to reverse the damage, other than a clean installation!

 

[Chalky]

So this eats up an install on that copy of windows?

Even if it does, you just got to mess with certain updates so windows will never check if its genuine

 

[Chalky]

Warning: Running sysprep can BRICK your Windows installation permanently with no way to reverse the damage, other than a clean installation!

This actually happened to me, as I was in an endless loop of "configuring -> cant get files, restarting-> repeat.
I somehow broke it by booting up in safe mode, which failed, then back to normal, turned off system for 10 mins, tried again and voila. Dont ask me why it worked.

 

[ObscuR]

Generating new Windows id is mor risky. Do this on WMs but note on your main.
Btw its not really neaded juste modify client id

 

[icebox]

dunno how reg keys work but if I have 2 hdds on my rig and install d3 to each, will it automatically create 2 client ids for the registry?

 

[ObscuR]

No they Will have th? same client id exept if you run ait as diferant users

dunno how reg keys work but if I have 2 hdds on my rig and install d3 to each, will it automatically create 2 client ids for the registry?

 

[justforwow]

obscur, after running sysrep with OOb, i rebooted my pc, now its giving this error when its Going on boot up menu & then windows logo comes and says
"Starting services, then i get a pop up error, " "Windows could not finishi confugraing the system, to attempr resume configuration, restart the computer.

 

[gamepwn]

Right.Who says though that ANY identifying information gets sent over the wire besides the client ID and ofcourse, the IP address ? There's a ton of crap that can be sent to identify a computer or OS installation, but does anything actually get sent?

 

[albeit512]

Correct me if i'm wrong. so basically when I change my client ID, every d3 client I run on same window user will have different client ID?

 

[johnwoo]

Correct me if i'm wrong. so basically when I change my client ID, every d3 client I run on same window user will have different client ID?

Yes and no. It appear 2 Unique Id in regestry, 1 for the account (client) and 1 other to identify the computer where the client is running, and also Buzzard verify on what IP you loggon.

If (account ID + Computer ID) or IP is not the data registred in Buzard database, it will ask you, your secret question, but if the account ID + Computer ID + IP is same as registred in Buzzard database, it's ok, and whatever the number of time you reinstall your Windows because, the registry saved have the same information for account id + computer Id and your IP is same before a fresh Windows installation.

If you connect with the same computer, you will have, X account ID on the same computer, but you dont have a fresh account ID + computer ID in your registry, it's really easy to Buzzard to flag all your account.

The account ID and computer ID are verified at loggon, to connected more then 1 account on the same computer, you must merge the Reg file of your other account after loggon the first, and repeat the manipulation each time you want loggon an other account.