> 1 - Does shelexview display anything? I had tried it but did not see anything
> wrong. I'll recheck it though and compare against 32-bit.
OK thanks. Just to confirm, you are using the 64 bit version and it is saying
the pproctx.dll is an installed 64 bit context menu handler/ shell extension
>
> 2 - There is a 32 bit regedit and a 64 bit regedit. The only thing different
> is that when using the 64-bit one it displays 32-bit keys in
> HKLM/software/wow6432node. Under there is the stuff normally in
> HKLM/software.
Just to confirm, none of the keys associated with the pproctx files should only
be under wow6432. They should be under the 64 bit version of the keys. Maybe
they could be under both, but that might be a concern.
As per MSDN, the keys that matter are:
HKEY_CLASSES_ROOT
CLSID
{00000000-1111-2222-3333-444444444444}
InProcServer32
(Default) = C:\MyDir\MyCommand.dll
ThreadingModel = Apartment
*
(Default) = MyProgram Application
Shellex
ContextMenuHandler
MyCommand
(Default) = {00000000-1111-2222-3333-444444444444}
expect of course the the pproctx guid used.
These keys should be detected by the 64 bit regedit.
BTW, it is hkey_classes_root (not HKLM) that the msdn and pproconf.exe target.
--------------------------------
I did verify that HKLM/software/wow6432node has a stilletoproducts key that
looks correct.
That one should not matter. Its only the ones above that matter for context
menu handlers, afaik.
---------------------------------------------------------
>
> 3 - When I run pproconf it does show "remove context" menu. Doing this
> removes the entries under HKCR/* and using "install" puts the values back in
> there.
That really bothers me. As I understand it, in order to implement running 32
bit programs like pproconf on 64 bit windows, the system automatically will not
let 32 bit programs write to 64 bit registry without special programming.
So my first guess would have been that pproconf.exe would not have been able to
access the 64 bit portion of the registry that explorer accesses when it looks
for 64 bit shell extensions. If you are saying it can remove the keys from the
64 bit portion of the registry that matters, something is not right (possibly
me, but possibly the keys are not really there for 64 bit explorer to see).
Are you comfortable using regedit 64 to manually delete and recreate keys
listed above? Of course, be careful not to delete the high level keys! Only
the lower level keys pertinent to pproctx. If this does not make sense, don't
try it.
>
> 4 - The pproctx.dll is in the location listed in
> HKCR\CLSID\{2EC41A81-AE31-11d2-A6E6-10E356C10000} but are you thinking of
> another location for wow64 files?
I had also heard that the wow64 system invisibly redirects c:\program files\ to
c:\program files (x86)\. One thing to try would be to move pproctx.dll to
entirely new folder and change the file name in the above list of keys to point
to that new folder.
