0XC0262508

Fix 0xC0262508: PVP Mirroring Not Supported Error on Windows

Windows Errors Intermediate 👁 0 views 📅 May 27, 2026

This error pops up when you try to mirror displays without video outputs on a Protected Video Path setup. The fix is usually a driver update or disabling PVP.

When This Error Hits

You're plugging in a second monitor or projector, trying to mirror your screen, and instead of a clean display you get the 0xC0262508 error. This usually happens on laptops with Intel integrated graphics or on desktops where you're using a GPU that's not connected to any video output—like a compute card or a secondary card used for PhysX or mining. I've seen it most often on Windows 10 and 11 systems with Intel UHD Graphics 620 or 630 running the latest driver from Windows Update.

Root Cause

The Protected Video Path (PVP) is a DRM feature Microsoft introduced to protect premium content—think Blu-ray playback or streaming 4K from Netflix. The culprit here is almost always the GPU driver's PVP implementation. When you mirror displays, the PVP expects each display to have a physical video output port. If one of the GPUs doesn't have one (like a headless GPU), it throws this error. It's not a hardware failure—it's a software lock.

You'll also hit this if your display driver is corrupt or outdated. Windows Update sometimes pushes a generic driver that lacks the proper PVP handling. Don't bother with updating the monitor's driver—that rarely helps. The fix is on the GPU side.

How to Fix 0xC0262508

Step 1: Update Your GPU Driver

This fixes 8 out of 10 cases. Don't use Device Manager's 'Update driver'—it'll pull the same broken generic driver again. Go directly to the manufacturer's site:

  • Intel: Download the latest driver from Intel Download Center. Look for 'Intel Graphics Driver' for your chipset.
  • NVIDIA: Use GeForce Experience or grab the Game Ready driver from NVIDIA's site.
  • AMD: Get the Adrenalin driver from AMD Support.

After the install, reboot and test mirroring again.

Step 2: Disable PVP in Registry

If the driver update didn't work—and I've seen it fail on some older Intel chipsets—you'll need to kill PVP. This disables DRM for protected content, so you won't be able to play 4K Netflix on that display. Trade-off is worth it if you need mirroring for work.

reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v "DisablePVP" /t REG_DWORD /d 1 /f

Then reboot. To revert later, change the 1 to 0.

Step 3: Use Extend Instead of Mirror (Workaround)

This isn't a fix, but it'll get you going. Instead of mirroring, set the display to extend mode:

  1. Press Win + P.
  2. Select Extend instead of Duplicate.

If extend works, your GPU is fine—the error is strictly about mirroring under PVP. You can then drag windows manually or use third-party tools like DisplayFusion to mimic mirroring.

Step 4: Check for Multiple GPUs

If you have two GPUs in your system and you're trying to mirror across them, make sure your primary display is connected to the GPU that has the monitor cable. Disable the secondary GPU in Device Manager temporarily:

  1. Open Device Manager (Win + X → Device Manager).
  2. Expand Display adapters.
  3. Right-click the secondary GPU (e.g., the one with no cables) and select Disable device.

Restart and try mirroring. If it works, you've confirmed the conflict. Keep the secondary disabled or physically disconnect it if you don't need it.

Still Getting the Error?

Check these three things:

  • BIOS/UEFI settings: Some motherboards have a 'Secure Boot' or 'CSM' option that interferes with PVP. Try disabling Secure Boot temporarily (be careful if you use BitLocker).
  • Third-party screen mirroring software: Apps like MirrorOp or AirServer can trigger this. Uninstall them, test native mirroring, then reinstall if needed.
  • Windows Feature Update: I've seen Windows 11 22H2 cause this on some Dell laptops. If you're on that version, consider rolling back or applying the latest cumulative update via Windows Update.

If nothing above works, the GPU hardware might have an issue. Test the card in another PC or swap in a different GPU. But honestly, that's rare—9 times out of 10, it's a driver or PVP setting.

Was this solution helpful?