Anyone solved how to run 2 Diablo rotw games on a single machine

Hi, has anyone solved how to run 2 games in rotw on a single machine. Process Explorer doesn't show the check process anymore

Cheers, Halldor

Process explorer works perfectly fine for me

Im running 2 d2r warlock dlc on my computer when i need to rush or xfer high profile items

U must do the following:

Do not use the battle.net app launcher
- go to the d2r resurrected folder, make an exact copy of the folder, pasted within that same directory in which your d2r rez resides, the new copied folder(call it d2r res copy, or leave it default copied naming)

- in the original d2r folder, make a shortcut of the d2r resurrected. exe file(rename it main if u want)
- in the 2nd d2r copied folder, make a shortcut of that same . exe and call it whatever, as long as its unique.


Run the first .exe > log into ur 1st acct, get to main char selection screen > closed your d2 launcher(dont close your game, just the launcher), run ur process.exe in admin mode > type d2r > sort by naming > find d2 process event as “event”, end the process

Now launch secondary .exe , if all done correctly, your new secondary game launcher will update automatically and will allow u to click play again. Once u launch the 2nd game > goes into char selection screen, u can close the 2nd launcher

Ive been doing this for over 2 yrs now, even with warlock dlc, i have no issue launching 2 d2r rez instances with the above methods

Anyhow, good luck, hope it works out for u

I can add to that that I'm successfuly running mixed double instances of rotw and expansion with process explorer.

Didn't want to pay double, kept most of my trash on old account and transfer whenever i need.

Kakumba wrote: 6 months ago

I use the script from shupershuff https://github.com/shupershuff/Diablo2RLoader

Works well for me, just read and follow the instructinos carefully, get the auth token

Just read over the page and thanks for sharing!

I have always been meh about the process killing method. Will look into this.

Thanks, found the event and killed it. It works. There was a change either between my computers or Process apps. Again, thanks alot.