Sandboxie Plus (Sbie fork)

You are using the installer not the zip right?

The "cannot start drivers" issue is a very basic problem not related to sandboxie.ini or the content of any sandbox.

And usually caused by some 3rd party security application interfering with the driver loading...
can you check if the sbiedrv.sys is present in the installation directory and please post
the reg key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SbieDrv
ImagePath
it should be "\??\C:\Program Files\Sandboxie\SbieDrv.sys"

if the ?? is missing that thats an issue try adding it.

cheers
David X.

 

Hello David, thanks for the quick reply. But I'm afraid that we are talking past each other.

Yes, I'm using the latest Installer. And yes, "sbiedrv.sys" is present in my installation-directory (in my case: "C:\WINTOOL\Sandboxie\").

But this has never been a driver-issue. In fact Sbie_v5.42.1 HAS ALREADY WORKED FLAWLESSLY on my sytem for 3 weeks before.

It is the SERVICE "c:\WINTOOL\Sandboxie\SbieSvc.exe" that from out of nowhere suddenly refused to start. No additional security software has been added in the meantime.

When looking at "SbieSvc.exe" directly in the Service-console it has status "automatic/stopped" and cannot be started manually with an error-message saying that upon manual re-start it has been (self-)terminating immediately again .

The whole problem began with a UAC-popup-window appearing upon re-boot asking permission for MS-service-host to alter the system which seemingly is the one trying to start the "SbieSvc.exe"-service and THAT one complaines (in the details-section) about some certificate-issue.

And - as requested - here comes the reg-key in question:

Code:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SbieDrv\\ImagePath

\??\C:\WINTOOL\Sandboxie\SbieDrv.sys

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SbieSvc\\ImagePath

"C:\WINTOOL\Sandboxie\SbieSvc.exe"

Note that there are quotes around the value for SbieSvc.exe (the one which fails) and no quotes around the value for the driver-image-path.

 

Ok, I apologize, problem solved.

For some reason that really is beyond my comprehension that damn' "Windows-Defender"=Troublemaker Anti-Virus-"protection" had auto-activated itself without my knowledge.

I had white-listed Sandboxie-folder before in Acronis-Active-Protection and my trusted anti-virus-software, the security-tools I am both willfully using - but not in MS-Defender because that one ought to be de-activated anyway. Somehow that nuisance obviously has found a way to sneak itself back into my system.

 

yea!

I'm looking into getting a certificate of my own so possibly in one of the next releases this issues will be no longer present.

 

David -- Are you waiting for me, or am I waiting for you on this question?

 

Hey can i make sandboxie plus working with chromium edge?

 

sorry, to much other work...

You can download those releases just set your Browser to not take you choice away, or use an other browser.
and please test those two as well.

 

Update: I have added a custom installer for the plus build to the current 0.3.5 build.
please test it if it works well it will replace the zip files in future.

https://github.com/sandboxie-plus/Sandboxie/releases/download/v0.3.5/Sandboxie-Plus-x64-v0.3.5.exe
https://github.com/sandboxie-plus/Sandboxie/releases/download/v0.3.5/Sandboxie-Plus-x86-v0.3.5.exe

Cheers
David

 

David -- My apologies. This test gave me completely different results! The only explanation (guess) I can come up with is that, the first time around I had tried 5.42.1 first, loading it from the ZIP (with a couple of aborted tries and deletions) and that that somehow "polluted" my first test sequence.

Today I found that MS Edge would download the versions that neither Firefox nor Chrome would previously, so I was able to get them all. I started from 5.33.6 (Sophos), which had been running all week, and successfully loaded (with overwrite) the following EXE (installer) versions in this order:

SandboxieInstall64 v5_40
SandboxieInstall64-v5.40.1
SandboxieInstall64-v5.40.2 -- I had not been able to download this one for the first test sequence.
SandboxieInstall64-v5.41.0 -- This (and 5.42.1) are the ones that wouldn't run Outlook previously, so I had stopped the first test sequence here. (This one is also the only one for which Windows Defender complained about a Trojan this time around, as it had previously.)
SandboxieInstall64-v5.41.1
SandboxieInstall64-v5.41.2
SandboxieInstall64-v5.42
SandboxieInstall64-v5.42.1 -- I used your original installer.

