Notepad Plugins Failing to Install on Windows 10? Fix

If Notepad++ plugins fail to install on Windows 10, it is almost always because the plugin is compiled for a different architecture (32-bit vs 64-bit) or because the plugin manager is outdated. The fix is to match the plugin version to your Notepad++ installation and, if using the built-in Admin tool, update it first.

Why Notepad++ Plugins Fail to Install

Notepad++ is a popular text editor, but its plugin system is notoriously picky about versions. The most common reason a plugin fails to install is a mismatch between the plugin’s compiled architecture and your Notepad++ installation. If you installed the 64-bit version of Notepad++, you must download 64-bit plugins; 32-bit plugins will not load and often cause an error dialog at startup.

Another frequent cause is the Plugin Manager itself. The built-in Plugins Admin (introduced in Notepad++ 7.6) relies on an online repository that can be temporarily unavailable or outdated. If the list of available plugins is empty or the install button is greyed out, the repository connection is the problem.

Finally, Windows 10’s User Account Control (UAC) can block plugins from writing to the plugins folder if Notepad++ is installed in C:\Program Files. This is a protected location, and even if you have admin rights, the installer may silently fail.

How the Plugin System Works

Notepad++ loads plugins from a subfolder named plugins inside its installation directory. Each plugin is a DLL file (plus optional supporting files) that must match the bitness of the editor. The editor reads these DLLs at startup; if a DLL is incompatible, it logs an error and skips it.

There are two ways to install plugins:

Plugins Admin – Built into Notepad++ 7.6 and later. It downloads and installs plugins from a central repository, handling the DLL placement automatically.
Manual installation – Download the plugin ZIP, extract it, and copy the DLL into the plugins folder. You may need to create a subfolder named after the plugin (e.g., plugins\NppExec\NppExec.dll).

After manual installation, you must restart Notepad++. If the plugin still doesn’t appear, check the ? > Debug Info menu to see the exact plugin load errors.

Step-by-Step Fix for Failed Installations

Follow these steps in order. Most failures are resolved by step 2 or 3.

Check your Notepad++ bitness. Open Notepad++, click ? (or Help) and select Debug Info. Look for the line that says Build time or Architecture – it will show either 32-bit or 64-bit.
Update Plugins Admin. If you are using Plugins Admin, click Plugins Admin from the Plugins menu. If it shows an update button, click it. If the list is empty, close Notepad++, download the latest PluginsAdmin.zip from the official Notepad++ GitHub repository (search for “PluginsAdmin releases”), and replace the PluginsAdmin.dll in the plugins folder.
Install manually with the correct architecture. Go to the official plugin page (usually the GitHub repository of the plugin). Download the release that matches your Notepad++ bitness. Extract the ZIP, and copy the DLL into the plugins folder. If the plugin has a subfolder structure, preserve it.
Run Notepad++ as Administrator once. Right-click the Notepad++ shortcut and select Run as administrator. Then try the installation again. This bypasses UAC restrictions on the Program Files folder.
Check the plugin’s dependencies. Some plugins require other plugins or specific versions of Notepad++. Read the plugin’s documentation. For example, the popular NppExec plugin requires a separate DLL that must be in the same folder.
Disable antivirus temporarily. Some security software flags plugin DLLs as suspicious. Temporarily disable real-time protection, install the plugin, then re-enable it. Only do this with plugins from trusted sources.

Common Plugin-Specific Issues

Some plugins have known quirks on Windows 10:

NppExec – This plugin needs its own subfolder. If you put the DLL directly in the plugins folder, it won’t load. Create plugins\NppExec and place NppExec.dll inside.
Compare – The Compare plugin often fails if you have an old version. It requires Notepad++ 7.9 or later. Check the plugin’s release notes.
Python Script – This plugin requires the 32-bit version of Notepad++ even on 64-bit Windows. If you have 64-bit Notepad++, it will never load. You must install the 32-bit editor to use it.
Emmet – Emmet for Notepad++ is outdated and frequently fails on newer Windows 10 builds. Consider using a browser-based alternative or a different editor.

How to Choose the Right Plugin Version

Before downloading any plugin, verify three things:

Bitness: 64-bit plugins only work with 64-bit Notepad++. If the plugin page offers both, download the one that matches your editor.
Notepad++ version: Many plugins state a minimum Notepad++ version. If you have an older editor, update it first. Notepad++ updates are free and fast.
Source: Only download from the official GitHub repository or the plugin’s official website. Third-party download sites often host outdated or modified DLLs that cause errors.

If you are unsure which version to get, look at the plugin’s releases page on GitHub. The latest release usually has a file name that includes win64 or win32. If there is no such indicator, read the release notes.

Manual Installation vs. Plugins Admin: Which to Use?

Plugins Admin is convenient, but it has limitations. It only lists plugins that have been whitelisted by the Notepad++ team. Many excellent plugins are not in the repository, so you must install them manually. Manual installation gives you more control but requires you to manage updates yourself.

For manual installation, always create a dedicated subfolder for each plugin. This keeps the plugins folder tidy and prevents DLL name conflicts. For example, if two plugins both have a file named utility.dll, they would overwrite each other if placed directly in the plugins folder.

After copying the files, restart Notepad++. If the plugin still doesn’t show up, open Debug Info and look for the Plugins loaded section. It will list any DLL that failed to load, along with a reason.

Safety and Security Considerations

Plugins run with the same privileges as Notepad++. A malicious plugin could read your files or even execute commands. Only install plugins from well-known developers or official repositories. Before installing, scan the DLL with Windows Defender or your antivirus.

Be especially wary of plugins that ask for administrator rights or that modify system files. Legitimate plugins rarely need such access. If a plugin’s installation instructions tell you to disable UAC or turn off antivirus permanently, that is a red flag.

If a plugin causes Notepad++ to crash or behave erratically, remove it immediately. Simply delete the plugin’s folder from the plugins directory and restart the editor. This is safe and does not affect your documents.

Frequently Asked Questions

Why does Plugins Admin show an empty list?

This usually means the plugin repository is unreachable. Check your internet connection, then update Plugins Admin to the latest version. If you are behind a corporate firewall, the repository may be blocked. In that case, use manual installation instead.

Can I use a 32-bit plugin in 64-bit Notepad++?

No. The two architectures are incompatible. A 32-bit DLL will not load in a 64-bit process. You must download the 64-bit version of the plugin. If the plugin only offers 32-bit builds, you have to install the 32-bit Notepad++.

Where does Notepad++ store plugins?

By default, plugins are stored in the plugins subfolder of the Notepad++ installation directory. If you installed Notepad++ via the Microsoft Store, the path is different – it is under %LOCALAPPDATA%\Packages\...\LocalState. Check Debug Info for the exact path.

Why does the plugin install but not appear in the menu?

This is often due to a missing dependency or a subfolder structure issue. The plugin may have loaded but failed to register its menu items. Check Debug Info for errors. Also, some plugins only appear after you restart Notepad++ completely (not just close the window, but exit from the system tray).

Is it safe to copy a plugin DLL from another computer?

It is generally safe if the source computer has the same Notepad++ version and architecture. However, some plugins store configuration in the registry or in the user profile, so copying only the DLL may not transfer all settings. It is better to download the plugin fresh from the official source.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →