We have just got this problem with a VB6/Access system that has been as solid as a rock for years. I noticed above the part
Well, they ran some remote tests on my machine, got me to reproduce the error, uploaded some logs, and it seems they have acknowledged the problem and have told me they will fix it in the next release (12.9), which they said will be out in a month or two.
Has anything been done in this regard. Can we expect a fix from McAfee? If we can that would be really good.
We tried to restrict total protection to programs and documents - but we're not covinced this solves the problem and it leaves a possible gap in protection.