4.17 Beta Available (Latest Version 4.17.8)

[stonerd]

Perhaps a regression. I was running 4.17.1 ... with no errors

this
the 4.17.2 broke a few apps that worked fine in 4.17.1

i'd like to go back for now too.

so far i've noticed this alongside a "unable to create direct 3D" error.


Edit: reverting to the latest stable fixes my issues.

[Curt@invincea]

Someone is using an undocumented flag to ChangeDisplaySettings. This was allowed in the Sandboxie code, but there was no documentation on why. So I took it out to see if something broke. I will put it back in next beta.

What is the application that is getting this error? It is most likely just a bug on their part.

[stonerd]

it was multiple games trying to launch in full screen. (not at a single time or anything)
only 1 fan made game was unaffected, and a couple of cheap ports got stuck in launching/crashing loops, repeating the error message each time.

[stonerd]

Also it isn't a massive issue, but with norton installed, when trying to open a windows explorer window sandboxed, it creates this error.

and often the "symerr.exe" process will linger in the sandbox, and refuse to terminate. a restart is required to clear it.

Again, not a priority by any means (no noticeable loss of functionality), just thought i'd bring it to your attention in case you weren't aware and it snowballs or affects other programs similarly. it's also not exclusive to the beta builds.

[bo.elam]

Also it isn't a massive issue, but with norton installed, when trying to open a windows explorer window sandboxed, it creates this error.

Hi Stonerd, read Curts post for that message related to Norton's symerr.ese.
http://forums.sandboxie.com/phpBB3/view ... it#p101514

Bo

[stonerd]

Also it isn't a massive issue, but with norton installed, when trying to open a windows explorer window sandboxed, it creates this error.

Hi Stonerd, read Curts post for that message related to Norton's symerr.ese.
http://forums.sandboxie.com/phpBB3/view ... it#p101514

Bo

Yeah, I seen that moments after posting... felt like an idiot lol.

Thanks tho Bo.

[cornflake]

Sandboxie 4.17.2 x64 in Windows 7 x64. I opened Chrome x86 and as it was restoring my tabs it closed with this error:

SBIE2101 Object name not found: , error OpenProcess (C0000022) access = 00101401
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
(repeated many times)

There were like 20 tabs opened so my guess is there was probably a 'canceling process' for each tab. No idea what happened and I can't reproduce.

[Curt@invincea]

Sandboxie 4.17.2 x64 in Windows 7 x64. I opened Chrome x86 and as it was restoring my tabs it closed with this error:

SBIE2101 Object name not found: , error OpenProcess (C0000022) access = 00101401
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
(repeated many times)

There were like 20 tabs opened so my guess is there was probably a 'canceling process' for each tab. No idea what happened and I can't reproduce.

This looks like another case of something trying to open a process out of the sandbox. What other security apps do you have running?

[cornflake]

Sandboxie 4.17.2 x64 in Windows 7 x64. I opened Chrome x86 and as it was restoring my tabs it closed with this error:

SBIE2101 Object name not found: , error OpenProcess (C0000022) access = 00101401
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
SBIE2314 Canceling process chrome.exe
(repeated many times)

There were like 20 tabs opened so my guess is there was probably a 'canceling process' for each tab. No idea what happened and I can't reproduce.

This looks like another case of something trying to open a process out of the sandbox. What other security apps do you have running?

None except Malwarebytes Anti-Malware, the old version 1.75.

[bjm]

I can't use 4.17.x with Norton Security v22.2.x
Browsers won't open

[nick s]

I do have Drop Rights enabled for Chrome's sandbox. I've now disabled it and thus far no Chrome-related errors. Hopefully that resolves things for Chrome. After upgrading to 42.0.2311.90 m (64-bit) yesterday, I was getting at least one per hour of usage. None so far now.

Well, that didn't work. The Chrome errors reappeared within two days. I'm going to enable Sysmon and see what it reveals.

[gino074]

Hi, I'm a lifetime registered user of Sandboxie, first time I need to post a problem that I've seen with NVIDIA 780GTX card & some games. Most of my games are installed in sandboxes and till now I haven't seen many problems running them.
Now from NVIDIA drivers > 344.65 a very annoyng problems appear with some sandboxed games: "Cannot find a compatible 3D device" or similar error about opening the 3D screen. This of course happens immediately after starting the game.
I'm currently reverted to Sandboxie 4.14, before I was on 4.16 and I tried also this latest beta 4.17.2, the problem still happen, then I reverted from NVIDIA 350.12 to older NVIDIA drivers till 344.65 where those games work again.

Games I tested that with latest NVIDIA drivers 350.12 and Sandboxie (tried 4.14, 4.16 and 4.17.2) do not work are Valkyria Chronicles and Dead or Alive 5 last round, but there can be more as I didn't tested all games that I have...

[Curt@invincea]

4.17.3 is released.

The AllowPrintToFile is going to cause some confusion, because it is a very complicated problem. The print spooler security hole is blocked -- no one needs to do anything unless you start getting the "SBIE1319 Blocked request to print to file".

Would it be better to change this flag to "AllowStartDocPrinter"? That is more specific to what it actually does, but is a bit cryptic. It is probably confusing to see in Win 7 you can still print to files even though AllowPrintToFile=n.

[Mr.X]

Thank you very much Curt!

[cornflake]

4.17.3 is released.

The AllowPrintToFile is going to cause some confusion, because it is a very complicated problem. The print spooler security hole is blocked -- no one needs to do anything unless you start getting the "SBIE1319 Blocked request to print to file".

Would it be better to change this flag to "AllowStartDocPrinter"? That is more specific to what it actually does, but is a bit cryptic. It is probably confusing to see in Win 7 you can still print to files even though AllowPrintToFile=n.

What is all this? How about security notifications via e-mail? I still can't believe I'm the only one that wants that. REALLY? I need to be able to get in front of these things. If I didn't pay attention to the forums I'd have no idea.