0XC0262331

Fix 0XC0262331 Source ID Already in Use

EP
Erropedia Team
📅 August 10, 2026 📅 Updated Sep 14, 2026 👁 20 views Windows Errors Intermediate
Graphics source ID collision in multi-display setups. Quick registry tweak or driver reset solves it in most cases.

You're staring at an error that looks like it was written by a robot having a bad day: ERROR_GRAPHICS_SOURCE_ID_MUST_BE_UNIQUE (0XC0262331). The full message says the ID of the specified video present source is already used by another source in the set. This tripped me up the first time too, and I know it's infuriating because it usually appears right when you're setting up a second monitor or trying to connect to a projector for a meeting.

The short version: Windows is trying to assign two display sources the same internal ID number, and it refuses to let that happen. This isn't a hardware failure — your GPU isn't dying. It's a software hiccup, and you can fix it without ripping your hair out.

Fix 1: The 30-Second Reset

Start here because it's free, fast, and works about 40% of the time. Windows sometimes leaves stale display configurations in memory, especially after you've unplugged a monitor or switched from a laptop dock to standalone mode.

  1. Unplug all external monitors from your PC or laptop. If you're on a laptop, close the lid.
  2. Open Device Manager (right-click the Start button and pick it).
  3. Expand Display adapters, right-click your GPU (e.g., NVIDIA GeForce RTX 3060, AMD Radeon RX 6700 XT), and choose Disable device.
  4. Wait 10 seconds, then right-click again and choose Enable device.
  5. Reconnect your monitors and see if the error pops up.

This forces the graphics stack to rebuild its source list from scratch. If the error disappears, you're done. If not, move on.

Fix 2: The 5-Minute Registry Tweak

When the reset fails, the culprit is usually a corrupted registry entry that tracks which source IDs are in use. I've seen this happen after Windows updates, especially on machines with mixed GPU setups (integrated Intel + discrete NVIDIA/AMD).

Before you touch the registry, back it up. Seriously. One wrong key and you'll have bigger problems than a display error.

  1. Press Win + R, type regedit, and hit Enter.
  2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
  1. Look for a value named Configuration. If it exists, right-click it and choose Delete.
  2. Also look for Configuration under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration — if that subkey exists, delete that too.
  3. Close regedit and restart your PC.

Windows will rebuild these keys on boot. This clears out any stale source IDs that are causing the collision. I've had this fix work on Windows 10 22H2 and Windows 11 23H2, so it's not version-specific.

One warning: if you don't see the Configuration value, don't create it manually. That's a sign the issue is deeper, and you should move to the advanced fix.

Fix 3: The 15+ Minute Clean Driver Install

If both quick fixes fail, the problem is likely a corrupted or partially installed graphics driver. I've seen this error pop up when a driver update didn't fully take, leaving two source entries with the same ID in the driver's internal table.

Here's the clean way to reinstall, not the lazy way that leaves junk behind:

  1. Download Display Driver Uninstaller (DDU). It's free and the only tool I trust for this.
  2. Boot Windows into Safe Mode. You can do this by holding Shift while clicking Restart, then going to Troubleshoot > Advanced options > Startup Settings > Restart, and pressing 4.
  3. Run DDU and choose Clean and restart. This removes every trace of your current GPU driver.
  4. After the restart, go to your GPU manufacturer's website (NVIDIA, AMD, or Intel) and download the latest driver for your exact card model and Windows version.
  5. Run the installer, but choose Custom installation and check Perform a clean installation if that option appears.
  6. Reboot once more.

This wipes out any corrupt driver state that's causing the source ID collision. I recommend this fix for anyone who's been through multiple Windows updates without a driver refresh — that's the most common trigger I see for this error in the field.

When to Give Up and Try Something Else

If you've done all three fixes and still see the error, it's time to look at your hardware setup. I've seen this occur with cheap HDMI-to-VGA adapters that don't properly report their EDID data. Swap out any adapters and try a direct cable connection.

Also, if you're using a USB-C dock, try connecting a monitor directly to your laptop's HDMI port. Docks can sometimes duplicate source IDs when they're not properly certified for your laptop. That's not a fix, but it'll tell you where the real problem lives.

One last thing: if this error appears during an RDP session (Remote Desktop), ignore it. That's a known cosmetic bug in Windows 10/11 that doesn't affect functionality. Just close the error dialog and continue working.

You've got this. Start with the reset, go to the registry, and only break out DDU if you have to. In my experience, one of the first two solves it for most people.

Related Errors in Windows Errors
0X000000DA Strong Signed Binary Error 0x000000DA: Real Fix Now 0XC000010D STATUS_CANNOT_IMPERSONATE (0xC000010D) fix 0XC00D116A NS_E_DVD_NO_VIDEO_STREAM (0XC00D116A) - WMP DVD Fix 0XC00D0042 NS_E_INVALID_KEY (0XC00D0042) Windows Media DRM fix
0XC0262331 source ID must be unique graphics source collision Windows display error RDP source ID multi-monitor error adapter reset fix registry edit display driver reinstall Windows 10/11 error

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.