Sandboxie Portable 5.46.4 Dev Test 6

There is no way to install driver without admin rights. In case you're also wondering, the "Sandboxie-Plus" version require it too. Once installed, the driver will be removed completely after system restart/shutdown (since unloading kernel driver is impossible using NSIS native code, I believe).

On my Windows 10 LTSC, Sandboxie will shows that blinking exclamation mark for like a second but then it become normal again. Here is a manual step to analyze by yourself (also written on App\AppInfo\Launcher\Custom.nsh, based on this):

1) Open Command Prompt with admin access. You may need to restart your computer first to completely remove running Sandboxie drivers.
2) Type pushd "SANDBOXIEROOTFOLDER" (eg pushd "D:\PortableApps\SandboxiePortable\App\Sandboxie")
3) Type KmdUtil.exe install SbieDrv "SbieDrv.sys" type=kernel start=demand "msgfile=SbieMsg.dll" altitude=86900 and press enter. Does it show any error?
4) Again, type KmdUtil.exe install SbieSvc "SbieSvc.exe" type=own start=auto "display=Sandboxie Service" group=UIGroup "msgfile=SbieMsg.dll". Does it show any error?
5) Use sc query SbieDrv and sc query SbieSvc to check driver status (running/stopped/not installed)
6) If not started, you can use either KmdUtil.exe or sc.exe to start the services (eg sc start SbieDrv and sc start SbieSvc
7) Start SbieCtrl.exe directly (don't worry, we will clean up any leftover later). Does it start correctly?

Removing leftovers: (close Sandboxie first)
1) Open Command Prompt with admin access
2) Type pushd "SANDBOXIEROOTFOLDER" (eg pushd "D:\PortableApps\SandboxiePortable\App\Sandboxie")
3) Copy and run these commands:

KmdUtil.exe stop SbieSvc
KmdUtil.exe stop SbieDrv
KmdUtil.exe delete SbieSvc
KmdUtil.exe delete SbieDrv
del /F /Q "%WinDir%\Sandboxie.ini"
del /F /Q "%AppData%\Microsoft\Windows\SendTo\Sandboxie*.lnk"
reg delete "HKCR\*\shell\sandbox" /f
reg delete "HKCR\Folder\shell\sandbox" /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Run" /v Sandboxie /f

4) Use sc query SbieDrv and sc query SbieSvc to check driver status. Note that SbieDrv can't be removed completely until restart.

Let me know if you encounter any error.

App does not start and I got an error message (error 557) + The systray icon shows a blinking exclamation mark (no way to start the app)..

The x86 version: Error 1275 + The same symptoms as above except that the "Right-click → Show errors" is working.

Hmm.. strange. I don't think there is any difference between x86 and x64 installation process. Sadly, I don't have any x86 system or Windows 7 to test so I will test it on my Windows 10 x64 later (using Sandboxie x86).

EDIT: Error 1275 means Windows is blocking x86 driver from being installed on x64 machine. Of course you're not meant to install x86 Sandboxie on a x64 machine. As of error 557, I think it is related to Windows Defender (or other antivirus) false positive, simply whitelist Sandboxie directory and check if the error still occur. Kinda strange because Sandboxie driver (SbieDrv.sys) signature is correct.

Other error messages when trying to start the installed version of Sandboxie (after closing the portable one)

This is because my Sandboxie Portable will remove any Sandboxie service & driver (both portable and non-portable). Checking driver and service path is somewhat complicated so I currently have no plan on adding this kind of check (use only one version of Sandboxie, not both). Sandboxie (non-portable) will of course complain about it since the required service was removed. You can install it again by refering to my other reply (use Sandboxie non-portable directory as cmd working dir).

If you still need it for whatever reason, here's the link

It's passworded (1234) to bypass Google false positive (due to unsigned Sandboxie driver)

Also here's a reference if you need to modify something using kmdutil or sandman