Skip to content
TroubleGrid

Virtual display stops working after the NVIDIA 616.56 driver

Last verified September 2026Tested against GeForce Game Ready Driver 616.56 (released 26 August 2026), GeForce Game Ready Driver 616.64 (released 3 September 2026), GeForce Hotfix Driver 616.86 (released 4 September 2026) — first carried the fix, now superseded, GeForce Game Ready Driver 616.92 (released 9 September 2026) — contains the fix, WHQL, Windows 10, Windows 11Well documented

NVIDIA's 616.56 driver broke virtual display creation on Windows, which is what headless game-streaming hosts like Sunshine, Apollo and Artemis rely on. The fix is now in a normal WHQL driver: Game Ready 616.92, released 9 September 2026, lists the virtual display regression under its fixed bugs. Update to it and the beta hotfix 616.86 is no longer needed. 616.64 does not fix it, and a 610.74 rollback remains the route two independent reporters confirmed if you cannot update.

Start here

  1. Confirm which driver you are actually on
  2. Update to Game Ready driver 616.92 or later
  3. Get streaming again tonight by mirroring a physical monitor

This is a driver regression, not a misconfiguration of your streaming host. If your setup worked last week and stopped the day you updated your NVIDIA driver, nothing in Sunshine, Apollo or Moonlight needs changing — the virtual display never gets created for them to use. NVIDIA has acknowledged the bug by name and shipped a fix outside its normal WHQL release, which is the clearest signal available that this is on the driver side.

Symptoms

  • The virtual display is not created at all, so the streaming host has nothing to stream
  • Moonlight connects and then drops with a black screen or no video from the host
  • Windows display settings are stuck on "Show only on Display 1" and will not switch to extended
  • Apollo or Artemis can only mirror the primary monitor instead of using its own display
  • The host refuses to start when the physical monitor is powered off
  • Host logs show "Display helper IPC: timed out" or "failed to apply display configuration"
  • It began the day you installed NVIDIA driver 616.56 or 616.64

Why this happens

The 616.56 driver regressed virtual display creation

NVIDIA's own hotfix notes name this directly: "Fixed an issue where virtual displays could not be created after updating to driver 616.56". Virtual display drivers such as IddSampleDriver and the Virtual Display Driver project create an indirect display that Windows must then accept and activate. Under 616.56 that step fails, so the display either never appears or appears and cannot be activated. Because the failure is below the streaming host, no setting inside Sunshine, Apollo or Moonlight can work around it.

Update to Game Ready driver 616.92 or later · Roll back to driver 610.74 with DDU

Windows will not move off "Show only on Display 1"

One reporter describes a narrower shape of the same failure: the virtual display exists but Windows refuses to change the projection mode away from showing only the primary display, which leaves the host mirroring the physical monitor rather than driving its own. That is why a headless setup breaks hardest — with the physical monitor off there is nothing left to mirror, and the host will not start.

Get streaming again tonight by mirroring a physical monitor · Roll back to driver 610.74 with DDU

Fixes

Confirm which driver you are actually on

about 2 min

This regression belongs to 616.56 and 616.64 only. If you are on 616.92 or later the fix is already installed and something else is wrong.

Applies to: Windows 10, Windows 11

  1. Open a terminal and read the driver version straight from the GPU:
    nvidia-smi --query-gpu=driver_version --format=csv,noheader
  2. If you prefer a GUI, open NVIDIA Control Panel, then Help > System Information, and read the Driver version field.
  3. If it reports 616.56 or 616.64, carry on — you are on an affected driver. If it reports 616.86 you have the beta hotfix, and 616.92 or later already contains the fix in a WHQL driver. If it reports 610.x or earlier, this regression is not what is affecting you.

Confirmed by the vendor.

Source: NVIDIA, ClassicOldSong/Apollo, Nonary/vibeshine, NVIDIA

Update to Game Ready driver 616.92 or later

about 15 min

This is the fix, now in a WHQL driver rather than a beta hotfix. NVIDIA lists this exact bug number among the issues 616.92 resolves.

