BxDTO

How to uninstall BxDTO from your computer

BxDTO is a computer program. This page contains details on how to remove it from your PC. It was coded for Windows by Bitrix, Inc. Go over here for more info on Bitrix, Inc. BxDTO is commonly set up in the C:\Program Files (x86)\BxDTO directory, regulated by the user's option. You can remove BxDTO by clicking on the Start menu of Windows and pasting the command line MsiExec.exe /I{40AD14E4-22F2-4B65-99E8-B775C6D6991A}. Keep in mind that you might be prompted for administrator rights. BxDTO.exe is the programs's main file and it takes approximately 3.87 MB (4060600 bytes) on disk.

The executable files below are part of BxDTO. They take about 3.87 MB (4060600 bytes) on disk.

• BxDTO.exe (3.87 MB)

The information on this page is only about version 1.1.9 of BxDTO. For more BxDTO versions please click below:

• 2.0.9
• 1.0.34

If you are manually uninstalling BxDTO we advise you to check if the following data is left behind on your PC.

Folders left behind when you uninstall BxDTO:

• C:\Program Files (x86)\BxDTO

The files below remain on your disk by BxDTO when you uninstall it:

• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-console-l1-2-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-file-l1-2-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-file-l2-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-localization-l1-2-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-processthreads-l1-1-1.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-synch-l1-2-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-core-timezone-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-convert-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-environment-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-filesystem-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-heap-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-locale-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-math-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-runtime-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-stdio-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-string-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-time-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\api-ms-win-crt-utility-l1-1-0.dll
• C:\Program Files (x86)\BxDTO\bin\BxDTO.exe
• C:\Program Files (x86)\BxDTO\bin\BxDTO-from-svc старое.bat
• C:\Program Files (x86)\BxDTO\bin\BxDTO-from-svc.bat
• C:\Program Files (x86)\BxDTO\bin\bxdto-svc.log
• C:\Program Files (x86)\BxDTO\bin\db\documents.db3
• C:\Program Files (x86)\BxDTO\bin\fptr.dll
• C:\Program Files (x86)\BxDTO\bin\fptr10.dll
• C:\Program Files (x86)\BxDTO\bin\gui_engine.dll
• C:\Program Files (x86)\BxDTO\bin\libgcc_s_dw2-1.dll
• C:\Program Files (x86)\BxDTO\bin\libgcc_s_sjlj-1.dll
• C:\Program Files (x86)\BxDTO\bin\libstdc++-6.dll
• C:\Program Files (x86)\BxDTO\bin\libwinpthread-1.dll
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-49-24_dispatcher_Fprint22_3932.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-49-24_worker_Fprint22_3592.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-51-06_dispatcher_Fprint22_2772.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-51-06_worker_Fprint22_956.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-59-24_dispatcher_ATOL30_3288.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_16-59-24_worker_ATOL30_1540.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_17-35-21_dispatcher_ATOL30_3796.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_17-35-21_worker_ATOL30_4920.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_17-41-34_dispatcher_ATOL30_4784.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_17-41-34_worker_ATOL30_3260.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-06_19-56-13_dispatcher_ATOL30_4784.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_09-33-12_dispatcher_ATOL30_1288.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_09-33-12_worker_ATOL30_3800.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_10-01-44_dispatcher_ATOL30_3488.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_10-01-44_worker_ATOL30_3256.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_14-18-35_dispatcher_ATOL30_2396.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_14-18-35_worker_ATOL30_876.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_14-59-09_dispatcher_ATOL30_3588.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_14-59-09_worker_ATOL30_3804.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-18-43_dispatcher_ATOL30_2584.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-18-43_worker_ATOL30_2588.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-29-21_dispatcher_ATOL30_3276.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-29-21_worker_ATOL30_3272.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-34-02_dispatcher_ATOL30_3288.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-34-02_worker_ATOL30_3952.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-37-20_dispatcher_ATOL30_3836.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-37-20_worker_ATOL30_2512.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-42-26_dispatcher_Fprint22_1652.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-42-26_worker_Fprint22_236.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-43-06_dispatcher_Fprint22_2812.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-43-06_worker_Fprint22_2016.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-43-24_dispatcher_ATOL30_1888.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-43-24_worker_ATOL30_3036.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-59-51_dispatcher_ATOL30_1316.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-07_15-59-51_worker_ATOL30_3624.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-08_05-07-14_dispatcher_ATOL30_3276.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-08_05-40-54_dispatcher_ATOL30_1316.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-08_09-45-11_worker_ATOL30_3624.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-08_18-47-53_dispatcher_ATOL30_3276.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-08_19-20-20_dispatcher_ATOL30_1316.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_03-34-23_worker_ATOL30_3624.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_08-30-25_dispatcher_ATOL30_3276.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_09-02-47_dispatcher_ATOL30_1316.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_21-20-30_worker_ATOL30_3624.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_22-08-34_dispatcher_ATOL30_3276.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-09_22-40-26_dispatcher_ATOL30_1316.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-10_14-21-48_dispatcher_ATOL30_4068.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-10_14-21-48_worker_ATOL30_4060.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-10_14-27-18_dispatcher_ATOL30_1524.log
• C:\Program Files (x86)\BxDTO\bin\log\2025-02-10_14-27-18_worker_ATOL30_2136.log
• C:\Program Files (x86)\BxDTO\bin\mingwm10.dll
• C:\Program Files (x86)\BxDTO\bin\msvcp140.dll
• C:\Program Files (x86)\BxDTO\bin\msvcp140_1.dll
• C:\Program Files (x86)\BxDTO\bin\msvcp140_2.dll
• C:\Program Files (x86)\BxDTO\bin\msvcp140_codecvt_ids.dll
• C:\Program Files (x86)\BxDTO\bin\platforms\qt_ru.qm
• C:\Program Files (x86)\BxDTO\bin\Qt5Network.dll
• C:\Program Files (x86)\BxDTO\bin\QtCore4.dll
• C:\Program Files (x86)\BxDTO\bin\QtGui4.dll
• C:\Program Files (x86)\BxDTO\bin\QtNetwork4.dll
• C:\Program Files (x86)\BxDTO\bin\QtXml4.dll
• C:\Program Files (x86)\BxDTO\bin\ucrtbase.dll
• C:\Program Files (x86)\BxDTO\bin\vcruntime140.dll
• C:\Users\%user%\AppData\Roaming\Microsoft\Windows\Recent\bxdto-svc.lnk

