[HOW TO] Protect against Warden menu

User Tag List

Page 2 of 5 FirstFirst 12345 LastLast
Results 16 to 30 of 65
  1. #16
    Player821's Avatar Member
    Reputation
    3
    Join Date
    Apr 2017
    Posts
    2
    Thanks G/R
    1/2
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by Mojoguy01 View Post
    [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

    [HOW TO] Protect against Warden
  2. #17
    prrovoss's Avatar Contributor
    Reputation
    152
    Join Date
    Jan 2013
    Posts
    420
    Thanks G/R
    23/130
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by bobbydigital12 View Post
    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.

  3. Thanks bobbydigital12 (1 members gave Thanks to prrovoss for this useful post)
  4. #18
    bobbydigital12's Avatar Member
    Reputation
    2
    Join Date
    Mar 2017
    Posts
    13
    Thanks G/R
    59/1
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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.

  5. #19
    deadmarine's Avatar Contributor
    Reputation
    104
    Join Date
    Oct 2007
    Posts
    119
    Thanks G/R
    3/49
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Im usually pretty tech savy but for the life of me i cant get diablo to run under my new user account on windows 10. Any more help people could provide would be great.

    Things ive tried.
    *
    all the different shortcuts with the various permutations of the target
    *gave acess to the battle.net and diablo install dir
    *gave access to the appdata and programdata dir
    *reinstalled diablo

    EDIT:maybe an idiot can someone explain something to me about win 10 task manager.
    the user tab and details tab have different information which is accurate?
    Attached Thumbnails Attached Thumbnails [HOW TO] Protect against Warden-usertab-png   [HOW TO] Protect against Warden-details-tab-png  
    Last edited by deadmarine; 04-09-2017 at 09:12 PM. Reason: question

  6. #20
    yohudood's Avatar Member
    Reputation
    1
    Join Date
    Apr 2017
    Posts
    4
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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"

  7. #21
    bm206's Avatar Active Member
    Reputation
    73
    Join Date
    Mar 2017
    Posts
    285
    Thanks G/R
    57/64
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by yohudood View Post
    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!

  8. #22
    BaronNox's Avatar Member
    Reputation
    1
    Join Date
    Apr 2017
    Posts
    3
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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.

  9. #23
    Stasishe's Avatar Member
    Reputation
    1
    Join Date
    Mar 2017
    Posts
    21
    Thanks G/R
    7/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    try to run task manager with new user credentials. There must be something about [Error opening process] in a line with restricted programms

  10. #24
    BaronNox's Avatar Member
    Reputation
    1
    Join Date
    Apr 2017
    Posts
    3
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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.

  11. #25
    Stasishe's Avatar Member
    Reputation
    1
    Join Date
    Mar 2017
    Posts
    21
    Thanks G/R
    7/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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

  12. #26
    annee's Avatar Member
    Reputation
    1
    Join Date
    Apr 2017
    Posts
    1
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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.

  13. #27
    Stasishe's Avatar Member
    Reputation
    1
    Join Date
    Mar 2017
    Posts
    21
    Thanks G/R
    7/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by annee View Post
    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 именем.

  14. #28
    gjuz's Avatar Contributor
    Reputation
    121
    Join Date
    Mar 2017
    Posts
    228
    Thanks G/R
    49/118
    Trade Feedback
    0 (0%)
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by annee View Post
    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 View Post
    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

  15. Thanks Nerdygrim (1 members gave Thanks to gjuz for this useful post)
  16. #29
    moiiom050579's Avatar Member
    Reputation
    1
    Join Date
    Mar 2017
    Posts
    11
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    !!!!!!!!
    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

  17. #30
    Stasishe's Avatar Member
    Reputation
    1
    Join Date
    Mar 2017
    Posts
    21
    Thanks G/R
    7/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by moiiom050579 View Post
    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.

Page 2 of 5 FirstFirst 12345 LastLast

Similar Threads

  1. Replies: 12
    Last Post: 10-21-2016, 07:42 AM
  2. How can I find warden-like code on a non-WoW or non-blizz game?
    By popinman322 in forum WoW Bots Questions & Requests
    Replies: 0
    Last Post: 10-02-2010, 12:59 PM
  3. how to fight against chargebacks?
    By colm in forum WoW Scams Help
    Replies: 6
    Last Post: 12-27-2008, 01:45 PM
  4. [Bug/Exploit] How to walk against a mountain/wall.
    By TheBluePanda in forum Age of Conan Exploits|Hacks
    Replies: 5
    Last Post: 07-03-2008, 10:00 AM
  5. Protect PiroX AFKBot against Warden
    By LuBu in forum World of Warcraft Bots and Programs
    Replies: 14
    Last Post: 04-12-2008, 07:56 AM
All times are GMT -5. The time now is 04:58 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search