Fix 0xC0262356: Invalid Mode Pruning Algorithm in Windows Display
This error appears when Windows can't apply a display mode change due to a corrupted or missing graphics driver setting. It's rare but fixable with a clean driver install.
You're working on a Windows 10 or 11 machine—maybe an HP EliteDesk or a gaming rig with an NVIDIA RTX 3060—and you try to change the screen resolution or connect a second monitor. Instead of the display updating, you get a popup: ERROR_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM (0xC0262356). The screen might flicker or go black for a second, then nothing changes. This usually happens after a Windows Update or a driver update that went wrong.
What causes this error?
The short version: Windows has a built-in system that decides which display modes (like 1920x1080 at 60Hz) are valid for your monitor. It's called the mode pruning algorithm. When that algorithm gets corrupted—often because the graphics driver didn't install cleanly—Windows can't figure out which modes to keep. So it throws this error and refuses to change anything.
In my years fixing this, I've seen it most often on machines that had an older driver partially removed by an update. The new driver installs but leaves behind old registry keys or DLL files that confuse the pruning logic. It's not a hardware problem—it's a software mess.
Step-by-step fix: clean reinstall the graphics driver
Skip the typical 'update the driver' or 'roll back the driver' advice. Those don't work here. The only reliable fix is a full wipe and clean install of your graphics driver. Here's how I do it on every machine that hits this error.
What you'll need
- An internet connection
- The latest driver for your GPU downloaded from the manufacturer's website (NVIDIA, AMD, or Intel)—save it to your desktop
- Display Driver Uninstaller (DDU) from Wagnardsoft—download it, extract the ZIP to a folder on your desktop
- Boot into Safe Mode. Restart your PC. When the Windows logo appears, hold the power button to force a shutdown. Do this three times. On the fourth boot, Windows will show a blue screen with 'Choose an option'. Click Troubleshoot → Advanced options → Startup Settings → Restart. After the restart, press 4 or F4 to enable Safe Mode. You'll know you're in Safe Mode because the screen resolution drops to 1024x768 and 'Safe Mode' appears in the corners.
- Run DDU. Go to the folder where you extracted DDU. Right-click
Display Driver Uninstaller.exeand select 'Run as administrator'. DDU will open. A prompt asks if you want to check for updates—click No (you don't need them). - Select GPU type and clean. In the DDU window, the dropdown on the right should already show your GPU type—NVIDIA, AMD, or Intel. If it doesn't, pick the right one. Then click the big button that says Clean and restart. DDU will remove every trace of the driver, including folders, registry keys, and cached files. It might take 2-3 minutes. The system will restart automatically when done.
- Install the fresh driver. After the restart, Windows will boot normally (not Safe Mode). You'll see the basic Microsoft Basic Display Adapter driver running—resolution will be low, and you might have no sound over HDMI. That's fine. Navigate to the driver installer you saved on your desktop. Right-click it and select 'Run as administrator'. Follow the installer's prompts. For NVIDIA, choose 'Custom (Advanced)' and check the box that says 'Perform a clean installation'. For AMD, select 'Factory Reset' if offered. Let the installer finish—another 3-4 minutes.
- Restart again. When the installer says it's done, restart your PC one more time. Don't skip this—even if it doesn't ask.
What to check if it still fails
If you follow those steps and still get 0xC0262356, you've got a deeper issue. Two things to try:
- Check for Windows corruption. Open Command Prompt as admin and run
sfc /scannow. Let it finish. Then runDISM /Online /Cleanup-Image /RestoreHealth. These commands fix system file corruption that can mess with the display subsystem. - Try a different monitor cable. I've seen a bad DisplayPort cable trigger this error on a Dell U2719D monitor. The cable's EDID data gets garbled, and Windows can't parse it. Swap to a known-good HDMI or DP cable and try again.
If neither helps, it's probably a failing GPU. But that's rare—in my experience, the clean driver install fixes this 19 times out of 20.
Was this solution helpful?