Released Sandboxie Plus (Sbie fork) Versions with Signed Driver

Hi Stapp. When you say "clean install", do you mean when you uninstalled the previous version of sandboxie you also selected the option to remove the sandboxie ini file that has all your settings? Or is it OK to uninstall sandboxie, preserve your ini file, and then install 5.45.0? I'll be moving from 5.43.7 to 5.45.0. on Win10.

 

Yes, it's okay to Uninstall Sandboxie and preserve ini file moving from Sandboxie 5.43.7 to 5.45.0. on W10.
That's what I did.
Then I clean installed Sandboxie-Plus 0.5.0 .... preserving ini file.
I always preserve ini file with Uninstall Sandboxie/Sandboxie-Plus.
I have copies, too.

 

I just installed version 5.45.0, after first uninstalling version 5.43 and rebooting. For some reason windows defender throws all kinds of errors at me whenever SBIE tries to run. I set the required exclusions for it to work before, due to the unsigned cert. With this version, as I understand it, the cert has been signed on Windows 10. I can't understand why I'm still getting Defender interference. With Defender real-time scanning everything works fine. What must I add to get SBIE to work right. Here are my exclusions.

Thanks!

 

Thanks.

 

Hi @DavidXanatos

I just removed the old exclusions I'd had set up in Windows Defender and Malwarebytes Antimalware for the SbieDrv.sys, then I uninstalled 5.43.7 & rebooted. Then I installed 5.45.0. No problems with Windows Defender, but Malwarebytes immediately blocked SbieDrv.sys saying it is a trojan. I selected "always ignore" in MBAM, but unfortunately the installation was borked after that so I uninstalled and reinstalled 5.45.0. This time no complaints from MBAM, but the new driver was already added to exclusions before reinstalling.

I read where you said on github that Sandboxie should automatically rename the SbieDrv.sys.w10 file to SbieDrv.sys. It does not look like this has happened on my system though (Windows 10 1909). Here is a snip of my Sandboxie folder.

Do I need to delete Sbie.Drv.sys and rename the w10 file as per the comment on github?



EDIT: When hovering over the SbieDrv.sys file with my mouse, it does say it is version 5.45.0, unlike the person on github.

 

@catspyjamas
No that looks fine the file is also the same size as the *.w10 when you view the file properties you should see a tab with the certs and two signatures in it one for testing and the other from the MSFT Hardware portal.

 

@DavidXanatos
Ah thanks. Yes I do see those digital signature fields in both the .sys and the .sys.w10 files. I interpreted your comment on github to mean that the SbieSvc.exe thingy should magically transform that SbieDrv.sys.w10 file into the new .SbieDrv.sys file, so that on completion of the installation you would not see the .w10 file in the list at all. Good to know as I have another 3 machines to update now!

Thanks for all your work! It's so appreciated!

 

What do we do with the windows 7 situation? Providing separate installers would mean 8 downloads in total that's not good.

I'm not sure on what timescale the signature issue can be properly resolved, as of now just hoping MSFT will answer on the issue with a solution.
You could help by up voting the issue: https://answers.microsoft.com/en-us...-signing/ad230fb1-df94-4992-a937-3afd52249a36

I could make the installers for windows 10, without the obfuscated driver and provide a separate installer for a "Windows 7 x64/x86 compatibility pack".

This way the 4 installers would be 100% clean and could be signed such as to get instant reputation with MSFT Smart Screen, and alike, no more browsers not wanting to download them.

 

I think that solution with a separate compatability pack for those remaining on W7 sounds like a good idea if a way to get working as it should is not found soon, especially as that would mean 4 100% clean installers and an instant good reputation with MSFT Smart Screen. Some average users may not know the trick with MSFT Smart Screen to bypass the "don't run" option - it's deliberately made obscure. Also some AV/AM software is still blocking SbieDrv.sys like happened to me with MBAM. It messed up the installation even after choosing always ignore. Some people (I mean average users/non-Wilders people) might also be put off the software and query it's trustworthiness with those issues still present, which would be a shame because Sandboxie is awesome!

 

@DavidXanatos New version working fine, grouping seems not OK, you can create a new group when you right click on empty space, but you can't move boxes in. You only have "none".

Also if you ran Sandboxie before you want to overinstall or uninstall, the driver will not be removed and even if after a new start you can install fresh, it ends with no admin rights and finaly empty plus gui and error -2, which doesn't say much. However uninstall, restart, new install will fix.
Just the error -2 is a bit cryptic.

 

Related > Sandboxie doesn't upgrade properly from 5.44.1 to 5.45.0 #208
https://github.com/sandboxie-plus/Sandboxie/issues/208#issue-758724406

 

done

 

David, thank you very much for this progress. Much appreciated by me and clearly by so many others. You can now enter the Hall of Fame for internet heroes.

SUGGESTION: Could you put the install-over-previous-version instructions contained in
https://github.com/sandboxie-plus/Sandboxie/issues/208#issue-758724406
within the github article above the download button, probably with a separate subheading. I stood on my head trying to get the new version installed (details now irrelevant), then I found @-bjm's post just above, and all is solved (and thanks again to @_bjm for rescuing me a second time).

 

I've used the Sandboxie 45 exe file to uninstall Sandboxie 44.1 and, then, without any restart, I've used the same exe file to install Sandboxie 45.
And I'm currently using it.
I'm very happy.
Thank you, David.

 

Well, is not a big deal, worse is, to have the driver signed and that the antivirus continue seeing virus in the installer. That way I can't recommend this program to anyone because they will think it is a trojan or something like that.

Voted!

If u don´t want 8 different packages, maybe u can create 4 packages with 32 and 64 bit versions included autodetecting the system host (32 or 64 bits) and installing the correct version.

 

I would do/like that.

 

+1

 

I have renamed the old installers by adding "for windows 7" to them and re uploaded 4 new once without the provisionally signed driver.

I have also added a note about re installing.

About the "Windows 7 x64/x86 compatibility pack" that's not a workable solution, as every update would first break the instalation than a new support pack would have to be installed, and so on...

 

Thanks for providing a "clean" installer for W10.

At this point there is no reason to keep using the Sophos version. I would even close the thread dedicated to the old sandboxie, as it only generates confusion, cause David version is the real and usable open source version.

 

Thanks for your hard work and for keeping Sandboxie alive!
I've just tried to download SandboxieInstall64-v5.45.0.exe and Firefox reported that the file might be unsafe and the downloaded file size is 0 KB. It seems that you've only signed the included driver. Can you also sign the whole setup file? Thank you David!

 

Why? Sophos is still working perfect for me.
Acadia

 

Because it has unfixed sandbox escape and privilege escalation vulnerabilities.

 

I have been holding back downloading anything past the last Sophos v5.33.6.
@stapp (or anyone) With apologies, and so as not to have to pick through this entire thread would you be kind enough to post the link David's now signed Sandboxie ...
And any special instructions to fresh install - or upgrade (with any previous settings preserved) - to this latest (v5.45?)?
I primarily use Firefox (Win 10 only as per sig) and would just want the Classic, rather than the Plus version.