Windows Explorer problems

[Seeker]

I am running WinXP home, SP2 installed, all updates installed.

Having problems with Windows Explorer/My Computer.

Often, just clicking on a file will cause a Runtime Error, and close
Explorer. Or double clicking to open a file will cause it.

I am able to continue working, and re-open Explorer. But everything
seems to run much slower after this happens, so I usually re-boot. But
this keeps happening and has me worried. (I do not have these problems
when opening a file within an application, only when using Explorer.)

( I am not sure I can describe this next thing well, so I beg your
patience)

Another problem is that, within Explorer, when I move a group of files
to a new location, using the Menu "move to folder" command, and want
to create a new destination folder, it hangs up, and takes a very long
time to eventually create a "new folder", which I then have to rename.
This is not the normal behavior. I've done this particular thing
thousands of times without any problem. I hope this makes sense.

Bottom line, I am hoping to find a fix, or a diagnostic, something
that is short of a re-install, to figure out what is wrong and make it
right..

Is there a way to figure out what is causing this? Or some miraculous
instant fix?

Thanks

Seeker

 

[Ramesh, MS-MVP]

Hi Seeker,

Sounds like a shell extensions problem to me. Have you check the Event logs when the time the error occurred?

How do I view the error messages registered in Event Log?:
http://www.winxptutor.com/eventlog.htm

How to view and manage event logs in Event Viewer in Windows XP:
http://support.microsoft.com/kb/308427

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


I am running WinXP home, SP2 installed, all updates installed.

Having problems with Windows Explorer/My Computer.

Often, just clicking on a file will cause a Runtime Error, and close
Explorer. Or double clicking to open a file will cause it.

I am able to continue working, and re-open Explorer. But everything
seems to run much slower after this happens, so I usually re-boot. But
this keeps happening and has me worried. (I do not have these problems
when opening a file within an application, only when using Explorer.)

( I am not sure I can describe this next thing well, so I beg your
patience)

Another problem is that, within Explorer, when I move a group of files
to a new location, using the Menu "move to folder" command, and want
to create a new destination folder, it hangs up, and takes a very long
time to eventually create a "new folder", which I then have to rename.
This is not the normal behavior. I've done this particular thing
thousands of times without any problem. I hope this makes sense.

Bottom line, I am hoping to find a fix, or a diagnostic, something
that is short of a re-install, to figure out what is wrong and make it
right..

Is there a way to figure out what is causing this? Or some miraculous
instant fix?

Thanks

Seeker

 

[Seeker]

Hi Ramesh.

Thanks for the quick response.

(Can you define "shell extensions" for me?)

I have looked at the event log many times. Needless to say it is not
understandable to me. I assume you are not suggesting that I post the
data from one of those events here. (Although I would happily do so if
you are willing to look at it!)

But here are the description lines from two of these events:

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module ntdll.dll, version 5.1.2600.2180, fault address 0x000106c3."

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module unknown, version 0.0.0.0, fault address 0x02ed7e30."

When these Runtime Errors occur there is a link which I follow.It
provides only very vague information. At least to me it is. And it
goes on to describe at least 2 dozen possible causes. Extremely
confusing, and unhelpful.

Hi Seeker,

Sounds like a shell extensions problem to me. Have you check the Event logs when the time the error occurred?

How do I view the error messages registered in Event Log?:
http://www.winxptutor.com/eventlog.htm

How to view and manage event logs in Event Viewer in Windows XP:
http://support.microsoft.com/kb/308427

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


I am running WinXP home, SP2 installed, all updates installed.

Having problems with Windows Explorer/My Computer.

Often, just clicking on a file will cause a Runtime Error, and close
Explorer. Or double clicking to open a file will cause it.

I am able to continue working, and re-open Explorer. But everything
seems to run much slower after this happens, so I usually re-boot. But
this keeps happening and has me worried. (I do not have these problems
when opening a file within an application, only when using Explorer.)

( I am not sure I can describe this next thing well, so I beg your
patience)

Another problem is that, within Explorer, when I move a group of files
to a new location, using the Menu "move to folder" command, and want
to create a new destination folder, it hangs up, and takes a very long
time to eventually create a "new folder", which I then have to rename.
This is not the normal behavior. I've done this particular thing
thousands of times without any problem. I hope this makes sense.

Bottom line, I am hoping to find a fix, or a diagnostic, something
that is short of a re-install, to figure out what is wrong and make it
right..

Is there a way to figure out what is causing this? Or some miraculous
instant fix?

Thanks

Seeker

 

[Seeker]

Hi Ramesh.

Thanks for the quick response.

(Can you define "shell extensions" for me?)

I have looked at the event log many times. Needless to say it is not
understandable to me. I assume you are not suggesting that I post the
data from one of those events here. (Although I would happily do so if
you are willing to look at it!)

But here are the description lines from two of these events:

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module ntdll.dll, version 5.1.2600.2180, fault address 0x000106c3."

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module unknown, version 0.0.0.0, fault address 0x02ed7e30."

