Haven't seen any other reports of this.
Key thing here to note is, this is a process crash event. Which means, you'll be able to get a process dump of the failure - so long as it can be reproduced.
Use ProcDump from SysInternals to capture a 2nd chance exception of Scan64.exe, and to monitor for the process to start.
i.e. procdump -e -ma -w scan64.exe
The dump it creates will be of interest to us/Support.
It could be indicative of a bug in our code, or in the DAT content, or the Engine, or Windows, or in a 3rd party that has hooked the process - so, too many possibilities to go speculating on... hence the need for data.
Have you tried to disable the prevent hooking AP rule and see if the scan finish? I have seen a similar crash when running ODS and it was this rule causing the issue.
The solution was trusting the dll injecting as per https://kc.mcafee.com/corporate/index?page=content&id=KB73521