FileZilla File Associations Issue After Notepad Update

If you’ve been using FileZilla to edit files on a Server and have customised your file type associations, you might have encountered a frustrating issue where your text editor suddenly fails to open. This is particularly common with the default Windows Notepad, a problem that stems from recent changes Microsoft made in Windows.

The root of the issue is that Microsoft now offers two versions of Notepad, and the incorrect one tends to disrupt your FileZilla settings.

Identifying the Core Issue: The New Notepad.exe

Previously, you could instruct FileZilla to open file types like .txt, .html, and .ini in Notepad.exe without a hitch. This worked because the executable was found in a consistent location, part of Windows’ default search path (the PATH environment variable).

However, Microsoft has transitioned to a new, modern Notepad.exe that gets distributed and updated via the Microsoft Store. Unlike the classic version, which received infrequent updates alongside the main operating system, this new version receives enhancements and bug fixes much more frequently.

Understanding the Path Issue

The traditional Notepad can be found in a stable, well-known directory such as C:\Windows\System32\notepad.exe.¹

In contrast, the new, Store-installed Notepad resides in a version-specific folder structure that looks something like this:

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

Notice the lengthy string of characters, particularly the version number in the middle? Each time the Store updates Notepad (which happens quite regularly), that version number—and the entire folder path—changes. When you set an association in FileZilla or when it tries to inherit the system’s associations, it saves this intricate, version-specific path. After the update, that path becomes invalid, resulting in errors like “File not found” or “No program has been associated.”

How to Fix It: Use a Stable Editor Path

Given that the new Notepad often leads to complications, the best solution is to instruct FileZilla to use an editor with a consistent and reliable path. You have two excellent options to resolve this issue.

Option 1: Stick with the Classic Notepad

Although the new version is now the default, the classic Notepad remains available at a predictable location. To resolve the issue permanently, you can simply input this path into FileZilla.

1. Launch FileZilla and navigate to Edit > Settings…
2. Select File editing > Filetype associations.
3. For all your text file types, use the following format pointing 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) will cover any file type that lacks a more specific association.
   • The complete path ("C:\Windows\notepad.exe") is essential.
   • The %f serves as the placeholder for the file path that FileZilla relays to the editor.

Option 2: Choose a Reliable Third-Party Editor

Many developers prefer more feature-rich text editors such as Notepad++ or Visual Studio Code. These applications come with stable installation paths that rarely change, making them ideal for FileZilla associations.

1. If you’re using Notepad++, your custom associations might look like this (make sure to adjust the path according to your installation location):
   . "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 setting a static, complete path for your editor, you avoid the instability of Windows’ new Store-based applications, ensuring your FileZilla associations remain intact.