I have downloaded the new 2.49 version but have not installed it yet, because there is a substantial size difference between the new version and the other recent versions.

The new one is about one-third smaller (235kb vs. 349kb) than its recent predecessors, so I'm wondering if the new executable is corrupt or whether you have just found some new coding efficiencies.

I would appreciate hearing your response before I try the new version.

Thanks.

SBIE (Happy) User

It's intentioal: I removed the UseGuide.rtf help file. Instead I added a Help | Topics command to the Sandboxie Control application. It opens a this web site. Though I didn't do the actual help page yet...

Thanks, Tzuk.

I was hoping this was intentional. I'm going to install it now!

SBIE (Happy) User

So far so good with 2.49?

Yes, and no.

With 2.49 all works fine, but there is an annoyance at bootup with this version installed.

At every bootup I get a new msgbox that says:
"Please click OK to start the core component of Sandboxie."

Because my machine is loaded with lots of programs and services that begin at startup, my bootup processes take quite a while and I like to just walk away while the machine is booting up. If I don't hang around now and wait for Sandboxie's popup msgbox with this message, the whole process just goes into limbo and waits for me to come back to press OK. As soon as I press OK, the bootup continues normally and all goes well.

Is there a way to avoid this new msgbox and just have Sandboxie load automatically at bootup like it did with previous versions?

Thanks.

SBIE (Still Happy) User

The message appears after Sandboxie Control has been trying to talk to the driver for 30 seconds, with no luck.

The new Sandboxie Service should start the driver when it comes up itself, so first check the Services screen to see if Sandboxie Service (or SandboxU) is, in fact, set to start Automatically.

But if that's fine, or doesn't make a difference, you can resolve this another way: Set Sandboxie Control to not start automatically, and let it start with the first program you run sandboxed.