SBIE2204 Cannot start sandboxed service RpcSs (-1)

[Craig@Invincea]

Yes, If you can relaunch the program that caused the -1 issue immediately to see if it repeats. Chances are it may not. It's "race" issue within Win 8. Happens more in W10.

I'd also recommend you get 8.1....and yes, please try the v5.01.12 Beta.

[BishopJ]

Yes, If you can relaunch the program that caused the -1 issue immediately to see if it repeats. Chances are it may not. It's "race" issue within Win 8. Happens more in W10.

I'd also recommend you get 8.1....and yes, please try the v5.01.12 Beta.

Well I'm now on Win8.1 with SB v5.01.12 but unfortunately the problem remains, although it has changed very slightly. Now when I try to run Opera or Firefox Sandboxed the initial message is "Sandboxie RpcSc — Could not instrument service functions".
I'm still not sure quite what you mean when you say "relaunch" (or "'race' issue" for that matter). The initial attempt to open a Sandboxed browser produces the message above and generates much machine activity (as described in earlier post) and then the looping SBIE2204 message but no browser. Trying to launch a Sandboxed browser again – the same one or a different one – while the looping is going on seems to be ignored totally. Stopping the looping (with Task Manager) then opening the browser again just starts the fail process over again...

[Craig@Invincea]

Yes, If you can relaunch the program that caused the -1 issue immediately to see if it repeats. Chances are it may not. It's "race" issue within Win 8. Happens more in W10.

I'd also recommend you get 8.1....and yes, please try the v5.01.12 Beta.

Well I'm now on Win8.1 with SB v5.01.12 but unfortunately the problem remains, although it has changed very slightly. Now when I try to run Opera or Firefox Sandboxed the initial message is "Sandboxie RpcSc — Could not instrument service functions".
I'm still not sure quite what you mean when you say "relaunch" (or "'race' issue" for that matter). The initial attempt to open a Sandboxed browser produces the message above and generates much machine activity (as described in earlier post) and then the looping SBIE2204 message but no browser. Trying to launch a Sandboxed browser again – the same one or a different one – while the looping is going on seems to be ignored totally. Stopping the looping (with Task Manager) then opening the browser again just starts the fail process over again...

Yes, when it crashes, it will spool up resources. And yes, this can occur in Win 8.1 as parallel task assignment for cores was there, but not as stringent in 10. Are you on a multicore machine? probably so..as they are pretty standard. This is the root cause of it and how Windows loads and what SBIE expects to be loading. In testing, in a VM running one core and 1 processor. It never happens.

Relaunching, as your are viewing program in SBIE control crash. they will disappear from the list. Once they do, try and relaunch that same program. In testing, since the time is ever so slightly different each time, it usually loads up and works. This isn't a fix, but a work around for now as this error goes back to the very beginning of SBIE.

[BishopJ]

Hello again
"Are you on a multicore machine? probably so..as they are pretty standard."
I've looked up 'multicore' and can confirm the AMD A10 is a quad core processor, apparently.
"Relaunching, as your are viewing program in SBIE control crash. they will disappear from the list. Once they do, try and relaunch that same program."
I've no wish to be a nuisance but I'm afraid I still don't understand what you are saying. (This may be a US English < > English English issue, or a guru < > technical ignoramus issue, or both, and I apologise.) But may I beg your patience and ask you to detail, ideally click by click and in non-tech-speak, what it is you are suggesting I do.
I try to open a Sandboxed browser from a task bar icon ("Sandboxed Web Browser") or from the browser's own desktop icon (right click option "Run Sandboxed"). Currently this produces first the message box headed "Sandboxie RpcSs" saying "Could not instrument service functions", then the larger box headed "Messages from Sandboxie" containing the repeating SBIE2204 message and sometimes first a SBIE2303 message. Neither message box offers functional options. Nothing else opens (nor does the browser) and as mentioned the only way I have found to stop it all is through the Windows task manager. I cannot match this sequence with what you have written.
Still interested to know why this all suddenly started happening...
Thanks some more.

[Craig@Invincea]

