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.
William W. Warren | S.I.R.R. | Customer Success Group | McAfee
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.