I have had this behavior happen to me multiple times, on multiple computers. I have quite a few computers in my home, some laptop and some desktop. I don't turn some of them off, so my problem of having McAfee start a scan after being powered on does not apply routinely to most of my computers.
As a programmer myself, I understand the concept of an interrupt and how it can be used to stop a process and either terminate it or allow the CPU to work on another task. I also know that it is possible for one to program a process such that it does not respond to interrupts, or does not respond very often, as a strategy to allow the process to advance with as little interruption as possible.
However, it seems to me that when you program a "cancel" button into your application, and a cancellation does not materially affect the operation of your application (eg. you have a process to count from 1 to 1000...who cares if you stop it in mid-process?), I expect a cancel button to respond immediately.
Good feedback, Dr Tech -
I'll raise this with the Development team. 1) Cancel should be responsive. 2) Catch-up scans after a period of being turned off. This last one is a bit more sensitive...and need to think about what the appropriate behavior should be. Thanks!
As it also does on my wife PC.
If this cancel issue is only on 1 PC maybe a uninstall reinstall is needed. I notice R19 just got installed so maybe see if that fixed anything.