Chrome Extensions Crash
- Thread starter HiddenWindow
- Start date
BilleBarrett
New member
My Chrome has been crashing and crashing since several Sandboxie updates, I setup my extension unsandboxed and when I open Chrome Sandboxed my extension are trashen, my start up link are gone.
then I get errors:
04.07.2026 10:23:49.484 chrome.exe: SBIE2112 Object is not accessible: \device\namedpipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-620072444-2846605723-1118207114-1642104096-81213792-2370344205-2712285428\_Sandbox_BilleB_DefaultBox_Session_1, call CreateFile (C0000034) access=001F0006 initialized=1
At this point I can't use Sandboxie to do my work
I keep sending the error to somewhere and nothing is getting done
This is totally unexcitable, and I have 2 licenses that I renew every year and have for years
Please fix these issues or help with my settings, I have uninstalled and reinstalled several times
I will give you access to my PC to figure this out
PS my clients are complaining about the same thing
Bill e. Barrett
[email protected]
then I get errors:
04.07.2026 10:23:49.484 chrome.exe: SBIE2112 Object is not accessible: \device\namedpipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-620072444-2846605723-1118207114-1642104096-81213792-2370344205-2712285428\_Sandbox_BilleB_DefaultBox_Session_1, call CreateFile (C0000034) access=001F0006 initialized=1
At this point I can't use Sandboxie to do my work
I keep sending the error to somewhere and nothing is getting done
This is totally unexcitable, and I have 2 licenses that I renew every year and have for years
Please fix these issues or help with my settings, I have uninstalled and reinstalled several times
I will give you access to my PC to figure this out
PS my clients are complaining about the same thing
Bill e. Barrett
[email protected]
The issue is cause by chrome locking the settings to the Application Bound Encryption mechanism, which is mediated by the GoogleChromeElevationService (elevation_service.exe) which a sandboxed process can not access.
A green box with ```Template=OpenCOM``` works fine, but obviously is not the best choice in many scenarios.
We have devised a workaround first we force "Secure Preferences" to be migrated into the sandbox also on read accesses and during that process we remove all "*_encrypted_hash" entries this makes chrome fall back to the old HMAC based verification which we bypass by making chromium think the PC is domain joined by making IsOS(OS_DOMAINMEMBER) returns TRUE this makes chrome skip the check.
Please try out the x64 SbieDll.dll attached to the latest issue: https://github.com/sandboxie-plus/Sandboxie/issues/5184
A green box with ```Template=OpenCOM``` works fine, but obviously is not the best choice in many scenarios.
We have devised a workaround first we force "Secure Preferences" to be migrated into the sandbox also on read accesses and during that process we remove all "*_encrypted_hash" entries this makes chrome fall back to the old HMAC based verification which we bypass by making chromium think the PC is domain joined by making IsOS(OS_DOMAINMEMBER) returns TRUE this makes chrome skip the check.
Please try out the x64 SbieDll.dll attached to the latest issue: https://github.com/sandboxie-plus/Sandboxie/issues/5184
bjm_
Member
1.18.0 - Enable Sandboxed Elevation Service (Chrome, Edge, Brave, etc...) works my side. Brave, Edge, Chrome profile was okay after running Chromium based browser internal updater. I maintain Chromium based browser Services at Manual. Before calling browser update. I'll turn on Enable Sandboxed Elevation Service and turn off Enable all security enhancements (make security hardened box). After confirming browser profile survives update and before calling browser discrete sandbox. I'll turn off Enable Sandboxed Elevation Service and turn on Enable all security enhancements.
as always, your mileage may vary
as always, your mileage may vary
Last edited: