From 24388d8df8fc00b9fb9987b8b280e4d1a117f51d Mon Sep 17 00:00:00 2001 From: Jeanie Decker Date: Thu, 7 Mar 2019 13:29:51 -0800 Subject: [PATCH] tweak --- windows/configuration/kiosk-shelllauncher.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/configuration/kiosk-shelllauncher.md b/windows/configuration/kiosk-shelllauncher.md index b74f4a828a..95dc8e3528 100644 --- a/windows/configuration/kiosk-shelllauncher.md +++ b/windows/configuration/kiosk-shelllauncher.md @@ -48,9 +48,9 @@ Shell Launcher v2 replaces `explorer.exe` with `customshellhost.exe`. This new e > >- Shell Launcher doesn't support a custom shell with an application that launches a different process and exits. 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**, such as restarting the custom shell. -- A domain or local user account. +- A domain, Azure Active Directory, or local user account. -- A Windows desktop application that is installed for that account. The app can be your own company application or a common app like Internet Explorer. +- A Windows application that is installed for that account. The app can be your own company application or a common app like Internet Explorer. [See the technical reference for the shell launcher component.](https://docs.microsoft.com/windows-hardware/customize/enterprise/shell-launcher)