Lost file - can you help me find it ?

[Guest]

I have been using NORTON systemworks for some years now with very little
trouble but, since I obtained ntl broadband and installed the appropriate
software i keep getting an error repeated 10 to 20 times every time I run
'one button checkup' .. Basically several applications are trying to find a
file "msver80.dll" .. I have searched my XP installation disk and all the
other software I can think of to no avail. Can you tell me where I can find a
copy of this file and where should I copy (or install) it to ??

 

[Wesley Vogel]

A Google search brings up nothing for msver80.dll. This is a good
indication that msver80.dll is some kind of malware. Update yor antivirus
software and run a full system scan. Do the same for what ever anti-spyware
applications that you have.

If you meant msver70.dll, that may have something to do with Norton.

There are no Microsoft .dll files that start with msver that I can find.

*Never* install any ISP's software.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[JP]

Might be that the file is actually msvcr80.dll (not msver80.dll).

AFAIK:

This error usually is "caught" by NSW after a PC is updated with MS DotNET
Version 2.0.

The file is installed correctly in the appropriate directory:
Windows\WinSxS\x86_policy.5.2.Microsoft.Windows.Networking.Rtcdll_6595b64144ccf1df_x-ww_c7b7206f

NSW gives the error because it thinks the file should actually be located in
the Windows\System32 directory.

You can either select "Ignore the problem" within NSW or simply copy (NOT
move!) msvcr80.dll to Windows\System32 directory. That will keep NSW
*happy*.

Or one can always *Ignore NSW* - a course of action deemed wise by many,
including yours truly.

Double check the file name on your NSW error list before doing anything. The
above suggestion is worthless if the file name is not msvcr80.dll.

Anything you do, you do at your own risk.

JP

 

[JP]

Sorry, the location directory for msvcr.dll should read this way:

C:\Windows\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

Maybe I do need glasses after all as my better half always gently suggests
from time to time.



JP
---

Might be that the file is actually msvcr80.dll (not msver80.dll).

AFAIK:

This error usually is "caught" by NSW after a PC is updated with MS DotNET
Version 2.0.

The file is installed correctly in the appropriate directory:
Windows\WinSxS\x86_policy.5.2.Microsoft.Windows.Networking.Rtcdll_6595b64144ccf1df_x-ww_c7b7206f

NSW gives the error because it thinks the file should actually be located
in
the Windows\System32 directory.

You can either select "Ignore the problem" within NSW or simply copy (NOT
move!) msvcr80.dll to Windows\System32 directory. That will keep NSW
*happy*.

Or one can always *Ignore NSW* - a course of action deemed wise by many,
including yours truly.

Double check the file name on your NSW error list before doing anything.
The
above suggestion is worthless if the file name is not msvcr80.dll.

Anything you do, you do at your own risk.

JP
---

 

[Avatar]

Sorry, the location directory for msvcr.dll should read this way:

C:\Windows\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

Maybe I do need glasses after all as my better half always gently suggests
from time to time.



JP

You should listen to your "better half". You do need glasses!

Your correction itself apparently needs a correction: The first line should
read
".....msvcr80.dll....." and not as posted!

;-)

Avatar

 

[Guest]

JP
Many thanks, I think it must be me who needs 'new' glasses, you are quite
right about the file name, and I have completed the actions you suggested,
with favourable results - so far...
--
EREITIZ
But I am not quite sure what IT is ???

Sorry, the location directory for msvcr.dll should read this way:

C:\Windows\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

Maybe I do need glasses after all as my better half always gently suggests
from time to time.



JP

 

[Guest]

My anit-virus and spyware is current but it appears that I cant read the file
name - or I cant type !! the file name should have been mavcr.dll, and JP has
offered me some useful advice. thanks for your help...
--
EREITIZ
But I am not quite sure what IT is ???

A Google search brings up nothing for msver80.dll. This is a good
indication that msver80.dll is some kind of malware. Update yor antivirus
software and run a full system scan. Do the same for what ever anti-spyware
applications that you have.

If you meant msver70.dll, that may have something to do with Norton.

There are no Microsoft .dll files that start with msver that I can find.

*Never* install any ISP's software.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[JP]

