Skip to content

AEMS release notes

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.

The AEMS documentation describes the current version only. Where behaviour depends on the version, the text says "from 1.0.x.0".

AEMS 1.0.8.0 (released 2026-11-20)

Components: AEMSvc 0.1.9.0, AEMS driver 1.0.8.0 (a new driver, signed by Microsoft, protocol 0x00020004; there is no driver 1.0.7.0: AEMS 1.0.7.0 shipped driver 1.0.6.0), Allow-list Tool (AEMSAllowlist.exe) 1.3.0.0. AEMS 1.0.8.0 is the version to install. AEMS stays fully offline: no new network or online dependency.

Fixed

  • Programs that finish very quickly no longer run twice or only without elevation. Up to 1.0.7.0 the user's own start of an allow-listed program ran without administrator rights for a fraction of a second while AEMS decided. A program that did its whole work in that time ran twice (once without administrator rights, then elevated, event 1010), or, when the program that started it had already let go of it, it was not elevated at all (event 2004, "could not be opened (error 87)"). From 1.0.8.0 the driver holds the start of such a program for a moment until AEMS has suspended the new process, before its first instruction runs. The process is then ended and started again elevated, or resumed unchanged when it is not to be elevated. The program that started it (Explorer, cmd.exe, PowerShell, a script) sees a normal, successful start: no "Access is denied", no error dialog. See Programs that finish very quickly.
  • The uninstall removes the empty key HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard. On a device that ran on a Windows build newer than the validated ones, the uninstall of 1.0.7.0 and earlier left this empty key (and with it the Logic Unknown vendor key). The uninstall of 1.0.8.0 removes it, unless it holds the value BindAttemptBuild: that value means a connection attempt to the driver did not complete, and it is kept on purpose (see Driver connection guard). Uninstalling 1.0.7.0 or earlier still leaves the key; it goes with the first uninstall of 1.0.8.0 or later.

Changed

  • An allow-listed program that is to be elevated waits, suspended, until AEMS has decided. AEMS decides one launch at a time. When several allow-listed programs start at once (for example a logon script), the later ones wait their turn suspended instead of running without administrator rights first. See Programs that finish very quickly.
  • The upgrade loads the new driver at once. The installer stops the old driver and starts driver 1.0.8.0, so the hold works right after the upgrade, without a restart (measured on the upgrade from 1.0.7.0). When the old driver cannot be unloaded, the upgrade fails and asks for a restart. If the old driver 1.0.6.0 is nevertheless still loaded after a completed upgrade (not expected), AEMS behaves exactly as 1.0.7.0 for these programs and logs warning 2236 once at every service start; restart the device. The text of 2236 still says that it is expected right after an upgrade until the restart; with 1.0.8.0 treat it as a reason to restart.
  • New events 2235, 2236 and 2237 (Warning). See the event reference.

Validation of the new driver behaviour. Measured on Windows 11 25H2 (build 26200) and on build 26300. Windows 11 24H2 (build 26100) has the same kernel code base as build 26200 and is covered by that measurement. On build 26300 AEMS 1.0.8.0 still logs warning 2231: the driver's validated build limit stays 26200. Not validated: Windows 11 23H2 (build 22631). Windows 10 22H2 (build 19045) was not in the scope of this validation. 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.

Upgrade: install the AEMS 1.0.8.0 MSI over 1.0.7.0 or 1.0.6.0 (msiexec /i AEMS.msi /qn, one run); settings, allow-list and license are kept, and the new driver is loaded by the upgrade. A device that runs 1.0.5.0 or earlier is upgraded directly to 1.0.8.0 in one run, without installing 1.0.6.0 or 1.0.7.0 first; restart the device once afterwards. The upgrade moves the settings as described for 1.0.6.0 (Upgrading from 1.0.5.0 or earlier). Details: Upgrade and repair.

AEMS 1.0.7.0 (released 2026-11-20)

Components: AEMSvc 0.1.8.0, AEMS driver 1.0.6.0 (unchanged: the same driver file as in AEMS 1.0.6.0, protocol 0x00020003), Allow-list Tool (AEMSAllowlist.exe) 1.3.0.0. AEMS 1.0.7.0 is a service-only fix on top of 1.0.6.0; everything in the 1.0.6.0 notes below applies to it.

