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

[ssj100]

I don't think the Chrome installer has ever run inside Sbie.

Hi Curt. I never have installed Chrome in my real system. But I have tested Chrome a few times by installing it sandboxed. The installer does run sandboxed and the installation goes thru just fine, at least for me it does. To verify nothing has changed in that regard, a few minutes ago I ran the Chrome web installer and all went well. But I agree with Craig, I think installing Chrome for keeps in a sandbox is a bad idea and doing so will certainly pop up many errors after a few days or so. I tested in W7 32 bits.

Bo

Yes, I've installed Chrome directly inside Sandboxie for the last couple of years without trouble. Haven't tested with the latest update yet (had to uninstall it due to errors as noted earlier in the week).

[jclarkw]

Link to the forum topic here detailing the fix http://forums.sandboxie.com/phpBB3/view ... 54&t=21855
Direct link to the combo installer here: http://www.sandboxie.com/SandboxieInstall-505-2.exe

You just run the installer and have it over write your current installation. That's it.

Perfect! -- Between 5.05.2 and an update for Adobe Flash that Firefox recommended, all is good, even without taking Flash out of protected mode. You guys are great! -- jclarkw

[Hunter]

Thanks for fixing it.
Good job.

[electronpn]

Getting SBIE2314 cancelling steamweb. Cant work in steam. Found the solution. Uninstalled windows patches 3096447, 3096440 and 3096443. Dont know who s the right one to uninstall. Now it works as charm, till these guys publish new installation version.

[jw72253]

A new flash player plugin was just released today, with which this problem no longer occurs while running 64-bit SBIE 5.04 in latest Firefox and Windows 10 Pro. Adobe fixed its issue with the browser, with which SBIE was not cooperating. If you were foolish enough to have removed the Windows security update KB, you should reinstall it now. You also may want to reevaluate your priorities concerning good advice versus bad advice.

[sandboxienev]

Win7, Firefox in Sandboxie. I use it every day. I was getting the whole certificate and other errors, follwed by a BSOD and hard boot. Terrible!

I installed 5.05.2 beta. Now I could use Firefox in SB, but every time I closed Sandboxie I got the "could not delete" problem. I uninstalled SB, deleted the DefaultBox folder, reinstalled 5.05.2 beta. Delete and everything seems good now.

Thanks to Sandboxie crew for fixing this.

[Craig@Invincea]

Win7, Firefox in Sandboxie. I use it every day. I was getting the whole certificate and other errors, follwed by a BSOD and hard boot. Terrible!

I installed 5.05.2 beta. Now I could use Firefox in SB, but every time I closed Sandboxie I got the "could not delete" problem. I uninstalled SB, deleted the DefaultBox folder, reinstalled 5.05.2 beta. Delete and everything seems good now.

Thanks to Sandboxie crew for fixing this.

Glad it worked.

[huldu]

It this really fixed? It has caused some serious issues on my computer. It started a few days ago with the firefox/flash update. It would show that error but often it would actually cause a *bluescreen*! I think one time I got the bluescreen error "BAD_POOL_HEADER", beside that it was just a generic bluescreen. Everything worked perfectly fine *outside* the sandbox tho, so it was obviously sandboxie causing the issues. I'm only using the free version of sandboxie(sorry) - 5.04. Getting these issue as of now, I've worked for an hour trying to sort them out but I can't get anything flash related to work in sandboxie any longer. Please note, everything works perfectly fine *outside* the sandbox in firefox.

[Craig@Invincea]

It this really fixed? It has caused some serious issues on my computer. It started a few days ago with the firefox/flash update. It would show that error but often it would actually cause a *bluescreen*! I think one time I got the bluescreen error "BAD_POOL_HEADER", beside that it was just a generic bluescreen. Everything worked perfectly fine *outside* the sandbox tho, so it was obviously sandboxie causing the issues. I'm only using the free version of sandboxie(sorry) - 5.04. Getting these issue as of now, I've worked for an hour trying to sort them out but I can't get anything flash related to work in sandboxie any longer. Please note, everything works perfectly fine *outside* the sandbox in firefox.

Our Devs don't put out an update otherwise. Release notes are here http://forums.sandboxie.com/phpBB3/view ... 54&t=21855

I would strongly recommend you update your browsers and plugins, and any other software. Please also turn off "install automatic updates" in Windows unless you have read the Microsoft notices on what these updates might affect & are comfortable with that.

The update was a kernel patch in the OS, those causing access errors with SBIE. You can turn off "protected mode" in your flash plug in in Firefox (we recommended that in the past) to also get around the issue.

The new beta is v5.05.2. You also don't need flash plug in to run on all websites. Modern sites that use HTML 5 with render just fine in FF without it. Youtube and others are examples.

[cornflake]

Craig@Invincea"]I would strongly recommend you update your browsers and plugins, and any other software. Please also turn off "install automatic updates" in Windows unless you have read the Microsoft notices on what these updates might affect & are comfortable with that.