All of these versions successfully ran Outlook 2019 in its own sandbox (in my Standard User account) without the previous "Updating Office" message (which I had never seen before in 8 months of running this system with Sandboxie 5.33.1). I suppose I had better keep running 5.42.1 for a few days before I'm sure everything is OK...

Bottom line: I seem to be all good here. Do you need anything else from me?

Couple of Questions:
1) Is there something about these builds that expects you to install them in sequence? Might that have explained my earlier problems?
2) What is special about your "custom installer for the plus build to the current 0.3.5 build" (other than its 6X the size)? Did you want me, specifically, to test it, or was that a general request?

Cheers! -- jclarkw

 

I find that I prefer the old interface to the Plus version, so thank you David for the option. I can't pin down why I prefer the old interface (familiarity?), but does anyone else feel the same? Only for personal interest, no axe to grind.

 

1) no the order shouldn't mater...
2) the custom installer installs SbiePlus i.e. sandboxie with the new Qt based UI and the Qt Framework is Huge unfortunately, but its very powerful and a true pleasure to use.

It was a general request to test it as In future it will replace the zip release of the plus version.
The installer has the extract option that makes it behave like a self extracting zip basically leaving behind just the extracted files i.e. a portable version.

Cheers
David

 

Dear David -- SbiePlus 5.42.1 (original installer) is still producing the following errors when running Google Chrome or Microsoft Edge under Windows 10 (1909):

SBIE2303 Could not hook CoGetObject (33, 1655)
SBIE2303 Could not hook RegisterDragDrop (33, 1655)
SBIE2318 DLL initialization failed for 'ole32.dll'

While it was my understanding relative to Sandboxie 5.33.1 that these errors could be safely ignored (correct?), they can be annoying. Do you have plans to diagnose/fix this issue? -- jclarkw

 

And Win10 2004 Warns that at least 5.33.1 ist not campatible...Is Sandboxie plus compatible?

 

garack -- Bo Elam said that 5.33.6 is compatible:

https://www.wilderssecurity.com/thr...s-sbie-open-source.428156/page-9#post-2937617

I don't have 2004 yet, so I can't tell what else is. -- jclarkw

 

Dear David -- NEW User Account Control Issue: Yesterday I suddenly started seeing the following message (running Sandboxie 5.42.1 -- your original installer -- from my Standard User account under Windows 10 1909 as usual):

The UAC notice seems to appear when I open or close a program in one of my sandboxes. I'm unaware of any changes that took place to start this behavior, so my first question is, why is this message appearing?

I also don't understand the implications of the two choices, which continue to be required no matter how I answer the first time. Should I select "Yes" with the appropriate administrator password, "No," or just dismiss it? -- jclarkw

 

Hi jclarkw,
may I ask which accounts you've setup in your sandboxed Outlook 2019? POP3, IMAP or Microsoft Exchange/Outlook.com? I'm asking because I'm unable to get a simple Outlook.com account running sandboxed with Outlook 2019. If I start Outlook, only the startup screen appears, telling me "Opening profile", but nothing happens afterwards. I've tried Sandboxie 5.31.6 and 5.33.6 - of course with a new Sandbox as well.
--Thomas

 

Thomas -- My Outlook 2019 (bundled with Office 2019) was set up for POP3 and offline (on-demand) access only. (Another wrinkle is that I moved the standard Windows 10 "Documents" folder, including the Outlook data store, to another drive from its original location somewhere on C:\ -- not sure that matters in your situation.) I then just used Sandboxie 5.33.1 (I think it was at that time) to create a desktop shortcut to its own sandbox, which I had previously created with Sandboxie's default settings for Outlook (actually Outlook 2013 at that point I think). I'm afraid I don't remember many of the details, but the shortcut inherited by Sandboxie Plus 5.42.1 still works.

The only aspect that doesn't work (never has) is Outlook's indexing, which doesn't keep up to date while it's running inside the sandbox. (Maybe David will figure out how to solve this problem someday...) The solution is to run Outlook occasionally outside the sandbox so the indexing can catch up with new mail and filing.

I hope this helps a little. I'll try to answer more detailed questions if need be. -- jclarkw

 

Many thanks for your prompt response! Alright - POP3 is working for me too, the problem is that Microsoft Exchange accounts like Outlook.com/Live.com are not working any longer.
In fact, I found out that:

