mfcesd doesn't have any dependencies, at least on my system, so I don't know what Windows is talking about.
What has probably happened is that the TR/Crypt.XPACK.Gen detection by Avira was a false positive, and in "eliminating" the problem Avira has actually broken mfcesd. TR/Crypt.XPACK.Gen is not a virus - it's a generic routine used by various trojans - so it can't have "infected" mfcesd. (It's remotely possible that someone created a virus that includes TR/Crypt.XPACK.Gen, but in fact new software viruses are rare these days; they're no longer a preferred avenue of attack.)
Note that Avira is notorious in some circles for false positives with this particular signature. See for example this unsatisfying discussion between Avira and one developer:
Use Add/Remove Programs to repair your Enterprise Developer Personal Edition installation.