Script Tasks Fail with Error: "The interpreter for Command Script is not installed"

Products

• IT Management Suite

Issue/Introduction

Users may encounter failures when running Command Script or PowerShell tasks on specific client machines. The tasks fail immediately with an error stating that the necessary interpreter (such as cmd.exe or powershell.exe) is not installed or cannot be found, even though these interpreters are present and functional on the local system.

The interpreter for "Command Script" is not installed, or has not been added to the command path.
The interpreter for "PowerShell Windows" is not installed, or has not been added to the command path.

The Agent logs from the client machine shows this warning:

Failed to launch process on active desktop, error: 2.
-----------------------------------------------------------------------------------------------------
Date: 4/15/2026 3:11:08 PM, Tick Count: 721049609 (8.08:17:29.6090000), Size: 283 B
Process: AeXNSAgent.exe (33560), Thread ID: 68364, Module: BaseTaskHandlers.dll
Priority: 2, Source: aw32lib

 

Environment

ITMS 8.7.x, 8.8.x

Cause

While the Symantec Management Agent (SMA) attempts to execute a script, it relies on a specific helper executable, AeXAgentDesktop.exe, to launch the process on the active desktop. If this file is missing or blocked, the agent reports a "File Not Found" error (Error 2), which the console translates as a missing interpreter.

The root cause is the absence or inability to access the following file on the client machine: C:\Program Files\Altiris\Altiris Agent\AeXAgentDesktop.exe

Key Contributing Factors:

1. Security Software Interference: EDR or Anti-Virus tools may flag and quarantine AeXAgentDesktop.exe or block the temporary script files created in the TempExecutables folder.

2. Incomplete Installation: The file may have failed to copy during an agent upgrade or installation.

Resolution

1. Diagnostic Steps

To confirm if this is the cause, check for the presence of the executable and review the agent logs.

Diagnostic Check	Expected Result	Actual (Issue) Result
File Path Check	AeXAgentDesktop.exe exists in the Altiris Agent folder.	File is missing or renamed.
Agent Logs	Process started or Script saved messages.	Failed to launch process on active desktop, error: 2.
Manual Execution	Script runs fine when executed manually on the box.	Script fails only when sent via ITMS.

Note: Error 2 is a Windows system error code for "File Not Found".

2. Log Analysis

Review the Symantec Management Agent logs located at C:\ProgramData\Symantec\Symantec Agent\Logs. Look for the following entry:

Failed to launch process on active desktop, error: 2.

-----------------------------------------------------------------------------------------------------

Date: 4/15/2026 3:11:08 PM, Tick Count: 721049609 (8.08:17:29.6090000), Size: 283 B

Process: AeXNSAgent.exe (33560), Thread ID: 68364, Module: BaseTaskHandlers.dll

Priority: 2, Source: aw32lib

3. Resolution Steps

1. Verify Exclusions: Ensure your Anti-Virus/EDR provider has exclusions set for the Altiris Agent installation directory and the temporary execution path:

   • C:\Program Files\Altiris\Altiris Agent\

   • C:\ProgramData\Symantec\Symantec Agent\TempExecutables\

2. Restore Missing File: If AeXAgentDesktop.exe is missing, try a Repair or Reinstall of the Symantec Management Agent on the affected endpoint.
   
   Note: Manual File Replacement (if preferred approach): 

   1. Copy the missing executable from another managed computer running the exact same agent version to the Altiris Agent folder on the affected machine

   2. Service Restart: After replacing the file, start the Symantec Management Agent service.

---

Advanced Trace (If issue persists and further support is needed):

Use Process Monitor (ProcMon) to identify if a security "thread protection" software is deleting the script files instantly upon creation.

Steps to Capture ProcMon Trace

1. Download and Prepare

• Download Process Monitor from Microsoft Sysinternals:
  https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

• Extract it to a local folder (e.g., C:\ProcMon)

2. Initial Launch

• Run Procmon.exe (as Administrator)

• By default, it will start capturing immediately

3. Prepare the Capture Environment

1. Stop capturing:
   • Click File > Capture Events (or press Ctrl + E)
2. Reset filters:
   • When the filter window appears → Click Reset → Apply → OK
3. Clear existing events:
   • Click Edit > Clear Display (or press Ctrl + X)
4. Enable detailed logging:
   • Go to Filter menu → Ensure Enable Advanced Output is checked

4. Capture the Issue

1. Get ready to start the affected Script task against client machine.
2. Start capture: Press Ctrl + E
3. Reproduce the issue (trigger the failing script task). Wait until the task failure occurs. 
4. Stop capture: Press Ctrl + E again.
5. Record the time this task failed.

5. Save the Trace

1. Click File > Save (or press Ctrl + S)
2. Select:
   • All Events
   • Native Process Monitor Format (PML)
3. Save the file
4. Compress (ZIP) the .PML file before sending it to Broadcom Support team for further assistance.

Additional Information

What exclusions should be considered for Symantec Management Platform and Agents to function correctly with an anti-virus solution installed?