Outlook 2010:
Sandboxie 5.31.6 and Outlook 2010 is working fine.
Sandboxie 5.33.1 - 5.33.6 and Outlook 2010 is NOT working -> The Outlook.com accounts are "disconnected" when running sandboxed. POP3 is working fine.
i.e. between 5.31.6 and 5.33.1 something has changed which breaks compatibility.

Outlook 2019:
Sandboxie 5.31.6 or 5.33.1 - 5.33.6 and Outlook 2019 is NOT working for Outlook.com accounts. Until now I didn't find any Sandboxie version which is compatible with Outlook 2019 and Outlook.com accounts.

@DavidXanatos
Do you have Outlook 2019 or Outlook 365 installed and could find out what's causing this issue?

A simple way to reproduce this issue would be to start Outlook 2019 or Outlook 365 sandboxed, configure a new account and enter something like "test@outlook.com" (the email address don't have to be valid and password is not necessary yet).
In Sandboxie 5.31.6 -> Outlook does not respond and hangs.
In Sandboxie 5.33.1 - 5.33.6 -> Outlook tells me that "Something went wrong".

@jclarkw
Maybe you can try it out as well, just to make sure that it's not my mistake and I did something wrong on my computer.

If you need any further information, just let me know. Thank you

Cheers
Thomas

 

Thomas -- Do you mean to try only the first step of creating a new email account of unspecified type in Outlook 2019 from within its sandbox? (In other words, using the default template, not the advanced manual setup that I've always preferred?)

Note that I am currently running Sandboxie Plus 5.42.1 and do not plan to revert to 5.33.6. I've never tried to create an account from within a sandbox. I guess I'd be surprised if it worked. I have always set everything up un-sandboxed and only done routine email operations sandboxed. -- jclarkw

 

Hi jclarkw,

thank you so much for looking into that.
Yes, exactly. For outlook.com/live.com or other Microsoft Exchange accounts, it's only necessary to enter the email address (because the autodiscover feature behind is doing everything else). Manual setup (inbound/outbound server address) is only necessary for POP3 or IMAP accounts.

If I set up the account outside the sandbox and start Outlook sandboxed afterwards, it shows only the startup screen ("Opening profile"). Nothing happens after that.
If I set up the account inside the sandbox and try to set up the account, it tells me "Something went wrong."

Previously (in Outlook 2010) I was able to set up the accounts sandboxed as well and everything worked fine. In Outlook 2019 none of the methods above worked properly.

-- Thomas

 

Thomas -- I think I may need more coaching as I am unfamiliar with anything but POP3 accounts. I had Outlook 2019 open already inside it's dedicated sandbox. (By the way, did you set up the sandbox specifically for Outlook? As I recall, there were default selections within Sandboxie for specific email handlers.) I clicked File, then "Add Account," put in your test email address, and clicked "Connect," as shown here:

This caused the following screen to appear (no error message):

Were you expecting an error message already? Otherwise what am I supposed to do next? -- jclarkw

 

David -- The UAC message described at
https://www.wilderssecurity.com/threads/sandboxie-plus-sbie-fork.427755/page-16#post-2941335
Is getting really annoying. What does it mean and what should I do about it? -- jclarkw

 

jclarkw, thanks so much for helping me with that Usually I already got the error message after clicking on "Next", but what is happening if you click on the "Outlook.com" icon on the Advanced setup page?
I tried a completely new sandbox but also checked the "Office Outlook" compatibility option in the Sandboxie settings under "Applications".
-- Thomas

 

Thomas -- This is what I get:

But this doesn't surprise me much, since 1) there is no such account, and 2) I am "working offline" (but connected to the Internet) in the sense that Outlook is set to not automatically check for email. (Again I have no idea how this is supposed to work, since I've never used this type of account.) -- jclarkw

 

Has anyone else seen this behavior with Sandboxie Plus. (Does anyone else even run Windows 10 routinely as a "Standard User?")

I suppose what's happening is that Windows is objecting to changes within the C:\Sandboxie directory as individual sandboxes are opened or closed, although I can't think why or why it never objected before...

Failing explaining what's going on, does any of you Windows 10 experts know how to prevent, or to permanently accept, these UAC notices? --jclarkw