Summary
In a kiosk environment, assigned access users can press Ctrl+N to open a File Explorer window even though File Explorer isn't included in the list of allowed applications. This article explains why this behavior occurs, and how to prevent it by using the keyboard filter feature.
Symptoms
You create a kiosk environment by applying an assigned access configuration XML file that includes a list of allowed applications. That list doesn't include File Explorer.
When an assigned access user presses Ctrl+N while signed in to the kiosk environment, a File Explorer window opens.
Cause
This behavior is by design. The Ctrl+N shortcut isn't specific to File Explorer. This shortcut opens a new window of the currently active process or service (in this case, Explorer.exe). The shortcut works together with any application that supports it.
Because the Explorer.exe process provides the Windows shell experience, it always runs even if File Explorer isn't on the list of allowed applications. Therefore, it's possible for Ctrl+N to open new File Explorer windows.
Workaround
To block the Ctrl+N shortcut in a kiosk environment, use the keyboard filter feature. For more information, see Keyboard Filter.
Important:
Keyboard filter doesn't block Ctrl+N in Remote Desktop Services (RDS) environments.
References
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
