Can't start Sandboxie (SBIE2204)

[dnaman]

(Probably not a new issue but this doesn't involve Win-10)

Windows 8.1 (64-bit)
Sandboxie V4.2 (64-bit)
Firefox ESR 31.8.0
AVG Free 2015.0.6125

When I try to start the Sandboxed Web Browser, it fails with the message "SBIE2204 Cannot start sandboxed service RpcSs (-1)".

While I can find references to this message on the website, I cac only see explanations as to what it means but no indication as to how to fix it.

[Craig@Invincea]

(Probably not a new issue but this doesn't involve Win-10)

Windows 8.1 (64-bit)
Sandboxie V4.2 (64-bit)
Firefox ESR 31.8.0
AVG Free 2015.0.6125

When I try to start the Sandboxed Web Browser, it fails with the message "SBIE2204 Cannot start sandboxed service RpcSs (-1)".

While I can find references to this message on the website, I cac only see explanations as to what it means but no indication as to how to fix it.

Yes, it actually is related to the Win 10 issue, The race condition started to show up in 8.1. While Microsoft then really tweaked and enforced it in 10. It's much more rare condition in 8.1. There isn't a permanent fix at this time. It's been addressed since .11 Beta.

Fixes in 5.01.12
1) More fine tuning of service start to fix rare race condition that leads to SBIE2303 Could not hook PowerSettingRegisterNotification (1). SBIE 2204 Cannot start sandboxed service RpcSs (-1) cycling every 30 seconds.

Fixes in 5.01.11
1) Service start timing changes to fix rare race condition that leads to SBIE2303 Could not hook PowerSettingRegisterNotification (1). SBIE 2204 Cannot start sandboxed service RpcSs (-1) cycling every 30 seconds. This bug is machine dependent.

[BishopJ]

You are not alone: several other users (including me) seem to be encountering this problem in the last few weeks — no explanation as to why it started happening when it did. The newer beta versions do not seem to address the problem.
In some cases disabling AVG seems to allow SBIE to work properly. Though having to choose between the two safety measures is hardly a fix...!

[Craig@Invincea]

You are not alone: several other users (including me) seem to be encountering this problem in the last few weeks — no explanation as to why it started happening when it did. The newer beta versions do not seem to address the problem.
In some cases disabling AVG seems to allow SBIE to work properly. Though having to choose between the two safety measures is hardly a fix...!

Not correct & false. All of our change logs state we've been tweaking the beta as related to this exact issue. And we've run in house torture tests that run examples hundreds and hundreds of time very quickly, It's exceeding getting more rare.

Yes, All of our releases have attempted to correct the problem and we've been told that it may cause it to happen more and more in other places until it's solved 100%. 8.1 uses the same race condition to a much lower extent as Win 10. Win 10 just uses much much more. But it was always present in 8.1. Now that we are addressing it and tweaking the code, its popping up. It doesn't have direct relation to AVG, only on how programs race to load. So disabling something may get you a head. And if the timing ends up being such, you get the error. Parallel instructions on each core as Windows assigns the tasks. SBIE is a mono-processor program (how it was originally written.)

If you get this issue, and if the program does crash...you can watch it in program view of SBIE. Once it clears out (race works both ways) try it again, most times you're then ok.

We've never said disabling AVG was a fix. And not related to this error........ But antivirus and SBIE is entirely another issue. As for explanation, I've posted several, if not dozens of responses regarding this very error and what you can try. It's also listed in the change log that it's also very machine dependent. You'll see it fewer in a dual core vs a quad core and it's non-existent issue in single core units.

[dnaman]

Thanks for the response, Craig.

I installed beta 5.01.13 but it hasn't changed anything. As far as:

".....you can watch it in program view of SBIE. Once it clears out (race works both ways) try it again, most times you're then ok"

goes, I've just been sitting here for 10 minutes and it hasn't cleared out yet. Moreover the message window forces itself on top of other windows so even doing something else in the meantime is problematic. I don't see this as a realistic workaround (for me).

[Sajon184]

I have Windows 8.1 and get the same error message, as well as SBIE 2303. This started a month ago for no reason that I know of. I get windows updates regularly so that must have been the cause. I also updated my AVG, but Craig says that is not the problem. However, I cannot understand what Craig is saying is the problem since I am not a technical person. I therefore do not how to fix it. I am willing to buy the home version, but it seems that does not get any technical support. I tried uninstalling and deleting the contents but that was unsuccessful. If anyone knows what to do, or whether there will be an updated version of the download to correct the problem, please let me know. As I write this, the error messages keep coming.

