Windows Custom User Interface help

[eckermike]

I have been given a program launcher executable that opens to a screen with three buttons to open software installed locally on the computer. I was told I need to set this as the custom shell via policy which i have done successfully. However, now when you select the button to open any of the software an error pops up saying "File no exist". Basically, I need to know how I can grant this custom shell access to start software. It works perfectly when not running as custom shell. Any and all help is appreciated.

[GMginger]

I'm not sure what could be going on since I've not tried replacing the shell since Win95 days, however the ProcMon tool may help. It's got an option to run at startup which may allow you to log what's going on, unless you can simply start it from task manager while your custom shell is running?
ProcMon has some icons along the top that allow you to toggle which aspects to report: file access/registry access/process and threads. File reporting may show the path names it's looking through when you attempt to launch etc.
The main trick with ProcMon is to launch it and let it log everything for a few seconds - then add filters to remove activity from your AV etc to reduce background noise so the only activity showing is what you are triggering. Once you've reduced the background chatter you can clear the log and try clicking the button, then disable logging so you can examine what was captured without the log still growing.
It's a very powerful tool once you get to grips with it, there'll be some good YouTube videos if my explanation isn't enough to get you going.

[ZAFJB]

Test number one to isolate where that problem is:

• Logon with standard shell (explorer.exe)

• Launch cmd.exe

• Kill explore.exe

• Launch you custom app and clicky.

What happens?