We'd love to hear your response and we will working hard to fix them. Please don't hesitate to email us to if you encountered any issues on the new version. According to the security researchers, Ultraview removal might be tricky as the program cannot be simply detected in the Control Panel. We're still receiving reports about bugs and issues on this version. Ultraview is a remote administration tool which can collect logins and passwords, monitor desktop activity, read and send emails, and perform other potentially dangerous activity. You can re-download the latest vesion UltraViewer 5.1.1 at this link and re-install it : "To enable it to run on startup, you have to run it as Admin, but when you do it, the first time you look for this option, the checkbox is disabled, then you close the Settings window and open it again and then this option is enabled." With two shakes of an HDMI cable Id be back in dual-LCD business. Some option disabled on the first time open UltraViewer. Well, no problem, one of my monitors supports HDMI, and the laptop has an HDMI output. and you may receive this error when you start UltraViewer: Cannot start UltraViewer controller - Err5(5)ģ.
MULTI MONITORS WITH ULTRAVIEWER WINDOWS
When you start the Windows with auto-startup mode on, UltraViewer may not auto-start all time.
![multi monitors with ultraviewer multi monitors with ultraviewer](https://alternative.me/media/512/ultraviewer-thumbnail-vwi2q60ym0p4498m-c.png)
![multi monitors with ultraviewer multi monitors with ultraviewer](https://64.media.tumblr.com/e3589987e9669e3e8ad99456a45e7e17/7c16a4258ad1f977-6e/s400x600/c721dce4870d2a9a9d1fa520aaadef75b6df3728.png)
![multi monitors with ultraviewer multi monitors with ultraviewer](https://alternative.me/media/1280/chrome-remote-desktop-screenshot-ttjqd6gb8mbmkz4x.png)
UltraViewer doesn't auto-start every time on Windows 10. UltraViewer may show an error message or auto exit after network disconnected.Ģ. UltraViewer exit after network disconnected. We've worked hard to fix these bugs, and it seems to work fine now, here is what we've fixed:ġ. A few days ago, after released version 5.1.0, we received some reports from our users about the issues on version 5.1.0.