I've tried to download the source code quite a few times, waiting a few days, using a different browser, etc., but it always downloads, without reporting problems, as zero bytes. I doubt that I will attempt to make any modification so this doesn't matter to me, but thought I should report it. As nobody else has reported this, it might be something I am doing wrong; but don't bother to spend time on this. Best wishes.

One more viewer crash with DSM Plugin (0xc0000005 @ SecureVNCPlugin64.dsm): https://app.box.com/s/skyqrbl83lgks37favy7dr1p450z3f8i(v1.2.0.9u1 x64 viewer @ Win8.1 x64 __connecting to__ v1.2.1.0test1 x64 server @ Win8.1 x64)The crash happened after initiating windows reboot of the server machine (using uvnc session) -> viewer began trying to reconnect automatically (starting with "reconnect (3)" in the title-bar)...then it seemed to be stuck at "reconnect (1)". Waited a while after the login screen appeared on the (booted) server machine, but the viewer was still stuck...then I clicked on the "refresh screen" button in the viewer button-bar => viewer crashed immediately.(Have not tried to repeat this crash - just wanted to leave the crashdump here...maybe there is an unhandled exception anywhere - or something like that - and perhaps time will tell the root of it.)

Just wondering if this has been fixed in the lastest? I'll install and try if there is a patch????

As per babas3216 comment:

bababa3216 wrote:If I disable the system hook dll, the artifacts go away but the performance is much worse.แบล็คแจ็คออนไลน์

and my previous post

ultrVNCFan wrote:I noticed Dborth's issue from 1.2.0.8 is still happening. I haven't re-attached his/her screen shot from their original post.

Here's their post:

I've been trying this version out (server) and it seems to be working great! Except for one problem...I'm using Windows Server 2012 R2 with the "system hookdll" enabled and see some black artifacts on screen updates when moving windows around. If I disable the system hook dll, the artifacts go away but the performance is much worse. Here's a picture, you can see the RDP on the left is fine and the VNC connection isn't updating properly.

vncviewer.exe 1.2.0.9 constantly crashes at start on my WinXP SP3 32-bit at offset 0009dd9e with error: "vncviewer.exe has encountered a problem and needs to close."vncviewer.exe 1.2.0.6 runs fine on the same PC.

Running into a problem with using the ultravnc server and ultravnc sc that I need help with. I am trying to set up both the ability to do a reverse connection to a vncviewer in listen mode on a Linux system. In the past, this has worked but it no longer works from a Windows 10 system. For ultravnc sc I have tried both the experimental version for Windows 10 and the earlier Feb 2015 versions. Looking at the output from the vncviewer I can see that I do get the start of the vnc session going but then it hangs after announcing the version number of the RFB protocol that is being used. "Server supports RFB protocol version 3.8"

The vncviewer is based on the TigerVNC (XVnc). FWIW I can successfully do reverse connections using the TightVNC server on a Windows 10 system, so I know this is not a firewall issue. (port 5500 is open on the Linux system) But what I am really after is to use the ultravnc sc in order to provide helpdesk support for Windows 10 users, and I strongly suspect that the problem exists with both the ultravnc server (add clients) and with the ultravnc sc built in server.

Any ideas why I cannot do these reverse connections? Thanks in advance