Applies to: Windows 10, Windows 11

  1. Open the NVIDIA App and check for driver updates, or download Game Ready 616.92 or later from NVIDIA directly.
  2. Install it and restart.
  3. Start your streaming host and confirm the virtual display is created.
  4. If you were running the 616.86 hotfix, moving to 616.92 is the tidy end state — NVIDIA discontinues a hotfix once its fixes reach an official release.

Confirmed by the vendor.

Source: NVIDIA, NVIDIA

Get streaming again tonight by mirroring a physical monitor

about 5 min

A stopgap, not a fix. It restores a usable stream while you decide about the driver, but only if a real monitor is attached and powered on.

Applies to: Setups with a physical monitor attached to the host

  1. Leave a physical monitor connected and switched on at the host.
  2. In the streaming host, stop asking it to create or switch to a virtual display, and let it capture the primary display instead.
  3. Connect from Moonlight as normal. You will get the host's real desktop at the physical monitor's resolution rather than the resolution you asked for.

Reported to work by one user; not confirmed by the vendor.

Source: ClassicOldSong/Apollo

Roll back to driver 610.74 with DDU

Advancedabout 30 min

The route both independent reporters actually took and confirmed. Now a fallback rather than a recommendation: since 616.92 carries the fix, choose this only if you cannot move to that driver.

Applies to: Windows 10, Windows 11

Before you do this

DDU removes the display driver completely, and the screen will drop to a basic low resolution until you install a replacement. Do not start this over a remote session — you may lose the display you are working through. Download the 610.74 installer before you begin, and expect Windows Update to try to push a newer driver back afterwards.

First:

  • Download the NVIDIA 610.74 installer before removing the current driver
  • Have physical access to the machine, not only a remote session
  • Pause Windows Update so it does not reinstall 616.x automatically
  1. Download the 610.74 installer from NVIDIA's driver archive first, before you remove anything. Once the current driver is gone you will be on a basic display adapter.
  2. Download Display Driver Uninstaller (DDU) from its official Wagnardsoft page.
  3. Disconnect from the internet or pause Windows Update, so Windows does not silently reinstall the driver you just removed.
  4. Run DDU and choose Clean and restart, with GPU / NVIDIA selected.
  5. After the restart, install 610.74 and reboot again.
  6. Start the streaming host and confirm the virtual display is created.

Reported to work by 2 users; not confirmed by the vendor.

Source: ClassicOldSong/Apollo, Nonary/vibeshine

Known issues

  • NVIDIA first shipped the fix in Hotfix Display Driver 616.86 on 4 September 2026, and it reached a WHQL driver on 9 September 2026: the release notes for Game Ready 616.92 list "Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]" under Fixed General Bugs. Virtual displays no longer appear anywhere in that driver's open issues. Game Ready 616.64 never contained the fix.

    Affects 616.56, 616.64 · Status: fixed

  • The community issue threads that first reported this — Apollo #1567 and vibeshine #268 — were both still open when re-checked on 10 September 2026, each with only its original reporter and no maintainer response. Neither contains a report confirming that 616.86 or 616.92 resolves it. So the fix is documented by NVIDIA in a WHQL release but not yet independently confirmed in the field by the people who reported the break.

    Affects 616.56, 616.64, 616.92 · Status: unknown

If none of this worked

If the virtual display is created fine but the picture flashes dark or white, that is a different 616.56 bug — see our article on the 616.56 flickering and dark flashes, which has its own fix. If your virtual display never worked, rather than working until a driver update, the driver is probably not the cause: check that the virtual display driver itself (IddSampleDriver or Virtual Display Driver) is installed and enabled in Device Manager, since reports of Moonlight failing on a virtual display go back well before this driver existed. And if Moonlight drops the connection while the host's own screen shows the game running normally, look at the network path and the host's encoder settings before touching the driver at all.

Common questions

