View Single Post
  #4 (permalink)  
Old 08-08-2007, 03:58 AM
b1caez01's Avatar
b1caez01 b1caez01 is offline
Senior Member
 
About:
Join Date: Dec 2006
Posts: 220
b1caez01 is an unknown quantity at this point

Default Solution! For me only, but worth a looksee... ;)


1. BACK UP YOUR REGISTRY

2. mscoree.dll APPEARS TO BE a part of the .net Framework only. It does not appear to be serving any other purpose...

3. If you do not specifically need to use the .net Framework, then get rid of any and all references to it, in the registry. I made the mistake of thinking I did.

4. before you hit the kill switch be sure to be sure to be sure that what you are killing, is not connected to something important!!!

5. the following seemed o.k., in my case...zappo! ...here are the keys to search for, and any other combos you can think of...just kill them...along with all versions of mscoree.dll that are lurking everywhere it seems. Leave a couple copies of mscoree.dll in a cache somewhere, just in case

.NET
.Net
.net
.NetFrameWork
.Net Framework
.netframework
framework
Frame Work
FrameWork
DotNet
DotNetInstaller
dotnet
dotnetinstaller



Reply With Quote