Slow pictures context menu

Migrante on 05/01/2014 wrote:

"VanguardLH" ...

Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

http://i.cubeupload.com/GFwUzX.jpg

What filetype is that image? .jpg, .tif, something else? Where are you
seeing these images? within a program, like Photo Gallery (which you
have now uninstalled) or other photo gallery program, or File Explorer
preview or thumbnail images in its file list pane or an image in its
details/preview pane? Or are they displayed (embedded) on your desktop?
From where did you capture the images you show in your online pic? I'm
trying to get a handle on where you see the images on which you right-
click to know whose context menu you are seeing. The "Rotate" context
menu entries indicate you are viewing these images within a program, so
what is that program? Are those [previewed] image files in your online
pic or are they really huge icons from a file list somewhere?

Does the long delay occur only the first time you right click on an
image or every time you right click on an image?

When in the context menu and you click on Open With, what pre-selected
handlers are listed there? Similary, when in the context menu and you
click on Properties, are there any non-standard tab panels shown, like a
tab panel added by some software you installed? Is there a big delay to
show the Properties dialog?

Save your efforts and removing and reinstalling your application
software....it is extremely unlikely the source and cause is related to
WLPG...it does not control the rt context menu - Windows does.

What might be more significant, which you've failed to provide are your
system specs. Most Windows 8 systems have more than enough horsepower
but without verifying yours it might be premature to even suggest a
direction.

Hardware - mobo and how old
Processor on your machine (Intel, AMD) and type (PIII, P4, Core2, etc.)
RAM (installed memory capacity)

Also, imo, I doubt changing/deleting your user profile color calibration
profile will have any impact on the rt click menu in WLPG. It might
change the appearance of how colors are shown on the screen but Windows
Photo Viewer (for which the fix was intended) is not the same as WLPG
-the latter uses its own code for displaying pictures.

--
...winston
msft mvp consumer apps


Migrante wrote, On 1/5/2014 7:28 AM:
I've tried to verify if delay is related with windows photo gallery,
uninstalling wpg and movie maker from windows essentials 2012, but it
isn't.
.................................................. ..................

winston wrote
"Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

"VanguardLH" escreveu na mensagem ...

Migrante on 05/01/2014 wrote:

"VanguardLH" ...

Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

http://i.cubeupload.com/GFwUzX.jpg

What filetype is that image? .jpg, .tif, something else?

- jpg

Where are you
seeing these images? within a program, like Photo Gallery (which you
have now uninstalled) or other photo gallery program, or File Explorer
preview or thumbnail images in its file list pane or an image in its
details/preview pane? Or are they displayed (embedded) on your desktop?

- I was seeing in Photo Gallery.

From where did you capture the images you show in your online pic?

- I've take it from Google image.

Does the long delay occur only the first time you right click on an
image or every time you right click on an image?

- Long delay was occuring only in first click.

When in the context menu and you click on Open With, what pre-selected
handlers are listed there?

- Open with has image preview and editing programs options.

Similary, when in the context menu and you
click on Properties, are there any non-standard tab panels shown, like a
tab panel added by some software you installed?

- No, I think there's only standard tabs.

Is there a big delay to show the Properties dialog?

- Before the properties option there was menu delay on desktop 'problem' but
after menu shows up, there is no problem with properties dialog. I'm happy
with the shorter delay (~1second) I have now. Still it's not perfect but now
is better.

On 1/5/2014 4:41 PM, Migrante wrote:


- Before the properties option there was menu delay on desktop 'problem'
but after menu shows up, there is no problem with properties dialog. I'm
happy with the shorter delay (~1second) I have now. Still it's not perfect
but now is better.

I still recommend a short capture with Process Monitor.

The program will start tracing immediately. The left-most
menu, has a tick box you can untick to stop the trace. Then,
you can save the trace for later if you wish.

I've scrolled through as many as a 100,000 events, to find
a bug. So this is not a "casual" debugging tool. Using it,
to find a solution, is a lot of work!