Do I still need the 616.86 hotfix?
No. Game Ready 616.92, released 9 September 2026, lists this bug among the issues it fixes, so the fix is now in a WHQL driver. NVIDIA discontinues a hotfix once its fixes are incorporated into an official release, so if you installed 616.86 the tidy end state is to move to 616.92 or later.
Does this affect Sunshine as well as Apollo?
The reports we verified name Apollo/Artemis and vibeshine, which is a Sunshine fork. We did not find a confirmed report on upstream Sunshine itself. The failure is in Windows virtual display creation, below any of these hosts, so there is no reason to expect one host to escape it — but we are telling you what we actually saw rather than what seems likely.
Is 616.64 safe to stay on?
Not for this problem. 616.64 shipped on 3 September 2026, a week after the regression, and NVIDIA still had to put the virtual display fix in a hotfix the following day. Updating from 616.56 to 616.64 will not bring your virtual display back — you need 616.92 or later.
Why roll back to 610.74 specifically?
Because that is the version both reporters actually returned to and confirmed working. Other pre-616 drivers may well work too; we have not verified them, so we are not going to list versions we have not seen anyone test. Rolling back is now the fallback rather than the recommendation, since 616.92 carries the fix.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • GeForce Hotfix Display Driver version 616.86Official

    NVIDIA · Support page · checked Sep 21, 2026

    • NVIDIA lists "Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]" among the three issues Hotfix 616.86 addresses
    • Hotfix Display Driver 616.86 was released on 4 September 2026
    • Hotfix 616.86 is based on Game Ready Driver 616.64
    • NVIDIA describes its hotfix drivers as beta, optional and provided as-is, produced through a much abbreviated QA process
    • NVIDIA states that the safest option is to wait for the next WHQL certified driver
    • NVIDIA distributes hotfix drivers only through its Customer Care support site
    • The hotfix will be discontinued once its fixes are incorporated into the next official driver release
    • Hotfix 616.86 also fixes RDP sessions displaying a black screen after updating to driver 616.56 [6687328]
  • Release 615 Driver for Windows, Version 616.92 — Release Notes (RN-08399-616.92_v01)Official

    NVIDIA · Release notes · checked Sep 21, 2026

    • Game Ready driver 616.92, released 9 September 2026, lists "Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]" under Fixed General Bugs, putting the fix in a WHQL driver for the first time.
    • 616.92 also fixes the intermittent browser flicker [6673430] and the Remote Desktop black screen [6687328] that 616.56 introduced.
    • The Open Issues list for 616.92 does not mention virtual displays, so NVIDIA considers this regression closed as of that release.
    • Re-checked on 21 September 2026: 616.92 remains the newest Game Ready driver, and its Open Issues list still names only the "Prefer Maximum Performance" power mode [6007998], the Assassin's Creed Shadows crash [6685219] and the Judgement / Virtua Fighter 5 launch failure [6681537] — not virtual displays.
  • NVIDIA Releases GeForce Hotfix Driver 616.86 to Fix Browser Flickering, Broken Virtual Displays, and RDP Black ScreensReputable

    The FPS Review · News · checked Sep 21, 2026

    • Independent reporting on 8 September 2026 describes the hotfix as addressing virtual displays failing to be created after driver 616.56
    • Confirms Hotfix 616.86 is based on Game Ready Driver 616.64
  • Issue with new Nvidia driver. #1567Community report

    ClassicOldSong/Apollo · GitHub issue · checked Sep 21, 2026

    • A user reports that after updating to NVIDIA 616.56 the Windows display mode cannot be moved off "Show only on Display 1", so Apollo and Artemis can only mirror the primary display
    • The same user reports the host fails to start when the primary monitor is turned off
    • The user resolved it by removing the driver with DDU and reinstalling 610.74
    • The report is from a Windows 11 machine with an RTX 5080
    • The issue was opened on 27 August 2026 and was still open, with no replies, when re-checked on 21 September 2026
  • Nvidia's New 616.56 Driver #268Community report

    Nonary/vibeshine · GitHub issue · checked Sep 21, 2026

    • A second, unrelated user reports the virtual display producing a black screen or crashing after installing NVIDIA 616.56
    • Their logs record "Display helper IPC: timed out" and "failed to apply display configuration"
    • Downgrading to driver 610.74 resolved the problem for them
    • The issue was opened on 26 August 2026 and was still open, with no replies, when re-checked on 21 September 2026
NVIDIA 616.56 broke virtual displays: the fix | TroubleGrid