Apollo Virtual Display Not Working | Fast Fix Checklist

Apollo’s Virtual Display is built for game streaming setups where you want a clean, client-matched screen that only exists while you stream. When it breaks, it can feel random: no new monitor appears, the stream mirrors your main screen, apps open on the wrong display, or the client shows a black image.

This guide is for the Apollo Sunshine fork that works with Artemis or Moonlight clients on Windows hosts. In that setup, Apollo creates a SudoVDA virtual monitor when a stream starts, then removes it when the streamed app quits. If you never see that add/remove behavior, the fix is almost always driver, Windows display mode, or a cached monitor layout.

Apollo Virtual Display Not Working

If you searched “apollo virtual display not working,” start by matching the symptom to the fastest first move. Many problems look different but share the same root cause: Windows still thinks your client display is a mirrored copy, a stale layout is pinned, or the virtual display driver is not active.

What You See	What It Usually Means	First Fix To Try
No new monitor appears during a stream	SudoVDA driver missing, blocked, or replaced	Check SudoVDA install, then reinstall Apollo driver
Client shows the same screen as the main monitor	Windows set the new display to mirror mode	Use Win + P, switch to Extend, restart the streamed app
App launches on your physical screen, not the virtual one	Display state file or advanced device config is pinning the layout	Remove display_device.state, then disable physical display while streaming
Virtual display is black at 4K on Android TV	Cached layout from a different client resolution is stuck	Clear display cache, then reset Windows monitor config
Resolution no longer matches the client request	Rotation or old monitor config entries are interfering	Remove rotation, then clear GraphicsDrivers monitor cache
Virtual display becomes primary and stays that way	Advanced device configuration is set to force primary	Change device config, then set your preferred primary in Windows

Work top to bottom. Each section below includes a short set of steps, then a deeper reset if the first pass doesn’t stick.

How Apollo Virtual Display Works On Windows

Apollo uses SudoVDA to add a virtual monitor that behaves like a normal Plug and Play display. The monitor is created when a stream starts and removed when the app quits, so you should see it appear and disappear in Windows Display settings or Device Manager during a session.

Apollo also assigns a fixed identity per client device, so Windows can remember layouts for each client and reapply them next time. That’s great when it’s clean, and it’s also why a single bad layout can follow you until you clear the cache.

If you’ve used other virtual display tools, dummy plugs, or persistent “headless” adapters, take note. Mixing multiple virtual display solutions can confuse Windows and leave old devices active, which blocks Apollo from creating the virtual display when it needs to.

Fix No Virtual Display Added

When nothing shows up, treat it like a driver path problem first. Apollo’s documentation warns that if you do not see a virtual display added or removed during stream start and stop, the usual cause is driver misconfiguration or another persistent virtual display still active.

Confirm The Driver And Remove Conflicts

1. Open Device Manager — Expand Display adapters and Monitors, then look for a SudoVDA virtual display device while a stream is active.
2. Unplug Other Virtual Displays — Remove or disable other virtual display drivers and tools, then reboot so Windows drops stale devices.
3. Reinstall The Apollo Driver — Run the Apollo installer again, include the SudoVDA driver option, then restart Windows.

Sanity Check The Create Remove Behavior

• Start A Stream — Begin a session from Artemis or Moonlight and watch Windows Display settings for a new display to appear.
• Quit The Streamed App — Exit the game or app, then confirm the virtual display disappears after the app quits.

If the virtual display never appears, stop here and focus on the driver. If it appears but stays mirrored or acts odd, jump to the next sections.

Fix Mirrored Or Duplicated Screens

A new external display often comes up in mirror mode on first use. That can make the virtual display look “stuck” on the same image as your main screen, but the driver is fine.

1. Press Win + P — Pick Extend so Windows treats the virtual display as a separate screen.
2. Exit The Streamed App — Close the app you launched, not only the stream, so Windows saves the change.
3. Launch Again — Start the app again from your client and recheck the layout.

You only need this once per new client display identity. If mirror mode keeps coming back, the cached layout is likely dirty, so use the cache reset steps later in this guide.

Fix Apps Launching On The Physical Display

This is the classic “virtual display exists, but apps ignore it” problem. Windows decides where a window opens based on your display layout, the current primary display, and any stored state from earlier sessions. Apollo’s FAQ lists two clean paths: clear the display state file and let Windows manage the physical monitor, or use an advanced device setting that makes the virtual display primary.

Option One Let Windows Manage The Physical Display

1. Disable Advanced Config — Turn off advanced display device settings in Apollo if you do not need custom physical display resolution.
2. Quit Apollo — Close Apollo fully so it releases display state files.
3. Delete display_device.state — In the Apollo folder, remove the file if it exists, then start Apollo again.
4. Disable The Physical Monitor — While streaming, open Windows Display settings and disable the physical display you don’t want active.

