SOLVED: Permanent Fix For FileZilla File Associations Failing After Notepad Updates

If you use FileZilla to edit files on a server and have set up custom file type associations, you’ve likely hit the wall where, one day, they all suddenly fail to open your text editor. This is especially true if you are trying to use the default Windows Notepad, and it’s all thanks to a change Microsoft made in Windows.

The short answer is that Microsoft has created two Notepads, and the wrong one keeps breaking your FileZilla settings.

The Core Problem: The New, Awesome But Ever Changing Notepad.exe

You used to be able to tell FileZilla that .txt, .html, and .ini files should open with Notepad.exe, and it worked fine. This was because the executable was in a stable location that was part of Windows’ default search path (the PATH environment variable).

Then, Microsoft moved to a new, modern Notepad.exe that is distributed and updated via the Microsoft Store. This new version gets new features and bug fixes much more frequently than the classic version, which rarely updated with the main operating system.

The Path Problem

The classic Notepad lives in a stable, known location like C:\Windows\System32\notepad.exe.¹

The new, Store-updated Notepad, however, is installed in a version-specific, non-static folder structure, something like this:

C:\Program Files\WindowsApps\ Microsoft.WindowsNotepad_**11.2508.34.0**_x64__8wekyb3d8bbwe\Notepad\Notepad.exe

Notice that long string of numbers and letters, especially the version number in the middle? When the Store updates Notepad (which is often), that version number changes, and the entire folder path changes with it.

When you use FileZilla to set an association, or when FileZilla tries to inherit the system’s association, it saves that full, long, version-specific path. The next time Notepad updates, that path no longer exists, and FileZilla throws an error like “File not found” or “No program has been associated.”

The Fix: Use a Static, Stable Editor Path

Since the new, frequently updated Notepad is an ongoing source of frustration, the solution is to force FileZilla to use an editor with a stable, unchanging path. You have two excellent options.

Option 1: Force the Classic, Stable Notepad

While the new version is the user-facing default, the classic, stable Notepad is not officially deprecated and still exists in a predictable location. You can simply hard-code this path into FileZilla to solve the problem permanently.

1. Open FileZilla and go to Edit > Settings…
2. Select File editing > Filetype associations.
3. For all your text-based file types, use the following format, which points to the classic Notepad executable:
   . "C:\Windows\notepad.exe" %f
html "C:\Windows\notepad.exe" %f
txt "C:\Windows\notepad.exe" %f
ini "C:\Windows\notepad.exe" %f
   • Using . (dot) covers any file type that doesn’t have a more specific association
   • The full path ("C:\Windows\notepad.exe") is critical
   • The %f is the placeholder for the file path that FileZilla is passing to the editor

Option 2: Switch to a Reliable 3rd Party Editor

Most developers use a more feature-rich, dedicated text editor like Notepad++ or Visual Studio Code. These programs have stable installation paths that almost never change, making them ideal for FileZilla associations.

1. If you use Notepad++, your custom associations would look like this (adjust the path if you installed it elsewhere):
   . "C:\Program Files\Notepad++\notepad++.exe" %f
html "C:\Program Files\Notepad++\notepad++.exe" %f
txt "C:\Program Files\Notepad++\notepad++.exe" %f
php "C:\Program Files\Notepad++\notepad++.exe" %f

By explicitly setting a static, full path for your editor, you bypass the unstable nature of Windows’ new Store-based applications and ensure your FileZilla associations never break again.