The update was a kernel patch in the OS, those causing access errors with SBIE. You can turn off "protected mode" in your flash plug in in Firefox (we recommended that in the past) to also get around the issue.

The new beta is v5.05.2. You also don't need flash plug in to run on all websites. Modern sites that use HTML 5 with render just fine in FF without it. Youtube and others are examples.

I think it is not a good idea to steer people away from automatic updates from Microsoft. If it's possible for the Sandboxie team to get a hold of these updates in advance and test them with Sandboxie that would be good. This most recent update broke several computers I have Sandboxie running on. Because I am an advanced user I knew what to do however I can see if you've installed Sandboxie for a relative or a client or someone them not being able to react in the same way as someone who is familiar with a BSOD and WinDbg. Maybe you could add something that checks on every startup for known problems with their version and push a notification like "Warning: Many Sandboxie users are reporting problems using Sandboxie with Microsoft's most recent updates. Disable Sandboxie temporarily until this is fixed? Yes/No" and then "A new version of Sandboxie has been released that fixes compatibility with Microsoft's most recent updates. Click here to update Sandboxie to version x.xx"

Also can you tell us what exactly the problem was that caused this issue? Based on the access violation it looked like a null dereference, I believe the address was invariably 0x18 so I assume something in Windows was trying to access some information in a struct that wasn't present.

[Craig@Invincea]

Actually, it's wise to know what you may be updating first, most companies (and I would argue, home users) test updates first, or at least research them. (Also, weigh the risks of rolling back an update) As for steering people away, I would hope people would seek advice and make up their own conclusions. Weighing the risks of that decision.

Microsoft does not give 3rd party vendors a heads up on security updates. They just don't.

It was a Kernel patch. It added lines of new code and logic and the way it handles security tokens and when those tokens are locked down.

We would suggest to Download the KB, then research then with Microsoft to see that they may do. Usually, they offer a bulletin description. Or better yet, wait a day or 2 and see what problems crop up..because they will.

I'd also strongly suggest users create a restore point before applying any updates. Better yet, have a backup image of your Windows installation. It not only affected SBIE, but pretty much every 3rd party one way or another. SBIE was affected more because how SBIE interacts with Windows.

Adding more code would just cause more problems, we can't anticipate what every user may run into, it would be confusing at best. We did post a work around, we also suggested what KB to roll back.That was done Tuesday evening. We only found out when users tell us an Update has caused a problem (We knew Tues AM something was up with Win 10, but we didn't find out to hours later it was Win OS wide from Vista to 10).

Just because Windows issues an update, it doesn't mean it's mandatory, and it's best to go cautiously. Updates in general of those type, may cause issues to Windows, not just 3rd parties. I also should be noted that the MS website detailing how to roll back an update was giving "Server too busy" errors for days since the Tuesday updates with curious users.

The current beta will shortly morph into the new Stable release, because as of Tuesday, that was ruined by MS and their new code. When that will happen? Unknown, but soon. We're still looking at other stuff related to Chrome and Win10.

[bannerman19]

New to forum

Where do I find current 5.05.2 Beta to download.

[Craig@Invincea]

New to forum

Where do I find current 5.05.2 Beta to download.

here http://forums.sandboxie.com/phpBB3/viewforum.php?f=54

[sandboxienev]

We would suggest to Download the KB, then research then with Microsoft to see that they may do. Usually, they offer a bulletin description. Or better yet, wait a day or 2 and see what problems crop up..because they will.

That's not really practical. That's like telling people to read the EULA's. It just ain't going to happen.
.

I'd also strongly suggest users create a restore point before applying any updates. Better yet, have a backup image of your Windows installation. It not only affected SBIE, but pretty much every 3rd party one way or another. SBIE was affected more because how SBIE interacts with Windows.

Yes, this is the way to go. Windows often creates a restore point before installing updates. I'm not sure of the rules though, because of the 10 times I restored to a restore point, probably 5 of them were screwed up. I don't know exactly what MS is restoring, but it's not enough. I switched to Acronis and StorageCraft on my two machines. Acronis is much easier to use, but pretty flaky and frequently just doesn't back up. StorageCraft ShadowProtect seems to be much more solid, but is a royal pain to restore. So for a different reason it's not a good answer. I wish the two had a kid and AcronaCraft was rock solid *AND easy to restore. On my Mac, there is Carbon Copy which is perfect -- very reliable, and easy to restore -- but I don't know of anything great for Windows. Any suggestions?

[Mings]

I have recently installed Google Chrome 45.0.2454.101. I am using Windows 8.1 and AVG free 2015.0.6172. For the past week, every time I tried to start Google Chrome in Sandboxie I got this message: SBIE1222 Error with security token: [C0000061 / 33] SBIE2314 Canceling process chrome.exe. I was using Sandboxie 5.04 but have now installed Sandboxie 5.05.2 and THIS SEEMS TO HAVE FIXED THE PROBLEM.