Assigned Access kiosk mode
Answer: Assigned Access kiosk experiences are supported on Windows Pro, Enterprise, Enterprise LTSC, Education, IoT Enterprise, and IoT Enterprise LTSC.
Administrator playbook
Decide, verify, and document
Use the curated answer as a starting point, then prove the outcome against the target tenant or device.
What it means
- User Account Control must remain enabled
- Kiosk sign-in must occur at the console rather than over Remote Desktop
- Single-app and multi-app scenarios have different configuration options
What to check next
- Confirm the intended configuration is supported by the target release
- Use a least-privileged kiosk account
- Plan updates, recovery, keyboard restrictions, and escape behavior before deployment
Verify success
- Confirm the feature is present or enabled on the target edition and build.
- Test the intended workflow with a pilot device and least-privileged user.
- Confirm policy reports success from the actual management authority.
Escalate when
- The documented edition and hardware requirements are met but the feature is absent.
- Policy reports success while the user or device state is incorrect.
- Licensing or OEM terms—not technical prerequisites—control the outcome.
Copyable admin briefAnswer, next checks, source, and review date
Capture edition and build
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber,OsArchitectureRead-only. Edition and exact build often control availability.
List optional feature state
Get-WindowsOptionalFeature -Online | Where-Object State -ne "Disabled" | Select-Object FeatureName,StateRead-only. Not every Windows capability is represented as an optional feature.
Evidence to preserve
- Windows edition, version, and build
- Hardware and firmware prerequisites
- Management authority and policy source
- Required user or device experience