Language:

DC++ settings files guide

Unlike most of the applications DC++ does not use the Windows Registry to store its settings. Instead, most of the settings and application data are saved into individual files. Settings are stored in various files in XML format. This is a real advantage since XML files can be opened with any text editor so in case of any problems the settings are accessible outside of the program as well.

In this FAQ article you'll find all the information needed about settings files themselves, their possible locations and ways how to preserve and transfer them into another computer or Windows installation.

What are the different DC++ settings files for?

DC++ has many files in purpose of store its different kinds of application data and settings. Here's the complete list of settings files created and used by DC++:

DCPlusPlus.xml
This is the main settings file of DC++, it stores everything what you can set in the Settings dialog including the list of shared folders. Additionally it stores all the visibility settings of the GUI, size and position of columns and window splitters and the list of recently opened windows.
Favorites.xml
This file stores your favorite hubs and favorite users with all of their properties including login information and passwords.
Queue.xml
Your download queue items and their properties saved into this setting file. This file also contains information about what pieces (chunks) of the queued files have already been downloaded.
HashIndex.xml
HashData.dat
These files contain hashes for your shared and queued files. You can read more about them in this article.
ADLSearch.xml
This file stores your defined ADLSearch queries.
Users.xml
This is a temporary file for storing some user nicks to be able to display nicks correctly in the program interface when the users are offline.
Plugins.xml
This file contains the list of installed plugins and their specific settings.
Notepad.txt
This stores the contents of the Notepad window. Through this file the text can be kept across sessions.
DcppBoot.xml
This file is accessed only at startup and it stores information about where should DC++ find the rest of the settings files. It also determines the default path of the default finished and unfinished download folders.

Note that the information above is vaild for the most recent versions of DC++. Older versions may miss some files or behave otherwise.

Where can I find the settings files?

There are the three possible locations of DC++ settings files (the most probable location listed first):

  1. The DC++ subfolder of the Application Data directory of your user profile. This is the most probable location of the settings files if you used the installer (.exe) to install or upgrade your DC++. In a typical case the path is

  2. The same folder where the DC++ executable (DCPlusPlus.exe) resides. This is will be the default location of the settings files if you picked the zipped archive (portable) version from the download page.
  3. In a path relative to the folder where the DC++ executable (DCPlusPlus.exe) resides. In this case the path is manually set in dcppboot.xml.
The actual location of the files depend on the contents of the file called dcppboot.xml. This file is always located at the same folder where the DC++ executable (DCPlusPlus.exe) resides. As it mentioned earlier, dcppboot.xml can be opened with a simple text editor or viewer. Beside the settings themselves the file contains a brief explanation of the possible options and their effect. You can read more about this topic in this article.

Note that the information above is vaild for the most recent versions of DC++. Older versions may behave otherwise.

How do I move my existing settings to another installation?

In short, backup the settings files listed above, and then in the new installation, copy all of them to the same location where you've found them. If you place them to the correct location, DC++ will automatically use them. This can be done by the following easy steps:

  1. Determine the location of the settings files in your old installation the way described above.
  2. Backup the settings files you want to preserve.
  3. Install DC++ to the new operating system. Run it once so it'll create the necessary folders.
  4. Close DC++!
  5. If you used the installer (.exe) to install DC++ then place your archived settings files to the DC++ subfolder in Application Data directory of your user profile (see the exact path for your OS above). If you downloaded the zipped binary of DC++ (.zip, portable version) then place your archived settings files to the folder where you unpacked the binary. If it asks then overwrite the default files with your archived ones.
  6. Restart DC++. You're done.

Warning: do not unpack the portable (zipped) version of DC++ under the Program Files folder if you use Windows Vista or later unless you have the UAC service completely disabled. Doing so may cause loss of settings and/or unfinished downloads due to Microsoft's User Account Control Data Redirection technology.

How do I move my incomplete downloads, plugins configuration and other (temporary) data of DC++ to another installation?

To be able to continue your unfinished downloads you must copy the unfinished (.dctmp) files to the new installation. The location of these files depend on the Unfinished downloads directory settings. You must put the unfinished files to the default unfinished folder of the new DC++ installation or copy them to any folder you like and set it as a directory for Unfinished downloads in DC++ settings. Close DC++ while you copy the files!

Warning: Do not connect to hubs and start downloading before you copied the unfinshed files. This can reset some of your downloads so they'll lost their progress and will start from the beginning. In this case you have to overwrite the newly created unfinished files with the ones from the previous installation and use 'Recheck Integrity' menu command in the Download Queue to get back your progress.

There are some other data you may want to move to the new installation :

The actual location of the temporary data folder corelates with the location of settings files (described above):