Troubleshoot Issues

RoboDK may not start when using a Remote Desktop connection or if you are running RoboDK on a Virtual Machine. To solve this problem, you can start RoboDK by double clicking the file RoboDK-Safe-Start.bat located in the C:/RoboDK/ folder.

Starting RoboDK with this command solves any problems when running RoboDK using a Remote Desktop connection or a Virtual Machine.

Visit the robot connection troubleshoot section to fix issues related to the communication between your PC and the robot.