Error attempting to Shred a SINGLE file

[Peacekeeper]

So can you go through what you actually do when you choose to shred a file as I still cannot get the issue to happen. this in R6 and 5. I asked in our call and the tech will try to monitor it.  As you have 2.5 involved and he is 2.5 as well best they help though I am interested in your process.

[Former Member]

I have a folder - 'McAfee Test Shred Files' containing 3 different file types - see below

These files were used when I originally thought the issue was file-type dependent; however, as we now know, the issue occurs when a folder / file name contains a 'space' character,

I right-click any (or select all) of these files and choose  'Shred' from the drop-down menu.  This runs the 'shred' function of Total Protection and I get the error message similar to

The number of items varies depending on how many files I attempt to shred; in this example, I attempted to 'shred' all 3 files in the one operation.

A similar message occurs when I attempt to 'shred' the folder itself.

NB the McAfee ticket reference is #2269600696 .

I've just made a discovery that may shed some light as to where the issue occurs.

If I load Total Protection, select 'Shredder' from the Navigation Centre, use the 'Let Me Choose' option, click 'Shred' and select my test folder on drive M:, the folder is shredded OK!!

Weird eh?

[Peacekeeper]

Ok set it up your way

All files and folder shred by right clicking. This means Livesafe works. Sorry do not have TP any more worth telling Mcafee will pass this on.

  to note and pass on

[Former Member]

Just had a real 'live' telephone conversation with Siddhartha, the tier 2.5 tech who is overseeing this issue for me / us.

All he could offer in the way of a 'resolution' to this issue was that a further 'major' release of Total Protection is due to hit comsumers sometime next month, with the 'possibility' of a fix being enclosed in it.

I'm not holding my breath; however, watch this space for further developments.

[Peacekeeper]

Yes that was mentioned in our last call 16.0.R9 maybe but with the forum issues I got distracted and forgot to update you sorry. I gather as there is a workaround that it would not be a high priority.

[Former Member]

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!

[Peacekeeper]

LOL it is not near 1 year yet . Though 29 may is not that far away

[Former Member]

I’ve just been updated to Total Protection v16.0.R8; this issue still has not been resolved.

[Former Member]

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.

[Former Member · Accepted solution]

With the release of Total Protection v16.0.R9 this issue has finally been resolved!!