Fixed

  • Children in place did not work for standard users whose Windows logon has a split token. Windows gives a standard user a split token when the user is a member of a group that User Account Control filters (for example Network Configuration Operators, Power Users, Backup Operators or Print Operators) or holds a privilege that User Account Control filters. For such a user every program that an elevated allow-listed program started was refused with "Access is denied" (warning 2224 with [PRE_TOKEN]): in 1.0.6.0 children in place did not work for them at all. AEMS now builds the elevated token from the user's full token, and children in place work for these users too (measured: the elevated program, its children and a chain of them started in place, with no 2224). Event 1226 shows that this path was taken. See Users with a split token.
  • Failed installs no longer remove the driver service. When an installation failed, the installer's rollback could remove the driver service of an existing AEMS installation. The rollback no longer does this.
  • Users without a split token are not affected: they behave exactly as in 1.0.6.0 (measured: same events and results as with 1.0.6.0).

Changed

  • For a user with a split token the elevated program now runs in the user's full logon session, as a program elevated by User Account Control does; groups that are "deny only" in the user's normal session are enabled in the elevated program. The same applies to such users who do not use children in place. Details and consequences: Users with a split token.
  • New events 1226 (Information) and 2234 (Warning). See the event reference.

Upgrade: install the AEMS 1.0.7.0 MSI over 1.0.6.0 (msiexec /i AEMS.msi /qn); the driver file is unchanged. A device that runs 1.0.5.0 or earlier is upgraded directly to 1.0.7.0 as described for 1.0.6.0 (Upgrading from 1.0.5.0 or earlier).

AEMS 1.0.6.0 (released 2026-11-19)

Components: AEMSvc 0.1.7.0, AEMS driver 1.0.6.0 (protocol 0x00020003), Allow-list Tool (AEMSAllowlist.exe) 1.3.0.0. The components have their own version numbers: "driver 1.0.6.0" is the driver inside the AEMS 1.0.6.0 MSI; "driver 1.0.3.0" elsewhere in this documentation means the first driver with protocol 0x00020002 (wildcard matching), not the AEMS 1.0.3.0 MSI listed under earlier versions.

Highlights

  • Children in place. An approved application can start other programs elevated as real children, with their output, exit code and handle, instead of having them blocked and relaunched as a detached copy. Per entry, ChildInPlace (with AllowChildElevation=1): 1 direct children, 2 the whole tree up to 8 levels. For wrapper programs that call other programs use the whole tree. The programs must lie in a folder that standard users cannot change; a folder created directly under C:\ does not qualify until its permissions are hardened. See Children in place.
  • Machine drive letters for elevated programs. Elevated programs no longer follow the user's own drive letters. See Drive letters of elevated programs.
  • No upper Windows build limit. The driver loads on Windows 10 22H2 (build 19045) and every later build. This release, including children in place, was measured on Windows 11 builds 26200 and 26300. The driver is validated up to 26200; on 26300 AEMSvc logs warning 2231 and elevation worked. Children in place were not validated on Windows 10. See Supported Windows versions.

