Excel2016(365version) SERIOUS PROBLEM![RESOLVED Beta 5.17.6]

[henryg]

Sandboxie 5.17 is causing Excel 2016 to crash every time when using the data query editor (formerly Power Query) when I try to create a table query. I have lost so much time over this as it never occurred to me that Sandboxie c/would affect a program that was not being sandboxed! Ironically perhaps, often if I have a problem with a program crashing I try to see if it does the same when sandboxed.

I can tell you that with 5.17.1 it is ok, but I cannot spend any more time on this, eg going through the beta iterations. But this problem must not be allowed to escape into the next release issue; or my goose is cooked!!

Thank you Aomei for your imaging program!!!!

[Barb@Invincea]

Hello henryg ,

Can you please provide more information regarding how are you reproducing the issue?
If the problem is happening outside Sandboxie, then it is not Sandboxie related.

What are your OS, Antivirus and Sandboxie versions?

Regards,
Barb.-

[henryg]

Hello henryg , Can you please provide more information regarding how are you reproducing the issue?

Open spreadsheet, highlight data range, go to Data Tab and click on "From Table" under "Get & Transform". Watch the query editor window open...and crash!

If the problem is happening outside Sandboxie, then it is not Sandboxie related

The Sandboxie driver/Click to run stuff is loaded whatever, or isn't it? If regressing to 5.17.1 OR uninstalling Sandboxie (as the ONLY change) cures the problem, than IT IS Sandboxie related however much your logic says otherwise!

What are your OS, Antivirus and Sandboxie versions?

Window 10 x64 (v 1607 buld 14373.726) Sandboxie either 5.16 or 5.17.1 (no crash); 5.17.5 crashes Excel data query every time. Excel v16.0.7870.7034 32 bit ATM.

And I uninstalled and reinstalled Office 365 multiple times, including using the Microsoft "nuclear" remove tool, and also tried the 64bit version. And the behaviour is the same on my laptop - similar setup but different hardware/drivers and less software installed.

[Barb@Invincea]

Hello henryg,

Thanks for the steps! I am getting the same crash in Excel 2016 (the application freezes and I have to kill it). I did not see anything from Sandboxie...However, I think there's something going on, since reverting to 5.17.2 or older allows for this feature to work.
I am not sure why this happening, but I have made the devs aware.

We'll update this thread when more info becomes available.

Regards,
Barb.-

[henryg]

Thank you

[Curt@invincea]

This is fixed in 5.17.6.

[henryg]

It does appear to do so. How did SB affect a non-sandboxed program? Potential to do so for other programs?

Do you want to edit the title to say "SOLVED". I couldn't do so. And move it for that matter; I never intended for it to be separate from other beta issues.

[Barb@Invincea]

henryg,

This was a specific issue, not generalized and it has been fixed now.

Marking the issue resolved.

Regards,
Barb.-

[henryg]

henryg,This was a specific issue, not generalized and it has been fixed now.

Sorry, but not really good enough.

[Syrinx]

It does appear to do so. How did SB affect a non-sandboxed program? Potential to do so for other programs?

The "Click 2 Run Service" which is part of the Office version you had is modified by SBIE in order to allow them to work 'together'. I don't know the details but it is one of the few things altered outside of a sandbox. From what I recall it seemed to be something of a milestone getting the C2R versions working alongside SBIE. It was an 'in high demand' option [so while I hate MS Office myself] thus I can understand why they wanted to get it working well together. However before they added some automation to the changes, when the C2R option was first added (for paid users) the service would have to be manually restarted by the user [or a reboot would be needed] for the changes to take effect or some jazz.

In short, unlike most things, SBIE actually makes changes to an un-sandboxed process ~ in this case ~ The C2R Service included with some versions of office. I can't actually think of another off the top of my head so it may very well be (currently) the only process it will touch outside of a sandbox.

Either way, it isn't blindly injecting everything outside of a sandbox so the potential to cause issues with other software like you saw here should remain low to non-existent.

[henryg]

Many thanks Syrinx for your take on the issue.