Model 1 and 2 give error starting powershell "SBIE2211 Sandboxed service failed to start: CryptSvc"

K

KaloKerl

New member
Hi

Tested on a clean standard box with model 1 and 2.

Error is always: SBIE2211 Sandboxed service failed to start: CryptSvc

INI:

Code: 
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%Desktop%
RecoverFolder=%Personal%
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
BorderColor=#02f6f6,ttl,6,192,in,6
Template=AutoRecoverIgnore
Template=LingerPrograms
Template=BlockPorts
Template=qWave
Template=FileCopy
Template=SkipHook
Template=OpenBluetooth
ConfigLevel=10
AutoRecover=y
AutoDeleteSnapshotTarget=Current

OS: See attached sysinfo

Box: 1.18.2



Do you have any advice?

Thanks
Holger
 

Attachments

Works with 1.17.3

BTW: SbieDrv is a pain in the a**

Won't uninstall, can't be stopped with "C:\Program Files\Sandboxie-Plus\kmdutil.exe" stop SbieDrv

Always gives me "Driver busy try 1 2 3". And the Fan is blowing like mad. Every install of Sandboxie forces a reboot.

Will now test 1.17.4
 
Works with 1.17.4

I test with sandboxed start of "powershell" (implicit call to Crypt) and start "cmd" then "net start cryptsvc"

Now 1.17.5

BTW. Upgrading does not work. I have to uninstall (complains about SbieDrv not being removed), Reboot, delete all remains (SbieDrv) and then install.
 
So, now i'm here, all the way through to 1.18.2 and everything just runs fine.

until i created a new default box. Now, error SBIE2211 appears again... in both boxes.
 
In my environment, the bug has been introduced with 17.9

  • Install Sandboxie
  • Create a new Default Box
  • Start cmd
  • enter "net start cryptsvc"
 
Nope, also in 17.8

The bug is not 100% reproducable. Sometimes it only shows when sandboxie is closed via taskbar icon and then startet again.

All this installing and testing is getting a bit tiresome after 2 hours...

I'll revert to 17.3 like in the issue and see what happens...
 
You must log in or register to reply here.
Back
Top