Security

  • Elevated programs no longer create objects owned by the standard user. The token AEMS builds for a standard user is now owned by Administrators, with the default permissions of an administrator elevated through UAC. Files and keys an elevated program creates in protected places (for example an installer under C:\Program Files) can no longer be changed by the user afterwards. Objects created under AEMS 1.0.5.0 or earlier keep their owner; reinstall the affected applications. See The elevated token.
  • Elevated programs no longer receive the user's own environment variables. They get the machine environment plus profile variables computed by AEMS, never the user's HKCU\Environment, so a standard user can no longer make an allow-listed program load their code through variables such as COR_PROFILER, DOTNET_STARTUP_HOOKS or PATH. If that environment cannot be built, the program is not elevated (error 3009). The administrator passthrough keeps the administrator's own environment. See Environment of elevated programs.
  • Elevated programs use the machine's drive letters. Every program AEMS elevates for a standard user, every child started in place and the console host of each elevated console program resolve drive letters through the machine's drive letters, not through the user's own. A standard user can no longer redirect a drive letter (also C:) for an elevated program. Consequence: elevated programs do not see the user's own mapped network drives or subst letters. A thread that impersonates the user still sees the user's drive letters (known limit). If the machine drive letters cannot be applied, the program is not started (error 3240).
  • Children in place are checked against the file that runs. A child started in place must lie in a folder that standard users cannot change, on a local fixed drive, and must run as the same user with the same token. Everything else is refused, with no copy. See Children in place.
  • The driver closes a gap where an elevated application could start a program elevated through the system console host (conhost.exe), bypassing default-deny child governance. Elevated console programs such as cmd.exe work as before. A parent with AllowChildElevation=1 that starts a tool through conhost.exe --headless <tool> now gets the tool non-elevated.
  • Known limit: programs that finish very quickly run twice (fixed in 1.0.8.0, see above). The user's original start of an allow-listed program runs without administrator rights for a fraction of a second until AEMS has started the elevated program. A wrapper that does its whole work in that time runs twice: once without administrator rights (its work typically fails or is incomplete) and once elevated (measured in 10 of 10 quick starts, with EndOriginalDescendants on and off). This is how allow-listed programs have always been caught, also in 1.0.5.0; no AEMS setting changes it. Programs whose first action must not run without administrator rights are affected; programs that take longer than about half a second to reach their real work, or whose first attempt simply fails without side effects, are not affected in practice. See Children in place.
  • Known limits of children in place (see What cannot be closed):
  • helpers that an installer unpacks into the user's %TEMP% and starts are refused, with no copy (documented limit of 1.0.6.0; leave "Children in place" off for such installers);
  • an MSI that an in-place program installs runs its impersonated custom actions in the Windows Installer custom-action server, outside the elevated tree and outside AEMS control; the installation completes, but those actions are not governed;
  • scheduled tasks, COM servers and WMI processes that an elevated program starts are outside the tree;
  • children started through an 8.3 short name, an alias drive letter, a symbolic link or a junction, or from a network drive, a UNC path, removable media or a mounted ISO are refused;
  • sandboxed helpers of Chromium, Edge WebView2 and Electron programs are refused; more than 6 child starts waiting at once per program and trees deeper than 8 levels are refused;
  • children of programs started before an AEMS service restart are refused until the program is restarted.
  • Not changed by this release: %TEMP% and the profile stay writable by the user, and a file an installer stages in %TEMP% and then moves into place keeps the user's write access (see Limits).

Compatibility

  • Per-user PATH entries and all other per-user environment variables (for example proxy variables, JAVA_HOME, vendor variables) no longer reach elevated programs; set them machine-wide. OneDrive*, HOMESHARE and CLIENTNAME are not set; HOMEDRIVE/HOMEPATH and APPDATA always point to the local profile (an Active Directory home drive or redirected AppData is not reflected). Full list: Compatibility effects.
  • Files an elevated program creates in folders where users have write access only as creator (for example under C:\ProgramData) are no longer writable by the user's non-elevated programs.

New

  • Children in place (ChildInPlace, see Highlights). Entries without it handle child processes exactly as in 1.0.5.0.
  • License key. AEMS elevates only with a valid license key from Logic Unknown ApS; a new installation without a key does not elevate (event 3013). The key is checked offline on the device; AEMS has no portal and no online dependency. A trial license runs 30 days and has no grace after it expires. Keys can be applied with the MSI property LICENSEKEY, with AEMSvc.exe --set-license, as a policy value or bundled into a customer MSI. Devices that ran 1.0.5.0 or earlier get a one-time 30-day upgrade grace. See Licensing.
  • Wildcard path rules. An allow-list entry can name an executable by a path pattern (*, ?), pinned by publisher or hash and elevated only from a folder that only administrators can write. See Wildcard path rules.
  • Publisher pins. New values Publisher and PublisherThumbprint check the file's embedded Authenticode signature, also on exact-path entries. An entry with a malformed HashSHA (not 64 hex digits) or PublisherThumbprint (not 40 hex digits) is kept as a refusing entry (warning 2012; every launch it matches is refused with 2013 [MalformedRule]). An entry with a missing or empty DataPath is dropped (warning 2012).
  • Administrator override. When a rule's checks fail for an administrator, AEMS relaunches the app with the administrator's own real token and logs warning 2016.
  • Fail closed on unmatched catches. When the driver catches a launch but AEMS finds no matching entry, a standard user's program is not elevated (warning 2003, then 2004).
  • Inactive wildcard rules refuse. While the driver of the previous version is still loaded, wildcard rules never elevate, and a launch a wildcard rule matches first is refused (warning 2014 at start, 2013 [WildcardInactive]).
  • Service recovery. If AEMSvc ends unexpectedly, Windows restarts it after 5 seconds, twice; after a third failure within a day it stays stopped (event 5000).
  • New events 1011, 1012, 1013, 1014, 1015, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 3012, 3013 and 3014, and for children in place 1200-1202, 1221-1225, 2200-2216, 2218-2221, 2223-2233, 3200, 3201, 3210-3214 and 3240; event 5000 can also mean that AEMSvc stopped itself after an internal safety failure. See the event reference.

