Mofi wrote:It is of course possible to do the unregister of the shell extension DLL(s) with the uninstaller for the current user account. That would make the uninstall a little bit cleaner for computers with a single user account. For computers used by multiple users, there is most likely no chance that an uninstaller unregisters the shell extension for all user accounts.
You might have not understood what I described in previous post.
I will try to explain ti more clearly, in details.
The thing is that there is no need for additional implementation, workaround in the installer to perform cleanup. Of course, also as you have mentioned, due to it will not remove this for all users, but only for logged in user.
For example - If you install WinZip under system account or login with another user, there is no WinZip Shell Extension visible on right-click, until you first run WinZip application. So the behavior is the same as UltraEdit does. But if you simply delete shell extension DLL file or perform uninstall of WinZip under system account, then "WinZip" shell extension automatically hidden by Windows - for all users - and this is without extra cleanup, HKCU registries are still in place, only DLL file that registries are pointing to is removed.
It is simply as just 5 minutes to check and a WinZip trial is easy downloadable. There of course may be other software that also properly manages shell extensions. This just proves that there is no need for extra magic to do it. Another example of the same behavior is "Git" application. I'm sure there are plenty of another apps that also properly make their shell extensions.
Of course I would not complain and discuss this if same behavior of User shell extensions was in other applications. But since there is no such a problem with other Apps under the same conditions - this leads to the conclusion that "UltraEdit" developers team made it wrong.
I also have send this to the support team, so waiting till they comment on this.