aebrown wrote:In this case, I would install it, then within only a couple of minutes I would see a notification pop up that said it needed to be installed. I repeated that process 3 times, so it was very consistent. Then I ran through the procedure I described above, and it did not ever come back.
BTDT-GtTS. I have cleaned up the FHC, had everything working fine, and then a week later I'd have a few machines doing that again.
Yes, everything works fine - for now. But if for some reason
the prior security (Everyone: Deny) is reapplied to t2embed.dll, you'll see the same behavior. If the MS updater is denied permission to check the file version, it will re-offer the update. (And of course the update is completely ineffective with that permission.)
The unsolved question is how was the "deny" update getting applied to that file? That WAS a valid Microsoft work-around at one time before a updated file was offered. It seems to be something in the Church environment, because I've never seen it at work where I manage even more machines.
Again, you'll be perfectly fine, unless that security updates itself. That doesn't happen right away, but could happen over the next few days/weeks.