Skip to content

AEMS overview

Download this documentation as PDF

Applies to AEMS 1.0.8.0

This documentation describes AEMS 1.0.8.0 (service 0.1.9.0, driver 1.0.8.0, Allow-list Tool 1.3.0.0), released 2026-11-20. Install 1.0.8.0. Text marked "from 1.0.8.0" does not apply to earlier versions. Where the text says "from 1.0.6.0", it applies to 1.0.7.0 and 1.0.8.0 as well.

AEMS (Application Elevation Management Service) from Logic Unknown ApS lets a standard (non-admin) user on a Windows kiosk device run the specific applications you approve with administrator rights, without giving the user local administrator rights and without a UAC prompt. Every elevation is decided by an allow-list in the registry and written to the Windows event log.

What it does

  • You approve applications in an allow-list under HKLM\SOFTWARE\Logic Unknown\AEMS\Applications. An entry names an executable by its path or, from 1.0.6.0, by a wildcard path pattern, and can pin it to a SHA-256 hash or to the publisher of its Authenticode signature.
  • A path without wildcards is matched as a prefix of the launched path. Always write the full path including the file name: a folder path approves every program below it.
  • When the kiosk user starts an approved application, AEMS relaunches it elevated in the user's session. There is nothing for the user to click.
  • Everything that is not on the allow-list starts as it always does, unelevated.
  • Every elevation is logged to the Windows Application event log under the source AEMS.
  • There is no portal, no cloud service and no online dependency. Every decision is made on the device from the allow-list, and license keys are checked offline on the device. Signature checks use only the revocation information already cached on the device; AEMS does not fetch it from the network.

How it works

AEMS is a headless Windows service plus a kernel driver, installed from one MSI:

Component Role
AEMSvc (AEMSvc.exe) The LocalSystem service. Reads the allow-list from the registry, sends it to the driver, decides every caught launch and relaunches approved applications elevated into the active console session. No window, tray icon, shell menu or dialog.
AEMS kernel driver (AEMSDriver.sys) Catches process creation for allow-listed paths and provides the elevation capability. It is signed by Microsoft. Its device can be opened by SYSTEM only; in addition the driver accepts a caller only when its image path ends in \Program Files\AEMS\AEMSvc.exe (a path check, not a signature check).

The short form of the decision model: the driver catches, the service decides, the driver executes. From 1.0.8.0 the driver holds a caught launch and AEMS suspends it, with the user's own token, until the service has decided; then it is replaced by the elevated relaunch or resumed unchanged. If the service is stopped, top-level launches run unelevated. If the service ends unexpectedly while a launch is suspended, the driver ends that process. Child processes of a governed (elevated) application do not start while the service is stopped. The full model is on the Security model page.

Where to start

  1. Install and deploy - the MSI, silent install, Intune and Configuration Manager.
  2. Licensing - from 1.0.6.0 AEMS elevates only with a valid license key from Logic Unknown ApS.
  3. Configure - approve your first application and read the settings reference.
  4. Troubleshooting - common problems and the events you are most likely to see.

What AEMS does and does not do

  • It elevates only the specific applications you allow-list - not arbitrary programs.
  • Child processes are not elevated by default: an allow-listed app's children run non-elevated unless that app explicitly opts in with AllowChildElevation=1 (and even then only children that are themselves opted-in continue the chain). See Approve applications for the opt-in model and its security warning.
  • From 1.0.6.0 an opted-in app can start its children elevated in place, as real child processes with their output and exit code (ChildInPlace: direct children, or the whole tree up to 8 levels). This is meant for wrapper programs that call other programs. The children must lie in a folder that standard users cannot change. See Children in place.
  • From 1.0.6.0 elevated programs use the machine's drive letters, not the user's own mapped or subst drive letters. See Drive letters of elevated programs.
  • Every elevation is logged to the Windows Application event log (source AEMS). There is no network, portal or online dependency.

Requirements

