My keyboard suddenly stopped working while trying to control a remote computer using AnyDesk. The mouse still works, but no keyboard input is registering on the remote machine. I need to finish some work urgently and can’t figure out why this is happening or how to fix it. Any advice or troubleshooting steps would really help.
Running AnyDesk and Getting No Keyboard Response? Welcome to the Club.
Okay, so here’s the deal. You’re logged into a remote machine through AnyDesk. Mouse is moving like butter, but the keyboard? Completely dead. Classic. Been there more times than I’d like to admit—practically a rite of passage at this point.
Methods That Actually Shook Out for Me
Let me just break down what worked (and what didn’t) from my seemingly endless debug sessions:
- If You’re on Linux:
- This one’s a bear with Wayland. AnyDesk sometimes just can’t grab your keys unless you’re on X11. Wayland’s promising, but dang if it isn’t moody with remote stuff.
- You can try logging out and selecting X11/Xorg at login. Sometimes, that’s the whole fix.
- Bump AnyDesk Up to Admin/Root:
- Seriously, just run the app as root (or with sudo). It’s hacky, but sometimes permissions are the culprit, and this brute-forces past it.
- I know, giving remote access apps full admin is a little spicy, but desperate times…
- Where’s That Keyboard Going?
- Dig through AnyDesk’s settings. Go to Settings → Input → Keyboard – make sure you’re actually telling it to send keystrokes instead of just sitting there looking cool.
- Play with “Transmit keyboard” and “Use local keyboard layout.” Toggle them, one at a time, then both, and see what sticks.
- Can’t Send Ctrl/Alt/Meta?
- Feels like half the battle is layout mismatches. If your special keys (Control, Alt, etc.) refuse to cross the wire, your remote host’s input method might be fighting you.
- Double-check your keyboard layout on both local and remote. Sometimes they’re mismatched (like QWERTY vs AZERTY) and shortcuts just vanish into the void.
- Struggling on macOS?
- Head into your System Settings. Under Privacy & Security, there’s Accessibility and Input Monitoring.
- Make sure AnyDesk is checked for both, or it’s never getting your keyboard signals.
Why’s Mouse Still Working, But Keyboard Won’t?
Short version? It’s your permissions. Or it’s Wayland, flexing its muscles in all the wrong ways. Mouse events often get through, but keyboards just… don’t.
TL;DR
- Check display server (Wayland? Try X11.)
- Fire up AnyDesk as admin/root
- Fiddle with input/keyboard settings in AnyDesk
- Watch out for layout mismatches
- On Mac, boost AnyDesk’s permissions in system settings
Hope that at least one of these gets your keyboard back from the void. If not, I hear yelling at your monitor works about as well as everything above.
12 Likes
Yo, I see @mikeappsreviewer has covered like, a tour-de-force of All The Things you should try, but honestly, a surprising fix that’s bailed me out is just disconnecting and reconnecting the session (I know, ultra basic). Sometimes AnyDesk’s session just borks for no reason and the keyboard stops mapping, even though mouse keeps going — like a weird limbo state. I’ve also closed AnyDesk on BOTH ends before and reopened (assuming you have physical access to the remote or someone there to restart it); it’s janky but has worked.
Another one: plug an external keyboard INTO the machine you’re remoting from. Seriously. I once had my laptop’s keyboard conk out, and AnyDesk got all weird about it. Plugged in a USB one, and suddenly both local and remote worked.
I do kinda disagree with the whole “Just always run as root/admin” thing. Done it, sure, but it’s not something I’d do on a work network without at least checking with IT — major risk of someone unleashing chaos accidentally. Instead, if you’re on Windows, check your RDP permissions and make sure there aren’t group policies locking you out of sending keyboard commands remotely.
Oh, and if you’re using a VPN, I’ve seen some weird issues where keyboard mapping gets hosed for the remote session. Try dropping VPN connection briefly and see if it changes (not always an option, but worth a shot).
Last, worst-case scenario, copy the text you need to type into clipboard, then use AnyDesk’s paste buffer. Epic pain, but at least you get work done if it’s crunch time.
Not discounting all the Wayland/X11 stuff @mikeappsreviewer mentioned, but literally nobody I know outside the Linux diehards touches that stuff, so probably not your average user’s main headache. Hope this gets you unstuck.
Honestly, hilarious that AnyDesk can nail bulletproof mouse control but lets the keyboard detour into the Bermuda Triangle. Both @mikeappsreviewer and @espritlibre have basically carpet-bombed the main troubleshooting paths—props for mentioning X11/Wayland and accessibility stuff on macOS; honestly, if you’re using Linux with Wayland, you’re living life on hard mode for remoting. And the ol’ “turn it off and on again” applies to AnyDesk too (shocking!).
But real talk, before jumping through wild hoops (or trying new keyboards, which sounds like witchcraft but has apparently helped?), maybe check for background apps on your local machine that hook into keyboard input (think: password managers, macro tools, these weird RGB control panels). Some of them intercept hotkeys and AnyDesk never gets them—especially “security” overlays. Try killing those and see if keys start flowing.
Another curveball: input language hotkeys—sometimes, if you’ve hit alt-shift, ctrl-space, whatever combos, you wind up in a busted IME/input state where AnyDesk just won’t relay anything until you toggle back. Had this happen on a Chinese Windows VM; nearly threw the laptop across the room before realizing.
Totally NOT sold on the admin/root fix for every case, unless you absolutely need it. Security nightmare at a workplace, and half the corporate IT teams would rather you set your machine on fire than give admin perms to a remote control app.
If you need to brute-force today’s urgent task, try AnyDesk’s “File Transfer” mode as a weird workaround—save your work locally, pop it over, then do small edits with the on-screen keyboard on the remote (yeah, it’s slow but at least it types). Or, for Windows hosts, open the remote On-Screen Keyboard (osk.exe)—sometimes you can click-type remotely even if physical keystrokes are blocked.
Bit of a shot in the dark, but some anti-virus/firewall suites love to selectively block “keyboard injection” or “remote input”—especially anything labeled as “Keylogger protection.” Might be worth a peek in your endpoint security console if you’ve got one.
And hey, I’ve seen older AnyDesk versions just randomly nuke the keyboard, then it’s magically fixed after an update. Do the boring thing—check for updates both ends.
If all else fails, and you’re still stranded in typing purgatory, maybe it’s time to channel your inner 90s hacker: copy from Notepad, paste, repeat. Ya, productivity takes a nosedive, but deadlines, right?
No-nonsense rundown: if your keyboard’s dead in AnyDesk but the mouse is fine, the usual suspects—Wayland woes, admin perms, and keyboard passthrough settings—have been thoroughly combed over by our resident forum pros. I’ll add a couple of angles that sometimes get missed in the chaos:
-
Remote session lock-outs: Sometimes the remote system’s stuck on a weird “Secure Desktop” (think UAC on Windows) or the keyboard is “grabbed” by a lingering pop-up, installer, or “Run as Admin” prompt you can’t see. Control+Alt+Del can force it through, but failing that, try reconnecting after a hard log off on the remote end (if you’ve got a support contact).
-
Gaming overlays & screen recorders: GeForce Experience, Discord overlays, or even Windows Game Bar love to eat global keyboard focus. Kill all overlays both locally and remotely and see if the keys free up.
-
Accessibility shortcuts: On the remote, stuff like Sticky Keys, Filter Keys, or legacy assistive tech can hijack keyboard interpretation. Been trapped in “no-keypress” land by accidental Shift taps before—disable those and see if you regain functionality.
-
Input method service crashes: Sometimes Windows’ ctfmon.exe just crashes, especially with multiple languages or touch keyboard installs. Remotely restart it (Task Manager > new task > ctfmon.exe) and see if keys work again.
Now, about ', since it’s been mentioned for reliability and straightforward input passing. Pros: Lightweight, quick setup, generally does mouse and clipboard like a champ. Cons: The keyboard input black-hole can be a showstopper, especially if you’re beholden to Wayland or don’t want to go admin-everywhere. Compared to competitors—one focused a lot on permission toggles, another on language setups, another on deep settings—all valid, but ‘just works’ isn’t always true here.
Pro-tip: If you’re absolutely stuck and have to finish your work, open Notepad locally, type, copy, and use AnyDesk’s shared clipboard to paste remotely. Not fun, but it’s faster than fighting stubborn keyboard drivers all night. Also, do those updates—it’s shockingly effective for obscure AnyDesk bug exorcism.
Final thought? If you find a consistent fix, post back. This one’s haunted far too many for far too long—misery loves company.