[dnaman]

I am willing to buy the home version, but it seems that does not get any technical support.

Well, the support I believe is in this forum and you get it, I guess, for both paid and trial versions. Right now though, it doesn't seem that buying the product will make any difference to the problem. I have a paid, personal licence but the program at this time is unusable. I just have to hope and believe that the problem is being worked on with some priority and that a definitive solution will be forthcoming soon (and not just for Windows 10 ... I've tried that and it's unlikely that I'll be going there any time soon).

[Craig@Invincea]

I am willing to buy the home version, but it seems that does not get any technical support.

Well, the support I believe is in this forum and you get it, I guess, for both paid and trial versions. Right now though, it doesn't seem that buying the product will make any difference to the problem. I have a paid, personal licence but the program at this time is unusable. I just have to hope and believe that the problem is being worked on with some priority and that a definitive solution will be forthcoming soon (and not just for Windows 10 ... I've tried that and it's unlikely that I'll be going there any time soon).

Yes, Technical Support is in the forum only. As for the SBIE2204 error, yes it is being looked at (and has been for several beta releases) but it can persist. It was unique to Win10, but in addressing that code it was forecasted that it may increase the problem in 10 before it gets better and it may trigger it more in Win8.1 (because the same general program language of Windows is shared by both OS, just more so in 10.)

AVG is not a direct link to it, Any program loading up can trigger a race timing issue. Disabling any program can reduce the "race" as they all are trying to start. It's random. Now if you are seeing it every single time, then that is something else.

We've done in house automated torture tests to recreate the issue, we've seen it 1 out of 500 up to 1 out of 1000. Getting better, but it still persists. It may persist for sometime as it relates to the ORIGINAL SBIE code.

[dnaman]

Now if you are seeing it every single time, then that is something else.

That's just it actually, Craig. I am seeing it every time I try. I simply cannot use Sandboxie any more. Based on your comments, I haven't actually tried turning off AVG. Perhaps I should just to try it - although I don't feel that's a very good solution going forward. (Plus the last time I looked i had a devil of a time figuring how to turn it off .... they obviously don't want you to do that too easily )

[Craig@Invincea]

Now if you are seeing it every single time, then that is something else.

That's just it actually, Craig. I am seeing it every time I try. I simply cannot use Sandboxie any more. Based on your comments, I haven't actually tried turning off AVG. Perhaps I should just to try it - although I don't feel that's a very good solution going forward. (Plus the last time I looked i had a devil of a time figuring how to turn it off .... they obviously don't want you to do that too easily )

Do post here if turning it off eases the error. I will pass that along to the Devs as they have asked about every single time occurrences, which, we can't repro. We can trigger the error, but usually not in succession. I haven't been able to recreate it with AVG, but I have with other programs.

[dnaman]

Do post here if turning it off eases the error. I will pass that along to the Devs as they have asked about every single time occurrences, which, we can't repro. We can trigger the error, but usually not in succession. I haven't been able to recreate it with AVG, but I have with other programs.

I tried temporarily disabling AVG. It didn't make much difference in that I still got the problem - except once in maybe 10 - 15 attempts when it actually did start up. I don't really feel that's significant though. I'm inclined to think that if I tried enough times, with AVG active, I'd have probably had a random success.

If you need any more detailed info about system setup etc, just shout.

[BishopJ]

There seem to be at least two other threads on this forum relating fairly definitely to the same problem which could usefully be amalgamated. There is a helpful workaround in the "SBIE2204 Cannot start sandboxed service RpcSs (-1)" thread where an associated problem seems to be SBIE fighting with AVG.

[shalbe]

I have this 2204 problem after upgrading to Windows 10. I've spent all day trying so many things suggested in this forum without any change in the problem whatsoever. The suggestions here are useless. I am now giving up entirely. Yours isn't the only sandbox application. Maybe you'll get it fixed someday and I'll come back, but I wouldn't count on it.

[Craig@Invincea]

I have this 2204 problem after upgrading to Windows 10. I've spent all day trying so many things suggested in this forum without any change in the problem whatsoever. The suggestions here are useless. I am now giving up entirely. Yours isn't the only sandbox application. Maybe you'll get it fixed someday and I'll come back, but I wouldn't count on it.

A little more info does help. You just upgraded. Ok, did you upgrade your SBIE to the v5 Beta? Because v4.20 will not work with Win 10. What program is giving you the error.?

[dnaman]

Just updated my (Win 8.1) installation to the latest beta (5.03.1). No change to the problem.