The internal scan procedure trigger using cronjob mechanism provided by WordPress.
When you start a scan, the plugin creates cronjob entry with appropriate callback function and timeout.
When timeout fired, wordpress calls provided scanner function and perform the scan.
Please verify that cronjob mechanism is enabled in your WordPress and registered cronjobs executed properly.
If cronjob mechanism works properly and scan still didn’t start, please post here last 10 lines of plugin log file, you can find log file into plugins directory.
Please let us know whether it worked for you.
Some additional information from plugins FAQ section
Why when I run an internal scan, the scanned files count shows 0 (zero)?
The plugin scheduler invocation is based on WordPress Cron mechanism.
Some web hostings and servers do not enable the functionality required for WordPress Cron mechanism to work correctly.
There is a way to overcome this limitation by using alternative WordPress Cron. To enable alternative Cron, please add the following line to wp-config.php
define(‘ALTERNATE_WP_CRON’, true);
