From what I see...
Csc.exe is a file component of each install of MS.NET Framework.
I don't see anything indicating a relationship between NET Framework and the command prompt...so I draw blank as to why that would be impacted by a possibly damaged NET file.
The other error involving STOP 142...occurs for any number of reasons...again, damaged files would be my best guess.
Contrary to what suggestions you might find suggesting the use of "registry cleaners"...I advise you not to use such.
Bleeping Computer DOES NOT
recommend the use of registry cleaners/optimizers for several reasons:
- Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable.
The Windows registry is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component because it is where Windows "remembers" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry.
- Not all registry cleaners are created equal. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work.
- Not all registry cleaners create a backup of the registry before making changes. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE making any changes to the registry.
- Improperly removing registry entries can hamper malware disinfection and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable to removal tools.
- The usefulness of cleaning the registry is highly overrated and can be dangerous. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results".
Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily
could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great
What I would do:
a. First, try to run the chkdsk /r command.
b. Upon completion of that...I would try running the sfc /scannow command, which will replace any missing/damaged system files.
c. If the issues with csc.exe continued...I would uninstall all versions of MS.NET Framework on the system...then reinstall any required version. Not all versions are required and many users need no version of MS.NET. If needed by an application/game, a message generally appears telling users such.
<<(sorry I abandoned the other post, but I'm very sure it's not a virus problem now and that rather it's just a simple registry issue I'm having with this error)>>
We don't/cannot compel members...to pursue topics which they have initiated:), unless they then proceed to make maultiple topics about the same issue. I will check your posts and take care of anything which needs to be done to close that topic.
Your Am I Infected topic is now closed.
Edited by hamluis, 03 July 2012 - 07:19 AM.