4.19 Beta Available (Latest Version 4.20 RC)

[Mr.X]

4.19.4 has been released.

Thank you.

[Arbie]

FYI, this fixed a Windows 10 installation problem I was having. The latest stable release would download and install properly up to the last step (the driver). That threw an error which I simply accepted. Afterwards the main control window would not open, saying "user unknown; config won't be saved" etc.

This v4.19.4 beta installed fine all the way through and in limited testing seems normal.

Thanks

[otyg]

tested windows 10 (64bit, 10130), I don't mind testing since windows 10 is just installed to a vhd and I can revert back to my old os,....anyways everything seemed to go good -installed fine started up ok, but then I started getting error
I keep getting this error whenever I try to run something in the sandbox and it just loops until I force terminate, I tried to uninstall , reinstall , change paths ..etc dunno how else to debug...I even deleted the sandboxie.ini
SBIE2204 Cannot start sandboxed service RpcSs (-1)
SBIE2204 Cannot start sandboxed service RpcSs (-1)
SBIE2204 Cannot start sandboxed service RpcSs (-1)
SBIE2204 Cannot start sandboxed service RpcSs (-1)
SBIE2204 Cannot start sandboxed service RpcSs (-1)
SBIE2204 Cannot start sandboxed service RpcSs (-1)

[nanana1]

Another Windows 10 tester reported this :

Tried 4.19.4 x64 on Windows 10 Pro Insider Preview 10147 x64 & got this :

SBIE2205 Service not implemented: SetWindowLong8
SBIE2318 DLL initialization failed for 'user32.dll'
SBIE2205 Service not implemented: SetWindowLong8
SBIE2318 DLL initialization failed for 'user32.dll'
SBIE2205 Service not implemented: SetWindowLong8
SBIE2318 DLL initialization failed for 'user32.dll'
SBIE2224 Sandboxed program has crashed: SandboxieRpcSs.exe
SBIE2205 Service not implemented: SetWindowLong8
SBIE2318 DLL initialization failed for 'user32.dll'
SBIE2205 Service not implemented: SetWindowLong8
SBIE2318 DLL initialization failed for 'user32.dll'

[Peter2150]

The release notes for 4.19.4 don't say a thing about windows 10. Not surprised it doesn't work

[bo.elam]

Hi Curt, something that's working differently with 4.19.4 is Hiding the 2314 SBIE message. Before, with 4.19.3, the settings below took care of all SBIE messages when running Foxit sandboxed.

SbieCtrl_HideMessage=2314,FoxitReaderUpdater.exe
SbieCtrl_HideMessage=1308,FoxitReaderUpdater.exe [Foxit] *

Now, every time I run a PDF, I get a new SBIE message 2314 with a different code at the end. The code changes every time I run a PDF. So, despite hiding the message, the next time I open another PDF, I get another 2314 message with a different code. Like the ones below.

SbieCtrl_HideMessage=2314,FoxitReaderUpdater.exe [5640 / 0]
SbieCtrl_HideMessage=2314,FoxitReaderUpdater.exe [3292 / 0]
SbieCtrl_HideMessage=2314,FoxitReaderUpdater.exe [4684 / 0]
SbieCtrl_HideMessage=2314,FoxitReaderUpdater.exe [4592 / 0]

Other than not being able to hide the message for good, Foxit is working properly under this version (as in the past). I am using Foxit portable and this is in my W7 32 bits laptop.

Bo

[Curt@invincea]

Bo, we're trying to add more detail to the SBIE2314 to find out why some processes are terminating, so we added [PID / reason code]. Reason code = 0 means that the process never really started. Most likely due to a DLL being blocked. So for reason code = 0, I will change it so the PID and reason are not part of the error message, so hiding it will work as before. Thanks for letting us know. Are you getting any other reason codes besides 0?

[stonerd]

just wanted to post and say i see no loss in function with the latest beta on windows 8.1.

i tried a slew of programs. office software, media players and converters, steam... a bunch of crap, no changes to functionality.

[bo.elam]

Are you getting any other reason codes besides 0?

Reason codes show 0 every time.

Bo

[otyg]

The release notes for 4.19.4 don't say a thing about windows 10. Not surprised it doesn't work

True, whats strange is it actually worked once or twice where a few programs started sandboxed but then degraded and now I can get nothing to start in it and it just loops that message....

Edit - seems like sometimes it will work most of the time it doesn't probably some kind of race condition.
Edit2 - I noticed it is spawning two SbieSvc.exe processes (not sure if that's normal)
SbieSvc.exe
- SbieCtrl.exe
- SbieSvc,exe
^if I kill this sbieSvc.exe then run something in the sb it will work 40% of the time, then the service re-spawns and have to repeat.

oh yeah the separate 64bit installer also creates wrong shortcuts in the sendto menu where it points to the Program Files (x86) - non existent sandboxie folder (it should point to :\Program Files\ - this doesn't seem to effect the all in one installer though, either that or something is really buggered with the os - non the less tiny bug -

oh well looking forward to more builds.

[Craig@Invincea]

The release notes for 4.19.4 don't say a thing about windows 10. Not surprised it doesn't work

Yes, nothing directly tied to Windows 10. This is something we are still working on.

[Curt@invincea]

4.20 Release Candidate is available.

[Mr.X]

4.20 Release Candidate is available.

Thank you.

[bo.elam]

Hi Curt, the error that got fixed is 2314, you wrote 2313 in the first page of this thread.

Bo

[Mr.X]

Hi Curt, the error that got fixed is 2314, you wrote 2313 in the first page of this thread.

Bo

Yup. Besides it says: Fixes in 4.20 instead of 4.20 RC