Hello again
"Are you on a multicore machine? probably so..as they are pretty standard."
I've looked up 'multicore' and can confirm the AMD A10 is a quad core processor, apparently.
"Relaunching, as your are viewing program in SBIE control crash. they will disappear from the list. Once they do, try and relaunch that same program."
I've no wish to be a nuisance but I'm afraid I still don't understand what you are saying. (This may be a US English < > English English issue, or a guru < > technical ignoramus issue, or both, and I apologise.) But may I beg your patience and ask you to detail, ideally click by click and in non-tech-speak, what it is you are suggesting I do.
I try to open a Sandboxed browser from a task bar icon ("Sandboxed Web Browser") or from the browser's own desktop icon (right click option "Run Sandboxed"). Currently this produces first the message box headed "Sandboxie RpcSs" saying "Could not instrument service functions", then the larger box headed "Messages from Sandboxie" containing the repeating SBIE2204 message and sometimes first a SBIE2303 message. Neither message box offers functional options. Nothing else opens (nor does the browser) and as mentioned the only way I have found to stop it all is through the Windows task manager. I cannot match this sequence with what you have written.
Still interested to know why this all suddenly started happening...
Thanks some more.

It's always been possible for this to happen in 8.1 (and 8.0) however, it really showed up in Win 10. The fixes in the v5 Beta address Windows 10..and thus, it may trigger more -1 related issues in other OS versions. The Devs are working on more and more details of this. So please stay up on our beta releases.

To see program view is SBIE, Double click on your SBIE icon to open SBIE Control, View>Programs and you can see it there in real time.

You can also revert back to the stable v4.20 release. It may work better for you.

[BishopJ]

Once more...
I have reverted to v4.20 and now know how to view programs in real time — however, the 2303/2204 problem remains. Programs do not "disappear from the list": SandboxieRpcSs.exe keeps running and seems to stop anything else. Terminating it just restarts the fail process as before, absolutely every time...
This may have been something that might occur before but it never did to me in years of use. And now a whole bunch of users — it seems likely that the thread below "Re: reocurring Errors 2303 & 2204" relates to the same problem — suddenly all have the same issue at the same time. Maybe AVG security is a common feature (not something we would wish to disable just to be able to use SBIE); maybe an update to Win8 that is mirrored in Win10...
I'm giving up now. Perhaps you'll let us know when your guys have worked out what to do.

[Craig@Invincea]

Once more...
I have reverted to v4.20 and now know how to view programs in real time — however, the 2303/2204 problem remains. Programs do not "disappear from the list": SandboxieRpcSs.exe keeps running and seems to stop anything else. Terminating it just restarts the fail process as before, absolutely every time...
This may have been something that might occur before but it never did to me in years of use. And now a whole bunch of users — it seems likely that the thread below "Re: reocurring Errors 2303 & 2204" relates to the same problem — suddenly all have the same issue at the same time. Maybe AVG security is a common feature (not something we would wish to disable just to be able to use SBIE); maybe an update to Win8 that is mirrored in Win10...
I'm giving up now. Perhaps you'll let us know when your guys have worked out what to do.

First point, v5 is a beta product. Errors are expected in a beta environment.

SandboxieRpcSs.exe is required for SBIE to work. It's a timing / race loading issue. Which directly relates to SandboxieRpcSs.exe and what it expects. The issue has always been present. It was magnified by Win10. Win10 introduced a lot of new ways on how things are assigned and processed in parallel per core. It's not just "and upgrade" from 8.1. It's far more than that.

This existed in 8.1. Just not as much. It was limited. However, 10 made it main stream. Tweaking the code in SBIE awoken it in 8.1. This was to be expected. The Devs are fully aware and stated this was something to be expected. Multiple releases have addressed it better and better. In our in house automated torture tests in happens very rarely (once in almost a 1000) and given the 10s of thousands of SBIE users, we're confident those stats are valid and representative.

AVG doesn't have anything directly to do with this error. But it's a program that loads, and could contribute to the racing problem

