-
Member
Originally Posted by
Mojoguy01
[update]: Nevermind I figured it out. You have to add your limited security secondary account to the c:\programdata blizzard and bnet folders. Same thing for the AppData local and roaming Blizzard/Bnet folders. Works fine now
thanks for the tip! didnt think of programdata
-
Contributor
Originally Posted by
bobbydigital12
Can you list which folders you changed exactly? Which folders in AppData? The main account or secondary? Having the same problem as you had.
on win7 it is
C:\ProgramData\Blizzard Entertainment
C:\ProgramData\Battle.net
C:\Users\admin\AppData\Local\Battle.net
C:\Users\admin\AppData\Local\Blizzard Entertainment
C:\Users\admin\AppData\Roaming\Battle.net
admin is my "main" account that runs thud.
at least thats what worked for me now.
Last edited by prrovoss; 04-01-2017 at 04:43 PM.
-
Post Thanks / Like - 1 Thanks
bobbydigital12 (1 members gave Thanks to prrovoss for this useful post)
-
Member
Changing permissions didn't end up fixing the problem on Win10. Uninstalled battle.net, reinstalled battle app, uninstalled D3 from battle app, reinstalled D3 from battle app. And it now works.
-
-
Member
hello i have installed update 1703 (win 10) today but i get a black screen when running d3 with a secondary account but i have sound
and if i run it normal the game runs well
this is the target C:\Windows\System32\runas.exe /savecred /env /user:test "C:\Program Files (x86)\Diablo III\Diablo III.exe -32 -launch"
-
Active Member
Originally Posted by
yohudood
hello i have installed update 1703 (win 10) today but i get a black screen when running d3 with a secondary account but i have sound
and if i run it normal the game runs well
this is the target C:\Windows\System32\runas.exe /savecred /env /user:test "C:\Program Files (x86)\Diablo III\Diablo III.exe -32 -launch"
Use the TurboHUD Beta!
-
Member
How do I know that THUD's MEM cannot be read by D3 anymore? I followed to steps and D3 and THUD are running fine though.
-
Member
try to run task manager with new user credentials. There must be something about [Error opening process] in a line with restricted programms
-
Member
ok ill check it out. ty
Edit: Mmmh. Diablo is running on alt win10 account and THUD on "main" account. Though neither is listed as "restricted process"
edit2: Alt account (where D3 is running) has all permissions denied to THUD folder though.
Last edited by BaronNox; 04-14-2017 at 09:55 AM.
-
Member
As i know, limited users can not access processes, started by another users. Only administrators can do it. So if your new user isn't listed in an admin group, he can not access those processes
-
Member
das mit der Verküpfung ist bullshit
Lösung
1. Neues Textdokument erstellt.
2. Mit folgendem Inhalt füllen: runas /savecred /user:Benutzername@Domain "C:\Anwendung.exe"
Die Fett markierten Stellen müssen natürlich für den jeweiligen Benutzer/ die jeweilige Domain/ das jeweilige Programm geändert werden.
3. Die Endung des Textdokuments in .cmd umbenennen und ausführen.
4. 1 x Passwort für den Benutzernamen eingeben und dann nie wieder.
-
Member
Originally Posted by
annee
das mit der verküpfung ist bullshit
lösung
1. Neues textdokument erstellt.
2. Mit folgendem inhalt füllen: Runas /savecred /user:benutzername@domain "c:\anwendung.exe"
die fett markierten stellen müssen natürlich für den jeweiligen benutzer/ die jeweilige domain/ das jeweilige programm geändert werden.
3. Die endung des textdokuments in .cmd umbenennen und ausführen.
4. 1 x passwort für den benutzernamen eingeben und dann nie wieder.
прекрасно сказано, добавлю только одно замечание - в конструкции типа пользователь@домен доменное имя должно быть полным (fqdn), что в случае с домашним компьютером не актуально. А конструкция, доставшаяся со времён nt4 - домен\пользователь, оперирует netbios именем.
-
Contributor
Originally Posted by
annee
das mit der Verküpfung ist bullshit
Lösung
1. Neues Textdokument erstellt.
2. Mit folgendem Inhalt füllen: runas /savecred /user:Benutzername@Domain "C:\Anwendung.exe"
Die Fett markierten Stellen müssen natürlich für den jeweiligen Benutzer/ die jeweilige Domain/ das jeweilige Programm geändert werden.
3. Die Endung des Textdokuments in .cmd umbenennen und ausführen.
4. 1 x Passwort für den Benutzernamen eingeben und dann nie wieder.
nein, das ist kein bullshit. das funktioniert bei mir und vielen anderen wunderbar.
deine lösung ist halt nen alternativer weg. macht aber exakt dasselbe, über die console und einen eingeschränkten benutzer d3 zu starten.
Originally Posted by
Stasishe
As i know, limited users can not access processes, started by another users. Only administrators can do it. So if your new user isn't listed in an admin group, he can not access those processes
stop.
your new user who runs D3 mussn't be listed as admin.
that's exactly what you want to prevent in the first place - to run D3 with an windows account with admin rights.
the user who starts the shortcut has to be an administrator.
the idea is
user1: admin
user2: no admin
you are currently logged in to user1
user1 runs the shortcut - so D3 is launched by user2
Code:
runas.exe /savecred /user:user2 "C:\***\Battle.net.exe"
user1 runs THud (with admin rights) - because Hud needs to get all the info from memory
like this as you mentioned - D3 has no access to HUD process an cannot detect it this way.
greetz gjuz
-
Post Thanks / Like - 1 Thanks
Nerdygrim (1 members gave Thanks to gjuz for this useful post)
-
Member
!!!!!!!!
Something is wrong in the protection :
I m running D3 without lancher eg "runas .... c:\...\...\diablo III.exe -lanch"
and every time D3 is started by my user "toto" (with no admin rights) my main account launch agent.exe
because agent.exe is like a fck..g Trojan i m not sure that we are protected...
I m using the simple watchdog for JackCeparou i ll try to ask him if he can add a way to kill agent.exe when D3 an THUD are both started
hope this can help...
please tell me what you think about this things
-
Member
Originally Posted by
moiiom050579
I m running D3 without lancher eg "runas .... c:\...\...\diablo III.exe -lanch"
if u r running game directly, just delete this f*cking agent from hard disk. That shit need only to smooth update when new patch come to live.