-
Member
Originally Posted by
rossbacher
sorry for my bad english
ive run the 32bit version wit the follow comand line:
C:\Windows\system32\runas.exe /user:XXX /savecred /env"D:\Diablo III\Diablo III.exe -launch" and its works with the turbohud 32 bit version.
witch changes must be donbe to work it on 64 bit?
ive use the tutorial form the beginnig from the thread...
This is your new command line: (Change drive letters as needed)
C:\Windows\System32\runas.exe /user:XXX /savecred /env "C:\Games\Diablo III\x64\Diablo III64.exe -launch"
-
Post Thanks / Like - 1 Thanks
rossbacher (1 members gave Thanks to Dweeb1 for this useful post)
-
Member
thx^^ lol im stupid^^ i ve try hte same with a little dumb error....
.... Diablo III\x64\Diablo III64.exe" -launch
shame on me^^
thx alot
-
Banned
Does a topic like this, even really need to be made?
Blizzard has about a half dozen other ways to locate people using 3rd party programs, bots, and other cheats, and most likely do not even need Warden.
All 3rd party programs/apps not authorized by blizzard, are against the code of conduct, Blizzard is also fully aware of who is using what (Thinking they don't is naive), So If Blizzard wants to ban people for using 3rd party programs, they will, if they don't, then they won't there is no in between. Furthermore, Blizzard can made a program ok for one person to use and then not ok for others, Blizzard can even just shut the game down just because they can, in fact, Blizzard can do whatever they like, and there isn't a single thing anyone of us can do about it.
Last edited by TL gamer; 05-30-2018 at 09:57 PM.
-
Member
ok I've setup all this and can get into the game but im not seeing any overlay was i meant to go into the THUD folder and make it so the other user can only open the THUD launcher or the whole folder was the right thing and its just broken?
-
Member
There was an update of battle net this morning. I can no longer start battle net as /runas with a limited user. It asks for credentials then it fails.
-
Member
This tutorial doesn't work.
TurboHUD is now 64bit, i have a windows 7 64bit system with all the latest updates and sp, i run diablo 3 in 64bit mode, i followed the steps exactly, when i run the customised shortcut i see a cmd prompt window for about a split second and nothing else happens.
Trying to launch the turbohud exe does nothing, and launching the turbohud manager brings up some window that looks like a screenshot with an empty stash and tabs.
-
Member
Diablo III launcher.exe does not exist anymore after the new patch. There is Diablo III.exe, Diablo IIIp.exe and Diablo IIIra.exe
So how we do the step A now ?
Thanks.
EDIT : After the last fix the file is here again.
Solved.
Last edited by Guigui92i; 09-25-2019 at 09:11 AM.
-
Member
Hi there KillerJohn
think this steps need some update. win 10 dosent work at all as this steps show. (more or less alot of it works but the game dosent launch) if you where to launch the game from the new account but restrict the access to the folders where thud is located, that way seams to work... but you are not able to start the game from the main accaount (well i dont know maybe we all can but i havent got it to work)
-
Contributor
Originally Posted by
M4D_MAGIC
Hi there KillerJohn
think this steps need some update. win 10 dosent work at all as this steps show. (more or less alot of it works but the game dosent launch) if you where to launch the game from the new account but restrict the access to the folders where thud is located, that way seams to work... but you are not able to start the game from the main accaount (well i dont know maybe we all can but i havent got it to work)
It works as intended. You just have to set it up correctly. Requires some knowledge to do it properly. But is is not rocket science for those that are willing to learn.
You can start for example google "How can I run Diablo 3 without an administrator account".
But I don't see any reason why would you want to do it!
-
Member
Hi there,
I'm under Windows 10. No problem to launch battle.net and then diablo itself, appearing as diabloIII64.exe, process owned by the alternate account. Working perfectly. But when I run TurboHUD under the main account, THUD just iddles on the "launching turbo hud, please wait" small black window, as if it was not finding Diablo... The THUD process seems to be blocked, using a lot of CPU.
Does someone have an idea of what I'm doing wrong ? I denied any access to THUD directory for the alternate account.
Note that the whole thing is working perfectly when i'm running everything under the main account.
I wonder how THUD manage to find Diablo : does it list the processes on the PC ?
-
Member
Do you run THUD as admin? Do you have exception in antivirus?
-
Post Thanks / Like - 1 Thanks
juliebis (1 members gave Thanks to MlokCZ for this useful post)
-
Member
Originally Posted by
MlokCZ
Do you run THUD as admin? Do you have exception in antivirus?
I forgot admin on HUD ! Thx man. It's working now.
-
Member
Hi,
Please could you give me an advice should I do it all those things with create new windows user etc. in 2020, I'm using windows 8.1, or meybe now in season 20 and new thud i just need to install normaly on my admin account without worries and play with thud.
Thanks for advice
-
Active Member
It's only another layer to protect your account so you have to decide yourself.
I don't play much for a while now but never did it this way and still own my original account.
-
Member
Hi Guys,
I download the newest version of Turbohud but its not working. My bad my english is not so good and I dont understand all parts what to do. Iam from germany.
My diablo client says: Cant read D3 memory. Please use a compatible D3 client and run TurboHud as administrator.
I hope someone can help me pls.