I found a conflicting registry entry for my sound card,
which causes a problem with the sound control panel. And
I had to scroll through that many events, to find a single
"interesting" attempt to access the registry. The key in
question was missing, because another sound driver (competing
brand), had removed the key. Once I created the key with Regedit,
all was fixed again.

*******

There are other tools which give an even more microscopic view,
such as WinDbg, but without source or symbol files, that
wouldn't be any fun at all. I've debugged Firefox (because
Firefox source is available for download) with that tool,
and it's just awful (the Firefox source code, not the debugger :-) ) .

http://en.wikipedia.org/wiki/Windbg

That won't be of any use in this case, but still, it's
another example of a debugging tool. Windbg is what a software
developer might use.

Paul

On 1/05/2014, Ken Blake, MVP posted:
On Sat, 04 Jan 2014 16:45:40 -0800, Gene E. Bloch
wrote:

On 1/04/2014, Ken Blake, MVP posted:
On Sat, 04 Jan 2014 12:05:41 -0800, Gene E. Bloch
wrote:
On 1/04/2014, Ken Blake, MVP posted:
On Sat, 4 Jan 2014 16:22:06 -0000, "Migrante"
wrote:

I don't know why should I use an old newsreader or non microsoft
in a windows 8 forum.
If you can't help me I'll wait for something. I've tried
searching help in other places but couldn't find answer.


You should use whatever you want. Far be it from me to tell you
what to do.

My point is a simple one: if you make it hard for us to read your
messages, many of us will killfile you, as I am about to do.
Goodbye.

I don't killfile for mere etiquette violations or bad attitudes
(OTOH, pron or racism or insanity are other issues).


Nor I.


However, when someone's attitude is negative or when their reader
software makes it hard to figure out where their reponse is - and
especially when both are true - I sure won't put in a lot of
effort for the poster.


Exactly! And that's why I killfiled him.

ISTM that in your first remark you agreed with my stated approach to
killfiling and in your second remark you disagreed with it.

I'm puzzled.


In my first remark I said I agreed that I didn't killfile for
"etiquette violations or bad attitudes" (although there have been
some exceptions).


In my second remark, I said that I killfiled someone whose quoting
technique made their messages very hard to understand. Two different
things, as far as I'm concerned.

OK, so what to me was a seeming contradiction was really just a
reflection of our different attitudes towards the peccadillos in
question :-)

So, as examples, I don't killfile someone who violates netiquette by
top-posting (although there's occasionally someone whose top-posted
messages are very hard to understand, and I come close to
kill-filing them). But I do kill-file someone like the person to whom
I responded who refuses to either change to a newsreader that quotes
properly or put the signs in himself, and whose messages are
therefore very hard to read; I just don't have the time to try to
figure out what they are trying to say.

I usually spend a moment trying to figure it out, but my patience is
(by choice) short-lived.

--
Gene E. Bloch (Stumbling Bloch)

On Sun, 05 Jan 2014 15:07:43 -0800, Gene E. Bloch
wrote:

On Sat, 04 Jan 2014 16:45:40 -0800, Gene E. Bloch
wrote:


ISTM that in your first remark you agreed with my stated approach to
killfiling and in your second remark you disagreed with it.

I'm puzzled.


In my first remark I said I agreed that I didn't killfile for
"etiquette violations or bad attitudes" (although there have been
some exceptions).


In my second remark, I said that I killfiled someone whose quoting
technique made their messages very hard to understand. Two different
things, as far as I'm concerned.

OK, so what to me was a seeming contradiction was really just a
reflection of our different attitudes towards the peccadillos in
question :-)


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)



So, as examples, I don't killfile someone who violates netiquette by
top-posting (although there's occasionally someone whose top-posted
messages are very hard to understand, and I come close to
kill-filing them). But I do kill-file someone like the person to whom
I responded who refuses to either change to a newsreader that quotes
properly or put the signs in himself, and whose messages are
therefore very hard to read; I just don't have the time to try to
figure out what they are trying to say.

I usually spend a moment trying to figure it out,


