(I have just verified that this is in fact the case on my own system shortly after applying the update, before nuking the unauthorised scheduled task from orbit just to be sure.)
The reason being that a missing/non-existent task may be re-created on update/upgrade, but a disabled one should not (hopefully!) be re-enabled.
> We’ll respect user configured telemetry opt-out settings by looking at the most recently used Firefox profile.
Sleazy, this is disappointing.
> We’ll respect user configured telemetry opt-out settings by looking at the most recently used Firefox profile.
What am I missing?
> telemetry opt-out
to be sleazy.
Also this is way beyond the usual ‘we need it for debugging’ excuse. It’s just collecting data that is worth money.
And of course, the first time you launch Firefox on a new install they aren’t going to wait and see if you perhaps opt out. They’re going to get what they can before you opt out.