Slow pictures context menu

On 1/06/2014, Ken Blake, MVP posted:
On Mon, 06 Jan 2014 14:39:13 -0800, Gene E. Bloch
wrote:

On 1/05/2014, Ken Blake, MVP posted:

I guess so. And I *love* your use of the word "peccadillos," a
word I
very seldom see (even though some think the correct plural is
"peccadilloes." g)

As I was writing it, I found dictionaries on both sides of that
issue.


Yep! As I said "*some* think."

Yes, I was aware of that, but I didn't want anyone to think *I* hadn't
thought about it :-)

Call it vanity ;-)

Although if I were completely vain, I wouldn't have admitted that I
*did* check...

--
Gene E. Bloch (Stumbling Bloch)

VanguardLH wrote, On 1/6/2014 4:53 PM:


Note 1: The "Rotate" entries in the context menu shown in the online pic
hint that right-clicking was not on a desktop object but on an object
(image) within a viewer program.


+1

Also, on the English versions of Windows 7 or 8 for Photo Viewer or
Photo Gallery the the rotate options state - right or left, but not
clockwise or counterclockwise...thus my earlier statement that those
spefici items could be language specific (Windows or the software).

But it appears moot at this stage...the delay is now 1 sec surprisingly
from removal of a Bluetooth suite.


--
...winston
msft mvp consumer apps

Migrante on 06/01/2014 wrote:

You're a little bit late because the question was already solved without
your help.

You were creating a jumbled mess of mixing top- and bottom-posting in
many of your replies which makes following the conversation difficult.

You stated:

I've a 5 second delay when I do first right click on picture file. It
seems menu has to load in first click. After menu load, second click
is normal.

In my very first reply, I noted how the context menu is built by
scanning the registry looking for object handlers and shell extensions
and this is why it takes longer for the context menu to show the first
time within a Windows session but the cached version is quicker to
appear on subsequent access. So you now knew why the first appearance
was slow.

Whether 5 seconds was a long time on your computer wasn't really known
because your hardware was unknown, how many and what type of background
processes were running was unknown, and what else you might've been
running for apps was unknown. A very busy computer can be very slow to
respond.

Assuming 5 seconds was way too long under whatever scenario your
computer was setup and currently running, I suggested using Nirsoft's
ShellExView or even using a registry cleaner to find unresolved
references to shell extensions in the registry. Resolving them takes
time and can delay the appearance of the context menu. Slow responding
handlers can also slow the appearance of the context menu. If it takes
them a long time to populate their [sub]menu entry then it delays when
the context menu will appear. By disabling the shell extensions, you
could have found which one caused the slowdown rather than the shotgun
approach of uninstalling a bunch of stuff.

Note: After uninstalling program named Bluetooth Suite that was already on
system, delay takes about 1 second.

Which comes back to Paul's mention of another thread that mentioned
mapped drives caused delays in displaying the context menu. With
slow-to-respond-over-the-network other-host drives (mapped drives), they
slowed building the context menu (and its submenus). Apparently your
Bluetooth software was slow to respond probably while it went scanning
for existing Bluetooth devices or networks.

btmshell.dll (Bluetooth handler), if that's what you had (or still
have), is a shell extension. By using Nirsoft's ShellExView to disable
extensions and then reenabling them one at time would have shown the
disruptive shell extension causing the delay. This is the same
troubleshooting scheme used with startup program in msconfig.exe (or
other such tools, like SysInternals AutoRuns) or for add-ons in a web
browser. Disable all, test if problem went away, enable one at a time,
and when problem reappears then last one reenabled is the culprit.
Instead it appears you went the shotgun approach.

btmshell.dll is registered with a runtime identifier of "BTMTrayAgent"
and is loaded by running:

rundll32.exe "C:\Program Files\Intel\Bluetooth\btmshell.dll",TrayApp

It is a startup item defined in the registry at:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

It loads in all Windows accounts and presumably (by its name) shows an
icon in the system tray. Disabling startup items might've eliminated
the delay by not having this program load on startup. That is,
disabling startup items might've shown the context menu delay was caused
by startup item; however, this utility is also defined as a shell
extension in the registry:

CLSID = {9D843851-50AA-46EE-829A-784DEBA4716C}
Identifier = Bluetooth Property Page Extension

You said that you did not see any non-standard tab panels in the
Property dialog (when you showed the context menu and clicked on
Properties). That's because the object on which you right-clicked was
not a Bluetooth object. Tab panels for special-use properties don't
show up because they aren't germane to the object selected but they do
load into the cache. For example, some backup programs add a property
page so you can select to backup or restore just the selected object
(file or folder). Acronis True Image is like that. I won't show its
tab panel under Properties if, say, you right-click on the Recycle Bin.
However, if there is a problem in loading that property page then the
context menu is affected (slow or crashes). Again, using ShellExView to
disable property page extension would find the culprit. ShellExView
will show the type of shell extension, like property sheet, icon
[overlay] handler, context menu, and so on, so you can focus on
different type of extensions. I'm sure it would've showed you the
Bluetooth Shell Extension as a property sheet (tab panel in Properties).

You could leave the Bluetooth software installed but if you currently
have no Bluetooth devices then just disable the monitor or scanner
function. If you never plan to have any Bluetooth devices (e.g., cell
phones) then leave it uninstalled.

"VanguardLH" escreveu na mensagem ...

In my very first reply, I noted how the context menu is built by
scanning the registry looking for object handlers and shell extensions
and this is why it takes longer for the context menu to show the first
time within a Windows session but the cached version is quicker to
appear on subsequent access. So you now knew why the first appearance
was slow.

- I didn't know why context menu appearance was slow but after reading your
replies and other answers about same problem I did uninstall of Photo Viewer
program but it didn't work, then I tried to find bluetooth driver which was
mentioned on other replies but only thing I had related with bluetooth was
Bluetooth program that I didn't use, so I did uninstall that program. After
your long exposition, I've uninstall other programs already on system that I
think are no needed.

Whether 5 seconds was a long time on your computer wasn't really known
because your hardware was unknown, how many and what type of background
processes were running was unknown, and what else you might've been
running for apps was unknown. A very busy computer can be very slow to
respond.

- I've said the delay duration was 5 seconds but that was an approximate
value because I did not measure it . Next time I've a problem I'll try to
take out more information since you look like a lawyer helping a criminal.
Your text is so long but I'll read it because delay still takes a little
bit. For now I'm looking for what is starting on registry.