Windows 2000 Server: Explorer.exe problem

[Winchester]

Since it is Windows, it uses Explorer.exe for all its crap. On our server, when I try to open anything that possibly uses it, (recycle bin, search, several administrative tools, network neighborhood, internet explorer, etc) it takes about 20-30 minutes for it to open. The window opens, but the contents are not there. It is like it freezes, but if I just let it sit, it eventually begins to work.

On IE, I can click on the icon, it opens up, finds the website, but then takes 20-30 minutes for it to load EVERY page.

Why would it be doing this and how can I fix it?

 

[LiLithTecH]

Does it happen if you login to another account with admin rights?

If it doesn't, login to the other account and rename the account folder
under Document and Settings.

 

[Smilin]

have an sp4 cd and a 2000 cd handy and run sfc /scannow.

Should clear it up.

 

[Winchester]

LilithTech: No one else other than the Administrator account can login to that computer
Smilin: I will try that.

 

[Winchester]

It wont let me run SP4 installation. It stops at the "Checking local configuration" and sits there for hours.
I have tried both express and network installations.

Can I do a network installation (from CD) within safe mode?

BTW: I downloaded Firefox to use as a web browser, and it works fine. So it probably just has to do with explorer.exe.

 

[Smilin]

I didn't actually mean do an sp4 installation.

when you run sfc /scannow it will search for altered system files. If found it will replace them with the right versions. It may prompt for either your 2000 CD or an sp4 CD as required (assuming you have sp4 installed that is)

"BTW: I downloaded Firefox to use as a web browser, and it works fine. So it probably just has to do with explorer.exe. "
I would say probably the opposite. You swapped out your web browser and now you're having all sorts of UI problems. You likely have goofed up some sort of dependency. userinit, msgina or some crap might have been altered.

You should explore lithtech's suggestion a bit further too. Create another user and login with it. Use "net user" from the command line if things are horrible sluggish.

Also, see if you get the same behavior in safe mode. If not, look into killing some services or startup items that might be misbehaving.

 

[Winchester]

I tried to login as another user, Administrator is the only one that can. But that is with network logins, I will try one on the actual computer.

I downloaded firefox today, just to test it. These problems have been going on for months.

 

[RollWave]

I have 2000 pro on my dads comp, and one day it just started flipping out like that and would freeze or stick at windows forever...I couldnt figure it out so I just backed up all the info, and did a system restore. All is well and it hasnt reverted

 

[Winchester]

Smilin,

Your suggestion of the sfc /scannow, did not work. It asked for the Server 2000 CD, took a while then closed. Is it supposed to ask for confirmation or tell me to restart?

rnp614 re-installing windows is not an option in this case.

 

[LiLithTecH]

If the System File Checker does not encounter any changes you will not
get the reboot prompt.

Keep in mind that any HotFixes that you may have applied would be
overwritten had SFC done its job.

You can always login in DOS mode to add another account with admin rights.

 

[mikecel79]

Something that Explorer and IE depend on is corrupt. Do you have a backup of this server before this all started? What applications are installed on it? Does it have anti-virus? What about Terminal Services?