Run Diablo3 process as another user

[ryanwilliams]

I'm attempting to run Diablo 3 as a non-administrative windows account and run demon buddy from my main windows account which is an administrator.

My thoughts behind this is the security built into windows would prevent Diablo 3 from getting a list of running processes and detecting the presence of demon buddy.

If you can modify demonbuddy to operate in this way, then perhaps you can create a "Launch Diablo 3" button
which can create a windows user account and run Diablo 3 using "runas".

[10:28:02.807 N] Demonbuddy v1.0.1206.288 started
[10:28:04.666 N] Logging in...
[10:28:06.435 N] Error attaching to Diablo III, Reason:System.Exception: Could not successfully set up_synchronization_events!
at Zeta.MemoryManagement.Executor.
()
at Zeta.MemoryManagement.Executor..ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

 

[Cheerbear]

I tried the same thing and ran into the same issue. I couldnt figure out how to do a "run as" on a differnt user for D3 andget DB to work, even if I ran DB as that same "differnt user"

 

[Tinnvec]

YAR has added support for this, but I've not tried it yet. You might check it out in the Plugins section and see if it'll help

 

[alex189]

Impersonate as another user to run a program - CodeProject

 

[ManBearPig]

I tried the same thing and ran into the same issue. I couldnt figure out how to do a "run as" on a differnt user for D3 andget DB to work, even if I ran DB as that same "differnt user"

I had the same problem at first, but after I bumped that user account to an admin level it worked fine for me. I was then able to successfully run DB and D3 as a different user. Win 7 Pro 64 bit if that helps.

 

[ryanwilliams]

The primary reason for running D3 as a non-administrative user is that non-administrative users are not permitted to view the names of processes being run as other users.

if (System.Diagnostics.Process.GetProcessesByName("demonbuddy").Length > 0)
// Ban