Just so i get it when i open Task Manager/Details it shows diablo 3 on my other User name and HUD on Main is that right ?
Just so i get it when i open Task Manager/Details it shows diablo 3 on my other User name and HUD on Main is that right ?
Could someone help me with this..
I Have a admin account ''ADMIN'' and a non admin account '' PROVOSS1''
I make a shortcut of the Battle .net launcher .exe and put there beforeon the non admin account. Also I on the security tab I add the user PROVOSS1.Code:runas /user:PROVOSS1 /savecred
It should like this:
Code:C:\Windows\System32\runas.exe /user:PROVOSS1 /savecred "G:\Program Files (x86)\Battle.net\Battle.net Launcher.exe"
After that,If i run the shortcut what is modifyd on the desktop, It brings a popup screen with put your password.
What i'm doing wrong?
EDIT: Using A - Methode
Last edited by Hot12345; 06-02-2017 at 06:00 AM.
which password you give your non admin account? just simple type it in...
and please read in first posting - C) Troubleshooting
Methode A
Okay I give my test account password test. It runs on the admin account.
Where do I need to run it? On the test account (nonadmin) or on the admin account.. Im confused right now,
If I run it on the Admin account it runs on the admin account, and if I switch it doesnt startup there.
And If I run the shortcut on the test account it runst on the test account.
Also If I run this on a admin account and press play in the launcher it starts diablo 3 on the admin account instead on the test account...
I dont get it, how to run then Turbohud on the test account? I blocked the dirrecotry in the security tab..as is shown in info.
Could someone help me with this one.
Last edited by Hot12345; 06-02-2017 at 06:21 AM.
You start the shortcut from admin account. The runas command will run D3 through your restricted account.
Turbohud does not work anymore if I run d3 under another account
did you start 32-bit game client?
played yesterday, works fine for me - starting TH from main account, starting game directly ("D:\Games\Diablo III\Diablo III.exe" -launch) with limited user.
PS Try this - ShellRunas
Last edited by Stasishe; 07-24-2017 at 10:14 AM. Reason: added link
Hey, quick question: is it possible to directly start the diablo 3 64 bit client through another user? No matter what I try, the game is always starts in the 32 bit client for me
quick answer:
%SYSTEMDIR%\runas.exe /user:<another_username> /savecred "D:\Games\Diablo III\x64\Diablo III64.exe" -launch
but for WHAT? TurboHud didn't work with 64-bit client, and i can't imagine case in which you need another user without TH.
Hey Guys. I used THUD last time in season6 and now i want to use it again with this kind of protection but i feel abit helpless. I did the shortcut thing the shortcut's target is: C:\Windows\System32\runas.exe /user:User /savecred "C:\Spiele\Diablo3\Diablo III\Diablo III\Diablo III Launcher.exe" i rlly hope thius is correct i just added: C:\Windows\System32\runas.exe /user:User /savecred so far so good.. its starting the battlenetlauncher. i start diablo.. start THud (already denied access for the standard Windows user) 1. I dont get a cmd windows where i have to enter the password.. but its fine because the shortcut is starting the client, right? 2. When i look at the taskmanager THud is still used by Admin..
PS: Sorry for my bad english
Found another problem that may be confusing other people.
Running the command in a prompt terminal results in a new error that i was not awared of:
RUNAS ERROR: Unable to run - C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe -launch
1327: Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced.
So, you need to create a password to the secondary account
Use it as admin, dont try to cover anything, works fine, have 10k+ hours without doing your stuff, and none of my account are banned yet.
gentoo linux @ wine
Warden is BS, and blizzard dont ban people who use it what so ever, and have never done that.
Only botters = non legit people, like i allways hack there account and delete everything they ever found + change the account (even if you got authenticator or not) we know what we do.
To KJ keep up the good job, ill donate when i come back home.
So i just got a new computer, and i simple cant get it to work now. The new PC is Win10 (old was Win8.1)
This is what i have done, hopeful somebody can help me out:
- Enabled Secondary Login Service
- Created a new standard user with password (and tryed without - yes entered the password in the cmd promt as "hidden letters"
- Logged into the account, logged off and logged back to admin account.
- Gave the standard user full access to battle.net, diablo folder and documents folder (C - User - Documents)
- Tryed the ShellRunas (works with the Diablo III.exe -launch)
- Tryed the shorcut both to Diablo III.exe and Diablo 3 Launcher.exe
- Tryed the shortcut with: C:\WINDOWS\System32\runas.exe /user:COMPUTERNAME\USERNAME /savecred /env
- Tryed to remove the "write-protected" on battle.net and diablo 3 folder
- Tryed shortcut with "runas /user:PROVOSS1 /savecred" - "runas /savecred /user:PROVOSS1" - "runas /savecred /env /user:PROVOSS1"
- Tryed to create new standard user and a new admin user
- Tryed to start the shorcut as admin
- Tryed to reinstall the battle.net app
I can see the "Battle.net.exe - Agent.exe - conhost.exe" is running in the task manager as the other user - but the battlenet never popups. Also "Blizzard battle.net app - Blizzard Update Agent" is running.
So guys, what am i doing wrong here ? Anyone who can help me out here ?
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...