5.07 Beta Available (latest version 5.08 RC)

[Craig@Invincea]

I am seeing an error message "Could not hook Ishungappwindow" Hiding it and everything seems normal.

Win 10x64 Fast ring build 14251
Sbie 5.07.5
FF 44

Yep. It's the issue I stumbled onto this weekend.
It's directly bc of that new FR release. Not to Chrome, FF updates, etc.
The Devs have confirmed it. Working on a fix as we speak. A "call" that SBIE was making has changed on the MS side, and code and logic tweaks need to be added....

SBIE will function.....YMMV... You'll get inundated with that popup error. A few times it did in fact crash..but it depends on what you were doing at the time.

[Peter2150]

yeah Microsoft. I just hid the message and all is working fine. I'll retest when the fix is in. Of course there will then be a new FR build.

[nomnom]

I think there is something wonky with Chrome 49. I'm getting SBIE 2303 errors IsHungApWindow crash. Same when I attempt to install directly into a SB. v48 and older of Chrome seem to be ok (and I have a lot of extensions in this flavor I'm using...and it's always been ok for me..)

I've let Curt know, but don't count on anything until Monday for them to look @ it.

EDIT: IT appears to be related the the newest FR of Win 10. Seems ok in non-FR version of Win 10. It'll take more testing.

I'm running Windows 7 64 and having the Chrome "Aw Snap" problem on a freshly installed Chrome Beta 49 in a clean sandbox (SB 5.07.5). In fact I couldn't open anything in Chrome Beta 49 from the chrome:flags to the settings page they aren't working. Everything always end in "Aw snap". But there's no problem at all on 48.

[Craig@Invincea]

I think there is something wonky with Chrome 49. I'm getting SBIE 2303 errors IsHungApWindow crash. Same when I attempt to install directly into a SB. v48 and older of Chrome seem to be ok (and I have a lot of extensions in this flavor I'm using...and it's always been ok for me..)

I've let Curt know, but don't count on anything until Monday for them to look @ it.

EDIT: IT appears to be related the the newest FR of Win 10. Seems ok in non-FR version of Win 10. It'll take more testing.

I'm running Windows 7 64 and having the Chrome "Aw Snap" problem on a freshly installed Chrome Beta 49 in a clean sandbox (SB 5.07.5). In fact I couldn't open anything in Chrome Beta 49 from the chrome:flags to the settings page they aren't working. Everything always end in "Aw snap". But there's no problem at all on 48.

This issue had nothing to do with a Chrome build. I'm not sure what to say about that issue you are having with the Chrome v49 build.

I'm running Chrome v49 on a number of 7, 8.1 and 10 (32/64) VMs without issue using SBIE 5.07.5.
The current Stable release of Chrome is 48.0.2564.103 as of yesterday.
It's always a good rule of thumb not to mix beta's with other beta's... Such as Chrome Beta v49, Dev build v50

[Craig@Invincea]

yeah Microsoft. I just hid the message and all is working fine. I'll retest when the fix is in. Of course there will then be a new FR build.

Fix found and applies, testing is underway...a beta soon.

[Umbra]

Fix found and applies, testing is underway...a beta soon.

good to hear

[nomnom]

I think there is something wonky with Chrome 49. I'm getting SBIE 2303 errors IsHungApWindow crash. Same when I attempt to install directly into a SB. v48 and older of Chrome seem to be ok (and I have a lot of extensions in this flavor I'm using...and it's always been ok for me..)

I've let Curt know, but don't count on anything until Monday for them to look @ it.

EDIT: IT appears to be related the the newest FR of Win 10. Seems ok in non-FR version of Win 10. It'll take more testing.

I'm running Windows 7 64 and having the Chrome "Aw Snap" problem on a freshly installed Chrome Beta 49 in a clean sandbox (SB 5.07.5). In fact I couldn't open anything in Chrome Beta 49 from the chrome:flags to the settings page they aren't working. Everything always end in "Aw snap". But there's no problem at all on 48.

This issue had nothing to do with a Chrome build. I'm not sure what to say about that issue you are having with the Chrome v49 build.

I'm running Chrome v49 on a number of 7, 8.1 and 10 (32/64) VMs without issue using SBIE 5.07.5.
The current Stable release of Chrome is 48.0.2564.103 as of yesterday.
It's always a good rule of thumb not to mix beta's with other beta's... Such as Chrome Beta v49, Dev build v50

I'm sorry about that. I thought you and Umbra were talking about Chrome Beta 49 problem because on the few pages back I saw Umbra mentioned that he is having problem with Chrome Beta 49. And then I saw your post saying that it is related to FR of W10 but I'm the one that is on W7 also having problem with Chrome. Hence why I made a post.

