Prepare for the Remote Desktop client for Windows end of support

Not having start menu integration and not listing that as coming soon is an extreme concern, how long will we be able to use the MSI based app before it stops working all together? 

This one feature gap alone makes the windows app impractical in almost any enterprise, what would you want us to do? retrain the whole organization? why? 

Does Windows App support Windows server editions? MSRDC supports Server editions.

I just want a way to create desktop shortcuts for my users to be able to quickly connect to apps like back in the Remote App days. Why do they need to add more clicks to something that can just be a shortcut.

Why is Microsoft constantly pissing customers off with horrible UI changes?  Even if you do reach feature parity with the Remote Desktop client, all I'm going to hear from users is why are the icons so **bleep** big and they have scroll for miles to find the app they're looking for.  Even the list view is a disastrous waste of space.  Yeah, yeah favorites blah, blah, blah.  A totally unnecessary feature if the UI is designed efficiently.  

Does Windows App Support Remote Credential Guard now? This guidance states it doesn't work with the UWP app, but unsure if those limitations could still apply to Windows App since its in the msix container

WSLg, also from Microsoft, uses msrdc.exe as well and embeds it into WSL.

Really, I feel this is all the opposite direction most people want to go.  Enterprise customers generally do NOT want to deal with Store apps at all.  The lack of controls we have with the Windows Store makes it a poor choice for Enterprise customers.

This is a very poorly planned changed. MSRDC should not be deprecated if the Windows App does not have feature parity.

This is a catastrophic scenario for Devolutions and all of our customers. The built-in RDP ActiveX and mstsc lag behind MSRDC in terms of functionality for regular RDP connections. Things like RDP8.1 dynamic resizing introduced in Windows 8.1 are implemented in MSRDC but not mstsc. We have an integration with MSRDC and the RDP ActiveX it contains (rdclientax.dll) in Remote Desktop Manager, as it was often requested by our customers. Since MSRDC has a faster release cycle, bugs that find their way into mstsc are often "fixed" by switching to MSRDC.

https://blog.devolutions.net/2022/08/extending-the-microsoft-rdp-client-with-api-hooking/

https://blog.devolutions.net/2022/03/msrdc-is-now-supported-in-remote-desktop-manager/

The new Windows App ships a copy of MSRDC, but since it is packaged with an MSIX, we can't access msrdc.exe or rdclientax.dll directly. If Windows App had an MSI installer, we could at least adapt MsRdpEx (https://github.com/Devolutions/MsRdpEx) to load it from there.

I was at the RDP IO Lab in 2023, and discussed this directly with the RDP team: we need an official way to integrate with the out-of-box MSRDC core. Nothing has been done about this, and now you're literally making it impossible to even do an unofficial integration. This will kill the only third-party AVD support from a connection manager in the industry, since mstsc.exe does not support AVD.

Either backtrack on this decision, ship Windows App with an MSI installer, or allow third-party redistribution of MSRDC. We're fine with requiring that MSRDC be separately installed in order to use it, but this means having a package that is installed in a way that we can use the installation files.