Once Windows learns that layout, it can reuse it next time. If your goal is a “screen off” experience, Apollo’s FAQ also notes that after the first virtual display stream you can disable the physical monitor once, and future sessions can turn it off automatically.

Option Two Make The Virtual Display Primary

This path can fix stubborn launch placement, yet it can also mess up your monitor layout if you flip settings back and forth. Use it when the first option fails.

1. Open Apollo Audio Video — Go to the Audio/Video tab in Apollo.
2. Set Device Configuration — Choose “Activate the display automatically and make it a primary display.”
3. Set Preferred Display — In the app profile, set Preferred display to None or Auto.
4. Test A Launch — Start the app from the client and check if it opens on the virtual display.

If the primary display switches in a way you don’t want, Apollo’s FAQ suggests setting device configuration to Disabled, Verify that display is enabled, or Activate the display automatically, then picking your preferred primary display in Windows.

Fixing Apollo Virtual Display Problems After Updates

Black screens and odd layouts are often a cached configuration clash that can show up after an update or client swap. Switching between different client resolutions can leave a stale layout behind, then a 4K TV session boots to a black image. Apollo’s issue tracker includes reports where the virtual display stays black after changing to a different resolution client, even after cache clears and reinstalls.

Clear Windows Monitor Cache When Layouts Won’t Stick

Apollo’s FAQ calls out a safe reset when monitor configuration gets messed up. It clears Windows’ GraphicsDrivers monitor configuration cache so the next session starts from a clean slate.

1. Disconnect Clients — End all Artemis and Moonlight sessions.
2. Quit Apollo — Close Apollo so it stops touching display state.
3. Open Registry Editor — Press Win + R, type regedit, then open it.
4. Delete Monitor Cache Entries — Remove entries under Configuration, Connectivity, and ScaleFactors in GraphicsDrivers.
5. Reboot Windows — Restart the PC, then stream again so Windows rebuilds the layout.

Stop Rotation Changes On Virtual Displays

Rotation changes can break client resolution matching. Apollo’s FAQ warns to never set screen rotation on virtual displays, since Apollo can handle vertical display layouts without manual rotation.

• Reset Rotation To Default — In Windows Display settings, set the virtual display orientation back to horizontal.
• Restart The Streamed App — Exit and relaunch so the client gets a fresh mode list.

Handle 4K TV Black Screen Scenarios

1. Remove The Client Pairing — Unpair the TV client from Apollo, then pair it again so it gets a fresh identity.
2. Start With A Lower Mode — Begin with 1080p, confirm the image is live, then step up to 4K.
3. Reset The Monitor Cache — If black persists, use the cache clear steps above, then reconnect.

Settings That Keep Virtual Display Stable

Once you get a clean virtual display session, lock in the pieces that help it stay predictable. Apollo’s documentation frames the best mental model: treat your Artemis or Moonlight client like a dedicated Plug and Play monitor that only exists during the stream.

Pick A Simple Display Strategy

• Use Virtual Display Per App — Turn on “Always use Virtual Display” only for the apps that need it, since the Virtual Display entry behaves like a safe mode entry and won’t run custom commands.
• Use Headless Mode For All Apps — If you want all apps to run without a physical monitor, enable Headless Mode in Apollo’s Audio/Video tab, then set encoder capability manually as the FAQ notes.

Dual GPU Laptops And Adapter Choice

On laptops with an iGPU and dGPU, a mismatch can cause odd behavior like the virtual display showing up but encoding from the wrong adapter. Apollo’s documentation notes you can set Adapter Name to the GPU you want and pair it with Headless mode so a dummy plug is not needed.

1. Set Adapter Name — Choose the target GPU in Apollo’s adapter setting.
2. Enable Headless Mode — Turn it on in Audio/Video, then save and restart Windows.
3. Retest With One Client — Use a single client at first so Windows saves one clean layout.

Keep Troubleshooting Fast Next Time

If “apollo virtual display not working” hits again, you can often solve it in under five minutes by checking three things: the virtual display appears during a stream, Windows is set to Extend, and the physical monitor is disabled or the virtual display is primary based on your setup.

1. Check Display Add Remove — Confirm the virtual monitor appears on connect and disappears after app quit.
2. Switch To Extend — Use Win + P, set Extend, then relaunch the streamed app.
3. Clear display_device.state — Remove the file if app launch placement keeps ignoring the virtual display.
4. Reset GraphicsDrivers Cache — Clear the three registry areas if layouts keep snapping back.

Once the layout is clean, keep your display stack simple. One virtual display driver, one clear Windows layout per client, and Apollo’s default behavior will do the rest. Stay consistent today.