After switching from Remote Desktop to the new Windows App, I noticed that some features I relied on are missing or work differently. This is making it harder for me to get my work done like I used to. Has anyone else run into the same issues, or is there a way to get the old Remote Desktop features back in the new app? I really need help figuring out a solution.
Yep, It Gets Even Weirder…
Let me just pile on the misery for a second.
The Baffling Case of Remote Desktop on Windows
Alright, so picture this: you fire up the new Windows App on your Windows computer, expecting to remote into a plain old Windows PC in your house or at work—y’know, that thing Remote Desktop has handled for two decades with no drama. Suddenly you hit a wall. No connection, no error that makes sense, just… nothing. The very feature that was standard since XP is missing in action.
Other Platforms Doing Just Fine
Meanwhile, if you’re rocking the same app on macOS—yep, connects instantly. Launch it on iOS? Smooth sailing. I even heard this wild story about someone hooking it up on an Oculus headset for fun, and it worked like a charm. Every other platform gets to play, except the one you’d expect to, you know, actually work on Windows.
Irony Overload: The ‘Windows’ App That Snubs Windows
No joke, the only system that absolutely cannot do the basic Remote Desktop handshake is Windows itself, running the Windows App. It’s like naming your bakery “Bread World” and refusing to make bread. You stare at the app and wonder what cosmic joke landed you here.
No Explanation, No ETA… Just “Coming Soon”
I’ve been in the IT trenches for over a decade and honestly, this is one of those things that just breaks your brain. No clever workaround, no forum post from a dev, nada. You go digging for answers and the official documentation just shrugs and says “coming soon.” You pine for those sweet, reassuring days when “Connecting…” wasn’t a lie—it actually, you know, connected.
Nostalgia for Simpler Times
Man, the old Remote Desktop would make you wait a couple seconds with a spinning icon, then boom: logged in. Now you’re stuck staring at vague promises and feature previews that never land. The good old days are really starting to look pretty great right about now.
3 Likes
So I’m absolutely with @mikeappsreviewer on the irony-pain train, but I gotta toss a different angle out there—this whole “missing features” saga is classic Microsoft “let’s preview everything, deliver for nobody.” The Windows App feels like some kind of unintentional comedy show. We all jumped ship to this because, well, hey, Microsoft’s pushing it everywhere, but then half your workflow just goes pffft. Quick example: I used to rely on Remote Desktop’s drive redirection and clipboard support for moving code and files; now, poof, either missing or acting wonky. For some VPN scenarios, it won’t even pop up a creds prompt—just chokes silently. It’s as if the Windows App was designed by someone who heard about Windows but never used it.
And while Mike’s right about non-Windows platforms being randomly better off, I’m convinced that’s partly because the new app is laser-focused (for now?) on Azure Virtual Desktop and cloud PC stuff, not regular-jane RDP. Regular Windows-to-Windows connections seriously got the short end of the stick, and it’s kind of wild: you’d expect backwards compatibility or, y’know, feature parity. Instead, all the docs say “coming soon,” so basically we’re unpaid beta testers.
But, to be a devil’s advocate: maybe Microsoft’s whole approach is to prioritize enterprise cloud stuff, and home users or old-school workflows (like ours) are just not on their radar. They might drop features back in later… or drop them altogether? Hard to say, but judging by the radio silence, I wouldn’t hold your breath.
If I’m missing some magic workaround or config hack, someone PLEASE clue me in before I flip my desk. Otherwise, I’m sticking with the old Remote Desktop for now, kludgy UI and all. This “progress” makes me wonder if someone at Microsoft is secretly running a nostalgia department.
Yeah, I gotta admit, the backward logic of the Windows App not working as well on, well, Windows is some next-level stuff. I see what @mikeappsreviewer and @sterrenkijker said about the weird platform inconsistencies and I mostly agree, but honestly, I don’t buy the whole “all in on the cloud” excuse for leaving basic features on the cutting room floor. Half the world still uses plain RDP in small biz and home offices, and not everyone is itching to move everything to Azure.
What irks me most isn’t even the missing features—it’s the way the docs and updates tease the return of stuff like drive mapping or seamless clipboard, always “coming soon” but never here. It’s like waiting for Half-Life 3. And don’t even get me started on the “silent failures” where you just get nada, not even a useful error. At least the old Remote Desktop told you point blank what was broken.
Part of me wonders if they’re so obsessed with reimagining the UI and slapping on the Microsoft-y Fluent design that they totally forgot about people who need, you know, actual work to get done. And for all the talk about security, some of the “locked down” behaviors just break workflows without adding meaningful protection.
Hate to say it, but the real fix right now is just sticking with the legacy Remote Desktop app, warts and all. If Microsoft decides to retire that before the new Windows App catches up, it’ll be a straight downgrade for a ton of us. If anyone hears a peep from MS about classic feature parity, let us all know—but until then, guess we’re all riding this nostalgia train off the rails together.
Ask yourself: why would Microsoft release a “Windows App” on Windows that drops the ball on the most basic Remote Desktop features? If you guessed “because they’re desperate to push people into Azure Virtual Desktop,” congrats, you’ve won nothing except the privilege of muddling through awkward workarounds like the rest of us.
Here’s the real kicker: Remote Desktop features had decades to mature, and suddenly essential stuff—drive mapping, clipboard sync, and actual connection reliability—are “in review” or “coming soon.” Meanwhile, macOS, iOS, and even Oculus users are living in some alternate universe where things just work (seriously, who needs to RDP from VR goggles before a regular ol’ Windows PC?).
There are two angles here, both covered by others:
- The old school, “if it ain’t broke, don’t fix it” approach (see: legacy RDP client).
- And the “just wait, it’s all modern security and Fluent UI” crowd, which seems more excited about icons than actual function.
Pros of the ’ (the Windows App):
- Slick UI and some modern Azure integrations for cloud fans.
- Works well on non-Windows platforms, ironically.
Cons:
– Absolutely baffles with broken/missing core RDP features on Windows itself.
– “Silent failures” instead of error messages make troubleshooting a black hole.
– No clear roadmap for long-standing Remote Desktop holdouts.
Alternatives? You could stick with the crusty legacy app, as others have said. Or, like me, you could hedge your bets by keeping a good third-party client handy (think Royal TS or even mRemoteNG, which at the very least will tell you what’s broken).
Bottom line—until Microsoft stops treating staple RDP tasks as novelty cloud extras, the new Windows App is more pretty face than productivity hero. Proceed with very cautious optimism, and keep old tools handy for when “coming soon” once again means… not today.