Hi omar,
Welcome to Microsoft Q&A!
You've been creative with your setup, and you're definitely not alone in facing this frustrating issue with Remote Desktop Protocol aggressively redirecting your game controller. There's nothing that you did wrong — RDP just isn’t built for this specific use case, and Windows doesn’t offer native support for isolating controllers. Here are some recommendations:
1 - Use a virtual machine instead of RDP:
If your goal is to run a second game in isolation, consider using Hyper-V or VMware Workstation with GPU passthrough (if supported). This way, the controller stays on the host, and the VM won’t see it unless you explicitly pass it through.
2 - Use a different remote access tool:
I know you mentioned avoiding Parsec because it’s confusing, but it’s one of the few tools that lets you control exactly which devices are passed through. Other alternatives are:
- Moonlight/Sunshine
- Steam Remote Play (if both games are on Steam)
3 - Use a USB device isolation tool
There are third-party tools that can block specific USB devices from being visible to RDP sessions or isolate them per user session. However, they may require paid software or scripting, e.g. USB Network Gate, FlexiHub, RdpGamepad Plugin, etc.
RDP is generally not optimized for gaming. If you're open to alternatives, third-party tools offer better performance and device isolation. I really wish I could say there’s a built-in fix in Windows, but I think it's better to be direct: there isn’t one that works reliably (as you also already tried it yourself). Thanks for your understanding.
If this reply is helpful, please click "Accept Answer" and kindly upvote it to assist others who might face similar problem. If the issue persists or you have extra questions, please click "Comment" instead.
Note: To enable e-mail notifications, follow the steps in our documentation!