When these Runtime Errors occur there is a link which I follow.It
provides only very vague information. At least to me it is. And it
goes on to describe at least 2 dozen possible causes. Extremely
confusing, and unhelpful.

Whoops. Forgot to say THANK YOU

Seeker

Hi Seeker,

Sounds like a shell extensions problem to me. Have you check the Event logs when the time the error occurred?

How do I view the error messages registered in Event Log?:
http://www.winxptutor.com/eventlog.htm

How to view and manage event logs in Event Viewer in Windows XP:
http://support.microsoft.com/kb/308427

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


I am running WinXP home, SP2 installed, all updates installed.

Having problems with Windows Explorer/My Computer.

Often, just clicking on a file will cause a Runtime Error, and close
Explorer. Or double clicking to open a file will cause it.

I am able to continue working, and re-open Explorer. But everything
seems to run much slower after this happens, so I usually re-boot. But
this keeps happening and has me worried. (I do not have these problems
when opening a file within an application, only when using Explorer.)

( I am not sure I can describe this next thing well, so I beg your
patience)

Another problem is that, within Explorer, when I move a group of files
to a new location, using the Menu "move to folder" command, and want
to create a new destination folder, it hangs up, and takes a very long
time to eventually create a "new folder", which I then have to rename.
This is not the normal behavior. I've done this particular thing
thousands of times without any problem. I hope this makes sense.

Bottom line, I am hoping to find a fix, or a diagnostic, something
that is short of a re-install, to figure out what is wrong and make it
right..

Is there a way to figure out what is causing this? Or some miraculous
instant fix?

Thanks

Seeker

 

[Ramesh, MS-MVP]

Seeker,

Shell extensions:
http://msdn.microsoft.com/library/d...int_extending/extensionhandlers/shell_ext.asp

See if "Method 2" in this article helps:
http://windowsxp.mvps.org/slowrightclick.htm
(Ignore the article title)

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Hi Ramesh.

Thanks for the quick response.

(Can you define "shell extensions" for me?)

I have looked at the event log many times. Needless to say it is not
understandable to me. I assume you are not suggesting that I post the
data from one of those events here. (Although I would happily do so if
you are willing to look at it!)

But here are the description lines from two of these events:

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module ntdll.dll, version 5.1.2600.2180, fault address 0x000106c3."

"Faulting application explorer.exe, version 6.0.2900.2180, faulting
module unknown, version 0.0.0.0, fault address 0x02ed7e30."

When these Runtime Errors occur there is a link which I follow.It
provides only very vague information. At least to me it is. And it
goes on to describe at least 2 dozen possible causes. Extremely
confusing, and unhelpful.

Whoops. Forgot to say THANK YOU

Seeker

 

[Seeker]

Ramesh,

Once again, thank you for your response.

The article on Shell Extensions reminded me that I am technically
challenged, and I need to leave such things to the experts!

I did follow the second method, and downloaded and ran ShellExView.

All but one of the non-Microsoft handlers belong to programs that have
been on my system for years, such as my Anti-Virus, WinZip, WinRar,
and others. I did disable the one I do not recognize.

There is no immediate way for me to know if it helps or not, since my
problems arise so randomly and unpredictably.

If it does provide a fix I will let you know (and if it doesn't I will
also let you know!)

( I somehow doubt that this item is the cause of the problems. It is
dated May 2006. Since it has been on my system for so long, I cannot
see why it would suddenly cause problems.)

I appreciate your efforts, and will let you know one way or the other.

Thank You

Seeker

 

[Seeker]

Ramesh,

Disabling the unknown handler via ShellExView did not fix the problem.
I just had another Runtime Error when clicking a file.

Any other suggestions would be gratefully recieved.

Thank You

Seeker

 

[Ramesh, MS-MVP]

been on my system for years, such as my Anti-Virus, WinZip, WinRar

Disabling them does not cause any harm. There is no guarantee that the software that's been on your system for years do not get corrupt. (Example: http://windowsxp.mvps.org/playall.htm)

Going another step ahead, I'd try disabling all the third-party shell extensions (not only context menu handlers) to determine if the run-time / crashes are caused by those modules. You can re-enable the extensions anytime using ShellExView.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Ramesh,

Disabling the unknown handler via ShellExView did not fix the problem.
I just had another Runtime Error when clicking a file.

Any other suggestions would be gratefully recieved.

Thank You

Seeker

 

[Seeker]

Ramesh,

I shall do so.

But there is a small problem with 2 of these handlers. The only way to
access these programs is through the context menus. They have no
independent interface, except for choosing options. They are media
conversion programs, one for audio file (Wav to MP3) the other a video
converter. They are from 2 different companies, btw, and I have been
using them for years. So I see a potential problem, if one of these
turns out to be the culprit I willl lose the ability to use them.

But I had already started by disabling the next one in the list of
context handlers. With my luck, problably the very last one I try will
be the one. There are 18 context handlers, and about 35 other non MS
handlers of other types.

Wish me luck.

Seeker.