FlylinkDC++ r503-x64 build 19663

A guide to uninstall FlylinkDC++ r503-x64 build 19663 from your PC

This page is about FlylinkDC++ r503-x64 build 19663 for Windows. Here you can find details on how to remove it from your computer. It is made by FlylinkDC++ Team. Open here where you can get more info on FlylinkDC++ Team. You can read more about on FlylinkDC++ r503-x64 build 19663 at http://flylinkdc.blogspot.com. The application is frequently installed in the C:\Program Files\FlylinkDC++_x64 directory (same installation drive as Windows). The full command line for removing FlylinkDC++ r503-x64 build 19663 is C:\Program Files\FlylinkDC++_x64\unins000.exe. Keep in mind that if you will type this command in Start / Run Note you might be prompted for administrator rights. FlylinkDC_x64.exe is the programs's main file and it takes close to 11.82 MB (12389904 bytes) on disk.

FlylinkDC++ r503-x64 build 19663 is composed of the following executables which take 13.74 MB (14406256 bytes) on disk:

• FlylinkDC_x64.exe (11.82 MB)
• sendrpt-x64.exe (773.58 KB)
• unins000.exe (1.17 MB)

The current web page applies to FlylinkDC++ r503-x64 build 19663 version 7.7.503.19663 only. When planning to uninstall FlylinkDC++ r503-x64 build 19663 you should check if the following data is left behind on your PC.

Folders that were found:

• C:\Program Files\FlylinkDC++_x64
• C:\Users\%user%\AppData\Local\FlylinkDC++
• C:\Users\%user%\AppData\Roaming\FlylinkDC++

The files below are left behind on your disk by FlylinkDC++ r503-x64 build 19663 when you uninstall it:

• C:\Program Files\FlylinkDC++_x64\Settings\ADLSearch.xml
• C:\Program Files\FlylinkDC++_x64\Settings\CustomLocations.bmp
• C:\Program Files\FlylinkDC++_x64\Settings\CustomLocations.ini
• C:\Program Files\FlylinkDC++_x64\Settings\DCPlusPlus.xml
• C:\Program Files\FlylinkDC++_x64\Settings\Favorites.xml
• C:\Program Files\FlylinkDC++_x64\Settings\GeoIPCountryWhois.csv
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2016 - giugno\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2016 - giugno\dchub___international.dchub.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2016 - giugno\dchub___socialnet.dchub.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___dc.rutrack.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-01\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___dc.rutrack.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___dcraft.sytes.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___mezciems.no-ip.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___mir.feardc.net_1209.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___piter.feardc.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-03\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___aab-new-adrenalin.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___artcool.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___dc.rutrack.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___dcraft.sytes.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___mezciems.no-ip.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___mir.feardc.net_1209.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___piknik-dc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___piter.feardc.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-04\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___aab-new-adrenalin.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___artcool.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___dcraft.sytes.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___mezciems.no-ip.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___piknik-dc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-05\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___aab-new-adrenalin.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___artcool.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___dcraft.sytes.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___mezciems.no-ip.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___piknik-dc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-06\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___aab-new-adrenalin.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___allavtovo.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___artcool.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___dcraft.sytes.net.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___hub.odvinsk.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___kjirsiishi.sytes.net_7.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___kuums.lv.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___mezciems.no-ip.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___novosibirsk-forever.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___ozerki.hubdc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___piknik-dc.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-07\dchub___tsdhub.info.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___aab-new-adrenalin.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___a-galaxy.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___artcool.org.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___dc.filimania.com.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___dc.fly-server.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___dc.milenahub.ru.log
• C:\Program Files\FlylinkDC++_x64\Settings\Logs\2018-08\dchub___dcraft.sytes.net.log

Registry keys:

• HKEY_CURRENT_USER\Software\FlylinkDC++
• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\FlylinkDC++ x64_is1

Supplementary registry values that are not cleaned:

• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\program files\flylinkdc++_x64\flylinkdc-x64.exe.ApplicationCompany
• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\program files\flylinkdc++_x64\flylinkdc-x64.exe.FriendlyAppName
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\TCP Query User{D591560D-155E-41D5-834C-5315026304A1}C:\program files\flylinkdc++_x64\flylinkdc-x64.exe
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\UDP Query User{12511D77-15A7-4D25-8716-1CE5BA28669D}C:\program files\flylinkdc++_x64\flylinkdc-x64.exe

How to erase FlylinkDC++ r503-x64 build 19663 from your PC using Advanced Uninstaller PRO

FlylinkDC++ r503-x64 build 19663 is an application released by the software company FlylinkDC++ Team. Frequently, computer users choose to uninstall this program. Sometimes this can be troublesome because doing this by hand takes some experience regarding removing Windows applications by hand. One of the best QUICK approach to uninstall FlylinkDC++ r503-x64 build 19663 is to use Advanced Uninstaller PRO. Take the following steps on how to do this:





1. If you don't have Advanced Uninstaller PRO on your PC, add it. This is a good step because Advanced Uninstaller PRO is an efficient uninstaller and all around utility to maximize the performance of your system.

DOWNLOAD NOW

• navigate to Download Link
• download the program by clicking on the green DOWNLOAD NOW button
• set up Advanced Uninstaller PRO

2. Run Advanced Uninstaller PRO. It's recommended to take some time to get familiar with Advanced Uninstaller PRO's interface and wealth of functions available. Advanced Uninstaller PRO is a very good Windows tool.

3. Press the General Tools category


4. Activate the Uninstall Programs tool


5. A list of the programs existing on your PC will appear

6. Scroll the list of programs until you find FlylinkDC++ r503-x64 build 19663 or simply activate the Search field and type in "FlylinkDC++ r503-x64 build 19663". The FlylinkDC++ r503-x64 build 19663 application will be found automatically. Notice that when you click FlylinkDC++ r503-x64 build 19663 in the list , the following data regarding the application is available to you:

• Safety rating (in the lower left corner). This tells you the opinion other people have regarding FlylinkDC++ r503-x64 build 19663, ranging from "Highly recommended" to "Very dangerous".
• Reviews by other people - Press the Read reviews button.
• Technical information regarding the program you want to uninstall, by clicking on the Properties button.

For example you can see that for FlylinkDC++ r503-x64 build 19663:

• The web site of the application is: http://flylinkdc.blogspot.com
• The uninstall string is: C:\Program Files\FlylinkDC++_x64\unins000.exe

7. Press the Uninstall button. A confirmation window will show up. Confirm the uninstall by clicking Uninstall. Advanced Uninstaller PRO will remove FlylinkDC++ r503-x64 build 19663.


8. After uninstalling FlylinkDC++ r503-x64 build 19663, Advanced Uninstaller PRO will offer to run a cleanup. Click Next to go ahead with the cleanup. All the items of FlylinkDC++ r503-x64 build 19663 that have been left behind will be detected and you will be able to delete them. By removing FlylinkDC++ r503-x64 build 19663 with Advanced Uninstaller PRO, you can be sure that no Windows registry items, files or directories are left behind on your computer.

Your Windows computer will remain clean, speedy and able to take on new tasks.

Geographical user distribution

Disclaimer

The text above is not a piece of advice to uninstall FlylinkDC++ r503-x64 build 19663 by FlylinkDC++ Team from your computer, nor are we saying that FlylinkDC++ r503-x64 build 19663 by FlylinkDC++ Team is not a good application for your computer. This text only contains detailed info on how to uninstall FlylinkDC++ r503-x64 build 19663 in case you decide this is what you want to do. The information above contains registry and disk entries that our application Advanced Uninstaller PRO discovered and classified as "leftovers" on other users' computers.