Sandboxie Support

All,

Please try the latest beta 5.21.7 for full support for Windows 10 - Fall Update.

Here's a list issues that have been addressed:

- ReplaceFileW windows API function is causing a leak into the host. For example, Chrome extensions may leak outside the Sandbox and corrupt the host ones when trying to update them inside Sandboxie. [Fixed in Beta 5.21.6]

-Right-clicking on sandboxed Windows Explorer files/folders crashes explorer for 5 minutes (after 5 minutes or so, the right-click action starts working). Fixed in beta 5.21.7

-"SBIE2101 OpenProcess(C0000022) access=001FFFFF initialized=1" when using "OpenWith" via a Sandboxed Explorer --> Related to Windows Defender. Fixed in Beta 5.21.7

Please feel free to reply with any new issues you encounter while using the latest Windows Insider v17017 (Fast Ring), or once you receive the Fall Update and the latest Sandboxie beta.
Before posting a problem, be sure to test it in a new Sandbox with default settings + Sandboxie latest beta. If the issue persists, provide this information:
viewtopic.php?p=104180#p104180

For questions regarding betas (as well as download links), please see:
viewtopic.php?f=62&t=24741

Regards,
Barb.-

PS: Off-topic messages will be deleted. This thread is for windows Creator's Fall Update issues + Sandboxie latest beta ONLY.

I can confirm this -"SBIE2101 OpenProcess(C0000022) access=001FFFFF initialized=1" when launching certain apps. on sandboxie 5.20 with portable application ( firefox. opera. teamviewer) on windows 1703 Creators update(i stayed on it till you will release 5.21 for windows 1709)

vgishmasters wrote: ↑

Wed Oct 18, 2017 2:13 am

I can confirm this -"SBIE2101 OpenProcess(C0000022) access=001FFFFF initialized=1" when launching certain apps. on sandboxie 5.20 with portable application ( firefox. opera. teamviewer) on windows 1703 Creators update(i stayed on it till you will release 5.21 for windows 1709)

You need to update to latest beta 5.21.4.

Bo

Hi Barb, I upgraded my W10 64 bits laptop to FCU. I am glad to report that despite Sandboxie not officially supporting the Fall Creators Update as of yet, all programs and functions I run sandboxed work excellent in my laptop. I tested Firefox 32 bits, Internet explorer 11, Libre Office portable, Foxit portable, 7Zip, KMPlayer, Irfan view and Windows media player. Also, forcing my Download folder and forcing USB drives worked as good as ever.

Regarding the 2 known issues you reported in the opening post, I cant test Chrome as I dont install it in my real system but I can confirm the problem sandboxing Windows explorer. I dont open sandboxed Windows explorer by right clicking it but by clicking on a sandboxed shortcut. I waited about 25 seconds, and it didn't open. Thats really the only poblem I found using SBIE in W10 after updating to the FCU.

Let me point out something that might give the developers a clue for fixing the Windows explorer problem. I tested forcing my USB drives, it worked as good as ever. And lets remember, when you force USB drives, and you plug in one, the USB folder pops up open using a sandboxed version of Windows explorer. So, when forcing USB folders, Windows explorer runs sandboxed automatically with no delay. Maybe knowing that gives a ckue.

I saw this message below when using File explorer while navigating folders when running Firefox sandboxed. It can be hidden and doesn't cause any issues. Is a new message, I never seen it before. I discovered it while saving videos in YouTube. Easy to reproduce.

Bo

unluckily i missed this thread and update to the latest win10 update
now sandboxie is useless, SBIE2101 for firefox, chrome, media player classic, basically any app
so folks dun be so silly to update your windows unless u dont need sandboxie

Hello lopezgreat,

Please follow the guidance in the original post and provide the info required so that I can test your issue.

Regards,
Barb.-

os: win10 x64 1709 home edition
sandboxie: 5.20 64bit
firefox: 56.0 64bit
chrome: 61.0.3163 64bit
media player classic: 1.7.11.24

all showed SBIE2101 when run inside sandboxie, then quitted itself

Hello lopezgreat ,

Please see the original post, you need to use the latest beta.
Sandboxie 5.20 was released on June 2017, so it will not work with major Windows 10 updates released after that time.

Regards,
Barb.-

unfortunately same result

Hello lopezgreat ,

UPDATE---> Still unable to repro with latest beta + Creator's Fall Update
-----------------------------------------------------------------------------------------------------------------------------------------------
I am unable to repro the issue in the Fast Ring, I am currently updating my stable Win 10 to 1709 and will re-test then.

Do you have any security software installed?
Is the issue occurring in a new Sandbox with default settings + Sandboxie's latest beta?

Please post a copy of your Sandboxie configuration file: Configure--> Edit Configuration
Paste the contents here and edit them using the "</>" button.

I'll recreate your settings to see if that helps me reproduce the problem.

Regards,
Barb.-

If you "register" your Google Account in Chrome (sandboxied) you get also a registered chrome outside of the sandboxie.

it's a little sadly that we still doesn't have new stable version, and most disgusting that developers has not ETA. Good program, but with new windows redstone 3, it is incompatible. So we hope that devs will make all faster for compatibility problem solution.

All,

Beta 5.21.6 is out . It addresses the leak issues, please give it a go.
See original post for more information.

Beta section:
viewtopic.php?f=62&t=24741

Regards,
Barb.-

2nd Problem with Sandboxie 5.21.4 Beta and Windows 10 Pro 64-bit v 1709. Got Windows Blue Screen after I tried to create a new sandbox. Webroot was not running.

* Windows 10 Pro 64-bit, v 1709, build 16299.19
* Sandboxie 5.21.4 64-bit Beta
* Chrome 62.0.3202.62, 64-bit
* Webroot SecureAnywhere 9.0.18.38 (not running)

Blue Screen Problem:
* Stop Code: Page Fault in a non-paged area
* What Failed: SbieDrv.sys

Hello northch,

I am trying to get Webroot, but after using 2 different email addresses, both codes they sent me are incorrect. Running out of ideas (will give it a go again tomorrow).

Regarding the bsod, please provide the crash dump so the devs can have a look (Typically found under C:\Windows -->memory.dmp)

Are you able to reproduce it again? Does it occur if you uninstall your Antivirus software (disabling sometimes doesn't help).
Also, please try the latest beta (5.21.6).

Regards,
Barb.-