After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095 Feedback is always welcome
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128 There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127 Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
Man I have to say I did create a setup and it went perfectly smooth still some minor tweeks to do to it but other than that I dont know how I have lived with out something so easy for support. Normally I used Crossloop, which can be a pain to get the user to download and install and etc....
But on to the question, Is there a way to create your executable locally like instead of uploading the zip file to the site?
Yes, they finally published a creator and instructions a long time ago but I don't think it's being updated. It was kind of a hassle if I remember correctly.
Edit: Here's one thread on the subject: [topic=1359][/topic]
For "single click" purposes a lot of people are using either the SCPrompt project or the ChunkVNC project, both discussed and sort-of-hosted here. Both of these are wrappers around a full UltraVNC install.
Last edited by B on 2010-08-05 16:54, edited 1 time in total.
Thanks, I tried that long process and didnt get it to work, maybe I will look at the others. I guess my only thing is putting my config online, in the converter dont know if anyone is looking at it is all.
I completely understand; that was my big reservation as well -- you're handing all your keys and IP address to a 3rd party and asking them to generate an executable for you.
I (much) later learned that a main reason they did it this way was so that the resulting executable could be code-signed, and thus less likely to cause antimalware trouble.