After Installing Version 2.8.63.0
getting error
Source : Application Error
Message : Faulting application name: tvnserver.exe, version: 2.8.63.0, time stamp: 0x6110f829
Faulting module name: tvnserver.exe, version: 2.8.63.0, time stamp: 0x6110f829
Exception code: 0xc0000005
Fault offset: 0x000000000002496d
Faulting process id: 0x1458
Faulting application start time: 0x01d7b35929fae6e1
Faulting application path: C:\Program Files\TightVNC\tvnserver.exe
Faulting module path: C:\Program Files\TightVNC\tvnserver.exe
Report Id: 87f8a0bb-79a6-40c4-8cb5-a9fb4ca15157
Faulting package full name:
Faulting package-relative application ID:
EventID : 1000
Edition Windows 10 Pro
Version 21H1
Installed on 4/16/2021
OS build 19043.1202
Experience Windows Feature Experience Pack 120.2212.3530.0
Hi!
Could you look for crash.dmp file in C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\TightVNC folder?
I have the same problem. Just checked, there is no TightVNC directory in the location you suggested.
This error is happening on a machine I'm connecting to. It does not seem to affect its availability for connections, nor does it terminate any existing connections. I just happened to look at the Event Log for other reasons and I saw the application failure.
The viewer is 2.8.59 on the machine I'm connecting from.
Do you have a server running as a service or as an application?
"TightVNC Server" is running as a service.
BTW, another bug happened to me today: I connected to a machine and all it displayed was a black screen. The user on the other side said he saw the cursor move. The only thing that fixed it was booting the remote computer. Sorry, this is a different problem but thought I might as well mention it.
Hi,
I have the same problem (Version 2.8.63.0, installed as service only).
One thing, maybe it's can help : the service seem crash and restart when I access to remote control (one report by access).
Strange ...
Last edit: Benoit 2022-06-01
I noticed this on a Windows 11 setup when looking into a Chrome Update issue. This is a freshly [re]installed system. I've installed the following:
I found this VNC error when I started looking into events in hopes Chrome was logging some connectivity issue preventing updates.
I also don't have TightVNC folder as mentioned above:
Here's a copy of one of the errors.
This doesn't actually manifest in any usability issue. I'm able to vnc into the machine and sustain connections for days.
I wonder if this is just a result of some coding debugging that made it into production. Since it doesn't cause usability issues, I would consider this fixed if the logging level was set to warning or info.
TightVNC server is running as a service. Automatic and Running.
I haven't made any action to attempt to remedy this. I'm at your service to run any tests or provide info that might help.
The only test I'm considering now is to run older versions of TVNC to see if they generate the errors also.
Last edit: Andy Mills 2022-09-03
Hello,
Same error when running TightVNC Server as a service under Windows 10 Pro 22H2. Despite the error it is still possible to vnc into the remote machine ...
This error doesn't occur under Windows 7.
Last edit: Philippe Rossignol 2023-01-23
I have the same problem (my friend on their computer actually, that I connect to). Just noticed today when looking at the reliability report for other reasons. Fairly new computer updated to Windows 11.
The error is the same as everyons elses with this relevant data:
Here is three hours of the log file from today when the machine was rebooted. There are numerous error messages, which I do not understand, but some are serious enough to say they must stop the program. The reliability report says the program stops multiple times a day but then apparently restarts (it is running as a service, the service, I presume does not itself stop). These crashes starting in December last year have lowered the "reliability assessment" from 10/10 to 1/10 for this machine.
Sorry, don't know how to make this into a scrollable box on this system, I haven't used it before:
Last edit: BaxterBear 2023-01-28
помогло создание папки TightVNC по пути C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\
Last edit: Maslakov Kirill 2023-02-08