After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome

Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031

Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.2.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38083
Feedback is welcome

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

VNC can't work as service.

Here you will find help for frequently asked questions as well as for your specific question
Post Reply
tobias2121
Posts: 1
Joined: 2023-10-31 10:44

VNC can't work as service.

Post by tobias2121 »

I've been trying to solve this for a long time. I have never had any problems with my company's PCs that work with windows UVNC, but there is one in particular that, when installed, is not able to work with service mode. Of course I am checking the appropriate installation checks, with all possible permissions used during the installation. I can force it to work correctly using the following ps1 script, but when I restart the PC what I did is lost:

$process = Get-Process -name winvnc -ErrorAction SilentlyContinue

if ($process) {
Stop-Process -Name winvnc -Force -ErrorAction SilentlyContinue
}

Start-Sleep -Seconds 5

Start-Process -FilePath "C:\Program Files (x86)\UltraVNC\winvnc.exe" -ArgumentList "-kill" -NoNewWindow -Wait
Start-Process -FilePath "C:\Program Files (x86)\UltraVNC\winvnc.exe" -ArgumentList "-service_run" -NoNewWindow

When I reboot, it never starts in service mode, and I have to activate it manually. I have tried 1000 things, versions, ways to install and nothing works. The service is configured as autostart as well.
Thesus
Posts: 3
Joined: 2023-08-17 14:26

Re: VNC can't work as service.

Post by Thesus »

Its easy via powershell

"C:\\Program Files\\uvnc bvba\\UltraVNC\\winvnc.exe" -install

Set-Service -Name uvnc_service -StartupType Automatic
Start-Service -Name uvnc_service

reboot
Post Reply