Windows Explorer won't run in Sandbox

[FixMyPCMike]

I'm not using a shell replacement, and I've tried disabling all other programs including security programs, but Windows Explorer won't run -- Control window shows it along with two other processes, but nothing appears and after a minute they shut down. SB 3.0.17, XP Pro SP2.

[SnDPhoenix]

Damn, i really dont know what the problem could be, there is only one other reported instance of this problem, reported here, unfortunately it was never solved (or maybe it was and it just was never posted in that thread). But if i had to guess, i would say something on your pc blocking Explorer from opening (for example, it's reported that if you have RegDefend installed, it'll conflict with Sandboxie and you'll see this exact same thing happen), now you report that you tried disabling the security programs and that didnt work, but have you instead tried uninstalling the programs instead and seeing if that helps? Also what security programs are you using?

[Unknown_User_929]

SSM, Avast AV, SpywareTerminator, BOClean, Windows Defender, SpywareGuard, Comodo Firewall. I don't want to uninstall them all on the off chance it might get Sandboxie working. Does SB have a logfile that might give a clue what was happening?

[MitchE323]

Mike I was thinking, how are you accessing Windows Explorer? Is it as exe and not scf?

mitch

[Unknown_User_929]

It happens no matter how I try to start it -- from the status tray icon or with control open, using the built-in link or from the start menu or desktop. It lists explorer.exe as the process for a half minute, then returns to "no processes are running sandboxed."

[MitchE323]

Try this: add to sandboxie.ini in windows - ForceProcess=explorer.exe - open Sandboxie box and reload config and then run explorer.exe from run command.

[Unknown_User_929]

Still doesn't work

[MitchE323]

OK I was just trying to isolate it - conflict somewhere - I have same proXP2 and SB and all is good here.

[Peter2150]

I actually have the same problem. Can't get explorer to run from sandbox. Not sure I like forcing it as then it always would be there.

[SnDPhoenix]

Yeah, i highly recommend you dont force explorer or else it will always start sandboxed (thats not a good thing), anyways, wow, i dont what the problem could be, when did this start happening? Only with .17?

[wraithdu]

This was a strange problem for me. In my case, RegDefend was the culprit. The strange part is though, that RegDefend was not in fact blocking anything. It was just the mere fact that it was monitoring the registry, that was causing the problem. Disabling it (not shutting it down) was enough to let sandboxed explorer start.

Perhaps you have some similar type registry monitoring program active, even though it's not actually blocking anything? Outside of that, I wasn't able to figure anything else out.

[Unknown_User_929]

3.0.17 is the first version I've installed.

[MitchE323]

Well, I didn't mean to always run it sandboxed - I just wanted to see if it could go sandboxed at all - BTW if you "force" explorer.exe it is as everyone fears always going to be sandboxed, but explorer.scf works just like normal.

So you could have two shortcuts - SandboxedExplorer which points to explorer.exe and Explorer which points to explorer.scf and everything would be just fine.

I actually prefer to force it cause then any bad guys that try to get in or transmit out via that route will be sandboxed and when I want to go in I use explorer.scf and I've had no problems.

In fact, other than the way I use it, I can not imagine any circumstance that I would be opening and using Windows Explorer sandboxed. I mean that if I made any changes to any files, wouldn't I want to keep those changes? Explorer.exe is a web instrument and is tightly integrated with iexplore.exe so since I force IE, I force the other as well.

Prior to IE7, if you clicked a link from the standard toolbar from Windows Explorer you entered the web via explorer.exe, not iexplore.exe. IE7 is more standalone I agree, and now will only access the web as iexplore.exe, but any of the bad guys at least in theory, can still use explorer.exe.

mitch
anyway back to mikes problem ( sorry mike, but since it came up here, figured I'd jump in)

[SnDPhoenix]

Explorer.exe is a web instrument and is tightly integrated with iexplore.exe so since I force IE, I force the other as well.

Huh? No it's not, explorer is the shell, but whatever floats your boat i guess, personally i would never force explorer, but then again, i would never use any other piece of security software except Sandboxie, and ppl think i'm crazy. Anyways, back on topic, im all out of ideas, i really cant think of what might be causing this, other than something installed on your pc that is conflicting with Sandboxie. Btw, if you look at your system event log, does it show any Sandoxie related errors?

[MitchE323]

Well like Wraithdu says, it's gotta be where you'd least expect to find it. Not just in this thread but I think this has come up before so more than several people are having the problem, yet others do not.

I think I got in the other habit cause launching WE sandboxed was not an option in the earlier versions of Sandboxie, I think. And then it just stayed with me I guess.

But the fact is that if you clicked a favorite from the windows explorer toolbar prior to IE7, the process that took you to the web was explorer.exe, not iexplore.exe. IE7 provided more seperation. Is everybody that is having problems using IE7 or still on IE6?
mitch