Hi Barb, I installed 5.21,6 about 3 hours ago, all I do sandboxed appears to be at least as good as what it was in 5.21.4 and as I reported in an earlier post. As of yet, I don't see any regressions. Windows explorer still cant run properly sandboxed (as you guys know).

vgishmasters, Sandboxie needs our help. Helping them, helps us. Let me explain. A while back, one of the Sandboxie developers told me, fixing issues is the easy part, reproducing problems is whats hard and takes time. Thats were we come into play. If we can help them reproduce an issue by giving them the steps to replicate the problem, then fixing the problem is very likely and takes less time to do it. They cant fix what they cant reproduce. Some issues, the ones that affect every one are easy to replicate but the ones that have to do with specific systems and configurations are not. Thats why it behooves you to give the steps to reproduce your problems and answer the questions when they ask you about your system specs, etc.

Hi ,I have a S.B alert SBIE2205 Service not implemented: ConsoleInit (C00000D4)
I am using windows 10 1709 16299.19
S.B 5.21.6 64 bit
Firefox 56.0.1
Unfortunately the alert is very random. It appeared with beta version 5.21.4 when i opened firefox, after closing the message it did not reappear.
I updated to 5.21.6 and several hours after initially opening firefox it appeared again.
The alert may not be solely related to firefox, it may be that it is the only program i am using sandboxed.
Also i would add, apart from the alert i am experiencing no problems whatsoever.Upon closure the alert does not seem to reappear until reboot.
I am quite happy to just hide the message but thought i would post it, in case it helps in anyway.
Lastly sorry to see Sandboxie has been sold to Sophos, ( news to me ) can't see that ending well

I'm using Sandboxie on Fall Creators Update and noticed a strange behaviour with Chrome in Sandboxie.
I've set up that Chrome is forced to run in a specific Sandbox.
Before Fall Creators Update everything was working fine.
After the update I was using the release Version of Sandboxie and after downloading a file I received many errors before restoring the file.
So I switched to the Beta (I think it was 5.21.4 back then) which fixed the errors.

Everything worked fine for a while but at some time Chrome stopped loading websites in new tabs.
Already running tabs are working fine. When I then try to close Chrome completly it results in Zombie Processes showing up in Task Manager saying the Process chrome.exe belongs to user "ANONYMOUS LOGON".
I can kill the process via Task Manager or use Sandboxies "Terminate Programs" feature, but one process remains open.
When I try to kill that process via Task Manager it says "Access is denied" and killing it via Sandboxie just does nothing.
I have to restart my computer to get chrome working again as it won't start with that lingering zombie processes.

I then updated to 5.12.6 and was running that for a while now until the same happened right now.

I will remove the force Folder feature now and see if it works out of the sandbox (It's hard to reproduce as it just happens randomly).

I am testing now, all looks great for my case use, including running Windows explorer sandboxed. I am able to run explorer sandboxed via sandboxed shortcut or by right clicking folder. Opens fast enough with no messages. I turn off Windows defender and disable Smart screen so I cant test the setting in Miscellaneous but all appears to be fine in my end.

Hi anyone experience this error SBIE2101 "Object name not found: , error OpenProcess (C0000022) access=001FFFFF initialized=1'' too when you use sandboxie 5.20 with chrome on the newest official release of windows 10 update?

Just want to know after the sandboxie 5.22 patch, is everything back to as it should? What I had experienced with 5.20 and latest win10 was that chrome's extension installed in sandbox would be installed too into the original chrome. I'm still feeling a little paranoid even though with 5.22 everything looks normal.

Can any expert explain what had happened which resulted such "leakage" of chrome with sandboxie?

The responses to your first two questions are already covered in the thread. Please read all the posts for more information.
Full support for Windows 10 FCU started with Sandboxie 5.22. So you will need to upgrade to it in order to use that environment.

Can any expert explain what had happened which resulted such "leakage" of chrome with sandboxie?

A change in a Windows 10 FCU API caused the issue. It did not only affect Chrome, but any other program that would use that API. Sandboxie had to be updated to process those new changes and properly sandbox them.
The changes were added in Sandboxie 5.21.6 BETA, tested through Sandboxie 5.21.7 Beta, and then added to Sandboxie 5.22 official release.

I had to delete Sandboxie. It told me it had an update for it and so I let it run and when it finished and my PC was rebooted and it caused my PC to no longer start. It kept giving me and driver error message about the driver Sbiedrv.sys with a Blue screen of death.

I had to go into safe mode and delete the program in order to get my computer to start again.

Also, can I please get you to upload the crash dump file so that the devs can investigate it?
It is typically found under C:\Windows --> Memory.dmp
You can upload it to a free file hosting website and paste the link here, or , if you do not want to post the link here, you can send it to support@sandboxie.com