And we have let you know (the forum) . It's addressed in my posts regarding this (like my post to you) and in Curt's change log on what we are doing. Reason 4.2 works for you? It doesn't have to support Win 10 nor does it have all the coding to do that. This problem manifested from Win 10.

[Dun]

I almost forgot about this error. Happened once for last few days. I use latest beta

[BishopJ]

Once more...
I have reverted to v4.20 and now know how to view programs in real time — however, the 2303/2204 problem remains. Programs do not "disappear from the list": SandboxieRpcSs.exe keeps running and seems to stop anything else. Terminating it just restarts the fail process as before, absolutely every time...
This may have been something that might occur before but it never did to me in years of use. And now a whole bunch of users — it seems likely that the thread below "Re: reocurring Errors 2303 & 2204" relates to the same problem — suddenly all have the same issue at the same time. Maybe AVG security is a common feature (not something we would wish to disable just to be able to use SBIE); maybe an update to Win8 that is mirrored in Win10...
I'm giving up now. Perhaps you'll let us know when your guys have worked out what to do.

First point, v5 is a beta product. Errors are expected in a beta environment.

SandboxieRpcSs.exe is required for SBIE to work. It's a timing / race loading issue. Which directly relates to SandboxieRpcSs.exe and what it expects. The issue has always been present. It was magnified by Win10. Win10 introduced a lot of new ways on how things are assigned and processed in parallel per core. It's not just "and upgrade" from 8.1. It's far more than that.

This existed in 8.1. Just not as much. It was limited. However, 10 made it main stream. Tweaking the code in SBIE awoken it in 8.1. This was to be expected. The Devs are fully aware and stated this was something to be expected. Multiple releases have addressed it better and better. In our in house automated torture tests in happens very rarely (once in almost a 1000) and given the 10s of thousands of SBIE users, we're confident those stats are valid and representative.

AVG doesn't have anything directly to do with this error. But it's a program that loads, and could contribute to the racing problem

And we have let you know (the forum) . It's addressed in my posts regarding this (like my post to you) and in Curt's change log on what we are doing. Reason 4.2 works for you? It doesn't have to support Win 10 nor does it have all the coding to do that. This problem manifested from Win 10.

I'm sorry if I have antagonised you. We seem to be somewhat at cross-purposes. I have been persistent because the various responses do not quite answer the questions raised or I cannot understand them. I accept that I have an unlucky combination of machine and software. I accept that AVG is a separate issue.

To recapitulate in the hope it will help you and the developers:

I have used SBIE for years without this problem. It started happening while I was on Win 8.0 (since Jan 2014) and SBIE v4.20 (since its release). However that combination had worked without problems until roughy mid-August. It is not clear what happened then to cause the problem to start.

It continued happening after moving to Win 8.1 (as suggested by you). I have never been on Win10.

The problem continued with SBIE v5.01.12. Having reverted to v4.2 (as suggested by you) the problem continues.

Programs do not disappear from the live view (I have tried leaving it for more than an hour) in either v4.2 or 5.01.12. SBIE just seems to be stuck in a loop.

"Perhaps you'll let us know when your guys have worked out what to do." By this I meant that, being unable currently to use SBIE, I look forward to notifications that Sandboxie think further beta tweaks may have corrected the problem.

[uri]

Same problem happened to me too.
My settings: Windows 10.0.10240, Sandboxie 5.01.13 (64 bit), AVG Free 2015.

Disabling the AVG whole together solved the problem. But this is not wanted as was stated before.
So instead of doing that I added an exception on the sandboxie folder in the avg advanced settings, and then everything seemed to be working right.

[BishopJ]

Same problem happened to me too.
My settings: Windows 10.0.10240, Sandboxie 5.01.13 (64 bit), AVG Free 2015.

Disabling the AVG whole together solved the problem. But this is not wanted as was stated before.

So instead of doing that I added an exception on the sandboxie folder in the avg advanced settings, and then everything seemed to be working right.

Yes indeed! That does seem to work — though I am in no way technical enough to know if this solution has any other implications, esp. re security. Thank you very much!