Member Avatar for bettynew

Hi,

I have been trying to get Real VNC 4 to work with the lovely Vista.
I have managed to install it and get it up and running by changing a few settings here and their.
However the only way I could get it to run at start up without Windows defender freaking out was to add it as a scheduled task at start up.

Now this is where I am stuck. At start up it throws up a batch file to start the VNC service which does not close down when it has finished starting the service.
If I close the batch file manually it also closes the VNC service.

Any ideas how I can hide this batch file or even make it close down once it has loaded up correctly?
If thats not possible, can you tell me where to find the BAT file that the task scheduler has produced so I can amend the prompt to hide it?

Cheers.

  • 1 Contributor
  • 1 Reply
  • 222 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by bettynew

Dani AI

Generated

Short version: avoid the visible startup BAT by running the VNC server as a Windows service rather than launching an interactive instance at boot. ’s follow‑up that running as Administrator and switching modes helped points to a permissions/UAC issue — installing as a service removes that dependency and will start VNC before any user logs on, with no console window left open.

How to proceed (safe, non‑destructive steps):

  • Run the VNC Server/installer with elevated rights (right‑click → Run as administrator) and choose the option to install/register the server as a Windows service (or re‑run the installer and select service install).
  • Open Services (services.msc), find the VNC service, set its Startup Type to Automatic and leave it using the Local System account so it starts at boot. This removes the need for a startup BAT or scheduled interactive launch.

If you must use Task Scheduler:

  • Point the task at the VNC server executable (or better, start the Windows service) instead of wrapping it in a visible .BAT.
  • Configure the task to “Run whether user is logged on or not” and “Run with highest privileges” so it runs hidden and bypasses UAC prompts.
  • To confirm what the task runs, open Task Scheduler Library → right‑click the task → Properties → Actions.

Service start example (replace with your actual service name):

sc start "YourVNCServiceName"

Troubleshooting notes: if closing the BAT stops VNC, the batch is launching an interactive instance (not a service). Installing as a service or starting the service with sc/net start prevents that. Also add VNC to your firewall/Defender exceptions and use strong authentication — service mode is the most robust and secure long‑term solution.

Member Avatar for bettynew

I had to run it as an aministrator and run vnc in user mode, think thats how I solved it!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.