[SOLVED] : UltraEdit shell context handler no show in Win 10

[highend]

That's a trace for:
[ ] Show file system activity
[ ] Show network activity

Filters = resetted to default
and then added:
Detail contains UltraEdit then Include

23:34:29.9381634, XYplorer.exe, 2528, RegEnumKey, HKCU\Software\Classes\*\shellex\ContextMenuHandlers, SUCCESS, Index: 1, Name: UltraEdit
23:34:29.9737966, XYplorer.exe, 2528, RegQueryValue, HKCU\Software\Classes\WOW6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32\(Default), SUCCESS, Type: REG_SZ, Length: 138, Data: C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\ue32ctmn.dll
23:34:29.9778273, XYplorer.exe, 2528, RegQueryValue, HKCU\Software\Classes\WOW6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32\(Default), SUCCESS, Type: REG_SZ, Length: 138, Data: C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\ue32ctmn.dll
23:34:29.9809135, XYplorer.exe, 2528, RegQueryValue, HKCU\SOFTWARE\IDM Computer Solutions\UltraEdit\ContextMenuText, SUCCESS, Type: REG_SZ, Length: 22, Data: &UltraEdit
23:34:29.9809272, XYplorer.exe, 2528, RegQueryValue, HKCU\SOFTWARE\IDM Computer Solutions\UltraEdit\ContextMenuText, SUCCESS, Type: REG_SZ, Length: 22, Data: &UltraEdit

[highend]

Ok, what happens when you try the following:

- Start Process monitor and use the setting from my last post

- Open the 32-bit edition of Notepad
%windir%\SysWOW64\notepad.exe

- Use File / Open
and right click on e.g. a .txt file (not associated to UEdit)

Your trace in Process monitor should display exactly the same in comparison to what it displays when you do the click on the same file in XYplorer...

[iycgtptyarvg]

In that right mouse popup menu UltraEdit also doesn't show up. It seems UltraEdit does something special which doesn't work with any application other than Windows Explorer

[highend]

No. Notepad as a 32bit application behaves exactly the same as XYplorer and if you don't get what I get it's not about Windows Explorer (which is 64-bit only) but about UltraEdit / your OS. But it's not something "special" that is "done" by UEdit. It's a broken installation. Maybe the 32-bit context menu handler of UEdit wasn't installed succesfully or you have installed other tools that mess with it.

I would have tried: Uninstall UEdit. Both versions (because you added the 64-bit as well if I remember correctly). Restart. Install the 32-bit version to it's standard path. Still not working? I can't recommend any "clean up your registry tool" (maybe apart from using Total Uninstall in the first place) so my next step would have been: Install the OS from fresh
Why I never have to do "such" things -> Image for Linux, I always keep my OS'ses in a "safe" state...

[iycgtptyarvg]

I have installed and uninstalled UltraEdit dozens of times by now. 'Run as administrator', default path, reset configuration... I think I've tried everything by now. All have the same result.

What I don't understand is why XYplorer doesn't show the UltraEdit menu in the 64-bit context menu.

[highend]

It does it for me... With exactly the same registry calls apart that they are now using ue64ctmn.dll instead of the 32bit version.

But I guess I know the potential problem on your system:

Your setup of your TEMP folder. It normally points to your %LOCALAPPDATA%\Temp folder, not to %windir%\Temp.
%windir%\Temp is not accessible by default without tinkering with it's permissions and the "ContextMenu64.exe" from XYplorer works with a temporary file which is probably not created -> No context menu...

Switch back to the default temp folder, restart your OS and try it again!

[bdeshi]

and make sure you edit the %TEMP% and %TMP% variable for your own user account, not the system ones. (The system temp variables shouldn't matter)

envvartmp.png (26.18 KiB) Viewed 3659 times

[/size]

[iycgtptyarvg]

I finally got it working.

I found the solution on the UltraEdit forums (I went there to look for an older version to test, but found the solution instead).

It has to do with UAC (which I have turned OFF) and with having a user (which I don't, I use the default administrator account).

The solution is to register the shell context handler registry keys manually.
You have to add the keys in BOTH a 64-bit application (e.g., Windows Explorer) AND a 32-bit application (e.g., XYplorer).
After I did that, everything worked fine.

The keys are:

REGEDIT4

[HKEY_CURRENT_USER\Software\Classes\*\shellex\ContextMenuHandlers\UltraEdit]
@="{b5eedee0-c06e-11cf-8c56-444553540000}"
[HKEY_CURRENT_USER\Software\Classes\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}]

[HKEY_CURRENT_USER\Software\Classes\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32]
@="C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\\ue64ctmn.dll"
"ThreadingModel"="Apartment"

[HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}]

[HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32]
@="C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\\ue32ctmn.dll"
"ThreadingModel"="Apartment"

[HKEY_CURRENT_USER\Software\IDM Computer Solutions\UltraEdit]
"ContextMenuText"="&UltraEdit"
"IntegrateWithExplorer"=dword:00000001
"IntegrateWithExplorerOverride"=-

[HKEY_LOCAL_MACHINE\Software\Classes\*\shellex\ContextMenuHandlers\UltraEdit]
@="{b5eedee0-c06e-11cf-8c56-444553540000}"

[HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}]

[HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32]
@="C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\\ue64ctmn.dll"
"ThreadingModel"="Apartment"

[HKEY_LOCAL_MACHINE\Software\Classes\Wow6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}]

[HKEY_LOCAL_MACHINE\Software\Classes\Wow6432Node\CLSID\{b5eedee0-c06e-11cf-8c56-444553540000}\InProcServer32]
@="C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\\ue32ctmn.dll"
"ThreadingModel"="Apartment"

[HKEY_LOCAL_MACHINE\Software\IDM Computer Solutions\UltraEdit]
"ContextMenuText"="&UltraEdit"
"IntegrateWithExplorer"=dword:00000001
"IntegrateWithExplorerOverride"=-

Here is the registry file ready made for you to use. Please note that this works in the default install directory. If you install UltraEdit in another directory, you'll have to change the paths yourself.

Register UltraEdit Shell Integration.7z

(553 Bytes) Downloaded 365 times

[highend]

So "Bouwhuis" is the localized name for "Administrator"?

[iycgtptyarvg]

No, it's the user name you supply by default when installing Windows 10.

When you install windows you can do the following :
1. Use the predefined administrator account. This is the full administrator account that bypasses UAC (named 'Administrator).
2. Have a named administrator account. This is the limited administrator account and adheres to UAC (in my case 'Bouwhuis').
3. Have a normal user account. This is a limited account and adheres strictly to UAC (any name can be given).
4. Use the predefined guest account. This is a severely limited account (named 'Guest').

[highend]

I see but your statement:

It has to do with UAC (which I have turned OFF) and with having a user (which I don't, I use the default administrator account).

was somehow misleading in this case because that lead to the conclusion that you use the inbuilt "Administrator" account

[iycgtptyarvg]

Blame Microsoft for having two types of administrator accounts.

[jlippey]

Register UltraEdit Shell Integration.7z … Downloaded 151 times

Can anybody post a tested .reg file for 64-bit UltraEdit installed to the default location?
--
Jerry