Cached content deleted via this tool still shows as cached in a Task Sequence.

[icurnvs]

For example, in our Windows 10 feature update task sequence, I'm trying to get dynamic driver downloading going and I'm running into an issue with driver packages (task sequence downloads them, but when they move to sccm cache, they're 0 in size). So to redo the test, I'm deleting the driver package of 0 size via Client Center from cache and retrying the task sequence, the smsts.log still resolves the deleted package to its old (and now deleted) folder and continues on as if the content is already cached. It seems like there is some remnant of the old package somewhere in SCCM that the task sequence is referencing.

[SCCMAdmin]

I don't know what's going on, but a thought to try... So you have selected some items then removed them. OK cool. Now click on "Cleanup orphaned items" button to ensure anything lagging is cleared. Maybe something here may assist your scenario. :-)