Pauline's community posts

Hello Rene,

Thank you for your message.

Unfortunately, we couldn't reproduce the issue - Viewer opens the Full Control and View window in the same view mode (i.e. Stretch, Fullscreen, etc.) that was set during the previous remote session.
The issue might be occurring if the Viewer configuration file was somehow corrupted by some antivirus or firewall software, or if there are some issues with writing to the configuration file.
Please, try the following:
1. Fully exit the Viewer File -> Exit.
2. Locate the file config_4.xml in the C:\Users\[Your_username]\AppData\Roaming\Remote Utilities Files\ folder.
Please note that the AppData folder might be hidden by default in which case you need to enable "Hidden files and folders" in Windows Explorer settings.
3. Remove the config_4.xml file from that folder.
This will reset the Viewer settings. Your address books won't be affected by this action. However, you will need to register your Viewer with a license key once again. To do so, please follow this tutorial.
4. Run the Viewer and see if the issue persists when connecting to a remote Host.

Please let me know if this worked for you.

Hello Dimitris,

Sorry for the inconvenience. I'll forward your additional feedback to our developers for a review - perhaps, we will be able to review this in our future updates.

Please feel free to post another message if you have other questions.

Hello Brant,

Thank you for the provided details.

Allow me to ask one more thing - after configuring connection properties for RDP and clicking the "Save" button, do you proceed with selecting the Connect button?
If this is the case, could you please try closing the RDP properties window after clicking "Save" instead of connecting to a remote Host? Then try selecting the OK button in the RU's own connection properties window - this should save the properties correctly. Please see the screenshot below:


Please let me know if this worked for you.

Hello Boris,

Thank you for the clarification.

I'll forward the issue to our development department and ask them to look into it.

I'll get back to you with an update on the issue shortly.

Hello Boris,

Thank you for the provided screenshot.

Could you please also let us know if you're still able to connect to this remote Host, despite seeing the error in the Host logs? I'll forward this to our developers and ask for their input on the issue.

Looking forward to your reply.

Hello everyone,

This is to inform you that we've fixed the issue and released an updated version with an implemented fix. Please, download the updated 7.0.0.1 version from the main download page if you haven't tried updating yet.

You can also use the Automatic update (self-update) feature to update to the 7.0.0.1 version.

We appreciate any feedback. Thank you!

Hello Michał,

Thank you for the update on this.

We'll test this out additionally with the latest 7.0.0.1 version to see if we can reproduce the issue. Sorry for the inconvenience.

I'll keep you updated on the issue.

Hello Christ,

Thank you for your message.

We'll test this out to see if we can reproduce the issue and implement a fix for it in our future updates. Sorry for the inconvenience.

I'll keep you updated on the issue.

Hello Peter,

We've received the log file and have already forwarded it to our developers, thank you!

I'll keep you updated on the issue.

Hello Wayerspork and Peter,

Thank you for your messages.

Could you please provide us the Host connection log files for examination, so we could look further into the issue? The connection logs can be located in the following folder: C:\Program Files (x86)\Remote Utilities - Host\Logs\.
You can send us the log files to support@remoteutilities.com. I'll forward the logs to our development department for further investigation. Sorry for the inconvenience.

Looking forward to your replies.