-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win 11 mstsc.exe doesn't send RemoteFX capability #2400
Comments
This seems to be quite an issue for me. When connecting to the remote desktop from my Win 11 laptop, dragging windows etc is super slow. Also the solution of setting the connection speed to Lan as suggested in #2136 doesn't help. However when I try the same with my Win 10 desktop, changing the setting to Lan results in a performance boost while having it set to WLAN gives similar results on both systems. It seems to me like the issue described by @metalefty could cause the symptoms I see. |
@TuNeXiZz Yes, the issue seems to be caused due to this. @jsorg71 Jay, can we add Image RemotFX? I'm not very familiar with RemoteFX but as far as I read MS documentation, Image RemoteFX has little differences from (Video) RemoteFX. It will take a while until we implement GFX. I think some mitigation is needed. |
@metalefty I can look into this. I'm guessing that most of what we already have makes this possible... |
After #2400, codec GUID is recorded on the log. The Win11 client sends only 2 codecs:
2744CCD4-9D8A-4E74-803C-0ECBEEA19C54 is for Image RemoteFX. So we need to implement Image RemoteFX capability to reinstate performance with Win11 client. |
+1 Indeed, a Win10 client sends 3 codecs and the performance is good:
But with Win11, only 2 are sent:
And no RFX is used which affects the performance |
Try going to the settings described here: stascorp/rdpwrap#810 AVC444v2 wasn't working on my Windows 11 install until I went there as well. This is keyed for AVC444, but there are RemoteFX settings too. |
Started initial implementation: #2789 |
As far as I read the specification [MS-RDPRFX] the difference between Image RemoteFX vs Video RemoteFX is:
@jsorg71 What do you think? So it is much easier to implement than GFX and easier to backport to v0.9. |
While working on this, I found an issue that seems to be a FreeRDP bug. |
Just for record my development progress. Windows 11 mstsc.exe Connecting to xrdp with Image RemoteFX codec.
Here is the dump of
|
Thank you for working on this! This is important to my work because I spend much of it in RDP and the lag is awful. I downgraded to Windows 10 because of this problem. Thanks a lot Microsoft… |
@metalefty @FrederickGeek8 In the meantime on Windows 11, I'm using a wfreerdp.exe FreeRDP client downloaded from here: (linked to from https://github.com/FreeRDP/FreeRDP/wiki/PreBuilds) The performance is not as good as Win10 client, but it's much better than the lag when using the Win11 client. Make sure you call wfreerdp.exe with /rfx |
WIP pull requests: It's really WIP and not working yet. |
For the record:
|
I'm using this client: https://apps.microsoft.com/detail/9WZDNCRFJ3PS?hl=en-US&gl=US It seems to perform better than Windows 11 mstsc.exe and wfreerdp Note: MS does not develop that app anymore, but it's a good alternative while waiting for Image RemoteFX support |
Thank you guys for the information about other clients! We're working on implementing another efficient codec compatible with Win11. Use other clients such as FreeRDP for the time being as a workaround. |
BTW, running the latest xrdp versions I seem to be getting RFX Pro codec (from xrdp.log): xrdp_encoder_create: starting gfx rfx pro codec session which gives good performance when using Microsoft Remote Desktop client |
Yes, we have switched to RFX Pro from classic RFX. This issue can be closed now. |
Win 11
Win 10
The text was updated successfully, but these errors were encountered: