Not run as admin

[ubeogesh]

I have noticed that if I modify this program to not run as admin (set "asInvoker" in manifest), it cannot attach to diablo 2 process. I've debugged it a bit and notice that Process::Modules call gets an "access denied" exception.

Have you looked into this, if there is a workaround for this? My game.exe is not running elevated (i.e. not as admin). Also tried turning off UAC Virtualization for it in the task manager, didn't help either.

[ubeogesh]

I found 1 way to make it work. After starting D2, I can use Process Explorer tool (ran as admin) on Game.exe to change permissions on the process and allow "Everyone" (or just my user or "Users" group) allow all access to the process. By default It is marked as "Deny" on all permissions.

I wonder if I can make Game.exe start with these permissions by default. Or is it possible that these permissions are set "from inside" the Game.exe to "prevent 3rd party programs from hooking into the game"?

[Zutatensuppe]

I remember having the access denied problem so we added admin requirements. Didn't look into this further in more detail unfortunately. Your workaround requires admin user as well, so maybe there is no real good way around it other than using admin power at some point.

It's beyond my knowledge if the permissions can be set in detail from outside. And all my D2 and D2 Interface etc runs in a VM currently, so stuff is always elevated and I can't really test it atm.

If you (or someone else) finds a way that doesn't involve admin power, it would be a great to know! =)