Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

TightVNC install stopped working

epickett

November 14, 2017 15:52

For some weird reason, my TightVNC install stopped working recently(Nope, I didn't change anything). I've tried version 2.7.10(which I've been using) and also version 2.8. The install times out after an hour. It used to install in about 5 minutes. Is there a logfile somewhere that can tell me where/why it hangs? This is starting to tick me off...

Other installs work fine, so it isn't credentials/antivirus/firewalls/etc...

Thanks for any assistance.

Comments

3 comments

Steve Eller
November 15, 2017 21:14

Same here. I had 2.8.8.0 running on about 20 machines. All but a few recently stopped working. The "tvnserver" service is not running and doesn't even show up in the list of Services. I tried running the package again from Deploy. It sucessfully deploys all 14 steps, but still no running service and no connection.

0
epickett
November 17, 2017 00:13

I think we have/had different problems. I could no longer INSTALL the program through PDQ Deploy. This is all in an effort to remotely uninstall the old version and install the new version. So, I figured out the install. After 3 times deleting and re-creating the install, it worked. Now I have to figure out how to UNinstall through PDQDeploy using the free version...

0
Stephen Valdinger
November 17, 2017 14:51
A command step with this:
```
MsiExec.exe /qn /norestart /X{DEE0B752-52D8-4615-9BEE-1EDA46628960}
```
should do the trick. Make sure you get that GUID right. This will help you. Run this powershell command on a machine with TightVNC installed.
```
Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\**\' | Where { $_.Displayname -eq 'TightVNC' } | Select-Object -Expand PSChildName
```
The GUID returned will be the GUID you want to sub-in on that MSIExec step I listed first.
0