Windows 10 Sandboxie problem. Could not start Sandboxie. Reinstalled the latest version. Still won't start.

[Tom Walsh]

Could not start Sandboxie. Reinstalled the latest version. Still won't start. Messages I receive.

1. SBIE2331 Service start failed: [22/5] Access denied.
2, The Sanboxie driver (SbieDrv) is not available to sandbox programs. Nake sure both the driver and Sondboxie service (SbieSvc) have started seccessfully.

Been using Sandboxie for years with no problems until now. Only change is Windows 2004 was installed on this computer and 4 others. This is the only one Sandboxie won't start on.

 

[th3m]

You need to reinstall, i guess the SbieDrv.sys driver got uninstalled or deactivated for some reason.

Also Sandboxie is open-source nowadays so i should check a better optimized version you can get here:
https://github.com/sandboxie-plus/Sandboxie/releases

Last but not least, if you have Windows Pro or better, don't bother with Sandboxie and check Windows Sandbox instead.


EDIT: when i said reinstall, i meant clean install. Remove it completely with something like Revo uninstaller or BCUninstaller and then install again.

 

[cndps]

The problem could be because you are not installing as admin. No admin access, not able to install the driver.
Follow th3m instructions...

 

[Tom Walsh]

I have reinstalled several times. Same result. One from github.com.
Windows Sandbox is useless to me. I run Key Pass and RoboForm and use them constantly. I can install both in Windows Sandbox, but when I exit the sandbox, they are gone.
I use Revo Uninstaller Pro to remove any program I want gone.
I will try installing the program as Admin, although my other 4 computers worked fine after Windows 2004 update. All 5 computes are running Windows 10 Pro.

 

[DVDR_Dog]

Just a guess but it appears Windows isn't liking SbieDrv . Could be a digital signing problem. Unfortunately this may not be as easy as cleaning out the registry with Revo or CC. Sometimes in it's wisdom Windows remembers things anyway.
The big question becomes why do your other 4 work fine? There's your answer. Could be SbieDrv was grandfathered during the upgrade to 2004 on the other 4 machines and this 5th was installed at a different time or just the opposite. I've heard of this happening before and it was always some kind of screwy permission problem with SbieDrv and now that it's open source not sure how they are slipping that driver in.
As I said this problem is nothing new, not sure if the open source project maintains a public forum or not but that's your best bet. You may even be of help trying to solve this puzzle.

 

[Tom Walsh]

I have reinstalled Sandboxie as administrator. Still get same error message.

 

[DVDR_Dog]

I have reinstalled Sandboxie as administrator. Still get same error message.

It appears that the world is aware of the problem. No one has come up with a definitive answer. It may be Microsoft may have altered some things as a security update. I’ll post a solution if a universal fix becomes available.