Rightclick problem after SP1

E

e

T7700, Business
This problem arose since SP1, and persists after
previous advice. It's the only issue amid several
benefits, so I would like to fix it rather than roll back.

When rightclicking a desktop icon, I'll sometimes get
nothing. Rightclicking again produces a NOT RESPONDING
and then a white Explorer reboot. Then all is well...
until next time. It's unpredictable -- I cannot define
the circumstances that will reliably cause the problem.

SFC /scannow in safe mode found zero faults.

Various malware checks found nothing.

There are no other problems (it runs great!).

I installed the ShellExView tool but learned little and
solved nothing.

Any ideas?

Ike


PS - please don't suggest changing my OS. Those whose
hobby is Linux probably don't use a computer in their
job, because most professions (including mine) require
apps that run on another OS.
 
C

Carey Frisch [MVP]

Right-click is slow or weird behavior caused by context menu handlers
http://windowsxp.mvps.org/slowrightclick.htm


--
Carey Frisch
Microsoft MVP
Windows Desktop Experience -
Windows System & Performance

---------------------------------------------------------------

T7700, Business
This problem arose since SP1, and persists after
previous advice. It's the only issue amid several
benefits, so I would like to fix it rather than roll back.

When rightclicking a desktop icon, I'll sometimes get
nothing. Rightclicking again produces a NOT RESPONDING
and then a white Explorer reboot. Then all is well...
until next time. It's unpredictable -- I cannot define
the circumstances that will reliably cause the problem.

SFC /scannow in safe mode found zero faults.

Various malware checks found nothing.

There are no other problems (it runs great!).

I installed the ShellExView tool but learned little and
solved nothing.

Any ideas?

Ike


PS - please don't suggest changing my OS. Those whose
hobby is Linux probably don't use a computer in their
job, because most professions (including mine) require
apps that run on another OS.
 
E

e

Carey said:
Right-click is slow or weird behavior caused by context menu handlers
http://windowsxp.mvps.org/slowrightclick.htm
Click to expand...


I'll give it another try, as I may well have missed
something last time.

There are some items listed in the Context Menu column
that really don't seem to belong there...

If it's not found I'll go to Microsoft with my hat in hand.

Thanks to both of you.

Ike
 
E

e

e said:
I'll give it another try, as I may well have missed something last time.

There are some items listed in the Context Menu column that really don't
seem to belong there...

If it's not found I'll go to Microsoft with my hat in hand.

Thanks to both of you.

Ike
Click to expand...

I used ShellExView and eventually disabled all of the
non-Microsoft Context Menu items.

The problem persists. Rightclick on a desktop icon, see
the spinning blue ring, click again and watch Explorer
die. It happens once or twice for each boot, and not at
any predictable time. At some point, the problem dies
and the unit functions properly.

If no one has other ideas, perhaps the next step is
Microsoft. This should be interesting...

Ike
 
R

Ramesh, MS-MVP

Checked the Event logs for any clue? It might reveal the module name that crashed explorer.exe.

--
Regards,

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


e said:
I'll give it another try, as I may well have missed something last time.

There are some items listed in the Context Menu column that really don't
seem to belong there...

If it's not found I'll go to Microsoft with my hat in hand.

Thanks to both of you.

Ike
Click to expand...

I used ShellExView and eventually disabled all of the
non-Microsoft Context Menu items.

The problem persists. Rightclick on a desktop icon, see
the spinning blue ring, click again and watch Explorer
die. It happens once or twice for each boot, and not at
any predictable time. At some point, the problem dies
and the unit functions properly.

If no one has other ideas, perhaps the next step is
Microsoft. This should be interesting...

Ike
 
R

Ramesh, MS-MVP

E

e

Thank you.
I examined the Event Viewer, but remain confused. There
is a river of information there, and I'm probably
looking for a single drop of dirty water.

Next step is to call Microsoft...

Ike
 
E

e

Thank you.
I examined the Event Viewer, but remain confused. There
is a river of information there, and I'm probably
looking for a single drop of dirty water.

Next step is to call Microsoft...

Ike
 
R

Ramesh, MS-MVP

All you need to check is the Application logs, which store information about Explorer.exe crashes. Simply match the date/time when the problem occurred and you'll be able to locate the entry.

--
Regards,

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


Thank you.
I examined the Event Viewer, but remain confused. There
is a river of information there, and I'm probably
looking for a single drop of dirty water.

Next step is to call Microsoft...

Ike
 
E

e

Ramesh said:
All you need to check is the Application logs, which store information about Explorer.exe crashes. Simply match the date/time when the problem occurred and you'll be able to locate the entry.
Click to expand...

Thank you.
Under "Application", I found nothing under "Explorer" or
"Explorer.exe". This despite an Explorer failure a few
minutes before.

Microsoft later today...
 
Top