Win 11 issues
dave madsen <[email protected]> Sun, 14 Sep 2025 15:34:13 -0500
| Newsgroups | gmane.network.tight-vnc.general |
|---|---|
| Message-ID | <CAJ+e7EQdhREkNdAmKw=UOw=EC_UAZ7Qen5_hZES+qCKh=7pd9w@mail.gmail.com> |
--===============1355467884257615559== Content-Type: multipart/alternative; boundary="00000000000010efb2063ec8d00a" --00000000000010efb2063ec8d00a Content-Type: text/plain; charset="UTF-8" We have been using TightVNC for years on Win 10. It has generally worked well. After installing a Windows 11 system, Windows 10 clients don't seem to work well with it. This has happened for most Windows 11 systems we've installed. Many times, the windows 10 client connects to the remote machine, but the screen remains black. No cursor, nothing. None of the available controls seem to do anything. The MSP can use ScreenConnect to connect to the remote system and it works fine. I have tried using ultra VNC and real VNC to connect to Windows 11 using tight VNC server. That seems to work better, although not always. In the past, there were instances when connecting to a Windows 10 remote machine would give that same scenario, but it was pretty rare. I believe I've seen complaints in the past on this list about it. I would really really like to stick with tight VNC. Do you have any suggestions on what I should do? Is there any debugging information I can get that may shed light on this? --00000000000010efb2063ec8d00a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">We have been using TightVNC for years on Win 10.=C2=A0 It= has generally worked well.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"au= to">After installing a Windows 11 system, Windows 10 clients don't seem= to work well with it. This has happened for most Windows 11 systems we'= ;ve installed.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Man= y times, the windows 10 client connects to the remote machine, but the scre= en remains black. No cursor, nothing. None of the available controls seem t= o do anything.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">The= MSP can use ScreenConnect to connect to the remote system and it works fin= e.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I have tried using ul= tra VNC and real VNC to connect to Windows 11 using tight VNC server.=C2=A0= That seems to work better, although not always.=C2=A0</div><div dir=3D"aut= o"><br></div><div dir=3D"auto">In the past, there were instances when conne= cting to a Windows 10 remote machine would give that same scenario, but it = was pretty rare. I believe I've seen complaints in the past on this lis= t about it.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I woul= d really really like to stick with tight VNC.</div><div dir=3D"auto"><br></= div><div dir=3D"auto">Do you have any suggestions on what I should do?=C2= =A0 Is there any debugging information I can get that may shed light on thi= s?=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div></div= > --00000000000010efb2063ec8d00a-- --===============1355467884257615559== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1355467884257615559== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________ TightVNC mailing list, [email protected] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list --===============1355467884257615559==--