Agent Install Completes but the amagent Service Is Missing or Will Not Start (Windows)

The Automox agent installer can report success while the Windows service (amagent, shown as "Automox Agent" in Services) is missing, or is present but will not start and sits in a Starting or Stopped state. When that happens the device never checks in even though the install looked complete. Work through the checks below to identify which of the two situations you have, then apply the matching fix.

Applies to

• Windows devices where the Automox agent install completed but the device is not checking in.
• The amagent service is missing from Services, or is present but will not reach a Running state.

Step 1: Confirm the state of the service and the binary

1. From an elevated command prompt, run sc query amagent. If it returns "The specified service does not exist," the service is missing. If it returns a state such as STOPPED or START_PENDING, the service exists but is not running.
2. Confirm the agent binary is present at C:\Program Files (x86)\Automox\amagent.exe. A registered service with a missing binary is a common cause of a failed start.
3. Open the Windows Event Viewer, go to Windows Logs → System, and look for Service Control Manager events referencing the Automox Agent service around the time it tried to start.

Case A: the service exists but will not start

Common causes:

• The binary is missing or the install is corrupted. If the service is registered but amagent.exe is not in the Automox folder, Windows reports an error such as "Error 2: The system cannot find the file specified." This indicates a corrupted or incomplete install, and a plain reinstall usually will not fix it because leftover service definitions and registry entries interfere. Clean up the remnants first, then reinstall. See Cannot Uninstall Automox Agent and run the CleanUp-AxAgent script before reinstalling.
• Security software is blocking or quarantining the process. EDR, EPP, or application-control software can block or quarantine amagent.exe or a subprocess, which shows up as repeated start failures or timeout events in the System log (for example, "A timeout was reached (180000 milliseconds) while waiting for the Automox Agent service to connect"). Allow-list Automox through your security software. See Automox Agent Service Errors in the Windows Event Viewer, which covers the relevant Event Viewer signatures and allow-listing.
• The service failed to start once and did not recover. Windows recovery settings only trigger after an initial successful start. Try restarting it from an elevated prompt with net stop amagent then net start amagent, and review the resulting System log events.

Case B: the service is missing entirely

If sc query amagent reports that the service does not exist:

1. First, fully clean up and reinstall. Leftovers from a partial install are the most common reason a new install does not register the service. Run the CleanUp-AxAgent script from Cannot Uninstall Automox Agent, then reinstall the agent.
2. If the service is still missing after a clean reinstall and amagent.exe is present in C:\Program Files (x86)\Automox\, rebuild the service registration. See How to rebuild the Automox Service from scratch (Windows Only). Use this only when uninstalling and reinstalling has not worked.
3. Confirm the install ran with administrative privileges. An install launched without elevation can fail to create the service.

Not this article

If the amagent service is present and Running but the device still never appears in the console, that is a different issue (usually check-in or registration on silent or imaged deployments). See Agent Is Installed and Running but the Device Never Appears in the Automox Console (Intune and Silent Deployments).

When to contact Support

If the service still will not install or start after a clean reinstall, contact Automox Support with the device name, the output of sc query amagent, the relevant Service Control Manager events from the System log, and the agent logs from C:\ProgramData\amagent\.