Use Shell Launcher (Standard 7 SP1)

  • Article

7/8/2014

Shell Launcher enables you to replace the Explorer shell with a custom shell. Shell Launcher enables you to concentrate on your custom shell application while Shell Launcher handles issues such as executing the Run and RunOnce registry keys and restarting the custom shell if it crashes. Use the procedures in this section to configure your custom shell.

Note

Applications and other commands that are specified for execution by Shell Launcher are not logged if they do not run because they cannot be found. The commands that are listed in the following registry keys are affected.

  • HKLM\Software\Microsoft\Windows\CurrentVersion\Run
  • HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce
  • HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
  • HKCU\Software\Microsoft\Windows\CurrentVersion\Run
  • HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce
  • HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
  • HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
  • HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run
  • HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce
  • HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnceEx

To use Image Configuration Editor to reference a custom shell (preferred method)

  1. Determine which packages, if any, your shell needs, and select those packages.

  2. Select Command Prompt Shell with Custom Shell Support as your shell.

  3. Optionally set the CustomAction, DefaultAction, or ReturnCodes settings of the Command Prompt Shell with Custom Shell Support package.

    For more information, see Command Prompt Shell with Custom Shell Support.

  4. In the Settings Pane, click the Filter view by box then select 2 Offline Servicing.

  5. Set the CustomShell setting to the path of your custom shell.

    Note

    If your custom shell is in a folder included in the %PATH% environment variable, you have the option of simply typing the name of your custom. Otherwise, you must type the full path of your custom shell.

    Note

    The CustomShell setting supports using command line arguments with your application. For example myshell.exe -background blue if you program your custom shell to have a background color setting.

  6. Place your shell in the appropriate $OEM$ subfolder. An example of a $OEM$ subfolder is the $OEM$\$$\System32 subfolder, which is a folder that contains files to be copied to the %SYSTEMROOT%\System32 folder during setup.

    For more information, see Designing a Distribution Share on Microsoft TechNet.

  7. If you want to run a custom script after you image is deployed, you must create the script in a file named Setupcomplete.cmd. You must place the file in the \$OEM$\$$\Setup\Scripts folder in the distribution share.

    For more information, see Add a Custom Script to Windows Setup on Microsoft TechNet.

To use Image Builder Wizard to reference a custom shell

  1. Determine which packages, if any, your shell needs, and select those packages.

  2. Select Command Prompt Shell with Custom Shell Support as your shell.

  3. Update Setupcomplete.cmd to modify the HKLM\Software\Microsoft\Windows Embedded\EEF\Shell Launcher\Custom Shell value to include the name of your shell, using Windows Management Instrumentation (WMI).

    Note

    There is no Image Builder Wizard mechanism to modify an answer file (Unattend.xml).

    For more information, see Add a Custom Script to Windows Setup on Microsoft TechNet.

  4. Place your shell in the appropriate $OEM$ folder. An example of a $OEM$ subfolder is the $OEM$\$$\System32 subfolder, which is a folder that contains files to be copied to the %SYSTEMROOT%\System32 folder during setup.

    For more information, see Designing a Distribution Share on Microsoft TechNet.

See Also

Concepts

Command Prompt Shell with Custom Shell Support

Other Resources

Custom Shell