Tripedacus, thanks for looking at this post. No that is not what I am saying. Startnet.cmd launches perfectly all by itself. However following Microsoft's instructions for launching a "custom shell" or "custom apps" etc. It says to use the winpeshl.ini file, the LaunchApp with the AppPath = %systemdrive%\myshell.exe - etc. Then you are supposed to be able to uset the LaunchApps section to launch other applications after your shell starts. I followed the directions below using BSExplore as my shell, but it still didn't work: Winpeshl.ini FilesWinpeshl.ini controls whether a customized shell is loaded in Windows PE instead of the default Command Prompt window. To load a customized shell, create a file named Winpeshl.ini and place it in %SYSTEMROOT%\System32 of your customized Windows PE image. The .ini file must have the following section and entry. [LaunchApp] AppPath = %SYSTEMDRIVE%\myshell.exe [LaunchApps] %SYSTEMDRIVE%\mydir\application1.exe, -option1 -option2 application2.exe, -option1 -option2 Set the AppPath entry to the path to your shell application. The path can be either fully qualified, or you can use environment variables, such as %SYSTEMROOT%\System32\Myshell.exe. The AppPath entry does not support command-line options. Use the [LaunchApps] section to run applications with command-line options. The applications run in the order listed; separate the name of the application from its options with a comma. When you exit the Command Prompt window or your customized shell application, Windows PE restarts. This way I wouldn't have the "command prompt" as my shell. I know it is just a cosmetic change (the shell), but I just thought it sounded like a better way to do it. Thanks!