Repository navigation
Does SBIE2204 RpcSs or DcomLaunch affect sandbox integrity? #5687
Replies: 1 comment
|
This failure does not disable sandbox isolation or automatically allow unrestricted RPC calls to the host. Connections that normally use the sandboxed services still target the sandbox’s endpoints. If those endpoints are unavailable, the affected operations can fail or wait. The application itself can continue running because helper startup is normally asynchronous. Host RPC access already permitted by the sandbox’s configuration remains separate. There is no single application-facing error code for SBIE2204. Sandboxie returns the underlying connection status for the affected call. A missing endpoint can produce The code in parentheses after SBIE2204 is a separate startup diagnostic: it can identify a launch error, a helper’s exit status, or an internal readiness-wait condition. In particular, |
Uh oh!
There was an error while loading. Please reload this page.
When starting a sandboxed program, I occasionally get a
SBIE2204error:Cannot start sandboxed service RpcSsorCannot start sandboxed service DcomLaunch. There is no clear impact on the program; it still starts in the sandbox. I know the docs say those services are "sometimes" used for sandboxed programs to improve compatibility. So if the services fail to start, what does that mean for the program and sandbox?Like, does it mean the sandboxed program can make unrestricted RPC calls beyond the sandbox since they aren't being intercepted? Or does it mean those RPC calls automatically fail, because there is no service to properly forward them?
All reactions