Completed scan shows value "0" in all fields

Products

• Endpoint Security

Issue/Introduction

When running a scan on a machine after the time elapsed to have it performed (i.e. non-zero time), the local SEP client reports 0 files scanned, 0 risks found and 0 files skipped.
The same value is being reported in the SES Cloud console, like below:

Environment

SESC console; SEP Client

Cause

The issue is caused by improperly created scanning exceptions based on the files' extensions. The issue occurs whenever the extensions are specified as a wildcard for a file name with a given extension, rather than just the file extension itself, for exaplme: *.vbs instead of vbs.

Resolution

Make sure that when editing the Allow List Policy, only the extensions' names (usually 3-letter long) are being specified, without a preceeding asterisk and a dot (*.); for example: