Notepad++ with HexEdit won't run in Windows 7

Question

I use Notepad++ v5.9.6.2 (Unicode) on Windows 7 (64 bit) and I have installed the HEX-Editor v0.9.5 plugin.

The problem is that only administrators now seem to be able to run Notepad++. With guests and normal users the following happens after launching:

• First absolutely nothing happens for about 20 seconds.

• Then a dialog called "C:\Program Files (x86)\Notepad++\plugins\HexEditor.dll" appears. It reads:

  Fail loaded

  This plugin is not compatible with current version of Notepad++.

  Do you want to remove this plugin from plugings directory to prevent this message from the next launch time?

• After I click "No" a shorter wait, followed by another dialog, called "Exception On WM_CREATE". It reads:

  Unknown exception

Again, for administrators everything works fine.

I checked if it had anything to do with security constraints on the plugin files (or other Notepad++ files), but this doesn't appear to be the case. If I make a user member of Power Users but not Administrators, then Notepad++ works fine for this user as well. I granted the Power Users group almost the same local user rights as the Administrators group. (Administrative Tools > Local Security Policy > Security Settings > Local Policies > User Rights Assignment)

What could be the problem and how should this be fixed?

Answer 1

Try this

1. login as admin
2. right click on notepad++ then property,
3. in compatibility tab, check "Run this program as administrator".
4. Then click "Change setting for all user"
5. Logout and login with guest account or normal user account
6. run notepad++ again.

Problem is probably due to the fact that to access to .dll files require admin privilege.

Answer 2

I think the problem is in fact an attempt by the plugin to modify restricted files somewhere in Notepad++'s installation directory. I had the same problem with Notepad++ itself, which I solved by installing in the Public user profile directory. It seems that Notepad++ and its plugin authors are not very conversant with Windows security arrangements. Aside from moving the installation directory, you could liberalize the security permissions on the relevant Program Files subfolders.

Also, I think that raw disk access, which a hex editor would likely seek to acquire (I know all the hex editors I have used have done so) may require administrative privilege.