I have a Windows 10 computer running Remote Utilities 184.108.40.206. When I connect to the host computer, also Windows 10, using voice chat with a handheld microphone connected to the viewer computer, no sound comes out of the host computer. This setup works fine fr om the same viewer computer to two other host computers running Windows 10. What should I be looking for on the Host computer wh ere this doesn’t work? Should I uninstall and reinstall the Host program? Thanks.
Before we proceed to further troubleshooting, could you please try updating your Remote Utilities to the latest version of Remote Utilities - as of this writing, it's 220.127.116.11. The latest releases contain a lot of improvements and bug fixes, so the issue you're experiencing might have already been fixed in these updates.
The 18.104.22.168 version is available for the download on this page. When updating Remote Utilities, please make sure to update both Host/Agent and Viewer as the version mismatch might lead to performance issues and some features not working.
Please let us know if the issue persists even after updating both Host and Viewer to the 22.214.171.124 version.
Hello Polina, Thank you for your reply. Since the 126.96.36.199 version is a Beta version I am hesitant to install it. I am our only tech support if something goes wrong, and I am not a computer wiz. The Beta version says it is known to contain defects, so that has me concerned. I did install the most current released version, 188.8.131.52, on the host and viewer and the problem remained. I noticed the current Beta version has been around for a while. If it is indeed very stable that would put my mind more at ease. Thank you.
Please note that despite its name, the Beta version is still a fully functional release as it only contains bug fixes and improvements for the previous Remote Utilities versions. A full list of Release notes is available here.
Alternatively, you can also try using a non-installable Agent and Portable Viewer of the latest 6.12 Beta 2 version first, to see if the issue persists when using the most recent version. We always recommend that our users try updating to the most recent update available as the issue might have already been fixed in the release.