explorer.exe errors

I have a customer(side job), whose w2kpro machine is constantly giving explorer.exe errors. It generates an error log and restarts explorer. This starts as soon as you log onto the machine and just keeps going like this in a loop. I was able to start in safe mode, it gave the same errors but after doing it 3-4 times it was done. I will not be able to look at the machine again until after work today, but was hoping that someone would have a few suggestions on what I should look for. The customer swears that he hasnt changed or added any new software to the machine.

One of the things to look for is possibly a virus. I suggest this due to the last 5 days I have had (17) machines get the KLEZ or ELKERN virus. These virus' attack the .exe files on all programs.

In most cases when the machine has reached the stage you are talking about, a clean install is required. The data will not be lost but all programs will have to be reinstalled.

I will check for virus, but I dont think that is what it is. I installed Norton corporate on all machines at that location and the virus definitions have been kept up to date. I looked at the norton control console on the server and it didnt show any virus for that machine.

<a href="http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q255758&LN=EN-US&rnk=4&SD=tech&FR=0&qry=explorer.exe%20error&src =DHCS_MSPSS_tech_SRCH&SPR=WIN2000&" target="_blank">This</a> or <a href="http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q319124&LN=EN-US&rnk=15&SD=tech&FR=0&qry=explorer.exe%20error&sr c=DHCS_MSPSS_tech_SRCH&SPR=WIN2000&" target="_blank">this</a> may help.
Good luck.

I had the exact problem on my XP Pro box. Worked fine in safe mode, though. I finally just had to go buy a 6-pack of Heineken and reformat it.

I've also heard that replacing the explorer.exe file from a good machine can help fix it. You'll have to do it from the recovery console, though, I believe.

I ran into this setting up a new PC with Win 2000 Pro also. After surfing the net I found this solution which worked for me.

If you get the following message when logging into Windows 2000.

"explorer.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created"

Then open Windows Explorer and navigate to find the shortcut for Windows Explorer under Start Menu -> Programs -> Accessories, select it's properties, shortcut tab and change the target to c:\%SystemRoot\explorer.exe /e,/n.

Strange, but it seems to solve the problem.

I only did this on my profile since it was the only one that had a problem. I have yet to see the error pop back up for anyone else. If it does I will change the setting on the default user as well as the user that experiences the problem.

Let us know if you get it fixed!

Thanks for everyones suggestions, but none of it has worked. If anyone has any other suggestions please let em fly. I am willing to try anything. There is way too much valuable information on this machine, and I really dont feel like backing it all up formating.

Everything seems to be fine when I log in under a different profile. I think I will just have them use the other profile for a couple days. That should give me some time to try a few other things. Thanks for everyones suggestions so far, and keep them coming. I really do appreciate everyones help!!!

this can happen if you have a prog loaded that needs to interact with the desktop. the one that caused it for me was a version of ws_ftp. there are a few others out there and there is a KB article listing some of the others this is know to happen with.

i suggest you start in safe mode then take a look at the programs that require a shortcut on the desktop and/or are loaded in the systray. you can use msconfig for w2k to disable or remove one at a time till you find which one is causing the problem.

good luck

Thanks for the suggestion storm, I will give it a try next time I make it over there.

Is the user an administrator?

Coincidentally I ran into this problem today. Here's what the deal was:

1. I logged on to a workstation on our domain as domain administrator.

2. I changed the local rights of the primary user's domain account on this particular machine to "User" from "Administrator".

3. Logged-on as that user, got the explorer.exe error.

4. Same thing happens with power-user rights. Changed that person's account back to Administrator and no error.

Hope it helps.

This might not be the same thing because of the explorer errors but does this person have Adaptec installed? If so, make sure Direct CD isn't installed as it messes with the AV software. I've seen it before with McAfee and Direct CD on a Win2K box so who knows.

</font><blockquote><font size="1" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif">Originally posted by gpint:
<strong>Everything seems to be fine when I log in under a different profile. I think I will just have them use the other profile for a couple days. That should give me some time to try a few other things. Thanks for everyones suggestions so far, and keep them coming. I really do appreciate everyones help!!!</strong></font><hr /></blockquote><font size="2" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif">If this is the case, then just recreate the profile and call it a day. No need wasting time, unless you have a reason to figure out what happened. Typically a profile should only take about 10 minutes to configure all of the settings. Of course that may vary either way, but from my position it seems as if it is the best thing to do.

It is just better to eliminate the problem with the first solution that presents itself, even if it is not the exact fix. If the problems surfaces again, then spend more time figuring out why it is there…

I would check for any VB5 or VB6 apps that may have overwritten any IE scripting components or activex files with older versions. IE6 seems to be particularly sensative to this. Many VB developers often forget that IE and most of Office is written in VB also and that have to be careful when implementing customized or older versions of shared files.