Start a new topic

Issues with freeRDP

Hi there,

I'am using the Beta of RoyalTS V7. Sometimes when I try to connect on a server with freeRDP the complete application freezes and I have to force terminate it. The only thing you can see is a small bar in the left downer site of the window. For me it looks like a bug.



P.s. I configured the connection to use a SOCKS5 proxy.

Hi Daniel,

we have heard that on a handful systems the app is freezing sometimes but we weren't able to reproduce the issue on our systems yet. Maybe it's related to the target system and protocol version used. One thing we know from the feedback is that killing the wfreerdp.exe using task manager will "unfreeze" Royal TS. If we can somehow reproduce this issue, we can look into it.




We also experience the same issues with FreeRDP when it just hangs until we kill the process.

If you can share repro steps for us or more details (OS/RDP versions involved), we can try to reproduce this and see if we stabilize this.

Windows 10 (Version 21H2 OS Build 19044.2251).

Computer joined to Windows AD domain.

Brand new installation of RoyalTS version 7.0.11108 - Beta

Active plugin RDP Based on FreeRDP 7.00.11108.0

Initial connection opens fine, once window closed and  I try to reconnect - it hangs until I kill the wfreerdp.exe process. See screenshot below:


Hi Alexander,

thanks for the details. We did some tests and for a short period of time we were able to see a similar issue but as soon as we investigated further, we weren't able to repro it anymore. Can you always reproduce the issue? Or maybe you have repro steps which reliably reproduces the issue? Is it with every connection/server or just specific ones?

Not sure what's blocking the UI/app in this scenario. We will continue to look into it and hopefully we can figure out what's going on and fix or improve the issue.


Hi Stefan,

It happens randomly, I just launched RoyalTS this morning and it hanged on the first attempt to connect via freerdp plugin.

Hi Stefan,

Feel free to reach out directly if you need more info/logs/etc or access to check it out.



Updated to Royal TS 7.00.11221 - issue still persists.

Updated to Royal TS 7.00.20116 - no change. It keeps hanging.

Hi Alexander,

we still haven't figured out what could cause this. Can you send us a mini dump when that happens. Maybe we can figure out what's blocking the UI.



Stefan, how do I create a mini dump? Thanks

The easiest way would be to open the Windows task manager, go to the Details view, select wfreerdp.exe which hangs, right-click and select "Create dump file".

1 person likes this

Thanks, I have the dump now, where do I send?

I ran analyze on the dump file:

0:000> !analyze -v
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *


    Key  : Analysis.CPU.mSec
    Value: 2234

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 44122

    Key  : Analysis.IO.Other.Mb
    Value: 14

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 29

    Key  : Analysis.Init.CPU.mSec
    Value: 468

    Key  : Analysis.Init.Elapsed.mSec
    Value: 45456

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 91

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 1625320

    Key  : Timeline.Process.Start.DeltaSec
    Value: 10

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  wfreerdp.DMP





ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0


PROCESS_NAME:  wfreerdp.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.


00000084`c21df698 00007ff8`978a306e     : 0000024c`e8b6dbe0 00000000`00000000 00000000`00000000 0000024c`e8b6e790 : ntdll!NtWaitForSingleObject+0x14
00000084`c21df6a0 00007ff6`54b463be     : 00000000`00000000 00000000`0000000c 00000000`00000000 00000000`0000032c : KERNELBASE!WaitForSingleObjectEx+0x8e
00000084`c21df740 00007ff6`54ed8910     : 00000000`0000000a 00007ff6`54ac0000 00000000`00000000 00000000`0000000a : wfreerdp!RdpClientEntry+0x194e
00000084`c21df810 00007ff8`998d7614     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wfreerdp!smartcard_pack_read_cache_return+0x126b50
00000084`c21df850 00007ff8`99f226a1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000084`c21df880 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  wfreerdp+194e

MODULE_NAME: wfreerdp

IMAGE_NAME:  wfreerdp.exe

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_wfreerdp.exe!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release


OSNAME:  Windows 10

FAILURE_ID_HASH:  {1fa1ce24-e6ea-bbe3-d753-51fb72f71ce5}

Followup:     MachineOwner


Login or Signup to post a comment