Hi Jacob,
While a registry cleaner might find the discrepancies ,I'm not particularly fond of them,
because you can create more problems than you started with, unless you know what you're doing
and are prepared to scrutinize all "the faults" it finds.
In your case I would start by running SFC (System File Checker)
Use the System File Checker tool to repair missing or corrupted system files
https://support.microsoft.com/kb/929833
Next are the repair tools.
Microsoft .NET Framework Repair Tool
http://www.microsoft.com/en-us/download/details.aspx?id=30135
Aaron Stebner's WebLog
http://blogs.msdn.com/b/astebner/
In the left side menu bar is a link to this tool:
.NET Framework Cleanup Tool
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
You may have to reinstall some versions of .NET afterwards
Is all this on your primary system? if so, I would strongly advise you to conduct your experiments
on a test system or at least in a virtual environment.
I wil post an entry in a followup submission labeled Virtual Systems
Peter E.
--------------------------------------------------
From: "Jacob Smith"
Sent: Wednesday, February 05, 2014 5:35 PM
To: <[log in to unmask]>
Subject: [PCSOFT] .net error still there
This is the same issue I sent a while back, but I know a little more about
it, and I figured I'd try you guys again. A long while ago, I had a stroke
of brilliance: run a .reg file containing an entire registry backup, un the
computer with Windows running. Evidently, Windows lets you try to do that.
It failed, and ever since, I've had this error when I run a lot of
software: "C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll could
not be loaded". I renamed the file to
"C:\Windows\Microsoft.NET\Framework\was v4.0.30319", for diagnostic
purposes. I am now getting
"C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll could not be
loaded" I tried renaming this folder as well, but it was in use, so
something in that folder is working. I could rename the dll, but I don't
know if I'd learn anything useful. Anyone know what my issue might be? I've
tried .net fix tools, repairs, reinstalls, and a few other things. Logic
says that it has to be a registry issue that reinstalling won't fix.
--
Blessings,
Jacob Smith
The NOSPIN Group is now offering Free PC Tech
support at our website:
http://freepctech.com
|
