Windows 10 Kiosk Mode Shell Launcher Access

Introduced in Windows 10, version 1809. It adds support for UWP apps and offers more robust monitoring through CustomShellHost.exe . It is typically configured via XML profiles or MDM solutions. Prerequisites Quickstart: configure a kiosk with Shell Launcher

Windows 10 Shell Launcher provides a powerful mechanism for creating secure, dedicated kiosk environments using custom Win32 applications. While requiring more careful configuration than standard Assigned Access, it offers superior flexibility for enterprise scenarios where legacy or multi-function applications must serve as the primary user interface. Administrators must, however, implement complementary lockdown policies and application resiliency to ensure a stable, tamper-resistant deployment.

Replace $UserSID with the actual SID or remove the parameter to reset globally if supported by your version. windows 10 kiosk mode shell launcher

ensure you test your exit codes thoroughly. If your application crashes, ensuring the return code 0 is properly handled is the difference between a minor glitch and a site visit.

The original version, focused purely on replacing Explorer.exe with a Win32 application. It uses a WMI provider for configuration. Introduced in Windows 10, version 1809

While you can configure Shell Launcher via MDM (like Intune), the most direct method for testing and local deployment is PowerShell. The Shell Launcher Configuration APIs allow you to define exactly how the kiosk behaves.

$result = $shellLauncherClass.SetCustomShell($userName, $shellPath, $null, $null) Replace $UserSID with the actual SID or remove

$ReturnCode = 0 # Restart the shell if the app crashes or closes

Windows 10 Shell Launcher replaces the standard explorer.exe interface with custom Win32 applications, providing a locked-down kiosk experience suitable for Enterprise or Education editions. This tool enables automated application restarts and utilizes WMI/PowerShell for configuration to secure dedicated workstations. For comprehensive implementation details, see the documentation at Microsoft Learn . Quickstart: configure a kiosk with Shell Launcher

$shellLauncherClass = Get-WmiObject -Namespace "root\standardcimv2\embedded" -Class "WESL_UserSetting" -ErrorAction Stop

| Feature | Shell Launcher (Classic) | Assigned Access (Kiosk Mode) | | --- | --- | --- | | Supports Win32 apps | Yes | No (UWP only, except via XML hack in Enterprise) | | Supports multiple apps | Yes (app can launch others) | No (single app) | | Complexity | High (manual WMI) | Low (Settings UI) | | UWP support | No | Yes | | Recommended use | Custom launcher, legacy apps, multi-app kiosk | Simple content viewer, Edge kiosk |