On Windows XP SP2, with all updates, I encountered the SBIE2204 and SBIE2006 errors the first time I tried to use Sandboxie after completing the latest Windows Update cycle. After confirming that KB979683 was one of the updates installed, I downloaded and installed version 3-45-07. After rebooting, the problem with initializing Start.exe was gone, but a new error prevented Sandboxie from operating. Almost as soon as Start.exe could be seen in the Sandboxie Control, the program began to produce a series of SBIE2204 error messages, each saying "Cannot start sandboxed service RpcSs (-1)." A new error message was generated about every 10 seconds. The sequence apparently would have continued indefinitely if I had not used the right-click option within Sandboxie Control to terminate Start.exe. The new problem persisted after deleting the RegHive and RegHive.log files in the existing sandbox. It also persisted after deleting all contents, including folders, from the existing Sandbox folder.

As a followup to my earlier post (Tue Apr 13, 2010 10:10 pm), I want to report that I repeated the installation of 3-45-7, this time over itself, with no effect after exiting from Comodo Firewall 4 (with Defense + enabled), and "stopping anti-virus" on Panda Cloud Anti-virus. This are the only real-time scanning components which I could imagine might interfere with the installation or functioning of Sandboxie. Both had functioned without conflict with Sandboxie 3-44, which was the version of Sandboxie installed on my system before the Windows Update. Comodo 4 itself had an update today. The timing suggests that it also needed to adjust the functioning of its sandbox to work with the new Microsoft components. When I checked Comodo's Defense + Events log, it showed no evidence that it had ever had any conflicts with Sandboxie or the update process.

I'm posting about these troubleshooting steps in sequence in hopes they will help Tzuk identify the cause of this problem.

Following my last post, I uninstalled KB979683. I discovered that Microsoft is aware of Sandboxie. The uninstall process detected that 3-45-7 was installed, and warned me that if the security update was removed, "these programs might not run properly." They were correct. After completing the uninstall and rebooting, I found that, as expected (designed?), Version 3-45-7 did not work. I thought it might produce a different error, but it continued to report problems with RpcSs. Then, thinking that the sequence of installation might be related to the problem, I repeated the installation of KB979683 while 3-45-7 was still installed. After completing that, and rebooting again, I found that the experiment failed. Sandboxie still could not start RpcSs.

My last hope for "peaceful coexistence" between the latest Microsoft security update and existing versions of Sandboxie had disappeared. I used the "add/remove programs" to uninstall 3-45-7, rebooted, and then did a clean install after stopping all processes except XP system processes. Even with all defaults, Sandboxie still could not start RpcSs.

Just to clarify my last post, when I uninstalled Sandboxie, I chose the option to remove my configuration, so that the "clean install" which still failed included the default Sandboxie.ini file, fresh copies of all files, and a fresh Sandbox with the default name, in the default location.

I'm happy to report that I've now returned to my status as of Monday: Sandboxie 3-44 and no patch for the KB979683 vulnerability. Sandboxie should guard against any successful exploitation of that vulnerability, as well as a host of others possible evils more likely to strike. Good luck finding a cure for the problem.

I did Windoze update. Running W2K SP4. Sandboxie gave 2204 and (I believe 2306) errors. Help directed me to 3.45.07. I did verify that KB979683 is installed. I did the installation without apparent issue. Now I get a system error messages that says sandboxierpcss.exe has generateed errors ... closed by windows. This results in a sandboxie error list of 2204 errors, although Firefox seems to work OK inside sandbox. Of course, I tried rebooting and reinstalling 3.45.07 after deleting sandbox.

Something still is not right here.

I deleted sandbox, uninstalled sandboxie, rebooted, installed sandboxie, rebooted, still have "sandboxierpcss.exe has generated errors ... closed by windows. If I OK that message, then Firefox opens UNsandboxed. Close firefox, then it opens sandboxed next time. But that error message box is stuck on the screen with increasing numbers of SBIE2204 errors.

In that case, the "SandboxieRpcSs has generated errors" message box might have some "more info" button or link that indicates a couple of "dump files" that were created and contain information about the error. Can you find these files and send them to me or upload them to some shared hosting space? Thanks.

I am sorry. Dr. Watson log has no contents. System log under event viewer only says Sandboxie driver loaded. I do not see any other files that would appear to be logs related to this event.

I think the Application log might be more appropriate in this case. If not a complete log, do you at least get some information about the name of the faulting module offset within it?

Sorry - The application log did not record the event. Dr. Watson only gave a start and stop and I looked right after I closed the message. Typical Windoze - world's record for unhelpfulness in error messages and logs.

One more thing. Unlike many error boxes, this box did not have a button for additional information. This is W2K SP4.

That still didn't work for me. I get this error over and over: Cannot start sandboxed service RpcSs (-1).

Those of you who are seeing this error, it is likely caused by some conflict with another software, most likely security software. Can you list the security software to see if we can identify anything you have in common? Thanks.