The file name set by the downloader is not effective

Recently, many users have encountered problems with abnormal file names, such as garbled file names, folders not created as expected, etc. This is mainly caused by the recent update of IDM extensions (IDM Integration Module). If you have installed the IDM extension, you can temporarily disable it when downloading.

Here are the detailed instructions:

The downloader detects that the file name after downloading may be abnormal. If the file name is a string of random letters and numbers, or does not use the naming rules in the downloader settings, it means that this problem has occurred.

This is not a problem with the downloader itself, but is affected by other extensions, resulting in the loss of the file name set by the downloader.

When you encounter this problem, you can consider the following solutions:

1. Recommended: You can create a new browser local user to use this downloader. For Chrome and Edge browsers, you can click the avatar icon in the upper right corner of the browser and create a new profile (no need to log in to a Google or Microsoft account). Each user has a separate browser window, so you can install this downloader for the new user and do not install other extensions. When you need to use this downloader, use this user to download to avoid being affected by other extensions.

2. You can find out which extensions are causing this problem and temporarily disable them when using this downloader. These extensions usually have the function of downloading files and managing downloads, such as: IDM Integration Module, Chrono Download Manager, mage Downloade, etc. If you are not sure which extension is causing this problem, you can disable all extensions first, then enable them one by one and use the downloader to download, so that you can find out which extension is causing this problem.

Technical details:

Some extensions listen to the chrome.downloads.onDeterminingFilename event, which can easily cause the preset file name to be lost.

Suppose this downloader sets a custom file name for a file: user/image.jpg.

If another extension listens to the onDeterminingFilename event, the browser will ask it for suggestions for the file name (giving it a chance to modify the file name). The problem is: the file name passed by the browser at this time is the default (that is, the last path in the URL), not the file name set by the downloader.

So the file name set by the downloader will be lost, and the file name will become the last path in the URL.