Page 1 of 1
Posted: Thu Mar 08, 2018 7:02 am
I once thought /nosbiectrl could prevent SbieCtrl.exe from running. But it couldn't.
/nosbiectrl can be used to make sure Start.exe does not try to run Sandboxie Control before running the sandboxed program.
But actually I see SbieCtrl.exe run always before the sandboxed program.
So in what scenarios (for what purpose) should we use this parameter?
Posted: Thu Mar 08, 2018 2:15 pm
Hello sbf ,
You would use that command after having used these settings:
If you uncheck "When a sandboxed program starts" , and Sbie control is closed, you can then invoke apps using the /nosbiectrl command.
PS: Since sbiectrl.exe will not be running, you will not see the frame around the program's window. To check that the app is sandboxed, see Task Manager and find the user running the process. Sanboxed processes are run by AnonymousLogon.
To triple check, after running the app you can invoke sbie control and you will see it listed there as well.
Posted: Fri Mar 09, 2018 1:16 pm
Thank you, Barb. You are so kind.
But the fact makes me even puzzled.
While that option is checked, SbieCtrl.exe always starts along. /nosbiectrl never works.
While that option is unchecked, SbieCtrl.exe never starts along. Unless I run it. /nosbiectrl is never needed.
So what's the exact use of /nosbiectrl ?
Re:PS: Yes, no frame... This is not good. (Though I don't worry about the processes since I'm running ProcessHacker, which has trees and highlights.)