[SOLVED]Chrome|Firefox|Etc|SBIE1222 ERROR|After Win Updates*

[cornflake]

Thanks. We're aware of that. But, the only flaw is 4.20. We're testing with Stable v5.04, 4.20 has been deprecated.

I've since tested with 5.04 and otherwise the same configuration and the results are the same. It's 100% reproducible. Windows never saves a crash dump even though it tells me it wrote it to disk.

[John2]

Something very odd just happened. I accidentally clicked the icon to launch my default browser in Sandboxie, and for the first time since this whole SBIE saga began, my computer went straight into BSOD as a result. Do not pass go, do not collect $200. You could tell it was just about to open the browser too. Before it would only occur after FF was open for a while with some of the errors happening, FF on Win 7.

Additionally, I discovered the available space on my hard drive was down around 500 MB from where I had seen it shortly before.

So here's what I'm wondering: did MS push out another update that took up that ~500 MB and is even worse for Sandboxie now, resulting in immediate BSOD even before the SBIE's start popping up?

P.S. Okay, the available space is back up to normal now. So the real question is why clicking the icon would go straight to BSOD like that. Sandboxie is still one of the greatest and one of my most favorite software of all time and I have every confidence the dev team will get to the bottom of this and be able to deal with this latest challenge, just as they have the whole time until now. I routinely recommend it to others and will continue to do so heartily. I hope they are allowed to have access to all the technical information they need to deal with this fallout from the updates.

[vnt]

I have noticed in Firefox 14.0.1 on Vista Home Premium with latest updates, that if you disable (unsandboxed) Shockwave Flash 19.0.0.207 "Protected Mode" option in the FFox Plugin screen under options.... then clear and re-launch firefox in a sandbox that it plays flash content without crashing. Not sure if it plays all... as havn't had the time to check.

I can confirm that disabling "Protected Mode" option in the Plugin settings works as a workaround also for SeaMonkey 2.38 (german localization) and Sandboxie 5.04 under Windows 7 64-Bit.

[Craig@Invincea]

Yes, flash plug in is a known culprit at this time.

[gwseckin]

In addition to SBIE 1222, I'm getting error code SBIC 2314 Canceling process chrome.exe????

[sandboxienev]

Same here.

I got the same errors listed above. I couldn't clear them fast enough, and my machine dropped to a blue screen of errors. I couldn't pull up my phone camera soon enough to get a picture of the BDOD though. I tried again, and if I click away the errors and then close Sandboxie fast enough, my machine doesn't BSOD. I tried re-installing 5.04, had to shut off Bitdefender, still got the same thing. After finding this thread, I guess it's not Bitdefender causing the problem.

Thanks for doing what you can to get Sandboxie up and working again. I really love the protection provided by Sandboxie.

I take it from my scan of this thread that a Windows update caused this and you have to find a work-around.

[Craig@Invincea]

In addition to SBIE 1222, I'm getting error code SBIC 2314 Canceling process chrome.exe????

Yes, If SBIE cannot get the token, Then access is denied. Thus your browser will terminate and close.

[traderskot]

I have just experienced a BSOD crash that appeared to be caused by Sandboxie. I switched from chrome to aviator, a chrome browser, and while I get the same error on starting the browser, by closing the error message box I am able to continue using the browser, unlike chrome, which shuts down. I had been using it without issue since yesterday until a few minutes ago, the error message flashed midway through typing an email and I got an instant blue screen crash. machine not happy now.... when will sandboxie fix the issue? is this dangerous to my machine to continue using it???

[Craig@Invincea]

Same here.

I got the same errors listed above. I couldn't clear them fast enough, and my machine dropped to a blue screen of errors. I couldn't pull up my phone camera soon enough to get a picture of the BDOD though. I tried again, and if I click away the errors and then close Sandboxie fast enough, my machine doesn't BSOD. I tried re-installing 5.04, had to shut off Bitdefender, still got the same thing. After finding this thread, I guess it's not Bitdefender causing the problem.

Thanks for doing what you can to get Sandboxie up and working again. I really love the protection provided by Sandboxie.

I take it from my scan of this thread that a Windows update caused this and you have to find a work-around.

Pictures of the BSOD rarely help, but the dump files they produce might. If you're running FF/or one of it's forks w/ player plug in, that may be your culprit. There is not permanent fix at this time, a work around is posted in the announcement.

[Craig@Invincea]

I have just experienced a BSOD crash that appeared to be caused by Sandboxie. I switched from chrome to aviator, a chrome browser, and while I get the same error on starting the browser, by closing the error message box I am able to continue using the browser, unlike chrome, which shuts down. I had been using it without issue since yesterday until a few minutes ago, the error message flashed midway through typing an email and I got an instant blue screen crash. machine not happy now.... when will sandboxie fix the issue? is this dangerous to my machine to continue using it???

How can it be dangerous to your machine?
The issue is with Windows updates that came out Tuesday. If you read the announcement & are getting similar errors, that's your issue.
If you're using the flash plug in with your browser, this may be the culprit. I cannot comment with Aviator browser as it's not test with SBIE.
There is a work-around solution listed in the announcement.

[bob@jandrpc.com]

I came to report this but see it is being addressed. I expect calls from dozens of people that I asked to install Sandboxie and that use either Firefox or Chrome. I knew it was a Flash related issue as I see two quick Flash messages before the crash. Firefox runs fine without Flash installed. There's not much lost without Flash.

[Craig@Invincea]

I came to report this but see it is being addressed. I expect calls from dozens of people that I asked to install Sandboxie and that use either Firefox or Chrome. I knew it was a Flash related issue as I see two quick Flash messages before the crash. Firefox runs fine without Flash installed. There's not much lost without Flash.

Yep, Flash will fix any BSOD issues. Removing the offending KB will address the token issue as well. So you have (2) issues.... if using Flash w/ any browser (minus Chrome) + and the token issue.

[Mickes]

Firefox and Flash 19 debug version works without problems. I have this tested in Virtualbox with Windows 10.

Download the Flash Player content debugger for Firefox - NPAPI https://www.adobe.com/support/flashplay ... loads.html

[bob@jandrpc.com]

I came to report this but see it is being addressed. I expect calls from dozens of people that I asked to install Sandboxie and that use either Firefox or Chrome. I knew it was a Flash related issue as I see two quick Flash messages before the crash. Firefox runs fine without Flash installed. There's not much lost without Flash.

Yep, Flash will fix any BSOD issues. Removing the offending KB will address the token issue as well. So you have (2) issues.... if using Flash w/ any browser (minus Chrome) + and the token issue.

Here's what actually happens, it helps to fix this issue. I see a quick flash of a grey Flash box in the upper left corner of the screen. Chrome starts. The box flashes again. Chrome runs but no tabs respond. I'm running Chrome 46 on Windows 10 Pro. The only version of Sandboxie that worked until Tuesday, on my machine, was 5.01.11. All other betas up to and including "stable" version 5.04 crashed Chrome where it would not even start. Out three Windows 7 PC's worked fine with Chrome and Sandboxie 5.04.

Best of luck getting it all to work. I'm rooting for you.

[Craig@Invincea]

The issue with Chrome is the token error. SBIE cannot get access and thus it's denied.

Firefox is also a token issue. It also has an issue with Flash if you have that seperate plug in installed.

The updates were Kernel level. Thus, many many many programs can be affected.

It has nothing to do with SBIE vXXX. If you've installed those updates (Again, please read the notice), SBIE will not work to surf web.