When connecting to WIN11 PC via TightVNC it freezes on logon to remote computer and have to disconnect and reconnect.

Welcome to Microsoft Q&A!

Thank you for providing the details.

Based on your description, this behavior is commonly related to how TightVNC interacts with the Windows 11 logon and desktop initialization process. During the initial sign-in, Windows is still loading the user profile, display driver, and desktop session. In some cases, TightVNC may not refresh the display or input state correctly after the logon transition, causing the remote session to appear frozen. Once you disconnect and reconnect, the desktop session has fully initialized, allowing the connection to function normally.

Similar issues have been reported on Windows 11, particularly after feature updates, where VNC sessions become unresponsive, display a frozen screen, or require a reconnect after logon or unlock. The possible causes include:

• Compatibility issues between TightVNC and the current Windows 11 build.
• Graphics driver or display adapter initialization delays.
• Problems during the Windows lock screen to desktop session transition.
• Third-party security software interfering with desktop capture.
• Windows updates affecting remote display handling.

I would like to recommend troubleshooting steps:

1. Ensure you are running the latest version of TightVNC.
2. Update the graphics driver directly from the hardware manufacturer's website.
3. Perform a clean boot to determine whether a third-party application or service is causing the issue.
4. Verify whether the behavior started after a specific Windows update or feature upgrade.
5. Test with an alternative remote access solution, such as Remote Desktop, UltraVNC, or RealVNC, to determine whether the issue is specific to TightVNC.

If the issue occurs only with TightVNC and only during the initial logon, it is generally indicative of a VNC display refresh or compatibility issue rather than a problem with Windows authentication or the user profile itself.

I hope this helps clarify the issue. If you find this information helpful, please click Accept Answer. 

Thank you for bringing your concern to Microsoft Q&A.