Run PoE as a limited user

[bipolardefect]

yep, bat file dont even start

[hharrj123]

Why I cant use minimap??

[bizi123]

I also want to use this method but in another game, but when I open it it won't work, can someone help me?

my code : C:\Windows\System32\runas.exe /user:POE /savecred "cmd /C cd "D:\\Albion\\launcher\" && start AlbionLauncher"
and it gives the message that is " windowns cannot find albionlauncher "

[mayla]

how does this work in this point in time?

[Duke65er]

So like a couple people here, my cmdlet opens aswell, closes after some seconds. the game is launched in the background as my admin account, closes shortly after. Permission to the whole poe folder is granted, cfgs are fine aswell. logging into my standard account (limited user) without any admin rights, i can start the game and play. I also tried via psexec but sadly this methode also desnt work. would nice to hear some suggestions

[vladdj3]

Need help, if I choose to deny everything for the user, the command line shows access denied, as soon as I give access to the profile, it starts from another user

[aurelion44]

How is running poe as limited user and hiding the exileapi (or whatever) folder, stop poe from checking for open handles through NtQuerySystemInformation(SystemHandleInformation)?

[EthEth]

How is running poe as limited user and hiding the exileapi (or whatever) folder, stop poe from checking for open handles through NtQuerySystemInformation(SystemHandleInformation)?

Anti-cheat engines can use NtQuerySystemInformation(SystemHandleInformation) to enumerate all open handles in the system, regardless of user context. It includes: File handles, thread handles, registry handles, device handles. This call returns system-wide information, meaning it can show handles opened by any process, even those launched by another user, including admin users.

So even if:
The game is running under User B (restricted)
The cheat is running under User A (admin)
The cheat is located in a directory that User B can't access

The anti-cheat can still:
List open handles from all processes
See that some other process (even from another user context) has a handle to the game process or its memory
Flag suspicious behaviour (e.g., external tool with a handle to game memory)

So... yeah, if they upgrade they anti-cheat methods, we can be cooked.

Thank you for making me to stop, think and search for answers.