Well rebooting into another OS is quicker than rebooting into Safe Mode (if you do a stop watch test) but both accomplish the same thing, a workaround.
There are many (many) workarounds to this problem, some more cumbersome than others.
I now have a feeling that the developers have been aware of this issue for some time.
If we can move to accepting that this is a side-effect of having Comodo software installed, that it is the price we pay for having Comodo installed, it would then be nice if someone posted something about the background of this problem.
Why it is happening and why it cannot be fixed.
At first there was a concern that all these workarounds served to prevent this issue from being taking seriously and finally resolved, but I am leaning towards this being a long-term problem and that it has been for a while.
Have you seen anyone post on the forums what the background story is, why does Comodo prevent ADS removal? What is it that makes this not an option you can tick?
Because labeling files is a way to track things, track people, by definition.
Explaining why Comodo blocks removal of ADS would prevent people from incorrectly assuming there are other reasons for keeping those Alternate Data Streams attached to people’s personal files.
Because of Microsoft’s new business model, evident in Windows 10, I incorrectly thought that it was Microsoft and not Comodo who was responsible.
Telemetry is front and center business model for Microsoft now. Data Mining. Microsoft is now doing what Google was doing all these years. Targeted advertising is big business.
Tracking people’s habits is central in that business model and that it why it wasn’t out of place to think it was Microsoft.
But it wasn’t Microsoft. It is Comodo.
So in conclusion, an explanation of why this is happening would go a long way in countering any discussion that Comodo has a hand in the telemetry-related world we live in today.
In other words, is blocking ADS removal a bug or is this by design?