I have Windows XP Home and I'm having problems opening folders that contain
pictures (jpegs, etc.). It takes a long time to "seach" when I click on a
folder and once it does open the picture file icons slowly refresh to the
Photoshop icon and then I get the "Windows has encountered an error and needs
to close" message.
The details from the Error Report are:
AppName: explorer.exe
AppVer: 6.0.2900.5512
ModName: ntdll.dll
ModVer: 5.1.2600.5755Offset: 00037453
I tried defragging, disbling third part browser extensions, etc. and nothing
seems to help.
Any help is appreciated.
You see this when you are in Windows Explorer navigating in a folder?
Why/how did you disable third part browser extensions?
If you see it while browsing folders it sounds like a Windows Explorer
Shell Extension, probably a non Microsoft Windows Explorer Shell
Extension.
You can download ShellExView from here to see which ones you have
loaded:
http://www.nirsoft.net/utils/shexview.html
ShellExView doesn't install anything on your computer, it just runs
and displays.
When you launch it, the non MS extensions will be in light pink, but
on some systems that is a hard color to see, so click View, Choose
Columns and move the Microsoft column closer to the top so you can see
it on your screen without having to scroll left and right.
Sort the display by clicking the Microsoft column so all the "No"s are
at the top and easy to see.
I am not a trial and error advocate, but I can't think of another way
to do this...
Right click and disable the non Microsoft extensions one at a time
keeping a list so you can enable
them again later if desired. The result of the change is immediate and
no reboot is required. Test your
failure condition.
If you recognize any extensions that may have been added or downloaded
recently, start with those. The
Extensions are not uninstalled, just disabled and you can enable them
later after fixing the afflicted one(s).
The hope is that you will find the one Extension that causes the error
and then you can figure out what to do about it.
I don't have your issue but I can see that the Extension is
immediately disabled, so disabling one does not require a reboot but
if you find the culprit, I would reboot anyway to really be sure.