5.11 Beta Available (latest version 5.12 RC)

[Craig@Invincea]

Instructions regarding Click2Run Service are here: http://forums.sandboxie.com/phpBB3/view ... 11&t=22645

[cj716]

Followed instructions for C2R. Seems to work. Some comments from my experience though on Win10 x 64 Office 2016. No other security apps installed.

Forced processes take a long time (10+ seconds to invoke the SBIE processes) i.e. forced apps start in box but it is more than 10 seconds until SandboxieRpcSs.ece and SandboxieDcomLaunch appear. same whether doble clicking file or navigating to it through main exe.

Right click/run sandboxed is slow too. Unable to close the office doc thereafter. Application does not respond with error.

If you're using start/Run you need to let FileCoAuth .exe start

DDE issue with Excel still there. i.e. there was a problem sending the command to the programme error

You'll need to disable Protected View in Trust Centre to view stuff you get from internet/USB etc.

Thanks

[Craig@Invincea]

You might notice a slight delay. But it wasn't anything more than I see in a VM. Def not much of one if you only restarted the service. (that is only done once.)

However, If you stopped the service, then opened Word without restarting the C2R service, yes, that first time will be a significant delay as SBIE has to then start it.

Either way, once it started, the delay is minimal.

You have to then considering how Win 10 is loading things and how SBIE is going to figure into that mix.

If you're using start/Run you need to let FileCoAuth .exe start

Nope, never had to. Forced was faster, right click, drag & start/run was only slightly slower. By no means 10 seconds. And that was with a VM overhead.

You'll need to disable Protected View in Trust Centre to view stuff you get from internet/USB etc.

That's a Microsoft "Feature" that is auto enabled.

[cj716]

Hi Craig,

Thanks for responding. Our experiences are varying then.

15 seconds from clicking to document opening here 10 of which are waiting on SBIE processes. Default sandbox with word, excel powerpoint forced for now for testing.

Without allowing filecoauth it starts even later, 30 secs plus and gives errors about AppVDllSurrogate64.exe not being able to start you don't get if filecoauth is allowed.

I'll try rolling back and starting again tomorrow to see if that helps or I've missed any steps.

Cheers

[Craig@Invincea]

The more feedback we get the better, it's why we released it to see what we can look at as we move along.

[cj716]

Good to hear. Anything I can do to help I will. I'll feedback after I roll back tomorrow. If it is still the same I'm happy to try out any approach you think might help fix or diagnose the issue.

Cheers

[henryg]

5.11.4 has been released including the much anticipated ClickToRun support!

Oooh, ooooh, oooohhhhh

Will try it later

[cj716]

OK, tried again.

Same issues with speed on Office 2016 ctr apps. 15 secs minimum wait.

FileCoAuth.exe is linked to One Drive folder so if you don't use One Drive or the files your opening are not in the One Drive folder you then you don't need to allow it.

Any ideas on what to try?

Thanks

[Craig@Invincea]

OK, tried again.

Same issues with speed on Office 2016 ctr apps. 15 secs minimum wait.

FileCoAuth.exe is linked to One Drive folder so if you don't use One Drive or the files your opening are not in the One Drive folder you then you don't need to allow it.

Any ideas on what to try?

Thanks

Nope.

I use OneDrive in SBIE as the default save location for files.

I haven't seen any delay of that long...maybe 2 seconds max. So far on 5 non-work related machines....This is from a VM...Non VM corei7 to a Dell Windows table running a dual core Atom & a MacPro running VirtualBox and Win 10x64.

Runs as expected. Slight delay, but nothing more than I've seen in a VM environment.

[Craig@Invincea]

If we get more reports, maybe we can sort it out.
Speed is such a subjective thing and It's almost impossible to recreate and one particular environment or variable. Unless a crash, were we have actual locations to look at, etc.

[Craig@Invincea]

On a ancient core i7, 16GB ram, Win 10x64 FR14316 build, Comcast Xfinity Norton Security Suite (and Norton Outlook addon.)

*from Clicking on Outlook 2016, until seeing the "outlook loading" box, almost 4 seconds. (Outlook preconfigured w/ @Live email account)
*When opened in SBIE (Dragging Outlook 2016) into SBIE Control, that box took almost 5 seconds. (and that was with an Office Update dl in the background for both tests..)
Outlook Forced 5-6 seconds.

Word in SBIE (Run from task notification menu) =8 seconds.
Word (w/o SBIE) 2-3 seconds
Word Forced=7.5 seconds.(there was a noticeable delay w/ Word.)

I watched everything load in SBIE, Start, RCPSS, etc..etc. then Word.exe

You also have to remember that SBIE isn't taking advantage of faster startups that running Office in Windows would have. SBIE has to run through it's startup processes while loading Word/Outlook inside a Sandboxed environment.

And you may see BETTER performance from single (if they're still around) and dual core systems than you would multiple cores. A few years back, a typical quad-core would always lose to a dual-core in single-threaded performance scenarios, but that has changed somewhat in brand new Intel chips.


This was non VM environment.

[beekn]

hello

Vivaldi browser very slow to start and works in sandboxie.

[Craig@Invincea]

hello

Vivaldi browser very slow to start and works in sandboxie.

That's why we stick with supporting the big 4, Chrome, FF and IE Opera. (32/64.)

How are you running Vivaldi in SBIE? Forced? Dragging to SBIE Control?

What addons do you have running? Disable any.

I'm running 1.0.435.42. It's bad on the host. Slow and appears to crash.

We support some forks of them as well, Cyberfox, Palemoon and others. There is a note about Vivaldi here http://forums.sandboxie.com/phpBB3/view ... di#p119984

[Craig@Invincea]

OK, tried again.

Same issues with speed on Office 2016 ctr apps. 15 secs minimum wait.

FileCoAuth.exe is linked to One Drive folder so if you don't use One Drive or the files your opening are not in the One Drive folder you then you don't need to allow it.

Any ideas on what to try?

Thanks

I spoke with one of the Invincea Dev's and the Invincea Support folks, there is known "lag" in Office when it comes to the container. They've customized some .XML files, reviewed client requirements and thus geared any performance bumps tweaked per the client (mainly Enterprise clients).

Some things they noted:
Lync running in the background w/ Office Docs, and causing delays....o they excluded Lync in various ways.
Another issue was McAfee for one client that had to be tweaked to to play nice, etc.
Blocking OneDrive (as it didn't meet many clients need for data security in the Cloud.)

The Invincea product doesn't support Win 10, so they have that going for them

Of course, SBIE has the .ini and there are ways to do certain things....I'll play with RAC in SBIE to see what extra stuff is loading/needing access and maybe get some ideas and go from there.

[henryg]

I followed the linked instructions regarding stopping and starting the click to run service but cannot get Word or Excel 2016 to run sandboxed - with or without drop rights - the usual old error message comes up. Office 365 programs are installed outside the sandbox.

Any idea what I could be doing wrong?

Sandboxie 5.11.4 64 bit; 32 bit Office 365; Windows 10 x 64 v1511(build 10586.164)