Registry keys:

• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{40AD14E4-22F2-4B65-99E8-B775C6D6991A}
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BxDTO-svc

Additional values that you should delete:

• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\BxDTO\bin\BxDTO.exe
• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\BxDTO\bin\BxDTO-svc.exe
• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\BxDTO\bin\BxDTO-svc-config.exe
• HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\BxDTO\bin\BxDTO-svc-control.exe
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BxDTO-svc\DisplayName
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BxDTO-svc\ImagePath

How to delete BxDTO using Advanced Uninstaller PRO

BxDTO is a program marketed by Bitrix, Inc. Frequently, users try to uninstall this application. This can be hard because doing this by hand requires some knowledge regarding removing Windows applications by hand. One of the best QUICK action to uninstall BxDTO is to use Advanced Uninstaller PRO. Take the following steps on how to do this:





1. If you don't have Advanced Uninstaller PRO already installed on your Windows PC, add it. This is good because Advanced Uninstaller PRO is the best uninstaller and general tool to maximize the performance of your Windows system.

DOWNLOAD NOW

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

2. Start Advanced Uninstaller PRO. It's recommended to take some time to admire Advanced Uninstaller PRO's interface and wealth of functions available. Advanced Uninstaller PRO is a very useful program.

3. Click on the General Tools button


4. Activate the Uninstall Programs feature


5. A list of the applications existing on the computer will be made available to you

6. Scroll the list of applications until you locate BxDTO or simply activate the Search field and type in "BxDTO". If it is installed on your PC the BxDTO application will be found very quickly. Notice that after you click BxDTO in the list of programs, the following information regarding the program is shown to you:

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

7. Press the Uninstall button. A confirmation window will show up. accept the uninstall by pressing Uninstall. Advanced Uninstaller PRO will uninstall BxDTO.


8. After removing BxDTO, Advanced Uninstaller PRO will offer to run a cleanup. Press Next to proceed with the cleanup. All the items that belong BxDTO that have been left behind will be detected and you will be able to delete them. By removing BxDTO using Advanced Uninstaller PRO, you are assured that no Windows registry entries, files or directories are left behind on your computer.

Your Windows PC will remain clean, speedy and able to serve you properly.

Disclaimer

The text above is not a piece of advice to remove BxDTO by Bitrix, Inc from your computer, we are not saying that BxDTO by Bitrix, Inc is not a good software application. This page only contains detailed info on how to remove BxDTO supposing you decide this is what you want to do. The information above contains registry and disk entries that other software left behind and Advanced Uninstaller PRO stumbled upon and classified as "leftovers" on other users' PCs.