Missing Files in Microsoft.NET\Framework\v2.0.50727

Norton System Works' WinDoctor has found the error of C:\Windows\Microsoft.NET\Framework\v2.0.50727\ missing files and I believe Windows should address the issue.

When I run Norton WinDoctor on my home PC, the following problems appear, with no repair capabilities:

Missing program files (10 Problems):

C:\Windows\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.reiis.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_state.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_wp.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\cvtres.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\ilasm.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe

C:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exe

As you can see, all of these "missing" program files are located in C:\Windows\Microsoft.NET\Framework\v2.0.50727\

I've seen a few recent postings about this "missing file" regarding certain gamers who use ActiveX 9.0 and have errors when attempting to load some games.  However, I am not a huge gamer, my WinDoctor found this problem.  Some postings say that they found Microsoft.NET 2.0 to conflict with ActiveX 9.0.  Many other PC savvy folks are posting that .Net 2.0 should be uninstalled and should keep .Net 1.0 until Microsoft addresses the issue.

I do run Registry Mechanic 4.0 every two weeks.  However, I also run Windows Updates every two weeks.  In addition, I run WinDoctor (also checks for and repairs registry errors).  I have a feeling that perhaps Windows provided an update that had created this error   My husband says that his WinDoctor is also receiving the same error reporting the missing files from C:\Windows\Microsoft.NET\Framework\v2.0.50727\ on his computer.  We both run on Windows XP and frequently run Windows Updates.  I remember just recently installing the Windows Update called "Windows Media Connect" before receiving this error.  Perhaps this error came from Windows Updates of Microsoft .NET Framework 2.0   I cannot say how the problem started.

Does anyone else have this problem or wish to address this problem

 




Answer this question

Missing Files in Microsoft.NET\Framework\v2.0.50727

  • Thomas Schulze

    I was having the same problem..thx so much for the solution!
  • Jan Buskens

    I too have this trouble.  I am experiencing the very same error messages in WinDoctor.  What do you do to take care of this problem
  • Stacy Bennett

    I have the exact same issues with exact same files when I run Norton.

    Anyone know how to fix it

    Denise


  • Sudhansu Tiwari

    yes I have the same problem, how it arose is a a mistery but instead of 10 missing i,ve gone 1 better 11, I did reinstall framework programme files from instalation disk but it did'nt work, would like to sort out these missing files without a total reinstalation, any suggestions


  • URLmon

    First of all I think you mean DirectX 9 rather than ActiveX 9. I've never heard of or encounted any problems with DirectX and .NET Framework.

    Second of all, are you actually having issues with running .NET Framework 2.0 applications These so called 'missing files' issue being picked up by Norton WinDoctor has come up a lot on this forum, and I suspect that this is a false positive.

    Can you physically check (using Windows Explorer) when those missing files are present

     



  • John Reilly

    I concur with windows fixing this ......................I have norton system works and it cinsistently gives me the same errors of all those files missing 10 in all at first I thought it was something that I removed or disabled but now I'm realizing it was when I updated to 2.0 on microsoft.

    God bless microsoft

    I've made my system check ignore for now until they or I come up with a fix...........possibly even removal as i saw in someone elses posting.


  • Dudley McFadden

     MarnieV wrote:

    Norton System Works' WinDoctor has found the error of C:\Windows\Microsoft.NET\Framework\v2.0.50727\ missing files and I believe Windows should address the issue.

    When I run Norton WinDoctor on my home PC, the following problems appear, with no repair capabilities:

    Missing program files (10 Problems):

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.reiis.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_state.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_wp.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\cvtres.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\ilasm.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exe

    As you can see, all of these "missing" program files are located in C:\Windows\Microsoft.NET\Framework\v2.0.50727\

    I've seen a few recent postings about this "missing file" regarding certain gamers who use ActiveX 9.0 and have errors when attempting to load some games.  However, I am not a huge gamer, my WinDoctor found this problem.  Some postings say that they found Microsoft.NET 2.0 to conflict with ActiveX 9.0.  Many other PC savvy folks are posting that .Net 2.0 should be uninstalled and should keep .Net 1.0 until Microsoft addresses the issue.

    I do run Registry Mechanic 4.0 every two weeks.  However, I also run Windows Updates every two weeks.  In addition, I run WinDoctor (also checks for and repairs registry errors).  I have a feeling that perhaps Windows provided an update that had created this error   My husband says that his WinDoctor is also receiving the same error reporting the missing files from C:\Windows\Microsoft.NET\Framework\v2.0.50727\ on his computer.  We both run on Windows XP and frequently run Windows Updates.  I remember just recently installing the Windows Update called "Windows Media Connect" before receiving this error.  Perhaps this error came from Windows Updates of Microsoft .NET Framework 2.0   I cannot say how the problem started.

    Does anyone else have this problem or wish to address this problem

     


  • Witold Jaworski

    The following works to fix this problem.

     

    Norton WinDoctor feels that msvcr80.dll is missing in the new NET 2.0...

    Hello all and thanks for trying to solve this problem.

    Hello Mr Martyn Lovell and special thanks to you for giving us all this valuable input on how to solve this problem.

    Now, let's try to focus on how to solve the problem.

    What worked for me was to:

    Do a search for msvcr80.dll on the disk that you have windows.
    In my case, C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd\msvcr80.dll

    Copy the file and paste it in the System32 directory
    In my case, C:\WINDOWS\system32

    Now Norton is pleased and I am pleased.


  • metasquier

    I also receive this message (Systemworks 2006). Is this a Microsoft problem or is it a Symantec problem. Between them, surely they can resolve this.
  • MTBG

    If you actually follow the link I give above, you will see that Martyn Lovell actually states that this is a Norton Systemworks problem.

    You should contact Symantec regarding this and not attempt to try and fix this by copying files to specific locations.



  • Saurav Kr. Basu

    As I suspected, it is probably a problem with WinDoctor, see the following thread (and scroll down to Martyn Lovell's post:

    http://forums.wugnet.com/msvcr80-dll-missing-NET-ftopict445120.html



  • GREESH KUMAR MAHESHWARI

    I replied by posting a quote Please click on thesolution I gave.
  • SMSMonster

    '

       I had the exact same issue with my Norton WinDoctor. The suggested solution worked perfect in my case. Thank you very much for you posts!!



  • JBlog0000

    I thought Mr Martyn Lovell was telling us NOT to copy the file to "system32" folder as that may introduce problem. His recommanded solution is to tell Norton to ignore it, as this is not a problem at all!
  • Missing Files in Microsoft.NET\Framework\v2.0.50727