Fix 0XC0262105: NVIDIA/AMD Can't Apply Settings Now

Yeah, that 0XC0262105 error is a pain. You're just trying to change a resolution or turn on G-Sync, and Windows throws this cryptic "try again now" message. Let's kill it.

The error code 0XC0262105 maps to ERROR_GRAPHICS_TRY_AGAIN_NOW. What's actually happening here is your graphics driver is in a temporary state where it can't accept new commands. Maybe the driver just crashed and restarted silently. Maybe an app holds a lock on the display mode. The system tells you to try again because the condition is supposed to fix itself. But sometimes it doesn't.

The Fix: Restart the Driver

Skip rebooting your whole PC first. That's overkill 90% of the time. Instead, force the graphics driver to reload.

1. Press Win + Ctrl + Shift + B. Your screen will flash black for a second. That's the driver resetting.
2. Now open your graphics control panel (NVIDIA Control Panel, AMD Adrenalin, or Intel Graphics Command Center) and try your change again.
3. If that didn't work, open Task Manager (Ctrl + Shift + Esc). Find any game or app that uses 3D graphics. Right-click it and select End Task. Then try step 2 again.
4. No luck? Press Win + R, type cmd, hit Enter. In the command prompt, type net stop "Display Enhancement Service" (if present) then net start "Display Enhancement Service". This restarts the Windows display-related service. Try the change again.

If after these steps the error still shows, reboot your computer. But honestly, the keyboard shortcut alone fixes it for 8 out of 10 people.

Why That Works

Win + Ctrl + Shift + B sends a signal to the Windows Display Driver Model (WDDM) to reset the driver stack without a full reboot. This clears the "currently existing condition" the error message mentions — usually a stalled command buffer or a failed mode set call. The reason step 3 works is because an active 3D app can hold a lock on certain display resources, preventing the driver from accepting new requests. Killing that app releases the lock.

Less Common Variations

Here are cases where the above fix might not be enough:

1. Multiple Monitors, Wrong Cable

If you use a DisplayPort cable that's not rated for your monitor's resolution and refresh rate, the driver can enter a retry loop. The error shows up when you try to set a mode the cable can't handle. Swap to a certified cable (look for the VESA badge).

2. Overclocking Instability

GPU overclocking — core clock or memory — can cause temporary hangs. The driver detects the card is unstable and refuses to apply further changes. Drop your overclock back to stock, apply settings, then overclock again.

3. Corrupted Driver Installation

This error happens a few times a week? Your driver install is likely busted. Use DDU (Display Driver Uninstaller) in Safe Mode to clean out all traces, then install the latest driver fresh. Don't just "upgrade" over the old one — that's how corruption persists.

4. Windows Update Interference

Windows 11 24H2 and some Insider builds have a known bug where they push a generic Microsoft Basic Display Adapter driver on top of your proper driver. This causes the "try again now" error randomly. Open Device Manager, expand Display adapters. If you see "Microsoft Basic Display Adapter" alongside your real GPU, right-click it and select Disable device. Then restart.

Prevention

Three things to do so this error never bothers you again:

• Keep your driver version stable. Don't install every Game Ready driver the day it drops. Stay one or two versions behind. Let others beta-test for you. I stick with NVIDIA's Studio Drivers on my gaming PC — they're more thoroughly tested.
• Disable hardware-accelerated GPU scheduling (HAGS) if this error repeats. Go to Settings > System > Display > Graphics > Change default graphics settings. Turn off "Hardware-accelerated GPU scheduling". HAGS is known to cause temporary lock conditions with some apps.
• Run your displays at a standard refresh rate. 144 Hz is fine. But 143.999 Hz from a custom resolution? That can confuse the WDDM mode-set logic. Stick to standard modes from the EDID list your monitor provides.

That's it. Next time the error shows up, hit the keyboard shortcut. Don't panic. You know what's happening now.