Not always, but when I try to shred a single file I get the following error message -
I've been in touch with Microsoft, and this is what they think -
Does anyone have any ideas as to what is going on?
Solved! Go to Solution.
With the release of Total Protection v16.0.R9 this issue has finally been resolved!!
Are you trying to shred a McAfee file? What is the name of this file?
I just shredded a temp file successfully.
Some files are "in use by another process" so can't be deleted under normal conditions.
Discussion successfully moved from Other McAfee Consumer Products to QuickClean and Shredder
The file I'm trying to shred is not a McAfee file; it is -
'Diary Report I F Mosley 09-04-1949.pdf'
It contains personal medical information, hence this is why I want to shred it. This file can be successfully opened by Adobe Reader and I delete it by Right Click => Delete.
Another file giving a similar issue is
which is an empty text file.
In fact, any number of files with different extensions can sometimes produce similar errors. The issue is not limited the Window Temporary files location.
This would have to ,be monitored by a support person lionked to your computer, and of course you may not like to do that.
Have you tried doing it in Safe Mode? Most software induced locks on files are inactive in that mode.
Yes I have loaded in 'Safe Mode'; however, the issue still persists.
I've had a couple of remote access sessions with McAfee support, the last being carried by a 2nd line tech; they are of the opinion that it is a permissions issue with the file / folder.
I feel like as if I'm between a rock and a hard face - MS & McAfee tech support each 'blaming' each other of being responsible for causing the issue.
However, this does help not resolve the issue for ME.
I will bring this up as a Topic of discussion on today's Conference Call.
By way of further information . . .
The issue was not present while running the Anniversary (1607) release of Windows 10; it was still OK after I'd updated - 'in-situ' - to the Creators (1703) release by downloading the update via Windows Update and installing it over my 1607 system. The issue has only arisen since doing a clean install of 1703.
This is why I believe the issue should be owned by Microsoft; this is what they initially said -
McAfee tech support say they do not rely on registry entries other than those specifically installed and used by them, which has a ring of logic and truth about it
The only one I can find is 22366782076 (484570 ?).
When I contact McAfee Support they usually find me on the systems by using my email address, which I can provide if necessary, which usually connects to my tickets; the sessions were on 14th & 21st May.
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: