SB Services timing not fixed for me

[Spoiler]

I saw in the resolved problems list that there was a timing problem with services. it sounded like a good idea to set the sb service to manual so I did. but when i went to run my browser sandboxed with the right-click context menu I got the same message that guy did the first time. I think you fixed it for him and yourself but not for me. I guess my system is slower than yours.

shouldn't sb keep trying a few times for a timeout period and not give up after several times? it takes 5-10 seconds for the service to start here and sb gives up with an error message before the service can really start.

if the timeout is too long you make someone who didn't install or start the service correctly wait for a while. that shouldn't happen often, not to the same person anyway! but if it's not long enough then anyone who sets the sb service to manual will see the error and have to launch twice every time on the first time he boots and runs something big in a sandbox. and it would be the same with the context menu as it is with autoruns.

[tzuk]

It isn't a question of waiting a specific number of seconds that could be not long enough, or too long for most. That fix you're talking about was supposed to make Start.exe wait patiently until Sandboxie finished its initialization, however long that process takes, but not any longer than necessary. Are you using the latest version of Sandboxie?

[Spoiler]

Hi Tzuk.

yes, I'm using 3.00.17 here and it puzzled me that both you and the original poster didn't get the error that I do. I can repeat it every time by stopping the service and then using the right button context menu on an item in my startmenu or quick launch area. it doesn't seem to matter much what I choose either but the first thing I tried was my IE7, which I dont normally sandbox but do it once in awhile.

I'd be interested to see if anyone else can replicate this. if not, then it's got to be something here and I'll try to run it down with my primitive capabilities and even more primitive smarts.

[tzuk]

When the service stops, it doesn't un-initialize or stop the driver, so you really shouldn't be getting these errors when you restart the service after it has already started once.

I think you should describe the process in some more detail, and quote the specific error messages.

[Spoiler]

Yes! That was a good idea, the messages are different from the other thread. Here's what I did.

1. My Sandboxie service is set to start Manual, not Automatic.
2. Stop the Sandboxie service
3. Use the right-click context menu to start IE7 from quick launch area of toolbar in sandboxed mode

The error messages that I see are:

SBIE2203 Failed to communicate with Sandboxie Service: connect C0000034
SBIE2202 Missing list of installed hardware devices

Those error messages appear together in one box, sometimes followed by several separate instances.

BUT, IE7 eventually comes up nicely sandboxed and working just fine anyway. So the generation of the messages do not prevent the programs from doing what they're supposed to.

Do you see this same behavior on your system?

[SnDPhoenix]

Damn, i know this isn't what you want to hear, but unfortunately, i dont get the same behavior, when i had the service set to manual and stopped, i went to the quick launch bar, right clicked ie7, hit run sandboxed, and the service started just fine, got no error messages, and then ie7 sandboxed just fine, so unfortunately, i couldn't reproduce this, maybe tzuk or somebody else will be able to, or maybe he'll just plain old figure out.

P.S On a side note, this is the first time i've looked at the service manager in Vista and it's awesome!

[Spoiler]

thanks for trying it, SDPhoenix. I'm using WinXP SP2 here, maybe that's the difference.

Not that this is a big problem that Tzuk should spend a lot of time on, after all it doesn't cost much to let that service run. Besides, once I run Sandboxie, which is usually once per session, the service starts and stays anyway. I was just curious why it got fixed on the other machines but not mine. Oh, well....

[SnDPhoenix]

Tell me something, have you tried reinstalling or uninstalling and then reinstalling Sandboxie? Also are you using any security programs on your pc, if so, what programs are they?

[Spoiler]

I've installed and reinstalled several times and I always disable my AV program when I do. I'm using CA Antivirus, and Windows Defender. So far they seem compatible with Sandboxie.

I've had infected web sites download a series of trojans but AV immediately reported and caught them, and SB put them in the sandbox and not in the normal IE cache.

The AV then quarantined and deleted them, and said I should reboot. But the SB registry hive caught all the poking around so when I deleted the sandbox everything was clean. Being a cautious (paranoid?) fellow, I rebooted anyway.

When I install/upgrade SB, Windows Defender always asks me if I want to let it modify the start-up list, to which I reply yes.

It seems like all three programs are doing their jobs as intended, and I couldn't ask for more.

A real easy "fix" for this "problem" would be to include in the instructions a statement to the effect that if you wish to turn off the SB service, just be sure to run SB control before you sandbox anything for the first time in that session. I can't imagine anyone objecting to that.