Desperately needing help with windows explorer problem!

T

terry_bogard_007

New Member
I have no idea why the hell I am getting this error now because I have never had it before and I am just so annoyed about it and am hoping someone can help.

first started after I formatted my computer and reinstalled windows XP and updated everything via windows update.
I receive the error "Windows Explorer has encountered a problem and needs to close" everytime I try to do just about anything... from simply cutting and pasting something to trying to create a new folder.
the error report contains -
AppName : Explorer.exe
AppVer : 6.0.2900.3156
ModName : User32.dll
ModVer : 5.1.2600.3099
Offset : 00009de9

btw I have scanned my hard-drives and there doesn't seem to be any viruses etc. present so I really do not know what is causing this error to come up?
any help would be greatly appreciated thanks.
 
If it's a right click (which is what it sounds like), that's a bad shell extension. You need to find out which one it is and get rid of it. ShellExView allows you to edit them.
 
Creating a new folder isn't a right click item there. It sounds more like something didn't fully unpack to the drive when seeing Windows reinstalled. Besides the debugging tool the system file checker is another included in Windows since 98 for verifying and replacing the essential files found damaged or missing. With the XP disk in the drive simply type "sfc /scannow" at the Run prompt.

Editing shell extensions won't correct missing or corrupted system files. Hopefully you won't have to see Windows reinstalled or the repair install method used. http://www.michaelstevenstech.com/XPrepairinstall.htm
 
PC eye said:
Do you have the file/printer sharing feature enabled? With some printers and other addon devices that has been known to see this type of error. http://support.microsoft.com/kb/811266

Microsoft has a debugging tool for the 32bit versions of Windows available at the link here since this is being seen on a fresh copy of Windows. http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Click to expand...

Thanks a lot for your help and the links you have provided.
I don't share files or have a printer attached to my computer so I am guessing I don't have it enabled?
I have downloaded the debugging tool but at present, I still have no idea how i am supposed to use it to fix my problem?

SirKenin said:
If it's a right click (which is what it sounds like), that's a bad shell extension. You need to find out which one it is and get rid of it. ShellExView allows you to edit them.
Click to expand...

Thanks a lot for your suggestion but I had actually tried using that problem as it was suggested on a site I checked out earlier but I still kept getting the error.
 
terry_bogard_007 said:
Thanks a lot for your suggestion but I had actually tried using that problem as it was suggested on a site I checked out earlier but I still kept getting the error.
Click to expand...

You probably haven't found the right extension. As you'll notice with ShellExView there will be a ton of them and it could take quite a while, or plain luck, to find the right one.
 
SirKenin said:
You probably haven't found the right extension. As you'll notice with ShellExView there will be a ton of them and it could take quite a while, or plain luck, to find the right one.
Click to expand...

on the site I found previously, it told me to sort the list by type and then one by one disable any non-microsoft "context menu" until the problem was solved.
and after doing that I still have the problem... so am I supposed to try disabling a different type under that huge list too? and if so, what type?
 
Have you tried running the system file checker at all? Also look over the things installed so far to see if something saw a bad install there. It's usually only thing when found that will see this cleared up.
 
PC eye said:
Have you tried running the system file checker at all? Also look over the things installed so far to see if something saw a bad install there. It's usually only thing when found that will see this cleared up.
Click to expand...

I have tried the "sfc /scannow" thing but for some reason I keep being asked for my XP CD even though it already is in my dvd-drive.

concerning your second sentence, how do I look to find a bad install?
 
You may have to browse to the drive to get the sfc to finally see where it is. With two optical drives here I've run into that on a few occasions. You may even have to restart the system with the disk left in the drive so that Windows detects it when booting up. Then try running the tool again.

The method used often to see what besides Windows itself is causing problems is to go into the msconfig utility and disable some if not all items in the startup group there. That's a selective startup method not as restricted as safe mode to see Windows load without certain starting up at the same time.

One by one you then re-enable each item until the problem returns if it stops while everything is unchecked. If something was incomplete when installed or the wrong version like drivers often you can pin point just what it is from doing this.

The last thing to consider when all else fails would be a hardware fault being realized. If Windows and everything else went on good then you have to start looking at memory, cpu, weak battery on the board if no bios problems are being seen, and the heads on the hard drive showing their last days.

That was the case for two XP systems lately when both were seeing XP freeze up and even the repair install method couldn't complete itself. You could read anything from the drives but couldn't write anything to them. That included replacing the existing primaries to see clean full installs of XP on each. Toss a new drive in and whamoo.. XP was running.
 
You must log in or register to reply here.
Back
Top