Running SbieCtrl as a different Windows user

If it's not about a problem in the program
Post Reply
Posts: 1
Joined: Thu Aug 10, 2017 4:44 am

Running SbieCtrl as a different Windows user

Post by Yyyyyy » Sat Aug 12, 2017 1:59 am


I'm trying to run a program with lesser privileges than my own Windows user account (which is member of Administrators). In general I believe I'm achieving my goals, however I am unable to control that user's sandboxes. In particular, running `runas /savecred /user:Test1 "C:\Program Files\Sandboxie\SbieCtrl.exe"`, nothing happens and I'm unable to control the sandboxes. I suspect this is due to the lesser privileges that the user account has, but adding further privileges would defeat the purpose of the setup.

Can you offer any advice on how to approach the problem?

Best regards, Yyyyyy

Sandboxie Support
Sandboxie Support
Posts: 2249
Joined: Mon Nov 07, 2016 3:10 pm

Re: Running SbieCtrl as a different Windows user

Post by Barb@Invincea » Mon Aug 14, 2017 11:43 am

Hello Yyyyyy,

Please have a look at the drop rights option:

Regarding runas, maybe this can help:


Sandboxie Guru
Sandboxie Guru
Posts: 620
Joined: Fri Nov 13, 2015 4:11 pm

Re: Running SbieCtrl as a different Windows user

Post by Syrinx » Mon Aug 14, 2017 1:59 pm

SBIECtrl should be able to see and manage all boxes if ran under the current user with exceptions being those set up explicitly to be applied to specific user names under Enabled=
By intentionally running it as a standard user from an admin account you are preventing it from being able to access and modify things such as the admin instance of explorer which handles the notification area/tray etc. If however you were to run as a standard user and run as admin, SBIECtrl would show up and function normally.
Simply put, I'd leave it the way it is and focus on running your non-security related software as a standard user instead.

On another note related to using runas and sbiectrl...It still has a bug
Let's say I'm running as an admin user called CURRENT
C:\Sandbox\%USER%\%SANDBOX% is set by default
When using runas a different username path is I use runas to launch calc under sandbox for TESTUSER
If you set a sandbox to delete upon close the wrong %user% path will used. It will pass CURRENT for the rmdir instead of the TESTUSER path.
So when using runas on sandboxed apps and wanting to set to delete, currently you must remove the %user% variable or it will not attempt to delete the correct path but thinks all went well.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests