Fix NS_E_CURLHELPER_NOTADIRECTORY (0XC00D132D) on Windows 10/11

You're trying to open something — maybe a link in an email, a document, or a program — and Windows throws up this error: NS_E_CURLHELPER_NOTADIRECTORY (0XC00D132D). The message says "The URL is not a directory." What that actually means: Windows expected to find a folder, but it found a file or nothing at all. This usually happens with older software, custom file associations, or after moving files around. Let's fix it.

1. The registry has a bad URL protocol handler (most common fix)

This is the top cause. Some program — like an old FTP client, a media player, or a game — registered a custom URL handler (like ftp:// or custom://) in the Windows registry, and that handler points to a path that's no longer a folder. Windows tries to open the URL as if it were a directory, but it's a file path or something else. I've seen this a lot with FTP links and old Adobe software on Windows 10 and 11.

What to do:

1. Press Windows Key + R, type regedit, and click OK.
2. In the Registry Editor, go to:

   HKEY_CLASSES_ROOT\ftp\shell\open\command

   (If your error uses a different protocol, like custom, go to HKEY_CLASSES_ROOT\custom\shell\open\command instead.)
3. Look in the right pane for the (Default) value. Double-click it.
4. You'll see something like: "C:\Program Files (x86)\SomeApp\app.exe" "%1". That's a file, not a directory. That's the problem.
5. Change it to point to a folder instead. For the ftp protocol, the real fix is often to use Internet Explorer's handler:

   "C:\Program Files\Internet Explorer\iexplore.exe" -nohome

6. Click OK, close Registry Editor, and restart your PC. Try opening the URL again. After the restart, you should see your browser open the link correctly.

If you're not sure what the correct handler should be, just delete the HKEY_CLASSES_ROOT\ftp key entirely. Right-click it and choose Delete. Next time you click an FTP link, Windows will ask which app to use. That's safe and resets things.

2. A file association is pointing to a directory instead of a program

Sometimes Windows gets confused and links a file extension (like .html or .txt) to a folder command instead of a program. This happens after installing and uninstalling badly written tools. I ran into this once after removing a junk "optimizer" tool.

How to check and fix:

1. Open Settings (press Windows Key + I).
2. Go to Apps > Default apps.
3. Scroll down and click Choose default applications by file type.
4. Find the file type that matches your URL's extension (if it's an .html file, look for .html or .htm).
5. Click the current app icon next to it. If it says "Look for an app in the Store" or shows a folder icon, that's wrong. Change it to your browser (like Microsoft Edge, Chrome, or Firefox).
6. After you set it, close Settings and double-click a file of that type. It should open in the browser now, not throw the error.

3. A shortcut or link uses a broken path (rare but quick to check)

If you're clicking a shortcut or a link in a document, the target path might be writen wrong. For example, a shortcut to a folder might have a file path instead of a folder path. I saw this with a user who created a shortcut to a network drive but typed \\server\share\file.txt instead of \\server\share.

Check this:

1. Right-click the shortcut or link and select Properties.
2. In the Shortcut tab, look at the Target field.
3. If it ends with a specific file (like index.html or file.txt), change it to just the folder path. For example, change C:\Users\Public\Documents\notes.txt to C:\Users\Public\Documents.
4. Click Apply, then OK. Double-click the shortcut. It should open the folder now.

If the link is in a document (like a Word file), try copying the URL and pasting it into a browser's address bar. If that works, the document itself has a broken link. You'd need to fix the link in the document's source.

Quick-reference summary