support

Forum Navigation
Please or Register to create posts and topics.

"Connected – Display Off" bug after Nvidia driver update 616.56 (RTX 5060 Ti)

Hello,
I am having a persistent “Connected – Display Off” issue on my primary PC after I updated my graphics card drivers.
My PC Specs:
  • GPU: Nvidia RTX 5060 Ti 16GB
  • OS: Windows 11
  • Viewer device: Samsung Tab S10 FE, Samsung Galaxy A56
The Problem:
When I connect my viewer app to the PC, it connects successfully but immediately says “Connected – Display Off” and the screen stays black. This started happening right after the GPU driver update.
What I have already tried:
  1. Reinstalled Spacedesk to the latest version (v2.2.30+).
  2. Turned OFF Nvidia In-Game Overlay in the Nvidia App / GeForce Experience.
  3. Opened Device Manager (with hidden devices shown), and uninstalled all gray/hidden “Generic Monitor” items.
  4. Used “Clear Windows Display Settings” in the Spacedesk Driver Console to reset the display database.
  5. Changed my main PC monitor refresh rate down to 60Hz.
  6. Changed the Encoding Type to “Software Encoding (forced)” on both PC and Viewer.
  7. Uninstalled “Spacedesk Graphics Adapter” from Device Manager and restarted the PC to let it reinstall clean.
Unfortunately, none of these steps fixed the problem. The display is still not showing up in Windows Display Settings and stays disconnected.
I have collected the diagnostic logs using DebugView as requested in other threads. Here is google drive link
Could you please help me find what is blocking the virtual display? Thank you!

Hi @kacper-6,

Please refer to the sticky post below:
Connected – Display Off Issue After Nvidia Driver update to 616.56 (RTX 5070)

Does yesterday’s driver update (version 616.64) resolve the issue?

Quote from Grassini on 04/09/2026, 14:24

Does yesterday’s driver update (version 616.64) resolve the issue?

Not for me. I’ve tried both the August and September Nvidia Game Driver updates and both produce the same effect. Reverting to the July version restored the programme to work properly.

 

 

Excuse me for using a translator. With driver version 616.64, it’s working perfectly again for me.

What graphics card do you have? Can anyone else confirm this?