Me too g


but my patience is (by choice) short-lived.


Me too vbg

But what bothers me the most is the person to whom one of us responds,
explaining what's wrong with his message and suggesting ways to fix
it, but who ignores what he's told. His viewpoint is "it's my message
and I'll do it any way I want to!"

That viewpoint is his right, and none of us can tell him what he *has
to* do. But my viewpoint is that I don't have to look at his crap, and
I don't have to try to help him with his problems. So people like that
quickly end up in my killfile.



Ken

Migrante on 05/01/2014 wrote:

I'm happy with the shorter delay (~1second) I have now. Still it's not
perfect but now is better.

In a different subthread, you remarked that you have since uninstalled
Photo Gallery. That was the slow context menu that started this
discussion. Without Photo Gallery and right-clicking elsewhere (File
Explorer, some other image viewer/editor), the delay is significantly
shorter than before. So it was Photo Gallery that was causing the long
delay to show the context menu.

The first time you right-click on an object, Windows has to scan through
the registry (although it's in memory after Windows loads) looking for
shell extensions and object handlers. That scan takes time but gets
cached so subsequent right-clicks on the same object type don't have to
scan the memory copy of the registry. Memory is fast but the registry
is huge.

Thankfully it was not a corrupted or invalid context menu handler.
Those also cause problems with the context menu, like longer delays to
load (because Windows is trying to resolve problems with the bad
definition in the registry for a handler) or even causing the context
menu to never appear (the build process for the context menu crashes).
I mentioned Nirsoft's ShellExView only if the problem was an bad context
menu handler since you can disable/enable them using that utility, and
why I touched on using a registry cleaner which will find the unresolved
references and list them to you for cleanup (but the user is still
responsible for understanding and allowing the proposed changes).

VanguardLH wrote:
Migrante on 05/01/2014 wrote:

I'm happy with the shorter delay (~1second) I have now. Still it's not
perfect but now is better.

In a different subthread, you remarked that you have since uninstalled
Photo Gallery. That was the slow context menu that started this
discussion. Without Photo Gallery and right-clicking elsewhere (File
Explorer, some other image viewer/editor), the delay is significantly
shorter than before. So it was Photo Gallery that was causing the long
delay to show the context menu.

The first time you right-click on an object, Windows has to scan through
the registry (although it's in memory after Windows loads) looking for
shell extensions and object handlers. That scan takes time but gets
cached so subsequent right-clicks on the same object type don't have to
scan the memory copy of the registry. Memory is fast but the registry
is huge.

Thankfully it was not a corrupted or invalid context menu handler.
Those also cause problems with the context menu, like longer delays to
load (because Windows is trying to resolve problems with the bad
definition in the registry for a handler) or even causing the context
menu to never appear (the build process for the context menu crashes).
I mentioned Nirsoft's ShellExView only if the problem was an bad context
menu handler since you can disable/enable them using that utility, and
why I touched on using a registry cleaner which will find the unresolved
references and list them to you for cleanup (but the user is still
responsible for understanding and allowing the proposed changes).

Hi,
The op did not need to do that...The Photo Gallery reference was
submitted as a possible picture viewer based on the graphic the op
provided. The op chose to uninstall a program that had no significance
whatsoever on the problem...Why? ...for one, the actual picture he
provided was not Photo Gallery but Windows Photo Viewer -and likewise
not a factor or cause of his original problem (slow context menu), and
second an probably more important limiting any remote diagnostic
attempts would be the fact that no information on the system beyond Win8
was provided.

Thus...neither Photo Gallery or Photo Viewer were the problem.

As you and others noted.....the cacheing and registry on first use is
more than likely the cause of the delay.


--
....winston
msft mvp consumer apps

""...winston‫"" escreveu na mensagem ...

VanguardLH wrote:
Migrante on 05/01/2014 wrote:

I'm happy with the shorter delay (~1second) I have now. Still it's not
perfect but now is better.

In a different subthread, you remarked that you have since uninstalled
Photo Gallery. That was the slow context menu that started this
discussion. Without Photo Gallery and right-clicking elsewhere (File
Explorer, some other image viewer/editor), the delay is significantly
shorter than before. So it was Photo Gallery that was causing the long
delay to show the context menu.

The first time you right-click on an object, Windows has to scan through
the registry (although it's in memory after Windows loads) looking for
shell extensions and object handlers. That scan takes time but gets
cached so subsequent right-clicks on the same object type don't have to
scan the memory copy of the registry. Memory is fast but the registry
is huge.

Thankfully it was not a corrupted or invalid context menu handler.
Those also cause problems with the context menu, like longer delays to
load (because Windows is trying to resolve problems with the bad
definition in the registry for a handler) or even causing the context
menu to never appear (the build process for the context menu crashes).
I mentioned Nirsoft's ShellExView only if the problem was an bad context
menu handler since you can disable/enable them using that utility, and
why I touched on using a registry cleaner which will find the unresolved
references and list them to you for cleanup (but the user is still
responsible for understanding and allowing the proposed changes).

Hi,
The op did not need to do that...The Photo Gallery reference was
submitted as a possible picture viewer based on the graphic the op
provided. The op chose to uninstall a program that had no significance
whatsoever on the problem...Why? ...for one, the actual picture he
provided was not Photo Gallery but Windows Photo Viewer -and likewise
not a factor or cause of his original problem (slow context menu), and
second an probably more important limiting any remote diagnostic
attempts would be the fact that no information on the system beyond Win8
was provided.

Thus...neither Photo Gallery or Photo Viewer were the problem.

As you and others noted.....the cacheing and registry on first use is
more than likely the cause of the delay.


--
....winston
msft mvp consumer apps
.................................................. .................................................. ...................

Hello, I must clarify one point about operating system. The 'trouble' was
happening on windows 8 but I was using windows 7 to contact you. The jpg
file was taken on windows 7 . Menu entries 'set desktop background' and
others were the same on both systems. I thought that way would be easier to
expose the question without having to send print screen from one system to
the other.

""...winston‫"" on 06/01/2014 wrote:

VanguardLH wrote:
Migrante on 05/01/2014 wrote:

I'm happy with the shorter delay (~1second) I have now. Still it's not
perfect but now is better.

In a different subthread, you remarked that you have since uninstalled
Photo Gallery. That was the slow context menu that started this
discussion. Without Photo Gallery and right-clicking elsewhere (File
Explorer, some other image viewer/editor), the delay is significantly
shorter than before. So it was Photo Gallery that was causing the long
delay to show the context menu.

The first time you right-click on an object, Windows has to scan through
the registry (although it's in memory after Windows loads) looking for
shell extensions and object handlers. That scan takes time but gets
cached so subsequent right-clicks on the same object type don't have to
scan the memory copy of the registry. Memory is fast but the registry
is huge.

Thankfully it was not a corrupted or invalid context menu handler.
Those also cause problems with the context menu, like longer delays to
load (because Windows is trying to resolve problems with the bad
definition in the registry for a handler) or even causing the context
menu to never appear (the build process for the context menu crashes).
I mentioned Nirsoft's ShellExView only if the problem was an bad context
menu handler since you can disable/enable them using that utility, and
why I touched on using a registry cleaner which will find the unresolved
references and list them to you for cleanup (but the user is still
responsible for understanding and allowing the proposed changes).

Hi,
The op did not need to do that...The Photo Gallery reference was
submitted as a possible picture viewer based on the graphic the op
provided. The op chose to uninstall a program that had no significance
whatsoever on the problem...Why? ...for one, the actual picture he
provided was not Photo Gallery but Windows Photo Viewer -and likewise
not a factor or cause of his original problem (slow context menu), and
second an probably more important limiting any remote diagnostic
attempts would be the fact that no information on the system beyond Win8
was provided.

Thus...neither Photo Gallery or Photo Viewer were the problem.

As you and others noted.....the cacheing and registry on first use is
more than likely the cause of the delay.

I assumed the OP did not lie so when he said he saw the pics in Windows
Photo Gallery and right-clicked on them there then that's what he did.
An app can use whatever context menu it wants. It did not appear the
context menu shown in his online pics matched up with what would, say,
show up in File Explorer. He said he was right-clicking on a pic inside
of Photo Gallery.

He started with saying he was right-clicking on images on the desktop.
Then it was right-clicking on images inside of Photo Gallery. Who knows
what he will say next.

"VanguardLH" escreveu na mensagem ...

""...winston‫"" on 06/01/2014 wrote:

VanguardLH wrote:
Migrante on 05/01/2014 wrote:

I'm happy with the shorter delay (~1second) I have now. Still it's not
perfect but now is better.

In a different subthread, you remarked that you have since uninstalled
Photo Gallery. That was the slow context menu that started this
discussion. Without Photo Gallery and right-clicking elsewhere (File
Explorer, some other image viewer/editor), the delay is significantly
shorter than before. So it was Photo Gallery that was causing the long
delay to show the context menu.

The first time you right-click on an object, Windows has to scan through
the registry (although it's in memory after Windows loads) looking for
shell extensions and object handlers. That scan takes time but gets
cached so subsequent right-clicks on the same object type don't have to
scan the memory copy of the registry. Memory is fast but the registry
is huge.

Thankfully it was not a corrupted or invalid context menu handler.
Those also cause problems with the context menu, like longer delays to
load (because Windows is trying to resolve problems with the bad
definition in the registry for a handler) or even causing the context
menu to never appear (the build process for the context menu crashes).
I mentioned Nirsoft's ShellExView only if the problem was an bad context
menu handler since you can disable/enable them using that utility, and
why I touched on using a registry cleaner which will find the unresolved
references and list them to you for cleanup (but the user is still
responsible for understanding and allowing the proposed changes).

Hi,
The op did not need to do that...The Photo Gallery reference was
submitted as a possible picture viewer based on the graphic the op
provided. The op chose to uninstall a program that had no significance
whatsoever on the problem...Why? ...for one, the actual picture he
provided was not Photo Gallery but Windows Photo Viewer -and likewise
not a factor or cause of his original problem (slow context menu), and
second an probably more important limiting any remote diagnostic
attempts would be the fact that no information on the system beyond Win8
was provided.

Thus...neither Photo Gallery or Photo Viewer were the problem.

As you and others noted.....the cacheing and registry on first use is
more than likely the cause of the delay.

I assumed the OP did not lie so when he said he saw the pics in Windows
Photo Gallery and right-clicked on them there then that's what he did.
An app can use whatever context menu it wants. It did not appear the
context menu shown in his online pics matched up with what would, say,
show up in File Explorer. He said he was right-clicking on a pic inside
of Photo Gallery.

He started with saying he was right-clicking on images on the desktop.
Then it was right-clicking on images inside of Photo Gallery. Who knows
what he will say next.
.................................................. .................................................. .....................
I must correct what you are saying. I had question on desktop. Then I was
asked to show menu entries on the system I was not using. But I remembered
menu entries had set desktop background and rotate image. I was not sure if
those entries belong to system but I said there were no extra options. My
desktop is full of icons and did not want to show them on print screen.
That's why I've made a print screen on preview program to show menu entries
that I was not sure if were standard. Plus, the windows 8 system language is
portuguese. I don't know if windows 8 and windows essentials 2012 are
portuguese from Brasil or Portugal. I thought it would be more confuse for
you to help.

Before we get too buried in what was said, what was meant, conflicting
statements, & what was omitted or vague, let's restart with the basics.

#1: WHERE are you right-clicking to get a slow appearing context menu?
- On a *desktop* object? (note 1)
- Inside a viewer *program*?
- Somewhere else (e.g., image for a tile)?

#2: After uninstalling Photo Gallery, does the context menu STILL take a
long time to show up when right-clicking (where specified by #1)?
- If yes:
* How long does it take to appear?
* Does the delay occur:
o Only the first time you show the context menu?
o Or every time (1st, 2nd, 3rd, Nth time) you show the context menu?
- If no then the problem was resolved.

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.

On 1/05/2014, Ken Blake, MVP posted:
On Sun, 05 Jan 2014 15:07:43 -0800, Gene E. Bloch
wrote:

On Sat, 04 Jan 2014 16:45:40 -0800, Gene E. Bloch
wrote:


ISTM that in your first remark you agreed with my stated approach
to killfiling and in your second remark you disagreed with it.

I'm puzzled.

In my first remark I said I agreed that I didn't killfile for
"etiquette violations or bad attitudes" (although there have been
some exceptions).

In my second remark, I said that I killfiled someone whose quoting
technique made their messages very hard to understand. Two
different things, as far as I'm concerned.

OK, so what to me was a seeming contradiction was really just a
reflection of our different attitudes towards the peccadillos in
question :-)

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.
Mostly, I was checking because I think the word is Spanish, so I don't
like the two c's. It *is* Spanish, but in English it happens that it
isn't spelled the Spanish way.

So, as examples, I don't killfile someone who violates netiquette
by top-posting (although there's occasionally someone whose
top-posted messages are very hard to understand, and I come close
to kill-filing them). But I do kill-file someone like the person
to whom I responded who refuses to either change to a newsreader
that quotes properly or put the signs in himself, and whose
messages are therefore very hard to read; I just don't have the
time to try to figure out what they are trying to say.

I usually spend a moment trying to figure it out,

Me too g

but my patience is (by choice) short-lived.

Me too vbg

But what bothers me the most is the person to whom one of us
responds, explaining what's wrong with his message and suggesting
ways to fix it, but who ignores what he's told. His viewpoint is
"it's my message and I'll do it any way I want to!"

That viewpoint is his right, and none of us can tell him what he *has
to* do. But my viewpoint is that I don't have to look at his crap,
and I don't have to try to help him with his problems. So people like
that quickly end up in my killfile.

I also react negatively to those sorts of responses (and the others who
day "why are you picking on me?" even after we explain why). That's why
my choice is to have little patience when trying to decode the posts.

In this area, we don't really disagree all that much :-)

--
Gene E. Bloch (Stumbling Bloch)

"VanguardLH" escreveu na mensagem ...

Before we get too buried in what was said, what was meant, conflicting
statements, & what was omitted or vague, let's restart with the basics.

#1: WHERE are you right-clicking to get a slow appearing context menu?
- On a *desktop* object? (note 1)
- Inside a viewer *program*?
- Somewhere else (e.g., image for a tile)?

#2: After uninstalling Photo Gallery, does the context menu STILL take a
long time to show up when right-clicking (where specified by #1)?
- If yes:
* How long does it take to appear?
* Does the delay occur:
o Only the first time you show the context menu?
o Or every time (1st, 2nd, 3rd, Nth time) you show the context menu?
- If no then the problem was resolved.

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.
.................................................. .................................................. .................
You're a little bit late because the question was already solved without
your help.
But let's suppose I was still experiencing the long delay between right
click on desktop and context menu apparition.

#1: - I'm right-clicking on desktop object (image file).
#2: - After uninstalling Photo Gallery, context menu still takes a couple
seconds to show up. Delay occur only first time context menu shows up.

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

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."


But what bothers me the most is the person to whom one of us
responds, explaining what's wrong with his message and suggesting
ways to fix it, but who ignores what he's told. His viewpoint is
"it's my message and I'll do it any way I want to!"

That viewpoint is his right, and none of us can tell him what he *has
to* do. But my viewpoint is that I don't have to look at his crap,
and I don't have to try to help him with his problems. So people like
that quickly end up in my killfile.

I also react negatively to those sorts of responses (and the others who
day "why are you picking on me?" even after we explain why). That's why
my choice is to have little patience when trying to decode the posts.

In this area, we don't really disagree all that much :-)


I didn't think we did. g