Who Put that Property Sheet there?

[spoon2001]

Is there a tool that will identify what application put a particular tabbed
page (Property Sheet) in a Properties dialog?

I right-clicked on a JPEG file, and lo and behold, there was an Image tab on
the Properties dialog, with a little red and blue square icon it. The EXIF
info was listed on this tab. Excellent!

But how did that tab (Property Sheet) get into that Properties dialog? I
have lots of graphics programs on my system, which one did it?

Ultimately I tracked it down the old fashioned way ... REGEDIT. Looked at
the .JPG key under \HKCR. This redirects me to "jpegfile". Looked at
\HKCR\jpegfile\shellex\PropertySheetHandlers. OK, there was
"PixVuePropertySheet". I exported that key to a REG file and deleted it.
Voila, that property sheet is now gone! Of course, I re-imported that key
so that I can have that nice property sheet.

But does anybody know of any easier way?

I went back to ShellExView and found PixVuePropertySheet. ShellExView lets
you disable and re-enable selected shell extensions, including
PropertySheetHandlers. It worked. Recommended.
http://www.nirsoft.net/utils/shexview.html

 

[hummingbird]

Is there a tool that will identify what application put a particular tabbed
page (Property Sheet) in a Properties dialog?

I right-clicked on a JPEG file, and lo and behold, there was an Image tab on
the Properties dialog, with a little red and blue square icon it. The EXIF
info was listed on this tab. Excellent!

But how did that tab (Property Sheet) get into that Properties dialog? I
have lots of graphics programs on my system, which one did it?

Ultimately I tracked it down the old fashioned way ... REGEDIT. Looked at
the .JPG key under \HKCR. This redirects me to "jpegfile". Looked at
\HKCR\jpegfile\shellex\PropertySheetHandlers. OK, there was
"PixVuePropertySheet". I exported that key to a REG file and deleted it.
Voila, that property sheet is now gone! Of course, I re-imported that key
so that I can have that nice property sheet.

But does anybody know of any easier way?

I'm not aware of any easier way. You have to use *something* to
examine these things and ShellExView is excellent at the job.

There, happy now? ;-)

 

[spoon2001]

I'm not aware of any easier way. You have to use *something* to
examine these things and ShellExView is excellent at the job.

There, happy now? ;-)

Not completely ... there was no way to tell from ShellExView that
PixVuePropertySheet was the source of my mysterious "Image" tab.
ShellExView has an "extensions" column but .JPG was not one of the listed
extensions. I had to do the REGEDIT thing first, to find the reference to
PixVuePropertySheet that way, by looking under the HKCR\jpegfile. But still
I agree, ShellExView is great to have. Those guys at Nirsoft and
Sysinternals have some great utilities for control-freak geeks like me.

What I really want is to be able to run a detector program, hover my mouse
over that mysterious image tab, and have a tooltip pop up and say "PixVue
put this tab here!" (I'd like the same thing for context menu choices, but
that's a whole other can of worms).

The window info programs (Dis@, Cowspy) were no help on this subject. All
they could tell me was the window handle number, etc.

 

[hummingbird]

Not completely ...

Sorry, I thought your original post was a plug for ShellExView!

there was no way to tell from ShellExView that
PixVuePropertySheet was the source of my mysterious "Image" tab.
ShellExView has an "extensions" column but .JPG was not one of the listed
extensions. I had to do the REGEDIT thing first, to find the reference to
PixVuePropertySheet that way, by looking under the HKCR\jpegfile. But still
I agree, ShellExView is great to have. Those guys at Nirsoft and
Sysinternals have some great utilities for control-freak geeks like me.

What I really want is to be able to run a detector program, hover my mouse
over that mysterious image tab, and have a tooltip pop up and say "PixVue
put this tab here!" (I'd like the same thing for context menu choices, but
that's a whole other can of worms).

The window info programs (Dis@, Cowspy) were no help on this subject. All
they could tell me was the window handle number, etc.

The latest ver of ShellExView can highlight in colour all shell exts
which are *not* Microsoft; that should nail it down a lot. I've got
about six running on my system and each one's easily identifiable, if
not by its name, then by its path etc.

Apart from that, I can only suggest trying some of the other context
menu/shell identifiers/editors: ContextEdit or Associate - both free.
I use both and haven't failed to get to the bottom of what causes any
shell ext/context entry or property page tab.