JP
Many thanks, I think it must be me who needs 'new' glasses, you are quite
right about the file name, and I have completed the actions you suggested,
with favourable results - so far...

I appreciate your follow-up. I am glad my input (from my own experience,
actually) was of some help.

AFAIK: the msvcr80.dll is one of the Dynamic Link Library files that is a
component of MS Dot.NET v2.00, and thereby, presumably, of Windows itself. I
do not know the exact function, but Dot.NET uses it from the directory I had
pointed out earlier.

NSW however, expects all system files (or most of them at least) - including
such dlls - to be located within the default Windows\System32 directory
which is the *normal* location for most essential system files. Which is why
it comes up with the 20 or so instances where it tries to find "links" or
such to this file from MS Dot.NET pointing to the System32 directory. Which,
naturally, it does not. Hence those "errors" that it finds on a scan!

I am not dissing NSW but WinDoctor has a habit of labelling as an error
whenever it encounters such situations and apparently cannot (or will not)
recognize that such "missing" files do exist elsewhere!

Cheerio.

JP
---

 

[JP]

You should listen to your "better half". You do need glasses!

Your correction itself apparently needs a correction: The first line
should read
".....msvcr80.dll....." and not as posted!

;-)

Avatar

Thanks O'Great Avatar! I do appreciate, and somewhat enviously admire,
*your* eagle-eyed ocular capabilities!

Let's not discuss my potential future visit to an optometrist when we meet
over coffee tomorrow morning, OK?

|;-)

JP

 

[Wesley Vogel]

Did you locate msvcr80.dll?

Copy it and paste a copy into the Windows\System32 folder to shut NSW up.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Wesley Vogel]

I wouldn't go as far as saying that msvcr80.dll is part of Windows. I have
Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have dot NET
either.

MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with Microsoft
SQL 2005 Server Enterprise and Microsoft Visual Studio 2005 Professional.
http://support.microsoft.com/dllhelp/?dlltype=file&l=55&alpha=msvcr80.dll&S=1&x=9&y=11

I do not doubt that msvcr80.dll is also included with dotNET.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Thanks for that, it could explain a few things, I belive the DOT Net was part
of XP SP2, but I am not completely sure. It did appear just after I updated
to SP2.. So did a few glitches ????

Thanks again

 

[Wesley Vogel]

Now that I think about it, .NET Framework may have come with SP1 or as an
update, I can't remember. I got rid of it though. The only thing that I
have is a .NET passport and I wouldn't have that if I didn't need it for
some MVP stuff. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Thanks Wesley
I wish I knew how much of the junk on my C: drive I could get rid of without
causing problems with any programmes, I suspect about 50% of windows & office
would be about right, freeing up loads of space and possibly stopping some of
the conflicts and slow-downs..

Thanks again

Byeeeeeeee

 

[Wesley Vogel]

If you want to be an expert, just start deleting stuff. Stop one step ahead
of rendering your machine in-operable. Just kidding.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

JP, Wes, Pete:

I received similar information after running Symantec Win Doctor on a
freshly installed XP SP2. Message is:

"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe" cannot access
a necessary file, "msvcr80.dll"

Yes, I took my glasses off and got real close to see it real good.

Just a guess, but this just might be related to Microsoft.NET. This was
installed during one of the many Windows Update passes. I try to take all
new or rebuilt computers through Windows Update to make sure all is
up-to-date. What's interesting is that I did a search for the "missing" dll
and found it in another directory under C:\WINDOWS. Now, why is it that this
WINDOWS.NET can't find it's own dll (with both hands) and all I had to do was
a simple Microsoft Search?

Is the answer to go out and direct all our users to uninstall Windows.NET?

 

[Wesley Vogel]

Lucky,

It's a Symantec error, not a Microsoft error.

Error: " . . . Cannot access necessary file, msvcr80.dll..." when running
One Button Checkup or WinDoctor
http://service1.symantec.com/SUPPORT/nsw.nsf/0/74fe2fa1b068a2438825711500100c4f?OpenDocument

I have uninstalled .NET Framework, whatever version came with XP, and I do
not get any of the .NET Framework updates. And I do not even have any
Symantec crap installed either. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Heh, heh ... guess that takes care of both sides of it.

Thank you.

 

[Wesley Vogel]

Keep having fun. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In