UltraVNC

Rudi De Vos wrote: ↑2025-03-12 19:22 I guess the plugin is still wrinting in the current folder instead of the ProgramData.

Which would be correct. Actually %ProgramData% is for data and not program/code files. So I believe storing plugins, DLLs or similar data there is not the intended use.

service will be changed like this %programdata%\UltraVNC\ultravnc.ini but when you install it with another name sample: "myvnc_service" %programdata%\UltraVNC\myvnc_service.ini is used When not found it fallback to current folder This should do the trick for multiple installed services Yes I think ...

There are 2 different cases: Multiple apps This can be solved using winvnc.exe -config filename (filename need to entered c:\xxx\yyy\abc.ini) Multiple service In this case we could use the "special_service_name" without the need to add extra parameters, a service is unique %programdata%UltraVNC ...

Mutiple services registerd: Is this how the multple instances are used, not manual starting several servers with the -multi option? In my case I do have a use-case where I do create a dedicated "Support" service which is configured to use a reverse connection to allow connections from behind NAT ...

@SkyBeam: In this special case, I have proposed to Rudi, a new command line feature "-portable" to force ultravnc.ini in the same UltraVNC Server folder. Important, since several years, Microsoft rules are to have not setting/log files in "Program Files" or "Program Files (x86)": %ProgramData ...

Can de path to ultravnc.ini be adjusted? E.g. by command-line parameter?

Reason I am asking for is that I am running multiple VNC configurations in multiple folders. Up to now it was easy to separate the configuration as it was reading ultravnc.ini from the program folder.

I also noticed some issue. Mainly I faced issues with the secure plugin in UltraVNC 64-bit installer. It includes SecureVNCPlugin.dsm with a size of bout 1.3MB from 17.11.2019. It might not even be 64-bit. Weirdly the 32-bit installer includes SecureVNCPlugin.dsm which is sized 2.2MB and build on 19 ...

Checking if i can't add a run once, then on reboot the old uac is also reset. You would have to create a scheduled task with SYSTEM privileges or a service. RunOnce is runing in login-user context (which might not have admin privileges). Another idea: If SC is crashing and cannot revert UAC then ...

I did some tests with this version and so far I did not come across blocking issues for me. One potential bug I spotted: The sharing indicator frame around shared screen is not shown even when enabled in admin settings. OSD seems to work however if I enable to show notification as OSD. But the frame ...

In addition you might want to check your DNS configuration. You were referring to a server machine. Those should usually not only have a forward-DNS but also a reverse-DNS entry. Even DHCP clients can have an automatic reverse-DNS (PTR) entry in corporate environments. If the configured DNS server ...

You can configure UVNC server to lock the workstation on disconnect. So it locks automatically. If you want to lock without disconnect you might just press Win+R or select "Run" from start menü or paste the following into the search box of start menu or on the command prompt: Rundll32.exe user32.dll, ...

Quick feedback:
Version 1.4.0.8 worked in all my tests:

• Repeater connection
• Direct connection
• Build-in authentication
• MSLOGON2 authentication
• Notification messages
• UAC prompts (in al my tests the server was running as service)

Rudi De Vos wrote: ↑2023-01-11 18:58 1.4.0.4 links

Thank you!
I did a quick test and did not discover any issues.

SkyBeam If you set notification ON and you provide a local or remote text it crash ? OS server I do specify the message remotely (in clieent) and the server is configured to show a notification if there is one provided by the client. Server OS: Windows 10 22H2 64-bit. EDIT: IT's WORKING! As I read ...

Unfortunately I have to report it's still crashing for me on every single connect when NOTIFICATION=1 is used in INI. Changing it to NOTIFICATION=0 is the only way to get a connection. It needs to be related to the notification message. I am also able to connect if notification is enabled but set to ...

Do you have long hostnames ? Well, the hostname (exclude domainname) of the compute I have used for esting is 14 characters long. Not sure whey this should have triggered the bug. But I was connecting via repeater and also submitting a notification message (which ideed is of course longer). I will ...

I think I have nailed it down. My INI containing Notification=1 When set to Notification=0 It does not crash. Another thing I noticed during testing is that the second WinVNC.exe process is taking about 50% CPU time for quite some time. Not sure what it's doing there. These things might be less ...

Alright. It might be just me then... Here is a quick dump of my unfiltered ini: [admin] UseRegistry=0 MSLogonRequired=0 NewMSLogon=1 DebugMode=0 Avilog=0 DebugLevel=8 DisableTrayIcon=0 LoopbackOnly=0 UseDSMPlugin=1 AllowLoopback=1 AuthRequired=1 ConnectPriority=0 DSMPlugin=SecureVNCPlugin64.dsm ...

Will there be an announcement once it is ready? Or at least, will you let us know here? Don't worry. I am quite sure there will be updated release candidates here and if common understanding is that the release is stable and good to be released it will also be put up to official download pages. So ...

Does that mean it is not yet approved as final official release ,or is it just an administrative thing you have not yet done? Version 1.4.x is not yet ready for release. It initially was planned to include some cloud-connect feature but this turns out to require some more fine-tuning. Instead Rudi ...

First of all many thanks for having a look. I hope you enjoyed your vacation. Just out of curiosity... Where do you actually still get machines which are 32-bit only and which (supported) OS do you run on them? Is there any other reason to still run any 32-bit applications? Sadly I have to report ...

No worries, enjoy your holiday!

I did also rollback to 1.4.0 and this version also included the issue. WinVNC.exe seems to crash on loading of the secureVNC plugin and cycling.
I did not find a workaround and rolled back to version 1.3.8.2.

Notification seems to be a hard nut to crack. Was working, need to check the merging. Parameter replaced, seems to work now. Unfortunately this release does not work for me at all. The service is running but I am totally unable to do any successful authentication, neither via mslogon2 nor via built ...

Hey Rudi Thanks a lot for the release and all your work you are putting in. I did some tests and I can confirm that most of the things seem to work. Basically the same level as version 1.3.8.2. Still I found the Notification on connect feature to be broken for me. The message is never displayed on ...

Just note my feedback above was about dev5 already, not dev4.

It's pretty simple to begin with: Download latest installer Install "Server" component on the PC you would like to remotely control Install "Viewer" component on the PC you would like to use to control the remote PC Connect to "Server" machine by starting Viewer on the "Viewer" PC and connecting to ...

Thanks for your support and development. I did not actually test backwards compatibility but I can do this later. Since the service was running as normal I would have expected it to work normally. I will also test the connection message via traditional repeater (which was broken in latest 1.3.8 ...

I did actually do some tests with 1.3.9 dev 5. It did not go very well. There seem to be lots of logic and state issues: I did run UVNC as service, the system tray icon does appear (if enabled in options). OK. Right-click on the menu and selecting cloud connect opens the cloud connect dialog. OK ...

I just did some tests. I could not run it as service. Winvnc.exe processes (2x) are running but no tray icon shown. Therefore no possibility to initiate cloud connect. Running as service does actually work (despite the missing tray icon). But due to the missing icon I could not open the cloud ...