Win7 HP, Various MMC Errors, Unable To Resolve, Please Help!

I went to get into Event Viewer yesterday and was greeted with the error below. I've done lots of research on how it might be resolved but have had no luck. I just checked every item in the Administrative Tools folder and three other components are giving me errors. Below is a list of information relating to the problem and what I've tried to resolve the Event Viewer issue thus far. Am I missing something obvious?

Error Message
"MMC could not create the snap-in. The snap-in might not have been installed correctly."

Administrator Tools That Are Not Functioning
CLSID: fx: {b05566ad-fe9c-4363-be05-7a4cbb7cb510} Event Viewer
CLSID: fx: {c7b8fb06-bfe1-4c2e-9217-7a69a95bbac4} Task Scheduler
CLSID: fx: {b05566ac-fe9c-4368-be02-7a4cbb7cbe11} Windows Firewall with Advanced Security
CLSID: {A22B5BA1-D8CF-4DB6-BC91-CFC1A04E2469} .NET Framework 2.0 Configuration

Steps Taken To Resolve Event Viewer Error

• Tried "sfc /scannow" with no problems/errors.
• Re-added the entire Event Viewer key to the Registry. Created a reg file from text in third to last response on that page (link).
• Tried replacing PATH variable (link).
• Tried deleting "machine.config" for .NET 2 and .NET 4 (link)
• Ran Microsoft .NET Framework Repair Tool. Only said .NET 4 might be an issue and took steps to resolve it. Since I am not installing a new .NET 4.0, this tool isn't particularly useful. (link)
• Tried launching "eventvwr.msc" from Run
• Restored Default System Fonts (link)
• Edited HKEY_LOCAL_MACHINESOFTWAREMicrosoftMMCSnapInsFX{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\RuntimeVersion, changing value from "v2.0.40607" to "v2.0.50727" which is my current version.
• Ridiculous level of Anti-Virus, Malware, and Rootkit scanning. My system is clean. Also worth noting I haven't ever tested positive for a virus on this Windows install (now five years old).

NOTE: I suspect this might all be related to a .NET 2.0 issue as some .NET programs have been crashing when I try to start them. However, I cannot confirm this is the cause. I found this article and plan to go through the steps tomorrow when I return.