Problème d'ouverture de session TSE

Bonjour,

Le problème survient après l'installation de ces deux mises a jour sur Windows 11 :



J'ai fais installé ces patchs a mon collègue et depuis il a le même problème que moi.

Merci,

I confirm after deleted the KB5030219 RDM works fine. Can you developp a new version compatible with this Microsoft Patch ?

Hello Neohara,

Thank you for contacting us on that matter.

Could you tell me if you open your session By embedded or external display?
Could you tell me which VPN you are using?

Could you try this with a portable version of RDM?
To do so, you will need to do the following:

1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmbin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe
5- Connect to your data source

Best regards,

Hi,

I'm using external display.
I'm using Forticlient VPN but it happen even without VPN object

I Have tryed the portable version and it don't works with the Microsoft KB installed (KB5030219)

Regards,

Hi,

I have KB5030219 installed on my system (Windows 11 22H2) and sessions using the RDP ActiveX or mstsc in external mode still work, and I have two external displays.

First, can you try disabling RDP API hooking (don't forget to restart RDM) to see if it resolves the issue?
https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking

Second, if disabling RDP API hooking doesn't help, re-enable it, but this time, enable the RDP logs provided by the RDP API hooking, which helps us gain a better understanding of the Microsoft RDP internal behaviour:
https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking/#microsoft-rdp-logging

Last but not least, you can also install MSRDC (https://learn.microsoft.com/en-us/azure/virtual-desktop/users/connect-windows) and modify your RDP connection entry to use it instead of the built-in RDP client (Advanced tab, change "RDP Version" to "MSRDC"). Sometimes Microsoft introduces regressions in the built-in RDP client, but since MSRDC is shipped out of box, it often works where mstsc doesn't: https://blog.devolutions.net/2022/03/msrdc-is-now-supported-in-remote-desktop-manager/

Best regards,

Hi,

I have disabled RDP API hooking and i'm able to connect now.
I have changed again the parameters on Default and it's keep working.

Regards,

Hi,

Thanks for giving it a try - can you try re-enabling RDP API hooking with the logs, reproduce the issue, and then send the logs to support@devolutions.net with a link to this thread? I would like to investigate the issue and get it fixed for the API hooking, such that you wouldn't need to disable it.

Best regards,

Hi,

Sorry but as i said i have already Re-enabled the API Hooking and now it works.
I don't know why it working just with a disable / enable. So i'm not able to reproduced the issue.

Regards,

Hi,

Fortunately I have a colleague for which the issue would occur consistently, so I could write a fix + test it. RDP API hooking should work again with the fix coming up in the next build (2023.2.29).

Best regards,

Hi,

same issue here, once KB5030219 has been removed it works again.
Any Ideas when 2023.2.29 will be released?

Regards

Hello,

Version 2023.2.30.0 is now available.
Could you update your RDM to the latest version and tell me if you still have this issue?

​​​​​​​Best regards,

Hi,

I've installed the update, the issue is gone and everything works as expected.

Thanks for the fast fix and the new release. It is really great to see that issues raised in the community do make it to the product. This is realy great and sadly not natural for all vendors.

Best Regards.

Hello Benjamin,

Thank you for this feedback.

I will let the developer know this works with the latest version.

Best regards,