1. "Faulting application helpctr.exe, version 5.1.2600.2180, faulting module mscoree.dll, version 2.0.50727.42, fault address 0x00004c44."

I go to Help and Support, enter the key word, it searches and provides "all the answers" but when I tap on one of the links, nothing appears in the field to the right where the reference is sopposed to be...

2. "Faulting application explorer.exe, version 6.0.2900.2180, faulting module mscoree.dll, version 2.0.50727.42, fault address 0x00004c44."

When I muss about a bit, error message #1 appears, sometimes, error #2 appears.

Accompanying the second error message is the opportunity to "debug" but upon debugging the entire task bar disappears and then reappears...

mmmmm...what's up with this...?

On first blush, it would be the corrupted mscoree.dll file, but I have six of them on board...so which one is the culprit? And if I use the one from the dll cache to overwrite the others, what then.

I downloaded a "new" copy of mscoree.dll from DLL-files.com - Download all your missing dll-files. and it sits in wait until I can copy it into the proper spot...but where is that?

I await further orders

P/S I have also had some .net installation problems...but no error messages related to mscoree.dll. I have just now found a site where the advice, in this regard, was to get the mscoree.dll file out of the system32 folder. I rechecked the file and find that it is directly related to the .net Framework program. Therefore, that may be the culprit. I'm going to give it a try, and move it out of the system32 folder, and see what happens.

This may be the location of the particular corrupted file.

DO WE NEED IT FOR ANY REASON...can I live without it.

IT WORKED...DELETED THE FILE FROM SYSTEM32 FOLDER...but should I delete all mscoree.dll files?

Now to "experiment" with other progs. I'll be back with a summary later.

Hello, just a quick one, your taskbar will disappear while debugging explorer, and won't come back until you stop.

Regards

Martin

Yes, I'm aware of that...but why? Obviously, the debugging missed something. What does the debugging entail?

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