I'm using UltraEdit v12 in Vista and the context menu "Edit with UltraEdit" is missing, which I've seen also occurred to others. This is what you can do to get around the problem:
[HKEY_CLASSES_ROOT\*\shell\UltraEdit]
@="Edit with UltraEdit"
Thank you for the temp fix. I did report the problem to IDM, so by the time vista goes public it will most likely be resolved. I told myself I wouldn't run vista until at least SP1, but when I got a hold of the non-beta I couldn't resist. I actually am really enjoying it. It's been a little rough, but none of the problems I've run into so far have been show stoppers.
Modify the red highlighted part to your environment. Instead of a single backslash you must type in this string always 2 backslashes (like in C/C++ and many other programming languages).
Save the file with the extension reg, for example UE_To_Context_Menu_For_Vista.reg
Now double click in Explorer on this file and Regedit will ask you if you really want to import this file into the registry. Click twice OK.
@= is in the exported registry file what is shown in Regedit at top in the right panel as (Default). The default value always exists for a key and is by default always a string value. If you want to enter the string with Regedit directly by double clicking on the default value, you must know that in this dialog the string must be entered without the escape character \ which means only a single backslash and only " instead of \".
Best regards from an UC/UE/UES for Windows user from Austria
I'm running retail Vista Business x64 for a week and my UltraEdit (12.20a) right-click option is working well. It shows up in the context menu as simply "UltraEdit."
I've noticed that disabling User Account Control has made my right-click UltraEdit option go away. I know how to fix this but thought I should note it here.
I have UAC disabled in Vista x64 and I dont get the context menu to work.
I get an error when trying to register "ue64ctmm.dll", so my guess is that ue64ctmm.dll has some UAC handling bugs that kicks in if UAC is disabled that prevents the dll from work or even register at all.
If this is the case, my guess is that IDM isnt using the "TOKEN_ELEVATION_TYPE" as they should to check if the splitted token is missing due to UAC being off or becuase the user really is a simple standard user.
I beleive that they are ONLY checking "TOKEN_ELEVATION" at this moment when they detect Windows Vista is the host OS.