Ant.
I CAN double-left-click on an item to 'Open' it... that will open the file
by the applictaion related to it by the filetype.
Double clicking in this case performs the Open command.
But using right-click on a non-folder object in Windows Explorer (file or
shortcut, in other words) or using File menu with a non-folder object
selected, results in Windows Explorer failing and desktop re-initializing.
Same on desktop, right-clicking on any object there (there can only be
shortcuts) causes desktop to re-initialize.
Is there a particular context handler I should be looking for in
ShellExView in these circumstances?
You have to use the process of elemination to find out what non-Microsoft
handler is causing the problem. Sort of a detective deal. ;-)
From Method 2 @
http://windowsxp.mvps.org/slowrightclick.htm
Run ShellExView...
It will scan the registry for all the shell extensions. Once the scan is
over and the list is displayed, you need to spot the context menu handlers.
Sort the results using "Type", so that the context menu handlers are
displayed together.
Click on the Type column header to sort by Type. You can also click the
Product Name header to sort by Product Name. I happen to have 12
non-Microsoft items. I have five Nvidia items and I have all of those
Disabled.
The rule is to disable non-Microsoft context menu handlers *one-by-one* and
verify if the problem is solved. If disabling one does not solve the
problem, undo the disabled item and disable the next non-Microsoft handler.
Do the same until the problem is solved and finally identify the culprit.
Scroll right to see the Company Name column in ShellExView.
The latest version of ShellExView marks all the non-Microsoft extensions in
Pink for easy identification. All other types of shell extensions that
ShellExView utility cannot recognize are categorized as "System" type.
The tip deal is quicker to try to eleminate half of the non-Microsoft items.
TIP
Even more quicker method is to bisect the list of context menu handlers into
two groups, disabling half of the entries at a stretch, rebooting and
testing the behavior again. JClarke commented on this article:
You can disable them ...they say "one at a time" and see what effect it has
on the problem. I did it a lot quicker by bisecting the list, disabling half
of the entries in one fell swoop, rebooting and trying the right click.
It worked, so I knew I just had to narrow it down, just as we used to do
with msconfig. Then I kept bisecting the list until it was just a few and
did those one at a time. The problem is that you have to reboot between
tries to get accurate testing of the results of your disabling. I didn't
find logging off to be consistent.
Also if you have any of these...
Intel®Graphics Controllers
Symptom(s):
Desktop right click menu is too slow for some customers.
Removing the custom desktop right click context menu
http://www.intel.com/support/graphics/sb/cs-003927.htm
This applies to:
Intel® 82810 Graphics Controller
Intel® 82815 Graphics Controller
Intel® 82830M Graphics Controller
Intel® 82845G Graphics Controller
Intel® 82852/82855 Graphics Controller Family
---
Intel® 82865G Graphics Controller
Intel® 82915G/82910GL Express Chipset Family
Intel® 82945G Express Chipset
Mobile Intel® 915GM/GMS, 910GML Express Chipset Family
Mobile Intel® 945GM Express Chipset Family
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
Can use ShellExView to