All Collections
Manuals, Tutorials, How to... FAQ's
Controlling Safety Options Against Malicious Files
Controlling Safety Options Against Malicious Files


Christian Kramer avatar
Written by Christian Kramer
Updated over a week ago

Note: You need admin rights to run the command and do changes!

Use the SafetyOptions command to prevent executable files with potential safety risk from running.

Safety settings protect the software and the computer against viruses and malware.

The SafetyOptions dialog box lets you control the restrictions for specific types of executable files.

The specification of trusted locations overrides the prevention of the execution of these files.

Executable files with potential safety risk

Executable file types that may contain malicious code and are affected by the safety options include the following:

  • .tx, .frx (C++ plugin files)

  • .lsp, .mnl (Lisp files, Menu Lisp files)

  • .scr files (script files)

  • .net assemblies

  • .dll files (dynamic link libraries)

  • startup.rx file

Trusted locations for executable files

The following folders and their subfolders are always trusted:

  • C:\Program Files

  • C:\Program Files (x86)

  • The folder which contains the binary files of the application

  • The application data roaming folder for the software and version you use (%AppData%\software_name>)

In addition to the above implicitly trusted folders, you can specify individual trusted locations in the SafetyOptions dialog box.

If a folder specification ends with a backslash and three dots (\...), all of its subfolders are also trusted.

You can specify whether The Start In folder is determined either by the Start In attribute stored in the properties of the desktop shortcut icon, or by the folder in which you double-click a file to start the executable of the software.

Safety Options Dialog Box

To control Safety Options against malicious files:

  1. Type SafetyOptions at the command prompt.

  2. In the dialog box, specify the Safety level:

    • High. Executable files from trusted locations are loaded. Executable files in other locations are ignored.

    • Medium. Executable files from trusted locations are loaded. For executable files in other locations a warning displays and you are prompted whether to load them.

    • Off. Executable files are loaded without warning. This option is not recommended.

  3. In Trusted locations, specify the trusted folders from which executable files can be loaded.

    • Click Add to add a folder to the list of trusted locations.

      Type a folder path or click Browse to navigate to a folder.

      Note: Add a backslash and three dots (\...) to the folder name to make all subfolders also trusted.

    • Click Remove to remove a trusted folder from the list.

      You cannot remove implicitly trusted folders.

    • Click Browse to specify a new location for the folder selected in the list.

      You cannot browse for implicitly trusted folders.

  4. Specify whether to exclude or include the Start In folder and the drawing folders to the trusted locations.

    It is recommended to exclude these folders.

    Note: The default starting path for the software is specified in the Start In text box of the dialog box that opens when you right-click a shortcut icon for the software and select the Properties option in the context menu. If you leave this box blank, the default folder is set to the folder where the executable file of the software resides.

  5. In Automatic Loading specify whether to load the start.lsp Lisp file once at the start of a session with the software or each time when opening a drawing.

    Note: The start.lsp file loads startup.lsp which is often used to load add-ons with executable files.

  6. Click OK.

The SAFETYOPTIONS command was introduced with ARES Commander 2020 SP0.

Right-clicking on the ARES Commander application icon takes you to the Run as Administrator menu to change safety options.

The trusted path settings are saved in the registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\Graebert GmbH\[ARES Commander XXXX]\security

Did this answer your question?