0XC00A0018

Fix 0xC00A0018: Bad Video Mode in Remote Desktop

Network & Connectivity Beginner 👁 0 views 📅 May 27, 2026

This Remote Desktop error pops up when the client's display can't handle the video mode the server sends. It's a mismatch in color depth or resolution. Here's how to fix it.

When Does This Error Happen?

You're connecting to a Windows 10 or Windows 11 machine over Remote Desktop (RDP). Everything looks normal at first. Then the connection drops, or you get a black screen with the error 0xC00A0018. Sometimes it happens right after you log in, sometimes after you switch a resolution or plug in an external monitor.

The official error name is STATUS_CTX_BAD_VIDEO_MODE. Microsoft buried it in the system files, but you're here now. I'll walk you through the fix.

Root Cause (Plain English)

Your client computer — the one you're connecting from — is asking the remote server to send a video mode that the server can't or won't deliver. It's like asking a DVD player to output 8K video. The player says "nope."

Most of the time, this comes down to one of three things:

  • Your client's display resolution is too high for the server to match.
  • Your color depth setting is 32-bit, which some older or virtualized servers can't handle.
  • You're using a high-DPI monitor (like a 4K laptop screen) and the scaling is conflicting with the RDP session.

The fix is to lower the load on the server side. We do that by changing your client settings before the connection starts.

The Fix: Step by Step

  1. Close any active RDP sessions. If the error is showing now, disconnect or close the Remote Desktop window. We start fresh.

  2. Open the Remote Desktop client. On Windows, hit the Start button, type Remote Desktop Connection, and click it. You'll see the Connection dialog box. It's the same one whether you're on Windows 10 or 11. Don't type a computer name yet.

  3. Click "Show Options" at the bottom left of that dialog. This expands the settings. Now you should see multiple tabs.

  4. Go to the "Display" tab. It's the second one from the left, between General and Local Resources.

  5. Lower the display resolution. You'll see a slider bar labeled "Display configuration." Drag it left to something like 1280 x 720 or 1024 x 768. Don't go too low — 800 x 600 is overkill. After you drag it, you'll see the resolution number update above the slider. After you change the slider, you should see the resolution number change immediately.

  6. Change the color depth. Right below the resolution slider, there's a dropdown called "Colors." Click it and select High Color (16 bit). Do NOT leave it on "True Color (32 bit)." That's the common culprit. After you select 16 bit, you should see the dropdown close and show "High Color (16 bit)" as the selected option.

  7. Uncheck "Use all my monitors for the remote session" if it's checked. That checkbox appears on the same Display tab, right under the Colors dropdown. If you have multiple monitors and this box is checked, uncheck it. Multi-monitor RDP sessions are picky about video modes. After you uncheck, the box should be empty.

  8. Click "Connect" with a working computer name or IP. Type the server's address in the General tab first (top box), then click Connect. You'll get the usual login prompt. Enter your credentials.

  9. If the error doesn't appear, you're done. The session should load normally. If you still see the error, we need to go further.

If It Still Fails: Advanced Tweak

If the basic fix didn't work, the server might be enforcing a specific video mode. We'll change a registry setting on the client machine. This tells RDP to use a lower color depth at the system level.

  1. Open Registry Editor. Press Windows Key + R, type regedit, and hit Enter. Click Yes if UAC asks.
  2. Go to this key: 
    HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
  3. Create a DWORD value. Right-click in the right pane, choose New > DWORD (32-bit) Value. Name it ColorDepth.
  4. Set it to 2. Double-click the new ColorDepth value, change the base to Decimal, and type 2 into the Value data field. Click OK. After you click OK, you should see ColorDepth listed with a value of 0x00000002 (2) in the right pane.
  5. Close Registry Editor and reconnect. That forces RDP to use 16-bit color regardless of what the Display tab says.

If you're on a laptop with a high-DPI screen (like a 4K model at 150% scaling), also try temporarily lowering the Windows display scaling to 100% before connecting. Right-click the desktop, choose Display settings, and set Scale to 100%. Reconnect. After the session ends, you can bump scaling back up.

What to Check If Nothing Works

  • Update your graphics driver on the client machine. Outdated Intel or NVIDIA drivers sometimes botch RDP video negotiation. Get the latest from the manufacturer's site.
  • Check if the remote server is a VM. Virtual machines (Hyper-V, VMware, VirtualBox) sometimes require specific video settings. On Hyper-V, ensure "RemoteFX" is disabled in the VM's settings. RemoteFX is buggy with high resolutions.
  • Disconnect any external monitors from your client laptop. Some docking stations confuse RDP's video detection. Unplug the dock, try again with just the laptop screen.

That's it. The error is almost always a resolution or color depth mismatch. Lower both, and you'll connect.

Was this solution helpful?

0xC00A0018 STATUS_CTX_BAD_VIDEO_MODE bad video mode remote desktop remote desktop error 0xC00A0018 RDP video mode fix 0xC00A0018 Windows 10 0xC00A0018 Windows 11 fix remote desktop display settings RDP color depth issue remote desktop connection failed video mode