To-day, I've had a 4 hour 'Chat' session with Microsoft Tech Support.
After much frustration, I managed to get them to, more or less, agree that this issue lies firmly in Microsoft's court. Furthermore, I'm having a remote access session with a MS 2nd line support tech on Wednesday afternoon.
Watch this space for a further update.
I was having my remote access session with a, supposedly, MS 2nd Line support when out of the blue the session was ended by him, no phone call in explanation, no email either. It turns out he dismissed the issue as a McAfee issue. Words do not fail me; however, I don't want to be sanctioned for verbal abuse!!
Had another 4 hour 'Chat' with another Answer Desk support tech; this lady / gent was as different again the 2nd line support tech earlier - like the difference between chalk and cheese.
I won't bore you with all the details; however, this issue has been referred to MS's Professional Support team. They will be contacting me on Saturday, 17th June hopefully to take this further.
After a spluttering and stuttering start, I did have my remote access session with MS's Professional Support.
After confirming what had transpired before, he has initially been concentrating on the permissions aspect of the file(s) & folder(s). However, little progress has been made other than they seem fairly sure it is a permissions related issue.
Ultimately we aim to have a couple of remote sessions per week or more frequently as necessary; however, due to our other commitments, we agreed to have our next remote session next Friday, 30th June.
I guess this could be unmarked as a question (for McAfee) at least? In my experience deleting PDF's has often been problematic unless all hooks from your PDF viewer programme, Adobe or whatever, are closed using the Task Manager "Show processes from all users" option. Safe Mode usually works however. It's interesting that Microsoft have taken ownership of this.
It's not just .pdf files that cause this issue; for sure .txt & .png files also exhibit the symptoms, and possibly others which I have not found.
I (eventually) had my remote session with a Microsoft 2nd-level support tech. Although they explored various possibilities as to the cause of this issue, they were not successful in diagnosing the problem.
The issue has now been referred to Microsoft's 3rd-level support for further investigation.
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: