Ok, someone explain THIS to me. I've been messing with my registry for the past couple of days trying to get Litestep set up such that I can use per-user shells and not have the "explorer shell pops up when I try to use it as a file browser" problem. I was eventually able to get that working, but now for some strange reason, Internet Explorer will not run under Litestep. I try to run it and nothing happens, I don't even see the iexplore.exe process appear in the task manager. I tried directly clicking on the executable and running it from a command line to make sure that it wasn't a path or evar problem too. The really strange thing is it ONLY happens when Litestep is running. If I boot to explorer shell IE works normally, in fact, if I boot to Litestep and then !quit (so there is no shell running at all) I can launch Internet Explorer just fine from the task manager. But if Litestep is running it simply will not execute. Any ideas on this one?

Ok...apparently this is caused (at least in 24.7b3) by the LSSetasShell setting being on. I'm not sure how why or when I actually turned this on...but I don't think there's any reason to. It seems to only cause problems.

That's true for any version of LS supporting this feature (and in fact for all shells that i know supporting this feature). It uses an undocumented API call which has more negative sideeffects than positive ones for most people, looks like there's something we haven't figured out yet (like something we have to implement to make it work properly). :p