New in 2019.10: Updated Command Line Scanner

Improved automation features

Part of all our Windows protection products is Emsisoft Commandline Scanner, a tool that allows admins and professional users to automate common malware scanning tasks. It’s also available as a standalone download package without any visual UI components.

We have slightly changed the behavior of the standalone package of Emsisoft Commandline Scanner in the most recent update:

• In the past, the /s (/service) parameter had to be used for all scans that were to be performed by the integrated Windows service. In the new version, the /s parameter is only used once to install the service, but then no longer needed to run scans. That helps to simplify the scanning process.
• A new parameter /uninstallservice was introduced that allows you to remove the service component if it’s no longer needed.

Note that these changes only apply to the standalone package of Emsisoft Commandline Scanner. When using the scanner as part of the endpoint protection products, it will always use the built-in service component.

The Windows service helps to save resources and time, as the entire signature database is kept in memory and doesn’t have to be loaded for each scan. That way you can perform frequent scans with very low system impact.

All 2019.10 improvements in a nutshell

Emsisoft Anti-Malware

• Changed service behavior in command line scanner.
• Several minor tweaks and fixes.

MyEmsisoft/Management Console

• New ability to move multiple devices at once to other policy groups, via drag&drop.
• Improved user interface in many sections.
• Several minor tweaks and fixes.

How to obtain the new version

As always, so long as you have auto-updates enabled in the software, you will receive the latest version automatically during your regularly scheduled updates, which are hourly by default.

Note to Enterprise users: If you have chosen to receive “Delayed” updates in the Update settings for your clients, they will receive the new software version no earlier than 30 days after the regular “Stable” availability. This gives you time to perform internal compatibility tests before a new version gets rolled out to your clients automatically.

Have a great and well-protected day!