Where Does TightVNC Store Settings?
Where TightVNC keeps settings in the registry and .vnc connection files.
Last updated
TightVNC splits settings: global server options live in the registry under its TightVNC keys, while per-connection files save as .vnc wherever you put them. Passwords encode into the registry entries.
Viewer and server share the pattern with separate keys. Back up both halves for migrations; fresh installs generate defaults that overwrite imports when merged carelessly.
Where TightVNC stores this, by platform
HKLM\SOFTWARE\TightVNC\Server
Global settings and encoded passwords in registry keys. Per-connection .vnc files live wherever saved. Export keys plus files for full migrations.
Frequently asked questions
How do I back up TightVNC completely?
Export the TightVNC registry keys plus any saved .vnc files. Passwords store encoded in the registry, so the export carries them where .vnc files alone do not.
Registry or .vnc files: which holds connections?
Save connection files as .vnc anywhere convenient; they hold host, port and options per server. The registry keeps global server settings while .vnc files keep per-connection ones.
Notice an outdated path? Let us know.