Changed

  • Registry path. The configuration moves to HKLM\SOFTWARE\Logic Unknown\AEMS and the policy override to HKLM\SOFTWARE\Policies\Logic Unknown\AEMS. The MSI upgrade migrates the settings key and verifies the copy; a policy that writes the legacy policy key must be re-targeted. Value names and meanings are unchanged. See Upgrading from 1.0.5.0 or earlier.
  • TamperProtection. The driver protects exactly HKLM\SOFTWARE\Logic Unknown\AEMS and its subkeys, and allows 64-bit registry reads with an explicit registry view (for example Intune detection rules) while TamperProtection is on.
  • Upgrade. The MSI removes the old version first and refuses to start while the driver of the previous installation is still loaded and marked for deletion ("Restart the computer, then run this installation again").
  • Repair. With TamperProtection on, a repair skips its registry write instead of failing with Error 1406.
  • Uninstall also removes a leftover legacy settings key from 1.0.5.0 or earlier.
  • Downgrade over 1.0.6.0 is blocked by the MSI.
  • Allow-list Tool 1.3.0.0, the tool version for AEMS 1.0.6.0: writes the new registry path, adds wildcard path rules, reads Publisher and PublisherThumbprint from a signed file, and has the "Children in place" choice (Off, Direct children, Whole tree). It always writes Arguments, AllowChildElevation, AllowUserArguments and ChildInPlace, so an import replaces a stale value.
  • Fewer double starts. When the user's un-elevated original of an allow-listed program is ended, the un-elevated programs it had already started are ended too (event 1224, warning 2232 when not all could be ended). A program that already did its work in that fraction of a second is not undone. The new value EndOriginalDescendants = 0 keeps the 1.0.5.0 behaviour (event 1225).
  • Warning for open folders. Warning 2233 at every service start lists the exact-path entries on local fixed disks whose program or folder standard users can change.
  • Driver connection guard on new Windows builds. On a build newer than the validated ones, AEMSvc does not connect to its driver again after a connection attempt that did not complete (error 3212; ClearBindAttempt under HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard to try once more), and the value DisableDriverBindOnUnvalidatedBuild = 1 forbids the connection on such builds (error 3213); error 3214 when the guard value cannot be written or removed. See Supported Windows versions.
  • Windows builds. The driver no longer has an upper Windows build limit. It loads on build 19045 and later; on a build newer than the validated ones elevation depends on the driver's start-up self-check (warning 2231 when it passed, error 3010 when it failed).
  • Customer MSI bundler (Build-MsiWithSettings.cmd, provided by Logic Unknown ApS). Optional license field; legacy key lines in older .reg files are rewritten to the new path.
  • License policy value. An empty or blank policy value License is ignored, so clearing the policy field never hides a valid base license.

Action required: run the MSI once and restart the device after the upgrade (again if AEMSvc logs 3011, 2014 or 2220 after the restart: the old driver is then still loaded); harden the folders of programs that should start in place, and check the folder of every exact-path entry, not only of in-place entries; apply a license key within the 30-day upgrade grace, and move policies and scripts to the new registry path after the devices run 1.0.6.0. Set environment variables that elevated programs need machine-wide, and reinstall applications that were installed elevated under 1.0.5.0 or earlier.

Earlier versions

AEMS MSI version Change stated in the documentation
1.0.5.0 Last version that uses the legacy registry key; upgrade path to 1.0.6.0 documented in Upgrading from 1.0.5.0 or earlier.
1.0.3.0 Driver protocol 2: the driver forwards the full command line and the identity of each caught launch. New value AllowUserArguments. The decision follows the token of the launched process ("Run as different user" with an administrator account, other standard accounts).
1.0.2.0 The allow-list is kept when AEMS is upgraded.
1.0.1.0 Upgrading from 1.0.1.0 removes the base allow-list; export it first.