0XC0262345

Fix 0XC0262345: Invalid VidPN Path Content Geometry Transformation

Windows Errors Intermediate 👁 1 views 📅 May 29, 2026

This error means Windows can't apply a display transformation, often from a bad driver or corrupt display config. Here's how to fix it step by step.

Quick answer

Uninstall your display driver with Display Driver Uninstaller (DDU) in Safe Mode, then reinstall the latest driver from your GPU manufacturer. That fixes 90% of these cases.

What's going on here?

Error 0XC0262345 — officially ERROR_GRAPHICS_INVALID_PATH_CONTENT_GEOMETRY_TRANSFORMATION — pops up when the Windows Display Driver Model (WDDM) rejects a geometry transformation you're trying to apply to a display path. Think of a "VidPN present path" as a connection between your GPU and a monitor, including any scaling, rotation, or stretching you've set. When that transformation (like 90-degree rotation or custom scaling) doesn't match what the driver or monitor can handle, Windows throws this error.

I've seen this most often on Windows 10 and 11 systems with multiple monitors, especially after a Windows Update or a GPU driver update that went sideways. Another common trigger: switching between integrated and discrete GPUs on a laptop (e.g., an Intel iGPU switching to an NVIDIA dGPU). The driver gets confused, writes a bad geometry setting into the registry, and you're stuck.

The real fix isn't poking at display settings — it's cleaning out the corrupt driver state completely.

Fix steps

  1. Boot into Safe Mode with Networking. Press Shift while clicking Restart in the Start menu. On the blue screen, go to Troubleshoot > Advanced options > Startup Settings > Restart. After reboot, press 4 for Safe Mode with Networking.
  2. Download DDU (Display Driver Uninstaller). Get it from the official Guru3D site. Safe Mode is key — DDU won't work right in normal mode with the driver loaded.
  3. Run DDU. Extract the zip, run the .exe. At the prompt, choose GPU and select your manufacturer (NVIDIA, AMD, or Intel). Click Clean and restart. DDU will remove all traces of the driver, including registry entries for display paths. After it finishes, the system reboots automatically.
  4. Reinstall the driver. Once back in Windows (normal mode), download the latest driver from NVIDIA, AMD, or Intel's site. Don't use Windows Update for this — it sometimes pushes older or generic drivers. Run the installer, choose "Clean Installation" if offered.
  5. Reboot and test. After the driver install, restart again. Try changing your display resolution, rotation, or scaling. The error should be gone.

Alternative fixes if DDU doesn't work

  1. Reset display settings in the registry. Open Regedit as admin. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. Delete the Configuration and Connectivity subkeys. Back them up first by right-clicking and exporting. Then reboot. Windows rebuilds these keys from scratch.
  2. Check for corrupt system files. Open Command Prompt as admin. Run sfc /scannow. If it finds issues, run DISM /Online /Cleanup-Image /RestoreHealth. Then reboot.
  3. Roll back the last Windows Update. Go to Settings > Windows Update > Update history > Uninstall updates. Pick the most recent update and uninstall it. This helps if the error started after a Windows Update.
  4. Disable fast startup. Fast startup can hang on to corrupt display state. Go to Control Panel > Power Options > Choose what the power buttons do. Click Change settings that are currently unavailable, uncheck Turn on fast startup, save, and restart.

Prevention tip

Don't rely on Windows Update for GPU drivers — it's notorious for pushing stale or wrong versions. Set your update settings to Pause driver updates via Group Policy or a tool like Show or hide updates from Microsoft. Manually update your GPU driver only from the manufacturer's site. This one habit will dodge most of these VidPN errors.

Also, if you're running multiple monitors, avoid mixing ports (e.g., HDMI and DisplayPort) on the same GPU unless necessary — it can confuse the driver's geometry mapping. Stick to one cable type per GPU if you can.

Was this solution helpful?