5.11 Beta Available (latest version 5.12 RC)

[cxmhiiemn00]

I experienced frequent BSOD with Sandboxie 5.11.4 with Windows 10 Preview 14316 x64 and Windows Defender. I reinstalled my OS recently so I doesn't have WinDbg now, but an online dump file analyzer suggests that the stack trace of system crash is related to Sandboxie.

Code: Select all

STACK_TEXT:  
ffff8981`83bfda08 fffff802`03ff9acf : 00000000`00000050 ffff9f06`21e21000 00000000`00000000 ffff8981`83bfdcf0 : nt!KeBugCheckEx
ffff8981`83bfda10 fffff802`03ee6fab : 00000000`00000000 00000600`00000000 ffff8981`83bfdcf0 ffff9f06`2570bdd0 : nt! ?? ::FNODOBFM::`string'+0x2447f
ffff8981`83bfdb00 fffff802`03fcfafc : fffff802`040b9dc0 fffff802`03eebf7e 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x8db
ffff8981`83bfdcf0 fffff802`03f07ca4 : fffff809`9a210fc2 ffff8981`83bfe120 00000000`0000001c ffff8981`83bfe160 : nt!KiPageFault+0x13c
ffff8981`83bfde88 fffff809`9a210fc2 : ffff8981`83bfe120 00000000`0000001c ffff8981`83bfe160 ffff8981`83bfe120 : nt!RtlInitUnicodeString+0x14
ffff8981`83bfde90 ffff8981`83bfe120 : 00000000`0000001c ffff8981`83bfe160 ffff8981`83bfe120 ffff9182`c8ce347b : SbieDrv+0x10fc2
ffff8981`83bfde98 00000000`0000001c : ffff8981`83bfe160 ffff8981`83bfe120 ffff9182`c8ce347b ffff9f06`0f43c008 : 0xffff8981`83bfe120
ffff8981`83bfdea0 ffff8981`83bfe160 : ffff8981`83bfe120 ffff9182`c8ce347b ffff9f06`0f43c008 ffff9f06`00000000 : 0x1c
ffff8981`83bfdea8 ffff8981`83bfe120 : ffff9182`c8ce347b ffff9f06`0f43c008 ffff9f06`00000000 ffff9f06`21e20f82 : 0xffff8981`83bfe160
ffff8981`83bfdeb0 ffff9182`c8ce347b : ffff9f06`0f43c008 ffff9f06`00000000 ffff9f06`21e20f82 00000000`00000000 : 0xffff8981`83bfe120
ffff8981`83bfdeb8 ffff9f06`0f43c008 : ffff9f06`00000000 ffff9f06`21e20f82 00000000`00000000 00000000`00000000 : 0xffff9182`c8ce347b
ffff8981`83bfdec0 ffff9f06`00000000 : ffff9f06`21e20f82 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9f06`0f43c008
ffff8981`83bfdec8 ffff9f06`21e20f82 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00020019 : 0xffff9f06`00000000
ffff8981`83bfded0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00020019 00000000`00000000 : 0xffff9f06`21e20f82

[Curt@invincea]

I experienced frequent BSOD with Sandboxie 5.11.4 with Windows 10 Preview 14316 x64 and Windows Defender. I reinstalled my OS recently so I doesn't have WinDbg now, but an online dump file analyzer suggests that the stack trace of system crash is related to Sandboxie.

This has been fixed and will be in the next Beta in a couple of days.

[Abdullah]

I have an old new problem when upgrading SBIE, the installation stuck and I have no choice other than uninstall/install it again.

I think I can stop SBIE services before upgrading but I am not sure.

Any suggestions ?

Abdullah

[Craig@Invincea]

I have an old new problem when upgrading SBIE, the installation stuck and I have no choice other than uninstall/install it again.

I think I can stop SBIE services before upgrading but I am not sure.

Any suggestions ?

Abdullah

Upgrading from what version?
uninstalling and copying the settings is a good solution.

[henryg]

Few things to try. [The Template is present & invoked when SBIE detects Office, even if you're *Not* a paid user, if you're not a paid user, that template will simply not work even if selected]
1. Stop the C2R Service. Then totally uninstall SBIE. (that'll help in removal of SBIE injection to C2R)
2. Reboot.
3. Reinstall SBIE 11.5.4 (if you copied settings, make sure that SB contents are empty.)
4. RESTART the C2R Service.

Fire up Word, etc in a SB.

Followed instructions but still doesn't work for me! Can't work out what I am doing wrong. Have paid version of course.

SB v11.5.4, Win 10 64bit

[Abdullah]

Upgrading from what version?
uninstalling and copying the settings is a good solution.

I saw this many times, and lately in 5.11.4

Yes, I have to uninstall first, but for me it is not an ideal solution.

Abdullah

[Abdullah]

BTW, I tried KAV last year and uninstalled it ( even KAV removal tool didn't detect any traces ) , but it is still exist in the SBIE compatibility list suggestions after uninstalling/installing SBIE !

Is it something in SBIE or I have to remove some KAV traces manually ?

Abdullah

[bo.elam]

BTW, I tried KAV last year and uninstalled it ( even KAV removal tool didn't detect any traces ) , but it is still exist in the SBIE compatibility list suggestions after uninstalling/installing SBIE !

Is it something in SBIE or I have to remove some KAV traces manually ?

Abdullah,you can delete the KAV Software compatibility settiung from your Sandboxie config file. Go to Sandboxie control>Configure>Edit configuration, Delete the Template for KAV under Global settings.

I haven't used many programs for which I tick Software compatibility settings but I remember one program in particular, that after uninstalling the program, the Software compatibility setting still showed up in Sandboxie control. I dont recall if I got rid of it the way I wrote above or another way. But you can safely remove it by deleting the Template line. I don't believe the template remaining means that you still have remnants from KAV. Probably something remains but I don't think that has anything to do with the template still showing in the Software compatibility window.

Bo

[Craig@Invincea]

there could be a GUID trace in your registry......

but first remove the line in the SBIE template regarding KIS.

And then see if that clears it. If not, I can post the KIS GUID that you would need to remove in your registry that SBIE looks for.

[bo.elam]

but first remove the line in the SBIE template regarding KIS.

And then see if that clears it.

It will.

Bo

[Curt@invincea]

5.11.5 has been released.

[bo.elam]

5.11.5 has been released.

So far, so good. I cant find nothing wrong with this version. All running smooth (XP W7 32 bits) . Note. Curt, FWIW, in this version I did not see the Windows message I told you I saw in the previous 3 maybe 4 versions of this beta, immediately after installing over the top (W7 32 bits).

Bo

[Optimus_prime]

Working fine with Windows 10 Insider Preview Build 14332

[Craig@Invincea]

Working fine with Windows 10 Insider Preview Build 14332

If you're running pure 32 bit, then yes. The issue is with WOW64. It's random depending on the programs, Especially 64bit OS and 32 bit OS.

[Curt@invincea]

5.11.6 has been released.