0XC01E0317

Fix STATUS_GRAPHICS_SOURCE_ALREADY_IN_SET (0XC01E0317)

This error pops up when Windows tries to add a video source that's already in a video source set. It's common with multi-monitor setups or VR headsets.

You're trying to add a second monitor, or maybe a VR headset like the Oculus Rift, and instead of a working display you get error 0XC01E0317: "The specified video present source is already in the video present source set." This usually happens with Windows 10 version 22H2 or Windows 11 version 23H2 when you've got a graphics card with multiple outputs. I've seen it most often when someone plugs in a third monitor or a projector while the system is already running a video streaming app like Netflix or a game in fullscreen mode.

What's really going on?

The short version: Windows thinks the video source (your GPU port) is already assigned to a display set. Think of a "video present source set" as a group of displays that share the same signal path. When you try to add a source that's already inside one of these groups, Windows throws this error because it can't double-book the connection.

Root cause is almost always one of three things:

  • Driver confusion - Your graphics driver (NVIDIA, AMD, or Intel) keeps a list of display configurations. If that list gets corrupted or out of sync, it thinks the source is already used.
  • DirectX state issue - An app like a game or a video editor holds onto a display resource after it closes. The video present source set doesn't get cleared.
  • Hot-plug conflict - You plugged or unplugged a display cable too fast. Windows didn't finish updating the display topology before you made the next change.

Fix it: Step by step

Skip the complicated registry edits for now. Here's what actually works in 90% of cases.

  1. Restart the graphics driver - The quickest first step. Press Win + Ctrl + Shift + B. Your screen will flash black for a second. This resets the video present source set without rebooting. Try plugging your monitor or VR headset again after the flash.
  2. Disconnect and reconnect the display - Unplug the cable from the monitor or headset. Wait a full 10 seconds. Plug it back in. Make sure you wait 10 seconds – 3 seconds isn't enough for the driver to fully release the source.
  3. Close any fullscreen apps - If a game, video player, or VR app is running in fullscreen mode, it might hold the video present source set. Press Alt + Tab to switch out, then close the app completely. Use Task Manager (Ctrl + Shift + Esc) to kill the process if it's stuck.
  4. Update or roll back your graphics driver - Go to Device Manager, find "Display adapters," right-click your GPU, and select "Properties." On the Driver tab, click "Update driver" and choose "Search automatically." If the error started right after a driver update, click "Roll Back Driver" instead. I've seen the NVIDIA 546.17 driver cause this exact error on RTX 3070 cards.
  5. Reset your display settings - Open Settings (Win + I), go to System > Display > Advanced display. Click "Display adapter properties for Display 1." Then go to the "Monitor" tab and set the color depth to 32-bit and the refresh rate to 60 Hz. Click Apply, then OK. This clears out any stale display topology.
  6. Run DirectX Diagnostic Tool - Press Win + R, type dxdiag, and hit Enter. On the System tab, click "Save All Information." This generates a log. In the log, look for any "MPO" (multi-plane overlay) errors – they often link to this issue. If you see them, disable MPO via a registry edit:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM
Create a DWORD: OverlayTestMode
Set value to: 5

Reboot after making that change.

If the error still shows up

You've tried everything above and it's still failing. Check these three things:

  • Your cable – a damaged HDMI or DisplayPort cable can confuse the driver about which source is in use. Swap with a known working cable.
  • BIOS settings – some motherboards have a "IGD Multi-Monitor" option in the BIOS. If it's enabled and you're using a dedicated GPU, disable it. This conflicts with Windows' display detection.
  • Third-party display software – tools like DisplayFusion, Actual Multiple Monitors, or NVIDIA Surround can hijack the video present source set. Uninstall them temporarily to test.

If none of this works, it might be a hardware issue with your GPU port. Try the display on a different port (like switching from HDMI to DisplayPort) or test a different monitor to rule out the screen itself.

I know this error is infuriating because it stops you from using your gear. But the good news is it's almost always a software hiccup, not a dead GPU. Give the steps above a try – starting with the quick keyboard shortcut – and you'll likely be back to a working setup in under five minutes.

Related Errors in Windows Errors
0XC0262323 Fix 0xC0262323: Graphics No Recommended VidPN 0X000036D0 Fix 0X000036D0: XML bad start name character in manifest 0X800F0231 Can't disable a device? SPAPI_E_NOT_DISABLEABLE fix 0XC000071C STATUS_INVALID_THREAD (0XC000071C) Fix: Corrupt Thread Handles

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.