Publishers

ToDesk ToDesk





How to uninstall ToDesk from your system

This web page contains thorough information on how to remove ToDesk for Windows. It was coded for Windows by ToDesk Remote Desktop. More information on ToDesk Remote Desktop can be seen here. Usually the ToDesk program is placed in the C:\Program Files\ToDesk folder, depending on the user's option during setup. The full command line for removing ToDesk is C:\Program Files\ToDesk\uninst.exe. Keep in mind that if you will type this command in Start / Run Note you may get a notification for administrator rights. The application's main executable file has a size of 45.84 MB (48064272 bytes) on disk and is called ToDesk.exe.

ToDesk is comprised of the following executables which take 48.61 MB (50969624 bytes) on disk:

  • CrashReport.exe (665.39 KB)
  • ToDesk.exe (45.84 MB)
  • uninst.exe (1.96 MB)
  • devcon.exe (81.50 KB)


This web page is about ToDesk version 4.7.0.2 only. You can find below info on other application versions of ToDesk:

...click to view all...
Following the uninstall process, the application leaves some files behind on the PC. Part_A few of these are shown below.

Folders remaining:
  • C:\Program Files (x86)\ToDesk
  • C:\Users\%user%\AppData\Local\ToDesk

The files below were left behind on your disk when you remove ToDesk:
  • C:\Program Files (x86)\ToDesk\config.ini
  • C:\Program Files (x86)\ToDesk\CrashReport.exe
  • C:\Program Files (x86)\ToDesk\drivers\tdgamepad\devcon.exe
  • C:\Program Files (x86)\ToDesk\drivers\tdgamepad\tdgamepad.cat
  • C:\Program Files (x86)\ToDesk\drivers\tdgamepad\TdGamePad.inf
  • C:\Program Files (x86)\ToDesk\drivers\tdgamepad\TdGamepad.sys
  • C:\Program Files (x86)\ToDesk\drivers\tdscreen\devcon.exe
  • C:\Program Files (x86)\ToDesk\drivers\tdscreen\tdidd.cat
  • C:\Program Files (x86)\ToDesk\drivers\tdscreen\tdIdd.dll
  • C:\Program Files (x86)\ToDesk\drivers\tdscreen\tdIdd.inf
  • C:\Program Files (x86)\ToDesk\ImageResources\2021060160b5c8a59082e.jpeg
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_05_12.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_05_13.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_06_01.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\client_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\clientphqghume_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\clientphqghume_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\clientphqghume_2023_08_04.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclient_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclient_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclient_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclient_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclientaylnlfdx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclientaylnlfdx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkclientaylnlfdx_2023_08_04.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkservice_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkservice_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkservice_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkservice_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_08_04.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_09_03.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_09_08.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_09_14.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_11_16.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_11_29.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdkserviceaylnlfdx_2023_12_19.log
  • C:\Program Files (x86)\ToDesk\Logs\sdksession_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sdksessionaylnlfdx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sdksessionaylnlfdx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_05_12.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_05_13.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\service_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\servicephqghume_2024_01_04.log
  • C:\Program Files (x86)\ToDesk\Logs\session_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\session_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\session_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\sessionphqghume_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\sessionphqghume_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_05_12.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_05_13.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_06_01.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclient_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclientfircvscx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclientfircvscx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcclientfircvscx_2023_08_04.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_05_12.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_05_13.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2022_12_03.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservice_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_08_04.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_09_03.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_09_08.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_09_14.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_11_16.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_11_29.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_12_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcservicefircvscx_2023_12_19.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsession_2022_05_06.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsession_2022_05_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsession_2022_10_02.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_09.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_09_1.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_09_2.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_09_3.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_10.log
  • C:\Program Files (x86)\ToDesk\Logs\zrtcsessionfircvscx_2023_06_10_1.log

Many times the following registry data will not be cleaned:
  • HKEY_CLASSES_ROOT\ToDesk
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ToDesk
  • HKEY_LOCAL_MACHINE\Software\ToDesk
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ToDesk_Service

Use regedit.exe to delete the following additional values from the Windows Registry:
  • HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\ToDesk\ToDesk.exe.ApplicationCompany
  • HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\Program Files (x86)\ToDesk\ToDesk.exe.FriendlyAppName
  • HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\TOOLS2\setup_Todesk.exe.ApplicationCompany
  • HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\MuiCache\C:\TOOLS2\setup_Todesk.exe.FriendlyAppName
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\bam\State\UserSettings\S-1-5-21-2416077194-4199072041-2086853048-500\\Device\HarddiskVolume7\Program Files (x86)\ToDesk\ToDesk.exe
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ToDesk_Service\Description
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ToDesk_Service\Dir
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ToDesk_Service\DisplayName
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ToDesk_Service\ImagePath


A way to uninstall ToDesk from your PC with Advanced Uninstaller PRO

ToDesk is an application offered by ToDesk Remote Desktop. Sometimes, computer users decide to erase it. This can be easier said than done because deleting this manually requires some skill related to Windows program uninstallation. The best QUICK practice to erase ToDesk is to use Advanced Uninstaller PRO. Here is how to do this:





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

DOWNLOAD NOW

  • visit Download Link
  • download the program by pressing the DOWNLOAD button
  • set up Advanced Uninstaller PRO
2. Start Advanced Uninstaller PRO. Take some time to admire Advanced Uninstaller PRO's design and wealth of features available. Advanced Uninstaller PRO is a very useful package of utilities.

3. Click on the General Tools category
Go to General Tools


4. Press the Uninstall Programs tool
Go to Uninstall Programs


5. All the applications existing on your computer will be shown to you

6. Scroll the list of applications until you locate ToDesk or simply activate the Search field and type in "ToDesk". If it exists on your system the ToDesk application will be found automatically. When you click ToDesk in the list , some information regarding the application is made available to you:


  • Safety rating (in the left lower corner). This explains the opinion other users have regarding ToDesk, from "Highly recommended" to "Very dangerous".
  • Opinions by other users - Click on the Read reviews button.
  • Details regarding the program you wish to remove, by pressing the Properties button.
7. Press the Uninstall button. A window asking you to confirm will show up. accept the removal by clicking the Uninstall button. Advanced Uninstaller PRO will then uninstall ToDesk.
Uninstall ToDesk


8. After removing ToDesk, Advanced Uninstaller PRO will offer to run an additional cleanup. Press Next to proceed with the cleanup. All the items that belong ToDesk which have been left behind will be found and you will be asked if you want to delete them. By uninstalling ToDesk with Advanced Uninstaller PRO, you can be sure that no registry entries, files or directories are left behind on your computer.

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



Disclaimer

The text above is not a recommendation to remove ToDesk by ToDesk Remote Desktop from your computer, we are not saying that ToDesk by ToDesk Remote Desktop is not a good application. This page simply contains detailed instructions on how to remove ToDesk supposing you want to. The information above contains registry and disk entries that our application Advanced Uninstaller PRO discovered and classified as "leftovers" on other users' PCs.

2023-06-22 / Written by Daniel Statescu for Advanced Uninstaller PRO

follow @DanielStatescu
Last update on: 2023-06-22 01:35:04.987