Hi, are these steps still necessary to run Turbohud against Warden?
Hi, are these steps still necessary to run Turbohud against Warden?
Hi all,
I've recently bought a new computer and I remember having performed these steps in the past to get Diablo 3 to load without using the launcher in Windows 10. However, I cannot for the life of me get this to work now. So far I can only make it work with the launcher.
Steps performed so far:
- Secondary Login Service set to "Automatic"
- Standard user account created with password
- I have completely removed all Blizzard games and content and power cycled my computer.
- Clean installation of Battle.net desktop app (Secondary Standard user given Full Control of this folder)
- Clean installation of Diablo 3. (Secondary Standard user given Full Control of this folder)
- Secondary Standard User given Full Control of these folders:
C:\ProgramData\Blizzard Entertainment
C:\ProgramData\Battle.net
C:\Users\<myaccount>\AppData\Local\Battle.net
C:\Users\<myaccount>\AppData\Local\Blizzard Entertainment
C:\Users\<myaccount>\AppData\Roaming\Battle.net
C:\Users\<myaccount>\Documents\Diablo III
- Steps in Section A-3 Performed
- Opening with launcher shortcut works and will bring me to the battlenet login screen. Here is the target:
C:\Windows\System32\runas.exe /savecred /env /user:<standarduser> "C:\Games\Diablo III\Diablo III Launcher.exe"
- I was prompted to enter the user password in a command prompt
- I can see in Task Manager that agent.exe is running under secondary user
- Opening without the launcher I notied the command prompt flashed very briefly but I was unable to input user credentials. Here is the target:
C:\Windows\System32\runas.exe /savecred /env /user:<standarduser> "C:\Games\Diablo III\Diablo III.exe" -launch
- Shift-Rightclick Diablo III executable
- Run as a different user
- loads battlenet launcher login page and not the login via the actual game.
What am I doing wrong?
Be sure you are using right version of game, as THud work only with 64-bit version. First of all, recommend to you to give admin rights to secondary user to test is it based on lack of rights. Also try to manually run from command prompt to see what is "flashing" in a line when you start game with "-launch"