MSVCR80.DLL Error Messages

Sponsored Links

I am running Windows 2000 SP4.
I've just installed the latest critical updates from Windows Update, ten in
total including three for Office XP.
As soon as I did this, I started to get error messages popping up, when I
boot up and when I run some program functions.

The messages are all basically the same -
"Entry Point Not Found : The procedure entry point __security_error_handler
could not be located in the dynamic link library MSVCR80.dll."
I have checked, and the MSVCR80.dll file was NOT changed by any of the
updates.

I have uninstalled the updates one by one to try and identify which update
has caused this problem. Unfortunately, I have now uninstalled six of the
ten, and the error messages are still there!

Of the remaining four, three are for Office XP, and I can't seem to find any
way to uninstall them. (The fourth is the Malicious Software Removal Tool,
which I'm assuming isn't under suspicion!)
The three Office XP updates are KB920816, KB929063, KB929061.
Does anyone know how to remove them?

I need to do this to eliminate them as the cause of the error messages.
Thanks.

Oops! Sorry for the double post!
I don't quite know what happened there.........

"Dave Hawley" wrote:

> I am running Windows 2000 SP4.
> I've just installed the latest critical updates from Windows Update, ten in
> total including three for Office XP.
> As soon as I did this, I started to get error messages popping up, when I
> boot up and when I run some program functions.
>
> The messages are all basically the same -
> "Entry Point Not Found : The procedure entry point __security_error_handler
> could not be located in the dynamic link library MSVCR80.dll."
> I have checked, and the MSVCR80.dll file was NOT changed by any of the
> updates.
>
> I have uninstalled the updates one by one to try and identify which update
> has caused this problem. Unfortunately, I have now uninstalled six of the
> ten, and the error messages are still there!
>
> Of the remaining four, three are for Office XP, and I can't seem to find any
> way to uninstall them. (The fourth is the Malicious Software Removal Tool,
> which I'm assuming isn't under suspicion!)
> The three Office XP updates are KB920816, KB929063, KB929061.
> Does anyone know how to remove them?
>
> I need to do this to eliminate them as the cause of the error messages.
> Thanks.

"Dave Hawley" <DaveHawley@discussions.microsoft.com> wrote in message
news:C8F67568-F230-4F34-AE29-40E9DCE5F080@microsoft.com...
>I am running Windows 2000 SP4.
> I've just installed the latest critical updates from Windows Update, ten in
> total including three for Office XP.
> As soon as I did this, I started to get error messages popping up, when I
> boot up and when I run some program functions.
>
> The messages are all basically the same -

> "Entry Point Not Found : The procedure entry point __security_error_handler
> could not be located in the dynamic link library MSVCR80.dll."

> I have checked, and the MSVCR80.dll file was NOT changed by any of the
> updates.


If you interpret the symptom from the point of view of the
entry point name: __security_error_handler, perhaps
an effective solution would be avoiding whatever it is
that requires the error handler? ; )

OTOH where did you get msvcr80.dll and why is it being used?
FWIW I have msvcr71.dll and it does have that entry point.
Perhaps whatever it is that is doing the call would really like to use
that one instead?

I'd try running ProcMon to see what the caller is--
ProcMon instead of just FileMon because apparently
in ProcMon you can capture the call stack for task events.
If necessary you could even configure symbols to get the
most insight from that diagnostic.


>
> I have uninstalled the updates one by one to try and identify which update
> has caused this problem. Unfortunately, I have now uninstalled six of the
> ten, and the error messages are still there!


That would suggest that the either the cause of the error was
a coincidence or accidental, hence whatever it changed
would not be backed up for the uninstall procedures.
Perhaps you should do a Restore instead?


>
> Of the remaining four, three are for Office XP, and I can't seem to find any
> way to uninstall them. (The fourth is the Malicious Software Removal Tool,
> which I'm assuming isn't under suspicion!)


Why not? Was anything removed by it? E.g. check the mrt.log
If something was removed and it was something which had its hooks
set in ways which were not completely understood by the procedure
removing it, it could be a perfectly credible cause of an error.


> The three Office XP updates are KB920816, KB929063, KB929061.
> Does anyone know how to remove them?
>
> I need to do this to eliminate them as the cause of the error messages.
> Thanks.


BTW How come you're the lucky one who keeps getting these weird ones? <eg>


Good luck

Robert Aldwinckle
---

"Robert Aldwinckle" wrote:

