Conrad Sallian's community posts

For those of you who are interested in the details of what is actually happening:
Driver Signing changes in Windows 10, version 1607

Lee, we will notify you about it in this thread. Besides, once Microsoft does its part they should update their records accordingly and this problem should be fixed.

Hello Lee,

According to Microsoft it takes them 5-7 days to re-verify our account data. We will try to speed things up and contact them too.

Hello Eddy,

Thank you for your message.

Please, check this Internet-ID connection troubleshooting guide.

Hello Armin,

Thank you for your post.

We never publish a detailed roadmap. But the most pressing priorities we are currently working on are as follows:

- Updated and improved authorization system based on TLS 1.2 (this will replace the current RSA+AES).
- 2-factor authentication for the Hosts and later for the self-hosted server as well
- Viewer for MacOSX (and possibly Linux)
- Updated and improved mobile version with a full-fledged address book.

These are just some of the things we are planning for the nearest future. There are also numerous fixes and little features that we are going to include with each update.

Hello Riz,

Please, update your Remote Utilities installations - Viewer and Host/Hosts. You can download the most recent version from here https://www.remoteutilities.com/download/

Hello Lee,

Thank you for your message.

If these are laptops the feature might indeed not work correctly due to the way the blank screen mechanism and monitor driver work in Windows 10. Unfortunately, we cannot do anything about it.

Hi Riki,

I'm sorry. Our work on the 6.9 update took quite a lot of time due to some serious improvements (specifically those that deal with security and authorization). It is soon to be released and more updates are coming this year.

Thanks.

Hello Pete,

After some investigation we found that it's not actually the driver or root drivers to blame. It's Microsoft's new policy that was put in effect after one of Windows updates. Now they require additional verification in their Dev Center (us as a vendor).

We went through all the necessary procedures and the changes we submitted are currently pending.

Hello Jack,

Thank you for letting us know about the broken link. It has been fixed now.