I cannot figure out what is going on here.
An application is deployed as part of a Task Sequence (without a targeted deployment). When that application is subsequently changed, it seems that Appdiscovery decides it needs to change that app on previously imaged machines even though there is still no deployment that targets the old machines.
Is SCCM remembering these installations and keeping track of changes? The documentation suggests that this should not happen (at least as far as supersedense is concerned).
How can I stop this unintentional application update happening?