FreeRDP: Unable to connect to an existing user session on the latest Windows

Describe the bug As long as a user is signed in (regardless of the session being in the disconnected or connected state), FreeRDP client is unable to connect to the user session. In order for FreeRDP client to connect, the user must be signed out.

Unable to reproduce on Windows 10 Version 1809 Build 17763.437. Able to reproduce 100% on Windows 10 Version 1903 Build 18362.295. (These are OS versions that I’ve attempted to connect to)

To Reproduce Steps to reproduce the behavior:

Use mstsc to connect to a user session
Disconnect from RDP (do NOT sign out)
Use FreeRDP client to connect to the same user session
See error (black screen) (Steps to get around the problem: if you sign the user out in step 2, then you will get the user session in step 3.)

Expected behavior Get the user session and be able to use the remote desktop.

Screenshots Just a black screen.

** Application details

Version of FreeRDP tried with the stable-1.1 build and the nightly build from 8/24/2019 (build 657)
Command line used wfreerdp.exe /u:username /p:password /v:ipaddress
output of /buildconfig N/A
OS version connecting to Windows 10 Version 1903 Build 18362.295 (server machine)
If available the log output from a run with /log-level:trace N/A

Desktop (please complete the following information):

OS: Windows 10 1809 Build 17763.437 (client machine)

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 25 (11 by maintainers)

Most upvoted comments

@yoonjm Ok, looks like you beat me (silly page refresh missing)

akallabeth on Sep 6, 2019

I have seen the exact same behavior using wfreerdp.exe with a Win10 1903 target. It also had the crash files with similar constent to the one that @yoonjm posted.

jacksondk on Aug 28, 2019

Yes, it works with mstsc.

There is nothing interesting in the logs. Log file generated from the failure case (RDPing into 18362.295) is identical to the one that is generated from the success case (RDPing into 17763.437).

Some additional information: I said it just results in a black screen, but sometimes, I get to the welcome screen where the circular loading symbol spins. But in the cases I get there, the display freezes immediately right away in the welcome screen. Also, if I already had an RDP session up and running with mstsc, I get kicked out of that session when I attempt to connect using a freerdp client.

Log file attached. log.txt

yoonjm on Aug 27, 2019