Item Requirement
Windows 64-bit (x64) Windows 10 22H2 (build 19045) or Windows 11; see Supported Windows versions.
Device type A kiosk with one interactive user. AEMS elevates into the active console session; multi-user Remote Desktop Services (several interactive sessions at once) is out of scope.
Driver signing On stock Windows 10 and 11 the AEMS driver must be signed by Microsoft to load. The AEMS MSI from Logic Unknown ApS contains that driver.
Installation Administrator rights on the device (interactive or silent MSI install, for example through Intune, Configuration Manager or your RMM tool).
Version Install AEMS 1.0.8.0 (service 0.1.9.0, driver 1.0.8.0, Allow-list Tool 1.3.0.0). It replaces 1.0.7.0 and earlier; a device on 1.0.5.0 or earlier is upgraded directly to 1.0.8.0 in one run, then restart the device once; see the release notes and Upgrade and repair.
License From AEMS 1.0.6.0 a license key from Logic Unknown ApS is needed for elevation; see Licensing.
Network None. AEMS has no cloud, portal or online dependency; license keys are checked offline and against the device clock.

Supported Windows versions

Windows 10 and Windows 11, x64 only, from build 10.0.19045 (Windows 10 22H2) and every later build. AEMS 1.0.6.0, including children in place, was measured on Windows 11 build 26200 (25H2) and on build 26300. The driver is validated up to build 26200. On build 26300 AEMSvc logs warning 2231 (the build is newer than the validated ones and the driver's start-up self-check passed), and elevation and children in place worked there; 26300 is not a validated build. Windows 10 22H2 is supported by the driver's build rule, but children in place were not validated on Windows 10.

AEMS 1.0.8.0 (driver 1.0.8.0, which holds the start of an allow-listed program until AEMS has decided, see Programs that finish very quickly) was measured on Windows 11 build 26200 (25H2) and on build 26300. Windows 11 24H2 (build 26100) has the same kernel code base as build 26200 and is covered by that measurement. Windows 11 23H2 (build 22631) is not validated, and Windows 10 22H2 was not in the scope of this validation. On build 26300 AEMS 1.0.8.0 still logs warning 2231: the driver's validated build limit stays 26200. On every build AEMS checks at every launch that the suspend took effect; if it did not, that launch is handled as in 1.0.7.0 and warning 2235 is logged.

  • Below build 19045 the driver refuses to load. This includes Windows 10 Enterprise LTSC 2021 (build 19044). sc start AEMSDriver then fails and AEMSvc logs 3005.
  • There is no upper build limit. The driver depends on internal Windows kernel structures and checks them itself at every start. On a build newer than the validated ones it loads, and elevation works only if that self-check passes: then AEMSvc logs warning 2231 at start, which names the build and says that the self-check passed. If it does not pass, AEMSvc logs error 3010 and nothing is elevated until an AEMS release supports that build.
  • Guard on a build newer than the validated ones. On such a build AEMSvc writes the REG_DWORD value BindAttemptBuild (the build number) under HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard before it connects to the driver, and removes it when the connection call has returned. If the device stopped during that call (for example a crash), the value is still there at the next start: AEMSvc then does not connect to the driver on that build, logs error 3212, and elevation stays off while the service keeps running. What to do: install an updated AEMS version. Only after you have checked the cause, set the REG_DWORD value ClearBindAttempt = 1 under the same key and restart the AEMS service to try once more (AEMS deletes the value after use). Do not create or edit BindAttemptBuild yourself. A value written on another build is ignored and removed, and on builds up to the validated one the guard is not active. If AEMSvc cannot write the value, it does not connect and elevation stays off (error 3214; retried); if it cannot remove it after the connection, the next start does not connect (error 3214, then 3212): check the permissions of the key. From 1.0.8.0 the uninstall removes the key when it is empty and keeps it when it holds BindAttemptBuild; see The driver connection guard key after an uninstall.
  • Policy switch. The REG_DWORD value DisableDriverBindOnUnvalidatedBuild = 1 under HKLM\SOFTWARE\Policies\Logic Unknown\AEMS (or HKLM\SOFTWARE\Logic Unknown\AEMS) stops AEMS from connecting to its driver on any build newer than the validated ones: error 3213, elevation off. Use it to keep devices that receive a new Windows feature update before a matching AEMS release unelevated instead of untested. Remove the value to allow the connection again.
  • Windows Server is not supported. AEMS targets single-interactive-session kiosk devices; multi-user RDS is out of scope.