Share via

"real" mouse goes to "console" instead "rdp-tcp" when using rdp

username 0 Reputation points
2025-04-06T20:30:27.6433333+00:00

Hello everyone. I have a stupid question. I want to connect a "real" mouse (for the so-called "relative mouse" mode) to rdp. But the problem is that remotefx does not work and I tried to connect via some "usb over ip" leads to the mouse going to "console" instead of "rdp-tcp" and is displayed only on the host machine's lock screen. I saw some videos on YouTube where people connected the mouse to rdp and their mouse works as it should there.. I did a study by installing windows10/11 in a virtual machine and immediately without making any settings I tried to connect the mouse through the mouse "emulator" via android and also via usb-over-ip but the result is the same - it gets to the "console". What's the problem? were those videos fake or am I doing something wrong? how to make the mouse get into "rdp-tcp" or at least make rdp run as "console"? (manuals about /console and /admin don't work, the option to write "PATH WIN32_TSPermissionsSetting.TerminalName="Console"" into the registry also apparently doesn't work on new windows, shadow connection is too slow) I'm at a dead end. haha.
(in general, I doubt that anyone will be able to help me, since this is clearly a very strange and specific... "problem")

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 160 Reputation points Microsoft External Staff Moderator
    2025-08-11T07:49:24.7433333+00:00

    Welcome to the Microsoft Q&A Platform and thank you for posting your question!

    Based on your description, the behavior is similar to device redirection in RDP, where redirected hardware (e.g a mouse) can end up being handled by the console session instead of the remote session. To prevent this, I suggest you can disable Plug and Play device redirection by following the steps below.

    Disable Plug and Play Device Redirection

    1.Open Local or Domain Group Policy Editor (gpedit.msc or gpmc.msc)

    2.Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Connection Client → RemoteFX USB Device Redirection

    3.Locate Do not allow supported Plug and Play device redirection

    4.Set it to Enabled

    5.On both client and server, run gpupdate /force and restart both machines

    This ensures that supported Plug and Play devices, including certain USB mice and other peripherals. It will not be redirected into the remote session, reducing the risk of them defaulting to the console instead.

    If the issue persists, you can check if other redirection policies (e.g USB or RemoteFX device redirection) are enabled and disable them as needed for your environment.

    Please let me know how it goes. Wishing you a successful resolution and a great day!

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.