Custom User Interface (Shell Replacement)

Custom User Interface (Shell Replacement) is a Windows Group Policy setting located under User Configuration > Administrative Templates > System. It applies to the User Configuration branch and is classified as a Informational-level policy in the Kiosk & Shell Access category.

Replaces default Windows Explorer shell with custom application. MSPs use this to lock down kiosk systems or special-purpose devices to single applications.

Microsoft sets the default value to explorer.exe while industry security baselines (CIS, NIST, DISA STIG) recommend custom.exe.

Under the hood, this policy is enforced through the Windows registry at HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer using the value name Shell. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.

This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.

The policy is grouped under Kiosk & Shell Access, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

1. Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
2. Create or edit a GPO linked to the OU containing the target user configurations. We recommend a dedicated baseline GPO (e.g. SEC – Kiosk & Shell Access) instead of editing Default Domain Policy.
3. Navigate to User Configuration > Administrative Templates > System.
4. Open Custom User Interface (Shell Replacement) and set it to custom.exe.
5. Click OK and close the editor.
6. On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Direct registry path: HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Shell. You can apply the same change with PowerShell:

New-Item -Path 'HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer' -Force | Out-Null
Set-ItemProperty -Path 'HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer' -Name 'Shell' -Value <value> -Type DWord