Search the Community

When attempting to update the RELAY G10 or TBP516G transmitter using Windows, some users have reported that the device either does not establish a connection via USB, or loses the connection during the update. It is worth noting that Windows supplies the driver for these Relay devices. There are two scenarios where the Relay device is not recognized by the updater app after connecting via USB: the updater is launched before the Relay device drivers have finished installing. This may occur more often on slower computers, computers that already have several open windows or processes, or with machines that have a slower internet connection. the "Driver not successfully installed" message appears. In this case, click "Change settings" then choose "Yes, do this automatically (recommended)" in the Device Installation Settings dialogue box, then select "Save Changes". In the event the "Driver not installed" message box is not present, you can navigate to Device Installation Settings using the following steps: Click Start, type "devices and printers" in the search box, and then click Devices and Printers. Under Devices, right-click the icon for the computer, and then click Device installation settings. Choose "Yes, do this automatically (recommended)" and select "Save Changes" button. After changing this setting, remove the USB cable, then insert it again so that Windows can detect the Relay device and install the driver for it. It is possible to see the Relay device update fail shortly after it starts. This can occur if one of the Relay device drivers has not finished installing before you initiate an update. In this case, the updater will typically display that the firmware version is unknown. The workaround here is to wait until the driver completes installation, or disconnect the USB cable, reconnect it, then start the update again. Lastly, it is worth noting that some USB cables are charge-only, so a change in cables may help. Also, trying all ports and even a different computer may resolve the issue, based on various USB port configurations.