When installing MS Mail, I get:SBIE2205 Service not implemented: schtasks.exe

I'm happy to post more info about my setup etc, but only if there's a realistic chance of getting them working... How many apps are there that *just* don't work with Sandboxie? (And how many of those apps are email clients?)

If I was trying to install something 'low-level' (eg encryption software) I could understand it not working with SB, but two relatively simple email clients... Is that too optimistic?

I'll try and install Zimbra Desktop 7.2.2 and Windows Live Mail (part of Windows Essentials) on Win7x64 and Win8x64 (looks like you are on a x64 variant of Windows) with Sandboxie 4.08 (pressume you are using the latest stable).

Zimbra installed inside the sandbox, but I got the same error messages when attempting a first launch. Zimbra launches via a Visual Basic Script, which is closed off (for security). Looks like we would have to poke a pretty big hole in the sandbox to allow these VB scripts to run. With a sandboxed Zimbra a no go (imho), I turned my attention to Windows Live Mail...

After several unsuccessful (sandboxed) install attempt, I installed it outside the sandbox; all the files that get left behind after an uninstall (via Control Panel) should persist inside the sandbox, which can easily be cleaned up. If you are willing to try this way, please read on...

Here're the steps I took to get Windows Live running in the sandbox (after installing outside the sandbox):1) Run Live Mail outside the sandbox once to accept its EULA, then immediately close it down.2) Right-click on "Sandbox DefaultBox" in the Sandboxie Control (I've only the DefaultBox on this VM), then select "Sandbox Settings".3) Under Applications->Email Reader, double click Windows Live Mail (a plus sign will appear next to it), then click Apply.4) Launch Windows Live Mail in the sandbox.

That's right. Just to clarify, by "closed off" what I really meant is sandboxed. Nicely behaved scripts can still run in the sandbox; eg, ones that don't want to launch DCOM objects at an elevated level to see how much disk space is avail (I peeked at the launch script).

I started the install process outside of Sandboxie. I think because I had a partial install before (although I'm not sure how because I'm sure all installs had been Sandboxed before) I wasn't asked to accept the EULA. By the time I realised that Live Mail was simply installing I decided to just let it finish...

So I can report that Live Mail definitely installs OK outside of the Sandbox!

Oh well - it seems quite a small footprint, so I'm happy.

Cheers, Richard

joohwan@invincea wrote:Richard,

Zimbra installed inside the sandbox, but I got the same error messages when attempting a first launch. Zimbra launches via a Visual Basic Script, which is closed off (for security). Looks like we would have to poke a pretty big hole in the sandbox to allow these VB scripts to run. With a sandboxed Zimbra a no go (imho), I turned my attention to Windows Live Mail...

After several unsuccessful (sandboxed) install attempt, I installed it outside the sandbox; all the files that get left behind after an uninstall (via Control Panel) should persist inside the sandbox, which can easily be cleaned up. If you are willing to try this way, please read on...

Here're the steps I took to get Windows Live running in the sandbox (after installing outside the sandbox):1) Run Live Mail outside the sandbox once to accept its EULA, then immediately close it down.2) Right-click on "Sandbox DefaultBox" in the Sandboxie Control (I've only the DefaultBox on this VM), then select "Sandbox Settings".3) Under Applications->Email Reader, double click Windows Live Mail (a plus sign will appear next to it), then click Apply.4) Launch Windows Live Mail in the sandbox.