Classic Shell Needs To Configure Itself For The New Operating System
Reconfigure Classic Shell
Classic Shell Needs To Configure
Classic Shell Needs To Configure Itself
Classic Shell Needs To Configure Windows 10
Configure Classic Shell Windows 10

You will get the following message at startup. 'open-shell needs to configure itself for the new operating system' If the user doesnt have admin right it will prompt. Aug 23, 2019 On every in-place upgrade install of major, new versions of Windows 10 by using a USB Flash Drive or a DVD, I have received a message stating that Classic Shell needs to configure itself for the.

-->

You can use Shell Launcher to replace the default Windows 10 shell with a custom shell. You can use almost any application or executable as your custom shell, such as a command window or a custom dedicated application.

You can also configure Shell Launcher to launch different shell applications for different users or user groups.

There are a few exceptions to the applications and executables you can use as a custom shell:

You cannot use the following executable as a custom shell: C:WindowsSystem32Eshell.exe. Using Eshell.exe as the default shell will result in a blank screen after user signs in.
You cannot use a Universal Windows app as a custom shell.
You cannot use a custom shell to launch Universal Windows apps, for example, the Settings app.
You cannot use an application that launches a different process and exits as a custom shell. For example, you cannot specify write.exe in Shell Launcher. Shell Launcher launches a custom shell and monitors the process to identify when the custom shell exits. Write.exe creates a 32-bit wordpad.exe process and exits. Because Shell Launcher is not aware of the newly created wordpad.exe process, Shell Launcher will take action based on the exit code of Write.exe, and restart the custom shell.
You cannot prevent the system from shutting down. For Shell Launcher V1 and V2, you cannot block the session ending by returning FALSE upon receiving the WM_QUERYENDSESSION message in a graphical application or returning FALSE in the handler routine that is added through the SetConsoleCtrlHandler function in a console application.

Note

You cannot configure both Shell Launcher and assigned access on the same system.

Use Shell Launcher V2, you can specify a Universal Windows app as a custom shell. Check Use Shell Launcher to create a Windows 10 kiosk for the differences between Shell Launcher v1 and Shell Launcher V2.

Shell Launcher processes the Run and RunOnce registry keys before starting the custom shell, so your custom shell doesn’t need to handle the automatic startup of other applications and services.

Shell Launcher also handles the behavior of the system when your custom shell exits. You can configure the shell exit behavior if the default behavior does not meet your needs.

Requirements

Windows 10 Enterprise or Windows 10 Education.

Terminology

Turn on, enable: To make the setting available to the device and optionally apply the settings to the device.
Configure: To customize the setting or sub-settings.
Embedded Shell Launcher: This feature is called Embedded Shell Launcher in Windows 10, version 1511.
Custom Shell Launcher: This feature is called Shell Launcher in Windows 10, version 1607 and later.

Turn on Shell Launcher

Shell Launcher is an optional component and is not turned on by default in Windows 10. It must be turned on prior to configuring. You can turn on and configure Shell Launcher in a customized Windows 10 image (.wim) if Microsoft Windows has not been installed. If Windows has already been installed and you are applying a provisioning package to configure Shell Launcher, you must first turn on Shell Launcher in order for a provisioning package to successfully apply.

Enable Shell Launcher using Control Panel

In the Search the web and Windows field, type Programs and Features and either press Enter or tap or click Programs and Features to open it.
In the Programs and Features window, click Turn Windows features on or off.
In the Windows Features window, expand the Device Lockdown node, select or clear the checkbox for Shell Launcher, and then click OK.
The Windows Features window indicates that Windows is searching for required files and displays a progress bar. Once found, the window indicates that Windows is applying the changes. When completed, the window indicates the requested changes are completed.
Click Close to close the Windows Features window.

Classic Shell Needs To Configure Itself For The New Operating System

Note

Reconfigure Classic Shell

Turning on Shell Launcher does not require a device restart.

Enable Shell Launcher by calling WESL_UserSetting

Enable or disable Shell Launcher by calling the WESL_UserSetting.SetEnabled function in the Windows Management Instrumentation (WMI) class WESL_UserSetting.
If you enable or disable Shell Launcher using WESL_UserSetting, the changes do not affect any sessions that are currently signed in; you must sign out and sign back in.

Classic shell needs to configure itself for the new operating system fix

This example uses a Windows image called install.wim, but you can use the same procedure to apply a provisioning package (for more information on DISM, see What Is Deployment Image Servicing and Management.

Enable Shell Launcher using DISM

Open a command prompt with administrator privileges.
Copy install.wim to a temporary folder on hard drive (in the following steps, we'll assume it's called C:wim).
Create a new directory.
Mount the image.
Enable the feature.
Commit the change.

Enable Shell Launcher using Windows Configuration Designer

The Shell Launcher settings are also available as Windows provisioning settings so you can configure these settings to be applied during the image runtime. You can set one or all Shell Launcher settings by creating a provisioning package using Windows Configuration Designer and then applying the provisioning package during image deployment time or runtime. If Windows has not been installed and you are using Windows Configuration Designer to create installation media with settings for Shell Launcher included in the image or you are applying a provisioning package during setup, you must enable Shell Launcher on the installation media with DISM in order for a provisioning package to successfully apply.

Use the following steps to create a provisioning package that contains the ShellLauncher settings.

Build a provisioning package in Windows Configuration Designer by following the instructions in Create a provisioning package for Windows 10.
In the Available customizations page, select Runtime settings > SMISettings > ShellLauncher.
Set the value of Enable to ENABLE. Additional options to configure Shell Launcher will appear, and you can set the values as desired.
Once you have finished configuring the settings and creating the provisioning package, you can apply the package to the image deployment time or runtime. See the Apply a provisioning package for more information. Note that the process for applying the package t