I get the following when invoking a sandboxed IE on Windows 7 32-bit:



RAM log:

snipped. --tzuk

Resource Access Monitor log is not going to help here, but perhaps the following:

Make sure IEXPLORE.EXE is a forced process.

Run the WINDBG debugger.

In the debugger, open the IEXPLORE.EXE program from the Program Files folder.

Press F5 (go).

You should presumably see some crash in the debugger, at this point please copy your debugger log, and paste it here.

Thank you!

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

Here's the debugger output:

snipped. --tzuk

There's no crash here... Probably the crash happens in the other IEXPLORE.EXE instance that starts up. Can you use Process Explorer to confirm that WerFault is the child process of that secondary IEXPLORE instance?

WerFault never appears in Process Explorer.

Actually I can reproduce the problem. Shame on me for not trying something trivial like running IE in 32-bit Windows 7. I'm pretty sure I spent quite some time in 64-bit Windows 7 and probably in my mind I thought that if stuff works in 64-bit Windows 7 then it certainly is going to work in 32-bit Windows 7. Anyway, let me take a look at this problem and I'll post an update.

Thank you .

I uploaded a revised 32-bit Sandboxie 3.51.01 installer package, I think it will fix the problem.

It does. Thanks again.

Sorry about the bad first impression