Removing that manifest file is the standard fix--but perhaps there's
something different going on. Have you tried a repair via control panel,
add or remove programs, windows Defender, change, update?
Can you tell from the error message what application it is that is calling
for the MSVCR80 file? I am recalling several threads here where specific
third-party applications raise this message after Windows Defender is
installed. The fix from the standpoint of those apps is to remove Windows
Defender. I don't believe that I have a resolution for this issue--which
appears to be an app compatibility or "dll hell" type issue--I believe one
responder stated that getting a copy of the named file in the install folder
for the third-party app fixed it for his particular case.
So--removing the .manifest file should fix this message if it is related to
execution of Windows Defender. However, if it's related to a third party
app, I'm not clear on how to resolve it, except perhaps removing Windows
Defender beta2.
--