sorry, please move the topic to "Problem Reports"


so glad to see new beta version released. I installed it, but maxthon3 (3.3.5.600) cannot start in it. And I tried to restart PC, but the problem is still there. I have to go back to v.3.64. Everything is ok then.

Here is the message I got from the beta,


SBIE2303 Could not hook NtCreateKey (4)
SBIE2304 Initialization failed for process Maxthon.exe


OS: win7sp1 x64
Security Software: Norton Internet Security 2012 (19.2.0.10) (Norton compatibility is selected in SBie)
Experimental Protection for 64bit is selected

I don't think Norton Internet Security 2012 is causing this problem. I installed the trial copy on 64-bit Windows 7 but I don't see the problem.

So my first question is, any other ideas as to which software might be conflicting with Sandboxie 3.65.01 on your computer?

Second question is, did you have maxthon.exe running using right-click Run Sandboxed, or as a forced program?

I ran MSCONFIG and dsabled everything possible except for Sandboxie 3.65.01 but the problem still occurs:

SBIE2303 Could not hook NtCreateKey (4)
SBIE2304 Initialization failed for process iexplore.exe

Thanks for your reply. I use portable version of maxthon and run it as a forced program. In my system, there is no other safety software. What's more, everything is ok when I go back to re-install v.3.64.

I tried new beta in another PC, win7 sp1 32bit. Same problem.

I can't reproduce the problem, and so far you two are the only ones reporting it. So I do think it has to do with some other program that you use. Darkwolf_99 you say that you see the problem on two of your computers, that could be because you're using the same program or utility on both computers.

It could even be something like a desktop utility which injects parts of its code into other programs. For example so that all windows in the desktop show a new button in their window frame. Do you use something like this?

I installed 3.65.01 too and now when I'm trying to run any software sandboxed, this error message appears:
SBIE2303 Could not hook NtCreateKey (4)
SBIE2304 Initialization failed for process processname.exe

When I force any program to run in sandboxie, then I don't get this error and the program is sandboxed and working fine. But if I try to run it manually in sandboxie, then this error occurs.
I also disabled all start up programs and services expect sandboxie but it didn't help.

I disabled everything possible using MSCONFIG but the problem still persists with 3.65.01. Even if it's a program that's still hooked in somewhere unless it's toally uninstalled, it's not clear why the problem occurs only with 3.65.01. Something must be different in 3.65.01 compared to 3.64 and all previous versions of Sandboxie.

Yes, a few things did change in version 3.65.01 as part of minor improvements and fixes.

But this error message, and specifically the reason (4) there, suggest that Sandboxie is trying to initialize a second time within the program.

The problem is that I don't understand how any of the changes I did in version 3.65.01 might cause this situation.

So what I need is to be able to reproduce the problem, so I can understand it and fix it.

Perhaps one of you guys can experiment with running a program under a debugger, to see if this gives an more information?

You would have to install the debugger and then try to open a forced program in the debugger. The following page explains in more detail:

http://www.sandboxie.com/index.php?HowToUseWinDbg

I found that it was Buster Sandbox Analyzer's log_api.dll what was causing the issue. After I removed InjectDLL of log_api.dll and reloaded the configuration, I was able to sandbox programs again.

That's the culprit! Removing Buster Sandbox Analyzer's log_api.dll also corrected my problem.

But I has not used Buster Sandbox Analyzer, only sbiextra. I'll try to remove it and feedback soon.

Everything is ok then after sbiextra is removed.

sbiextra has to be updated?

Good job guys! Haven't looked into this yet, but I'm sure neither BSA nor sbiextra are the problem here, but rather, the mechanism that loads "InjectDlls" is probably messed up.

Version 3.65.02 should fix the problem. Sorry about the inconvenience.

Windows 7 64 bit with Fsecure and Malwarebytes website blocking only.

Version 3.64 works perfectly, but both new betas result in "SBIE2204 Cannot start sandboxed service RpcSs (-1)"

Thanks in anticipation.