Troubleshoot AEMS¶
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.
Start with the event log: AEMS writes every elevation, every refusal and every configuration
problem to Event Viewer -> Windows Logs -> Application, source AEMS. The
event reference at the end of this page lists every event and where
each one is explained.
Reading AEMS events¶
AEMS 1.0.6.0 has no message table for its events. Event Viewer therefore shows a line such as "The description for Event ID 1009 from source AEMS cannot be found" before the actual text, or reports that it cannot retrieve the message text. The text AEMS wrote follows under "The following information was included with the event", and is on the Details tab (event data). In PowerShell, read the text from the event data:
Get-WinEvent -FilterHashtable @{ LogName = 'Application'; ProviderName = 'AEMS' } -MaxEvents 50 |
Select-Object TimeCreated, Id, LevelDisplayName, @{ n = 'Text'; e = { $_.Properties[0].Value } } |
Format-List
Quick checks:
sc query AEMSvc- the service must be Running and set to start automatically.sc query AEMSDriver- the driver service must showSTATE : 4 RUNNING."C:\Program Files\AEMS\AEMSvc.exe" --license-status- exit code 0 means elevation is on, 1 means it is off (AEMS 1.0.6.0 and later).
Common problems¶
| Symptom | Likely cause / fix |
|---|---|
| App launches but stays non-elevated | App not on the allow-list, or its DataPath/HashSHA doesn't match (a hash mismatch shows error 3009, then 2004). Re-check the Applications\<Name> subkey. |
| Warning 2003, then 2004 | The driver caught the launch but the service found no matching entry, so it was not elevated. Install the driver and service from the same AEMS MSI and check DataPath. |
| A wildcard rule does not elevate | Look for the AEMS warning events (2012 at start, 2013 at launch, 2016 for an administrator); they name the reason. Wildcard rules work only from fixed drives on an accepted storage bus (removable media and USB, FireWire, SD/eMMC, iSCSI or virtual-disk storage are refused), from folders that only administrators can write; point them at the system drive. Warning 2014 means the current driver is not loaded yet, so wildcard rules never elevate: install the current AEMS MSI, and reboot only if 2014 is still logged afterwards. See Wildcard path rules. |
| Error 5000 and the AEMSvc service stopped | AEMSvc stopped after an internal failure. Windows restarts it automatically after 5 seconds, twice; after a third failure within a day it stays stopped. Event 5000 is in the Application log (source AEMS); the restarts appear as Service Control Manager events in the System log. Then start the AEMSvc service manually and contact support. |
| From 1.0.8.0: after AEMSvc stopped unexpectedly (or was ended), an allow-listed program that was started at that moment does not appear and shows in Task Manager as suspended for up to about 10 seconds, then disappears | Expected: AEMS keeps a started program suspended until it has decided how to start it. When the service ends unexpectedly, the driver ends those programs once the service connection is closed, which takes up to about 10 seconds; they never run without the decision. Start the program again after the AEMSvc service is running (Windows restarts it after 5 seconds). |
| Nothing happens / service not running | Check the AEMSvc service is running; check the AEMSDriver driver with driver diagnostics. |
AEMSDriver won't start (0x241) |
The driver is not Microsoft-signed. Install the AEMS MSI from Logic Unknown ApS, which ships the driver signed by Microsoft. |
| Elevation on a second interactive session | Out of scope - AEMS targets the active console session only. |
| A program worked elevated before 1.0.6.0 and fails now (a tool "not found", no proxy, a missing setting or license variable) | From 1.0.6.0 elevated programs get the machine environment, not the user's own variables: per-user PATH entries and every value under HKCU\Environment are not passed. Set the variable the program needs machine-wide (System Properties > Environment Variables > System variables, or Group Policy / Intune) and start the program again. See Compatibility effects. |
| Error 3009 "The environment for the elevated start of ... could not be built" | The user's profile folder or account name could not be determined, so the program was not elevated (a top-level program keeps running unelevated, 2004; a child is not started). Check that the user has a profile under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList and that the machine environment is readable; sign the user out and in. |
| Error 3009 "Building the owner (Administrators) and the default DACL of the elevated token failed" | The elevated token could not be prepared; nothing was elevated. Restart AEMSvc; contact support if it repeats. |
Since 1.0.6.0 a non-elevated program can no longer change a file that an elevated program created (for example under C:\ProgramData) |
Files that elevated programs create are owned by Administrators. Where the folder gives users write access only as creator, grant the Users group the needed rights on that folder explicitly. See The elevated token. |
A tool that an application with AllowChildElevation=1 starts through conhost.exe --headless <tool> (or conhost.exe <tool>) runs non-elevated since 1.0.6.0 |
Expected: a program that the console host process itself starts is never elevated. Start the tool directly from the application (not through conhost.exe): a direct child of a parent with AllowChildElevation=1 is still elevated. Commands typed in the console window of an elevated, allow-listed console program such as cmd.exe are not affected: they follow that entry's AllowChildElevation as before. |
| An allow-listed browser, Electron or WebView2 application does not work (blank windows, crashes, helper processes in their own windows) | Not supported as an elevated application in AEMS (from 1.0.6.0): such programs start sandboxed helper processes. Without "Children in place" AEMS governs them like any other child and starts them again outside the sandbox; with "Children in place" they are refused, so the program starts but its helpers do not. Remove the entry and run the program without elevation. See Limits. |
| A program that an allow-listed application starts does not start; the application reports "Access is denied" | With "Children in place" the child was refused. Most often its folder can be changed by standard users (a folder directly under C:\ with default permissions, or the user's %TEMP%). See A child program does not start in place. |
An elevated program does not find a network drive or a subst drive that the user sees |
Expected from 1.0.6.0: every program AEMS elevates resolves drive letters through the machine's drive letters, not the user's own. Use a local path, or a drive letter that is defined for the whole machine. See Drive letters of elevated programs. |
An elevated console program (for example cmd.exe) closes at once without output, exit code 0xC0000142 |
Its console host could not be started. This can happen when AEMS refused the console host (see the warnings around that time) or could not give it the machine's drive letters. Restart AEMSvc; contact support if it repeats. |
| Error 3009 "Child ... is not relaunched: its creator runs below High integrity" | A process that is not an AEMS-elevated application was reported as the creator of a governed child (for example a process that lowered its own rights); the child was not started, in either child mode. Not expected in normal operation; if it repeats, collect the events and contact support. |
Launchers and programs that start allow-listed programs¶
- A launcher that gets its target as a command-line argument needs "Allow user arguments"
(
AllowUserArguments=1) on its entry. Without it the entry is locked: the elevated start gets only the configuredArguments, the user's argument is dropped, and the launcher starts without its target. Set it only for a launcher whose command line cannot be turned into arbitrary elevation (see the security warning under Command line and arguments). - A program that itself starts another allow-listed program without elevation sees AEMS elevate that program again through its own entry: the start is caught like any start of an allow-listed program. If that program must run without elevation when it is started this way, remove its entry.
Driver diagnostics¶
What it does: checks the AEMS kernel driver's health and helps fix the common "driver not running / not loading" problems.
Quick check¶
Confirm the kernel-driver service is up:
sc query AEMSDriver
A healthy driver shows STATE : 4 RUNNING. (The AEMSvc user-mode service is
separate - sc query AEMSvc.) If the driver is not running, start it from an elevated prompt with sc start AEMSDriver and compare the error with the table below.
Reading the results¶
| Symptom | Meaning / fix |
|---|---|
| Service STATE : RUNNING | Driver is healthy. The device \\.\AEMS now exists (SYSTEM-only). |
sc start -> 577 / 0x241 STATUS_INVALID_IMAGE_HASH |
The .sys/.cat isn't signed by Microsoft, and the machine enforces driver signing. Install the AEMS MSI from Logic Unknown ApS, which ships the driver signed by Microsoft. |
sc start -> 1275 / 0x4FB ERROR_DRIVER_BLOCKED |
Microsoft's vulnerable driver blocklist blocked the driver. Ask Logic Unknown ApS through the contact page. |
sc start -> 50 / 0x32 ERROR_NOT_SUPPORTED |
The Windows-version gate: the driver refuses to load on Windows builds below 10.0.19045 (Windows 10 22H2); there is no upper build limit (see Supported Windows versions). Check the build number (winver). |
sc start -> 31 / 0x1F ERROR_GEN_FAILURE |
DriverEntry failed for another reason. Reinstall with the MSI and reboot; contact support if it repeats. |
sc start -> 2 / 0x2 ERROR_FILE_NOT_FOUND |
The .sys isn't where the service's ImagePath points. Reinstall. |
Driver signing¶
On stock Windows 10/11, kernel drivers must be Microsoft-signed (WHQL or
attestation) to load. A driver that is not Microsoft-signed installs fine but won't start (0x241). The AEMS MSI from Logic Unknown ApS ships the driver signed by Microsoft; reinstall from that MSI.
A child program does not start in place¶
First check the folder. A program is started in place only when it lies in a folder that
standard users cannot change. A folder created directly in the drive root (for example
C:\Contoso) does not qualify by default, because Windows gives Authenticated Users Modify on
every new folder under C:\. Run icacls <folder> and harden the folder with the three
commands in The folder rule.
Then go through the table from the top:
| Check | What you see | What to do |
|---|---|---|
| Is the device on AEMS 1.0.6.0 and does the user have a split token? | Every child is refused with warning 2224 [PRE_TOKEN], also programs in C:\Program Files. In the user's normal session whoami /groups shows a group as "Group used for deny only" (for example Network Configuration Operators). |
Update to AEMS 1.0.7.0 or later (install 1.0.8.0), which builds the elevated token from the user's full token (event 1226). See Users with a split token. |
| Did you try it as a standard user? | Children run, but there is no "started in place" event at all. | An administrator's launch uses the administrator passthrough: AEMS does not check the children and logs nothing for them. Verify with a standard user account. |
| Is the setting on? | The entry has AllowChildElevation=1 and ChildInPlace 1 or 2 (reg query "HKLM\SOFTWARE\Logic Unknown\AEMS\Applications\<Name>"; with a policy allow-list, under HKLM\SOFTWARE\Policies\Logic Unknown\AEMS\Applications). |
Set both values. ChildInPlace without AllowChildElevation=1 counts as off (warning 2230 at service start naming the entry). |
| Was the service restarted after the change? | The child is still relaunched as a separate copy (a new window, the application does not get its output). | Restart-Service AEMSvc. Settings are read at service start. |
| Warning 2220 "Children in place (ChildInPlace) is configured for ... but is not active: ..." (and warning 2225 for each launch) | The reason is in the text: the loaded driver is the old one, AEMS has no valid license, or the service could not connect to the driver. With the old driver or no connection, children are relaunched as a copy; without a license nothing is elevated. | Old driver: restart the device (the upgrade normally loads the new driver at once). Not licensed: apply a license key (event 3013, Licensing). Connection not ready: restart AEMSvc; contact support if 2220 stays. |
Warning 2213 Start of a child refused [PathGuard] |
The program lies in a folder that standard users can change, for example the user's %TEMP% or a folder directly under C:\ with default permissions. The text names the folder, the account and the right. If the text ends with own entry '<name>' and names no folder, the child's own allow-list entry is refusing (see warning 2012): fix that entry. A detail [NotCanonical] means the program was started by its 8.3 short name: start it by its long path. |
Harden the folder (The folder rule) or install the program under C:\Program Files. For an installer that unpacks a helper to %TEMP%: leave "Children in place" off for that entry (documented limit, from 1.0.6.0). |
Warning 3200 Start of a child refused [PathAlias] |
The program was started through an alias drive letter (subst), a symbolic link or a junction. |
Start it by its real path on a local drive. |
Warning 3201 Start of a child refused [VolumeNotFixed] |
The program lies on a network drive, a UNC path, removable media or a mounted ISO. | Copy it to a protected folder on a local fixed drive. |
Warning 2211 Start of a child refused [FileIdentity] |
The program lies on a volume that is not NTFS (ReFS, Dev Drive, FAT, exFAT). | Move it to an NTFS volume. |
| Warning 2224 "The AEMS driver refused ... child start(s) [PRE_DEPTH]" | The program is deeper than the setting allows: a grandchild with "Direct children", or deeper than 8 levels with "Whole tree". | Use "Whole tree", or give the program its own entry with ChildInPlace. |
Warning 2203 Start of a child refused [CreatorNotHeld] |
The application was started before the AEMS service was last restarted. | Close the application and start it again. |
Warning 2216 Start of a child refused [ArgumentsLocked] |
The child has its own entry with locked arguments, and its command line does not equal that entry's Arguments (leading and trailing blanks are ignored). |
Set the child entry's Arguments to the arguments the application passes, or set AllowUserArguments=1 on the child entry if that is safe. |
Warning 2215 Start of a child refused [HashedEntryNoPrecompute] |
The child has its own entry with HashSHA; such entries are refused in place (from 1.0.6.0). |
Remove HashSHA from the child's entry, or remove the child's entry. |
| Warning 2224 "The AEMS driver refused ... child start(s) [PRE_TOKEN]" | The child runs with a reduced or sandboxed token, typically a helper process of a Chromium, Edge WebView2 or Electron program. | Not supported in place; leave "Children in place" off for such programs. |
| Warning 2224 "The AEMS driver refused ... child start(s) [LIMIT_CREATOR]" | The application had more than 6 child starts waiting at once. | Starts are refused, not queued; let the application retry or start fewer programs at once. |
| Error 3240 "... result=notApplied ..." | AEMS could not give the program the machine's drive letters, so it did not start it (fail closed). | Restart AEMSvc; contact support if it repeats. |
| No AEMS event at all for the child | The application was started by an administrator (administrator passthrough), or the child is not started through the allow-listed application (for example a scheduled task, a COM server or Windows Installer starts it), so AEMS does not see it. | Such programs are outside the elevated tree; see Children in place. |
Every refusal means: the program is not started, the application gets "Access is denied", and no copy starts. Similar refusals of the same application are logged at most once per 10 seconds per application and reason; the next line says how many were not logged. Events 3200 and 3201 are logged at Warning level although their number is in the 3000 range.
Wildcard rule events¶
| ID | Level | Meaning |
|---|---|---|
| 1009 | Information | Caught app relaunched elevated; for a wildcard rule the text names the rule. |
| 2003 | Warning | For a standard user (from 1.0.6.0): the driver caught the launch but AEMSvc found no matching entry; NOT elevated, the original keeps running (followed by 2004). For an administrator (no matching entry, or a file that does not match a HashSHA-only pin): relaunched with the administrator's own real token (passthrough; for a no-match with the own command line). For a child of a governed parent: relaunched with child elevation denied. |
| 2012 | Warning | At configuration load: a wildcard entry that breaks a validity rule, or any entry with a missing or empty DataPath ([path]), was dropped; or an entry with a malformed HashSHA or PublisherThumbprint was KEPT as a refusing entry (every match refused with 2013 [MalformedRule]). Names the entry and the rule (code in brackets). |
| 2013 | Warning | A wildcard match (or a publisher-pinned exact entry) was refused at launch; names the image, the entry and the reason (folder, SID and right; owner; reparse point; drive type or alias; file open for writing; short or non-canonical path; or the signature or hash problem). 2013 always means the rule did not elevate via its own entry; for a child the text ends with "relaunched UNELEVATED" (parent without AllowChildElevation) or "IS still relaunched elevated ... by design" (parent with AllowChildElevation=1). Codes include MalformedRule (the entry has a malformed HashSHA or PublisherThumbprint; correct it and restart AEMSvc), WildcardInactive (the loaded driver is older than the one shipped in 1.0.6.0; install the current MSI, and reboot only if 2014 is still logged), RemovableVolume (the device reports removable media, or the disk is attached over a bus wildcard rules refuse; the text names the bus, for example "is attached over the USB bus"; move the file to the system drive), NotFixedVolume (network, RAM disk, or a drive letter redirected for the user, for example by subst or a per-user mapping; use a real local path), OpenFailed, NotCanonical, ReparsePoint, UntrustedOwner, WritableByOther, NotSigned, SignatureInvalid, PublisherMismatch, ThumbprintMismatch and HashMismatch. |
| 2016 | Warning | ADMINISTRATOR OVERRIDE: the rule's checks failed, but the user is an administrator, so the app was relaunched elevated with the administrator's own real token. |
| 5000 | Error | Unexpected error. From 1.0.6.0 it can also mean that AEMSvc stopped itself after an internal safety failure; nothing is elevated until it runs again. If AEMSvc ends unexpectedly, Windows restarts it automatically after 5 seconds, twice; after a third failure within a day it stays stopped. Event 5000 is in the Application log (source AEMS); the restarts and the final stop appear as Service Control Manager events in the System log. If it stays stopped, start the AEMSvc service manually and contact support. |
| 2014 | Warning | Wildcard rules are inactive because the loaded driver does not support them (protocol minor below 2); logged once at start. They are never elevated, and launches they match first are refused (2013 [WildcardInactive]). Install the current AEMS MSI; its upgrade normally unloads the old driver and starts the new one. If 2014 is still logged after that, the old driver is still loaded: reboot. If it stays after the reboot, the installed package does not contain driver 1.0.3.0 or later: install the current AEMS MSI (1.0.8.0) from Logic Unknown ApS. |
The driver connection guard key after an uninstall¶
On a Windows build newer than the validated ones AEMSvc keeps the key
HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard (see
Supported Windows versions). From 1.0.8.0 the uninstall
removes it when it is empty (a leftover ClearBindAttempt is removed with it). It is kept, with
its content, when it holds the value BindAttemptBuild. That value is written before every
connection attempt and removed after it; it is left behind when the device stopped during the
attempt, and also when AEMSvc itself was ended during it (for example by a forced stop at that
moment), without any crash. A reinstall on the same Windows build then does not connect to the
driver (error 3212). If you are sure the device did not stop in the driver connection, set the
REG_DWORD value ClearBindAttempt = 1 under that key and restart AEMSvc: AEMS tries once more and
removes the value. Values that AEMS does not write also keep the key. The MSI log does not record
this step; to see the result, check after the uninstall whether the key is still there
(reg query "HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard"): gone means it was removed, a
remaining key holds BindAttemptBuild or a value AEMS does not write. Uninstalling 1.0.7.0 or
earlier leaves the key in every case.
Event reference¶
Every event AEMSvc writes (Application log, source AEMS). Licensing events are described in
Licensing, the upgrade and migration
events in Upgrading from 1.0.5.0 or earlier, the wildcard events in Wildcard rule events,
and the children-in-place events in A child program does not start in place.
| ID | Level | Meaning | What to do |
|---|---|---|---|
| 1000 | Information | Service starting. | - |
| 1001 | Information | Service running (names the version). | - |
| 1002 | Information | Configuration loaded: number of allow-list entries, whether the policy allow-list is used, LogLevel, AdminPassthrough. |
Check the entry count after a change. |
| 1003 / 1004 | Information | Service stopping / stopped. | - |
| 1005 / 1006 | Information | Service installed / uninstalled (by the MSI). | - |
| 1007 | Information | Driver connected (device opened, handshake done). | - |
| 1008 | Information | Allow-list sent to the driver. | - |
| 1009 | Information | A caught program was relaunched elevated (names image, session and rule). | - |
| 1010 | Information | The caught original exited before the decision; relaunched anyway. From 1.0.8.0 this happens only when the start was not held (see 2235 / 2236). | If it repeats with 1.0.8.0, look for 2235 or 2236 before it. |
| 1011 / 1012 | Information | Legacy settings copied / legacy key removed (upgrade from 1.0.5.0 or earlier). | - |
| 1013 / 1014 / 1015 | Information | Licensing: valid license / license applied / upgrade grace started. | See Licensing events. |
| 2000 | Warning | Configuration key not found or not readable; running with defaults. | Check HKLM\SOFTWARE\Logic Unknown\AEMS. |
| 2001 | Warning | The allow-list is empty; nothing is elevated. | Add entries, then restart AEMSvc. |
| 2002 | Warning | A caught launch was not from an interactive session; skipped. | - |
| 2003 | Warning | The driver caught a launch but AEMSvc found no matching entry, or (administrator) the file does not match a HashSHA-only pin; details in Wildcard rule events. |
See there. |
| 2004 | Warning | A caught original was left running unelevated; the text names why. Follows 2003, 2013 and 3009, and is also logged on its own when the launch is refused for another reason the text names (for example not the console user and not an administrator, or the process could not be opened). An unlicensed refusal is reported by 2011 alone, without 2004. From 1.0.8.0 a held original is resumed first and then left running; "could not be opened (error 87)" for a program that finishes very quickly then occurs only when the start was not held (2235 / 2236). At a service stop one 2004 names how many caught programs were not decided yet. | Read the event before it, or the reason in the text. |
| 2005 / 2006 / 2007 | Warning | Legacy settings key present or not removable / legacy policy key holds settings / loaded driver is older than 1.0.3.0 (TamperProtection not enforced). |
See Upgrading from 1.0.5.0 or earlier. |
| 2008 / 2009 / 2010 / 2011 / 2015 | Warning | Licensing: expiring soon / grace / upgrade grace / launch not elevated because unlicensed / license read retried. | See Licensing events. |
| 2012 / 2013 / 2014 / 2016 | Warning | Wildcard rules and pins. | See Wildcard rule events. |
| 1200 | Information | A child started in place, elevated (names the program, the pids and the session). | - |
| 1201 | Information | The console host of an elevated console program was allowed. | - |
| 1202 | Information | Further "started in place" lines of one elevated program in the last minute, summarised (count). | - |
| 1221 | Information | The service is connected to the AEMS driver for children in place (with the number of child starts refused while it was not connected). | - |
| 1222 | Information | Children in place is active again (after 2220). | - |
| 1223 | Information | Children in place, summary at service stop. | - |
| 2200-2216, 2218, 2219 | Warning | Start of a child refused [reason]: the child was not started, no copy. 2200 RequestInvalid, 2201 ServiceStopping, 2202 WorkersBusy, 2203 CreatorNotHeld, 2204 Unlicensed (the license stopped being valid while the application ran), 2205 DepthLimit, 2206 ChildOpenFailed, 2207 ChildIdentity, 2208 UserMismatch, 2209 ChildFileBusy, 2210 FileOpenFailed, 2211 FileIdentity (not NTFS), 2212 ImageMismatch, 2213 PathGuard, 2214 InternalError, 2215 HashedEntryNoPrecompute, 2216 ArgumentsLocked, 2218 ConsoleHost, 2219 VerdictDeadline. |
See A child program does not start in place. |
| 2220 | Warning | At least one entry has ChildInPlace, but children in place are not active (old driver loaded, no valid license, or the service could not connect to the driver); names the entries and the reason. Logged at service start and when the state changes. |
See A child program does not start in place. |
| 2221 | Warning | Console hosts of elevated programs started while the AEMS service was stopped, starting or restarting, without the machine's drive letters (count). | Nothing, unless it repeats often; see Children in place. |
| 2223 | Warning | A blocked child of a program with children in place was not started again as a copy. | - |
| 2224 | Warning | The AEMS driver refused child starts [reason] (for example PRE_DEPTH, PRE_TOKEN, LIMIT_CREATOR, LIMIT_SESSION, LIMIT_TOTAL, TIMEOUT, BREAKER_OPEN); no process and no copy. |
See A child program does not start in place. |
| 2225 | Warning | For one launch: ChildInPlace is configured but not active, so its children are blocked and started again elevated (see 2220). |
See 2220. |
| 2226 / 2227 / 2228 / 2229 | Warning | A child allowed in place did not start after all (the driver did not accept the allow, its answer was unclear, the driver was being unloaded), or a launch could not be recorded for children in place. | Start the application again; contact support if it repeats. |
| 1224 | Information | When the user's un-elevated original of an allow-listed program was ended, the un-elevated programs it had already started were ended too, so they do not run twice (count). | - |
| 2232 | Warning | Not every program that the un-elevated original had already started could be checked or ended; such a program may run twice. | Check the program; see Children in place. |
| 1225 | Information | At service start: EndOriginalDescendants = 0 is set, so programs that a user's un-elevated original start had already started keep running un-elevated next to the elevated start (as in 1.0.5.0). |
Remove the value (or set it to 1) and restart AEMSvc if that was not intended. |
| 1226 | Information | 1.0.7.0+: the elevated token for this program is built from the user's full token, because the user's logon has a split token (User Account Control). Text: '<program>': the elevated token takes its identity from the user's full (linked) token, because the user's logon has a split token (UAC). Written after the elevated start. |
Nothing; see Users with a split token. |
| 2234 | Warning | 1.0.7.0+: the program was not started elevated (a child: not started), because the user's logon has a split token and the user's full token could not be read. AEMS never uses the filtered token instead. Text: '<program>' is not started elevated: the identity for the elevated token could not be taken from the user's token (<step>, <error>). When the user's logon has a split token (UAC), AEMS uses the user's full (linked) token and never the filtered one. Log the user off and on again; if this persists, contact support with this event. (for a child: The child '<program>' is not started: ...) |
Log the user off and on again, then start the program again. If it repeats, contact support with the event. |
| 2235 | Warning | 1.0.8.0+: a caught program could not be held before it started, so it may have run without administrator rights for a moment; the decision then runs as in 1.0.7.0 (a program that finishes very quickly can run twice, 1010, or not elevated, 2004). At most once per program per hour. Text: '<program>' (pid <n>) could not be held before it started (<reason>); it may have run without administrator rights for a moment. The decision runs as in AEMS 1.0.7.0 for this launch. Reasons: the driver had already ended the hold (it timed out, or the hold breaker is open after repeated timeouts, or it was caught before the hold was armed at service start); the process could not be opened or suspended; no thread was found in the new process after the suspend; the decision queue is full; it was no longer pending in the driver; the decision worker is busy (an earlier caught program has waited suspended for its decision for more than 30 s; logged once for that period, new launches are not suspended until it is decided). |
Occasional: nothing. Often: the service is overloaded or was suspended; check the device load. "no thread was found" on a Windows build that AEMS 1.0.8.0 was not validated on: contact support with the event. |
| 2236 | Warning | 1.0.8.0+, once per service start: the loaded driver does not hold caught programs before they start (it speaks an older protocol, for example driver 1.0.6.0), so programs that finish very quickly can still run twice or only without elevation, as in 1.0.7.0. Not expected after a completed upgrade: the upgrade loads driver 1.0.8.0 at once, and when the old driver cannot be unloaded the upgrade fails and asks for a restart. The event text still says that this is expected right after an upgrade until the device restarts; with 1.0.8.0 treat 2236 as a reason to restart. Also logged when AEMSvc could not set up the hold (the text says why). | Restart the device to load driver 1.0.8.0. If 2236 stays after the restart, the installed package does not contain driver 1.0.8.0: install the AEMS 1.0.8.0 MSI. |
| 2237 | Warning | 1.0.8.0+: AEMSvc could not resume a suspended caught program (count and status, at most once per hour). Such a program stays suspended until it is ended. | End the program in Task Manager and start it again; contact support with the event if it repeats. |
| 2233 | Warning | Once per service start: lists the exact-path allow-list entries on local fixed disks whose program or folder standard users can change. The entries keep working, but any user can replace the program. | Harden the folder (The folder rule) or move the program under C:\Program Files. |
| 2230 | Warning | At service start: an entry's ChildInPlace is invalid or set without AllowChildElevation=1, so it counts as off; names the entry. |
Fix the entry, then restart AEMSvc. |
| 2231 | Warning | At service start, after a successful connection to the driver: the Windows build is newer than the builds this driver version was validated on (names the build); the driver's start-up self-check passed on this build. | Check for an updated AEMS version that is validated on this build. |
| 3000 | Error | AEMSvc.exe --install or --uninstall was run without administrator rights. |
Run it elevated (the MSI does this). |
| 3001 / 3002 | Error | Service install / uninstall failed, or the service recovery settings could not be set (3001; the install still succeeds). | Repair or reinstall with the MSI. |
| 3004 | Error | Internal service error (thread or event creation failed). | Restart AEMSvc; contact support if it repeats. |
| 3005 | Error | The driver device could not be opened; the service runs idle. | Check sc query AEMSDriver and Driver Diagnostics. |
| 3006 | Error | Driver handshake failed. | Reinstall with the MSI; reboot. |
| 3007 | Error | The allow-list could not be sent to the driver; the entries are not enforced. | Restart AEMSvc; reboot if it repeats. |
| 3008 | Error | The privileges the driver grants could not be enabled; elevation is disabled. | Reboot; contact support if it repeats. |
| 3009 | Error | Elevation failed; the text names the step. Includes a standard user's launch of a file that no longer matches the HashSHA of a hash-only entry ("On-disk hash ... no longer matches the configured HashSHA; refusing to relaunch", followed by 2004), a token, session or relaunch failure, a governed child whose command line is longer than the driver forwards, a governed child whose creator runs below High integrity ("Child ... is not relaunched: its creator runs below High integrity (0x...)", the child is not started in either child mode), an elevated start whose environment could not be built ("The environment for the elevated start of ... could not be built (machine environment, user profile folder or account name unavailable, ...); not elevated (fail closed)", followed by 2004 for a top-level launch: the app keeps running unelevated; a child is not started), and a token whose owner and default permissions could not be prepared ("Building the owner (Administrators) and the default DACL of the elevated token failed (error ...)", followed by "Building the elevated token ... failed (NTSTATUS 0xC000005A)"). |
For a hash mismatch: update HashSHA (after a vendor update) or investigate the file. For the environment: check that the user has a profile folder (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList) and that the machine environment (HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment) is readable; see Environment of elevated programs. For the owner: restart AEMSvc; contact support if it repeats. Otherwise read the step named. |
| 3010 | Error | The driver refused to grant privileges because its start-up self-check does not recognise the Windows token layout on this build; elevation is disabled. Most likely after a Windows feature update to a build newer than the validated ones. | Check the supported Windows versions; install a current AEMS release. |
| 3011 | Error | The driver protocol does not match the service (old driver still loaded, or driver and service from different packages); elevation is disabled. | Restart the device (an old driver can still be loaded after the upgrade); if 3011 stays, install driver and service from the same AEMS MSI. |
| 3012 | Error | Legacy settings migration failed; nothing was changed. | See Upgrading from 1.0.5.0 or earlier. |
| 3013 / 3014 | Error | Licensing: not licensed / license refused or not written. | See Licensing events. |
| 3200 / 3201 | Warning | Start of a child refused [PathAlias] (alias drive letter, symbolic link, junction) / [VolumeNotFixed] (network, UNC, removable, ISO). Logged at Warning level. |
See A child program does not start in place. |
| 3212 | Error | On a Windows build newer than the validated ones, the last attempt to connect to the driver did not complete (the device probably stopped during it, or AEMSvc was ended during it), so AEMSvc did not connect again: elevation is off, the service keeps running. | Install an updated AEMS version. Only after you checked the cause: set REG_DWORD ClearBindAttempt = 1 under HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard and restart AEMSvc to try once more. See Supported Windows versions and the guard key after an uninstall. |
| 3214 | Error | The connection guard value BindAttemptBuild under HKLM\SOFTWARE\Logic Unknown\AEMS-DriverBindGuard could not be written (AEMS does not connect to its driver, elevation is off, retried) or could not be removed after the connection (the next start will not connect, event 3212). |
Check the permissions of that registry key. |
| 3213 | Error | On a Windows build newer than the validated ones, the policy value DisableDriverBindOnUnvalidatedBuild = 1 forbids connecting to the driver: elevation is off. |
Install an updated AEMS version, or remove the policy value. |
| 3210 / 3211 | Error | The service's connection to the AEMS driver for children in place failed (retried every second) / its children-in-place component could not start. | Restart AEMSvc; contact support if it repeats. |
| 3240 | Error | The machine's drive letters (global device map) could not be applied to an elevated program, a child started in place or its console host; that process was not started (fail closed). The text names the step and the status. | Restart AEMSvc; contact support if it repeats. |
| 5000 | Error | Unexpected error, or AEMSvc stopped itself after an internal safety failure (see Wildcard rule events). Event 5000 is in the Application log; restarts appear as Service Control Manager events in the System log. | If AEMSvc stays stopped, start it and contact support. |