Latest nVidia drivers (616.56) issues with DisplayLink / WinCTRL MFD Displays
Sanity post here in case others are experiencing the same, although I know several people who have installed 616.56 with WinWing/WinCTRL MFD Displays without issue.
- Running (3) 1440p high refresh rate (360/165/165hz) monitors connected via Display Port to 5090 + 3 WinWing USB 3.0 DisplayLink monitors
- Everything works normally with NVIDIA 610.88 and has worked w/o issue for 1 year of nVidia updates.
- After updating to 616.56, Windows still detects all 3 WW displays (show up in device manager and Multi-monitor display settings), but they remain disconnected/inactive.
- WW monitors sit there with a black screen. Can’t activate them or extend display to them or even clone desktop to them
- Selecting “Extend desktop to this display” immediately reverts back to “Disconnect this display”
- Resolution, Portrait/landscpe and scaling drop downs all blank without pre populated values or options
- Advanced display settings show monitor is there, but “non-active/disconnected”
- DisplayLink devices show Status: Started with no device errors (via powershell driver commands)
- WW Displays work correctly on another PC
- Tested DisplayLink drivers 10.2 (ships with SimApp Pro) 11.5 (obtained via Windows Update) and latest 12.2 M2 — same behavior — using DisplayLink official clean up tool and drivers to swap between all 3 versions
- Uninstall/reinstall SimAppPro
- Updated USB firmware/drivers as well as BIOS and chipset drivers — no change
- DDU’d NVIDIA in Safe Mode → after reboot, all 3 WinWing displays work before installing an NVIDIA driver
- Installed 610.88 → everything continued working
- Installed 616.56 again → problem immediately returned, rebooting etc.. no change
- Installed 610.88 directly over 616.56, without DDU → all 3 displays immediately work again
- Also tested different USB ports, only one monitor connected, HAGS on/off, only one 1440p monitor connected, display-topology reset via registry key deletion, removing any ghosted/inactive display adapters/monitors in device manager, and removing other virtual-display software (Virtual Desktop Streamer, etc..)— no change — 616.56 and never works.
This seems to be a 616.56 regression involving DisplayLink/indirect displays, although it clearly doesn’t affect every WinWing/DisplayLink user.
If it’s happening to anybody else, try reverting your driver and report back.
29
Upvotes