Alternate Data Stream ":$CmdTcID:$DATA"

[c627627]

I respectfully disagree that it's a good point since his question assumes you only have one or few files you need to clear from potential harm. After you reinstall version 8 or 10, Comodo continues to block all Alternate Data Stream removals.
That's the point, not removing one or two existing ADS you have. The fact that Comodo permanently blocks ADS removal is the topic. Uninstalling Comodo or jumping through hoops of rebooting into Safe Mode is not a solution.
I'll say it again, this is also about why...
Could there be a reason they don't want us removing Alternate Data Streams?

It's more than legitimate to ask if this is being done on purpose, given that entire version 8 history came and went with this security hole being left in there... making sure we don't remove alternate data streams when normally booted... as long as Comodo is still installed.

[qmarius]

A quick fix would be to change name of mentioned variable. Oh well.

[c627627]

A quick fix would be to change name of mentioned variable. Oh well.

If this is true, then it strengthens the question if Comodo is doing this on purpose?

[qmarius]

Probably. Maybe it's just legacy code (eg case when you upgrade from version 8 to version 10). Only a developer would know that.

[c627627]

We don't have to be developers to understand with certainty that the same reason applies to both versions 8 and 10, however if I may say, you misunderstood.

Parallel reasoning: Microsoft Windows 10 Telemetry collects personal data in a legal, but highly privacy-compromising way.
Likewise, does © Comodo Holdings BVI have an interest in preventing us from clearing Alternate Data Streams?

Theoretically ADS can be used as a form of telemetry. Theoretically, there are other reasons companies may have to make sure ADS stay attached. If you are correct that this is a simple fix, then what are we left with, other than to ask if Comodo Holdings BVI wants to do what it can to increase the number of Alternate Data Streams that stay attached?
Otherwise, why was there no fix throughout the entire course of version 8, and now into the next one?

This is not trivial. This is a security hole. They must know that. If they are leaving it unfixed because they "don't have time to fix it", then that's equally troubling.