Sandboxie Support

Unfortunately this DLL load issue still exists with version 4.09.1:
http://forums.sandboxie.com/phpBB3/view ... hp?t=15797

ssj100 wrote:Unfortunately this DLL load issue still exists with version 4.09.1:
http://forums.sandboxie.com/phpBB3/view ... hp?t=15797

We have gotten a few reports that this problem still exists. But, it seems to be intermittent. This is a high priority item now.

Please run the resource access monitor and see if something is being blocked when you try to inject your DLL.

PM sent.

I don't see anything interesting in your access monitor logs. If someone has a way to reproduce this every time, that would be very helpful. It appears to have something to do with sandboxing Windows "stations" and desktops. Resources are being depleted somehow.

There are 2 different "Dll Initialization" problems.

1) The InjectDll setting was not working correctly. The Dll entry point (DllMain) was not being executed first, which caused many injected dll's to fail (even SbieDll.dll in some cases). Sometimes you would get a "CRT not initialized" error. This has been fixed in 4.09.01.
2) Intermittently, a sandboxed app will fail to initialize and return 0xC0000142 (STATUS_DLL_INIT_FAILED). This is an entirely different problem and is being researched now. It seems to be caused by a memory (or other resource) shortage.

Thanks for the update. Hope it can be fixed soon.

Curt:

1) So IS InjectDll a general injection mechanism (like 3.x I think) or not, as tzuk told me? The InjectDll help page makes it sound like it is... And it still also includes this sentence fragment that doesn't make sense:

"Inject" means the DLL is


2) Does that have anything to do with why I (or others) have NEVER been able to run Explorer sandboxed in 4.x (Win 7 at least) with SRP (AppLocker?) DLL enforcement enabled? See here: http://forums.sandboxie.com/phpBB3/view ... 286#p90286

I just upgraded the Win 7 system where Sandboxie is never used to the latest beta (from 4.05.05!) and it's still the same. Yet another thing on the list that it sure would be nice to see fixed someday!

1) Yes, InjectDll is a general mechanism for 3rd party Sandboxie add-ons. And we'll get rid of that sentence fragment.
2) Are you getting the same C0000142 error? We are still working on that one. I don't think it is related to AppLocker.

Also, the latest beta is 4.09.01

1) OK, cool. Thanks for clarifying. :-)

2) Yeah, when trying to "Run Windows Explorer" while SRP's DLL enforcement is applied. See other user's post 2 above mine that I linked to and that's what I get, forever. I saw you're still still trying to figure things out, just wondered if any change may fix that error code in my case too!


Of course ;^) -- I've installed almost every version since 4.01.01 (usually on XP). I was just stating that 4.05.05 was the last version I had tried on that system (HTPC).

That's interesting, because I use SRP with DLL enforcement too in a Limited User Account. However, I use SuRun to elevate privilege of the loaded DLL while loading it sandboxed. Perhaps since Sandboxie versions 4+ has the "lower rights can't access higher rights" thing, it blocks SuRun's job? But then I shouldn't be able to run the loader executable (which loads the DLL) either.

Still unresolved with 4.09.02.

ssj100 wrote:Still unresolved with 4.09.02.

Can you PM me a link to your files so I can repro this?

Curt@invincea wrote:

ssj100 wrote:Still unresolved with 4.09.02.

Can you PM me a link to your files so I can repro this?

I can e-mail you? I tried the support e-mail about 6 weeks ago, but got no reply. I basically forwarded the e-mail correspondence I had with tzuk. To be honest, from what tzuk said, I don't think it's fixable unless you re-write half the code in version 4 - tzuk really changed the internal mechanisms from version 3 to 4 big time. I'm pretty sure it's related to the lower/higher rights hierarchy mechanism that was introduced. It's basically sacrificing usability for more security. And I'm really over "security" now - I can't get infected even if I try haha.

isit fixed?

Please try 4.9.5. We have not had any reports of this problem in a while.