Thanks for the reply.
I know there is a work around; however, this issue has been lurching towards a resolution by McAfee since July last year. If you include the time I spent with MS 3rd line tech support in 'proving that it was a Total Protection issue', it originated on 14 May 2017.
As I said to Siddhartha, I'll soon be posting a message here celebrating it's first birthday, including an emoji of a 'birthday cake with a single candle' on it!
LOL it is not near 1 year yet . Though 29 may is not that far away
I’ve just been updated to Total Protection v16.0.R8; this issue still has not been resolved.
My contact at McAfee believes the fix for this issue will be released in the next update of Total Protection, due in early March 2018.
With the release of Total Protection v16.0.R9 this issue has finally been resolved!!
We are glad to know with latest McAfee release v16.0.R9 the issue got resolved. We will mark this discussion as resolved such that other peers might get benefitted from the solution.
McAfee Tier 2.5 Technician
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: