--- title: "Configure interpreters" slug: "configure-interpreters-3" tags: ["Product Usage", "ACC 8.3.x"] updated: 2026-09-09T18:02:33Z published: 2026-09-09T18:02:33Z canonical: "docs.trellix.com/configure-interpreters-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure interpreters You can configure interpreters to control the execution of additional scripts. 1. Map an interpreter with a file or script extension: `sadmin scripts add extension interpreter1 [interpreter2]...``sadmin scripts add .vbs wscript.exe cscript.exe` This command enables Application Control to enforce that `wscript.exe` and `cscript.exe` can execute a `.vbs` script (when the script file and interpreters are allow listed). After the association is defined, `wscript.exe` and `cscript.exe` can also execute other script files (provided the interpreter can read and understand the instructions in the script file). The association is effective immediately and applies to all new interpreter instances initiated after running this command. If needed, you can associate additional interpreters with a script or file type. For example: `sadmin scripts add .vbs zscript.exe` If you try to add an interpreter that is already associated with a file or extension type, no action is taken. > [!NOTE] > Note > > Application Control supports a special tag 16 Bits as a synthetic extension for the 16-bit binaries. To control execution for the 16-bit binaries, execute these commands. > > - `sadmin scripts add 16Bit wowexec.exe` > - `sadmin scripts add 16Bit ntvdm.exe` 2. View interpreter and file extension associations `sadmin scripts list` Sample output appears like this: ``` .ps1     "powershell.exe" .bat     "cmd.exe" .cmd     "cmd.exe" .pif     "ntvdm.exe" .sys     "ntvdm.exe" .vbe     "cscript.exe" "wscript.exe" 16Bit    "ntvdm.exe" "wowexec.exe" .vbs     "cscript.exe" "wscript.exe" .exe     "ntvdm.exe" ``` 3. Remove interpreter and file extension associations. - `sadmin scripts remove extension [interpreter1 [interpreter2]]...` — Removes the specified interpreter associations for the file or script type. - `sadmin scripts remove extension` — Removes all interpreter associations for the specified file or script type.