And yes, I know that the latest stable Chrome is 48 and it works all good there no problem at all. But on the new Chrome Beta 49, everything is broken. I remember I saw Curt's post mentioned that he usually test the beta build of chrome and stable build only (not chrome dev build) so he can prepare in advance because what is in Beta build in chrome will also make it into Stable build in the future.

I just tested it again today just to make sure. All latest W7 64 updates, no antivirus/antimalware, drop rights settings is unchecked, SBIE 5.07.5 and clean Chrome 64-bit Beta 49 installed in fresh sandbox = chrome broke. The only way to make chrome works again is by using the no-sandbox switch to disable chrome built-in sandbox. Probably something new in chrome broke its compatibility with Sandboxie again but because you said you were running Chrome Beta 49 and you have no problem I'm confused because it's not working here unless no-sandbox switch is used.

EDIT:

Curt released 07.6 probably several mins after I made this post. So I tested it right away same setup except running 5.07.06. All latest W7 64 updates, no antivirus/antimalware, drop rights settings is unchecked, SBIE 5.07.6 and clean Chrome 64-bit Beta 49 installed in fresh sandbox = chrome broke. Still have to use no-sandbox switch in order to use chrome 49.

[Curt@invincea]

5.07.6 has been released.

[Craig@Invincea]

Users that are using Chrome Beta v49.0.2623.39 should revert back to the current stable build of Google Chrome v48.0.2564.103.

The current beta of Google Chrome introduces a lot of new APIs, a new look, and other things that need to be further addressed with SBIE. (Appears at the moment to a be font issue..)

You will receive an "aw snap" screen and / or SBIE error that Chrome.exe has crashed

Windows 7, 8.1 this happens very frequently, if not immediately. Windows 10, It happens too, but not as immediate.

[bo.elam]

All programs run well under Sandboxie 5.07.6 in my XP and W7 32 bits.

Bo

[Umbra]

Users that are using Chrome Beta v49.0.2623.39 should revert back to the current stable build of Google Chrome v48.0.2564.103.

The current beta of Google Chrome introduces a lot of new APIs, a new look, and other things that need to be further addressed with SBIE. (Appears at the moment to a be font issue..)

You will receive an "aw snap" screen and / or SBIE error that Chrome.exe has crashed

good to know, i knew it was not about the "chrome://flags" tweaks. Chrome introduce the" Brolit" thingy to accelerate page rendering, i mentioned earlier it may be the cause.

[huldu]

I've been having a big problem with sandboxie(5.07.1 and 5.07.6), every time I open windows explorer inside the sandbox I get this error thrown at me: "The application was unable to start correctly(0xc00000e5). Click OK to close the application.". I know it's windows 10 that is the problem because it worked perfectly fine in windows 7.

[Craig@Invincea]

I've been having a big problem with sandboxie(5.07.1 and 5.07.6), every time I open windows explorer inside the sandbox I get this error thrown at me: "The application was unable to start correctly(0xc00000e5). Click OK to close the application.". I know it's windows 10 that is the problem because it worked perfectly fine in windows 7.

Are you using a Fast Ring builds of Windows 10?
Antivirus installed on this Win 10 machine? Have you run Windows updates?
There is a a few threads on this... In MS from a bad update to a virus infection http://answers.microsoft.com/en-us/wind ... d70f7f9a17

[huldu]

Are you using a Fast Ring builds of Windows 10?
Antivirus installed on this Win 10 machine? Have you run Windows updates?
There is a a few threads on this... In MS from a bad update to a virus infection http://answers.microsoft.com/en-us/wind ... d70f7f9a17

No idea what fast ring even is so that's a no. I have comodo, windows 10 updates whenever it feels like it, says up to date. The thing is that this *only* happens in the sandbox - never outside.

<edit> Could be something with shellcode injections, I'll see what I can do about it.
<edit2> Yeah, turns out it was that, funny thing sandboxie already appeared to be in the hips exclusion but not enabled or something. Anyways it *seems* it is fixed for now.
<edit3> It wasn't enough the problem came back after a bit. I removed comodo entirely, restarted the computer and now it actually works. Installed other firewall/antivirus software that actually has a less intrusive hips system. Would have been nice if comodo actually gave you a warning instead of just blocking it.

[Craig@Invincea]

Ah, did you follow the instructions listed here regarding Comodo and SBIE? http://forums.sandboxie.com/phpBB3/view ... 11&t=21539

Even with this work around with Comodo, there is no guarantee it will work with SBIE.