Hi Tzuk,
when starting the new Outlook 2010 in Sandboxie 3.442 the Identifier # is not showing up in the heading.
A colored frame is working as before.
Regards,
Bernie

Some programs paint their own caption bar, the Sandboxie [#]'s don't show in this case. Other than that, everything else seems to work fine?

Outlook 2010 always hang when run sandboxed ... I'm using the latest Sandboxie Beta

Running Outlook 2010 in Sandboxie results in an error after running a while:

Outlook calls the configuration routines, error is:

Error 1923. Service 'Office Software Protection Platform' (osppsvc) could not be installed. Verify that you have sufficient Privileges to install System Services.

I believe the directory access has to be redefined.

Regards,
Bernie

Hi Tzuk,
it is not only directory access.
I did open the directories Outlook 2010 seems to access, but still the same.
Regards,
Bernie

Bumblebee, can I ask you try with Sandboxie version 3.45.19 ?

http://www.sandboxie.com/phpbb/viewtopic.php?t=7511

Version 3.45.19 shows the same behavior - the configuration starts.

From reading through the internet I assume that sandboxie prohibits the access to the osppsvc.exe service - but it should not and cannot be installed a second time.

Regards,
Bernie

In that case please provide a Resource Access Monitor log, it might show which resources need to be excluded from sandboxing.

http://www.sandboxie.com/index.php?ResourceAccessMonitor

Start the monitor just before you run Outlook sandboxed, and close it after you get the error.

When the resource monitor is running I get at one time SBIE 1242
Here is the output anyway:

snipped. --tzuk

Thanks. Your log shows this:



Probably related as you were getting errors about 'osppsvc' service. Go to Sandbox Settings > Resource Access > IPC Access > Direct Access, click Add and paste:



Does that fix the problem?

OK, Outlook seems to run without getting into installion routines.

Now after about 5 minutes Sandboxie comes up with an error:
SBIE22Ü5 Service not implemented: CM_GDILX(1/00000200/{4d36e968-e325-11ce-bfc1-08002be10318}}

Good, so we fixed the licensing issue. I will add this exclusion as a Software Compatibility option for Office 2010.

As for the CM_GDILX message. Can you check if this happens just with Outlook or also with Word, Excel, PowerPoint, etc?

The same error message comes with WINWORD and EXCEL - nothing else installed on my PC

Thanks. I have already decided to fix this particular problem only after I release version 3.46. So as an immediate solution, I'm just going to hide this CM_GDILX message, starting with the next beta, 3.45.20.

Hi Tzuk,
thanks for your fast and efficient support to this nice and effective piece of software.
Waiting for 3.46.
Regards,
Bernie