Issue is fixed!
Updating to latest NVIDIA driver 616.92 fixed it!
NVIDIA driver 616.56 broke virtual/indirect display creation, and 616.64 inherited that regression — which killed the DisplayLink monitor, since a DisplayLink display is a virtual display.
Updating to 616.92 fixed it, and NVIDIA's release notes name the bug explicitly: "virtual displays could not be created after updating to driver 616.56."
|