Sometimes, it comes down to 'live with it' or spend hours to hopefully 'fix it'.  
Without any personal experience with this particular issue, maybe setting a restore point, doing a registry backup (also copy to an external drive), then run a registry cleaner.  I think Glary Utilities is one that may be available as a free download or a 30 day trial.  Run the reg cleaner and see if it resolves the problem.  
Some of the other utilities included may help if the reg cleaner doesn't resolve it.  
Net framework can be deleted and reinstalled as well.
Of course, everything has a risk to it, no matter how good the products are.
If you have a spare HD, you could ghost the existing drive before you start anything, just in case...  You can pick up 1 TB sata drives now for under  $70.
Paul Hachmeyer
.
-----Original Message-----
From: PCSOFT - Personal Computer software discussion list [mailto:[log in to unmask]] On Behalf Of 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

                  Visit our website regularly for FAQs,
               articles, how-to's, tech tips and much more
                          http://freepctech.com