> "Dave Hawley" <DaveHawley@discussions.microsoft.com> wrote in message
> news:C8F67568-F230-4F34-AE29-40E9DCE5F080@microsoft.com...
> >I am running Windows 2000 SP4.
> > I've just installed the latest critical updates from Windows Update, ten in
> > total including three for Office XP.
> > As soon as I did this, I started to get error messages popping up, when I
> > boot up and when I run some program functions.
> >
> > The messages are all basically the same -
>
> > "Entry Point Not Found : The procedure entry point __security_error_handler
> > could not be located in the dynamic link library MSVCR80.dll."
>
> > I have checked, and the MSVCR80.dll file was NOT changed by any of the
> > updates.
>
>
> If you interpret the symptom from the point of view of the
> entry point name: __security_error_handler, perhaps
> an effective solution would be avoiding whatever it is
> that requires the error handler? ; )
>
> OTOH where did you get msvcr80.dll and why is it being used?
> FWIW I have msvcr71.dll and it does have that entry point.
> Perhaps whatever it is that is doing the call would really like to use
> that one instead?
>
> I'd try running ProcMon to see what the caller is--
> ProcMon instead of just FileMon because apparently
> in ProcMon you can capture the call stack for task events.
> If necessary you could even configure symbols to get the
> most insight from that diagnostic.
>
>
Hi Robert,
Thanks for the response!
I've no idea where the msvcr80.dll file originally came from.
It's version 8.0.50727.163 from June 2006, so it can't be a file which
shipped with the OS. If it was originally part of Windows 2000, it's
certainly been updated by something.
I tried disabling it, and got a big complaint on boot that it couldn't be
found.

Anyway, I have moved on a bit in my researches, and found that the cause of
the error is actually Windows Defender. If I uninstall it, the messages go
away.
If I reinstall it, they come back!

Now before you tell me that I can't use WD under Windows 2000 (support was
withdrawn from W2K as soon as the release version was issued, despite the
fact that the betas HAD supported W2K!) I HAVE been using the release
version, installed from a hacked MSI file, for quite a few months without any
problems, and I believe quite a few others have been too.
This error message has only come up since the latest set of updates.
In fact if you ignore them, WD still seems to actually be working perfectly!

I am going to annoy the Windows Defender newsgroup now, to see if anyone
else has had the same problem.............

> >
> > I have uninstalled the updates one by one to try and identify which update
> > has caused this problem. Unfortunately, I have now uninstalled six of the
> > ten, and the error messages are still there!
>
>
> That would suggest that the either the cause of the error was
> a coincidence or accidental, hence whatever it changed
> would not be backed up for the uninstall procedures.
> Perhaps you should do a Restore instead?
>
I wish I could, it would have been the first thing I would have done, except
that Windows 2000 does not of course have System Restore!
>
> >
> > Of the remaining four, three are for Office XP, and I can't seem to find any
> > way to uninstall them. (The fourth is the Malicious Software Removal Tool,
> > which I'm assuming isn't under suspicion!)
>
>
> Why not? Was anything removed by it? E.g. check the mrt.log
> If something was removed and it was something which had its hooks
> set in ways which were not completely understood by the procedure
> removing it, it could be a perfectly credible cause of an error.
>
The mrt.log shows nothing untoward.
Scan done, nothing found..........
>
> > The three Office XP updates are KB920816, KB929063, KB929061.
> > Does anyone know how to remove them?
> >
> > I need to do this to eliminate them as the cause of the error messages.
> > Thanks.
>
>
> BTW How come you're the lucky one who keeps getting these weird ones? <eg>
>
I must just be lucky..... ;-)
Off topic, I still have an issue with KB923191, which goes back ages.
The new version of comctl32.dll issued with that update causes my system to
hang on shutdown (the ever popular "cannot unload your registry, access
denied.")
I'm not the only one suffering that one, and yet nothing has been done about
it.....

Thanks again, I'll let you know if I manage to reinstall Windows Defender
without the error messages coming back! Let me know if you have any other
thoughts.
Cheers,
Dave.
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>

To fix this error message, you need to replace the corrupted or missing msvcr80.dll file with new file that you can download from the following link.

After downloaded the file, restore this file in System32 folder.

This is the best source on the net I have ever found to fix almost all DLL error messages, which is caused because of corrupted or missing .dll files. Once you are on the site, click on the Run a DLL Scan link and you will see all other issues you might have on your pc has been resolved. Good Luck