My RDM crashes.

me too

我也遇到了同样的问题，当我试图打开第二个连接窗口时就会卡住，然后自动关闭

Hello,

Thank you for reaching out to Devolutions Support.

I attempted to recreate the issue, but with the information I have so far, I wasn’t able to.

Could you please provide the following details:
- The data source you are using
- The version of RDM you are on
- If possible a quick step-by-step guide on how to recreate the issue

This information would be very helpful for us to reproduce the issue on our end.

Best regards,

1 - Don't know what data source means.
2 - 2024.3.15.0 64-bit. latest version. it started only after I upgraded to the latest.
3 - Simple, open w windows RDP session and then try to open another one. RDM closes abnormally. Opening Linux sessions works;

I wanted to install the version again from fresh, but when I reinstalled it, all information was already there so I cannot have a fresh installation.
let me know how to delete all information and start fresh.

I'm using RDM for almost 5 years now, and now I cannot work with two windows sessions. and that means RDM is no longer a tool I can use, so probably I'll stop my subscription.

Joe

ok, I used local data source, and now i've managed to clean my machine and started from fresh.
tries using online data source. imported all my favotries. and the problem persists.
opening one windows rdp session works. trying to open another rdp session, and RDM crashes.

Hello,

Thank you for your follow-up. I tried to recreate the issue on my side but was not able to.
To help us investigate further, could you please check if there are any error logs or warnings in the Event Viewer after RDM crashes? Here's how you can do that:

1. Press Windows + R to open the Run dialog.
2. Type eventvwr and press Enter.
3. In the Event Viewer window, expand Windows Logs and select Application.
4. Look for any errors related to Remote Desktop Manager at the time of the crash and share the details with us.

This information could give us more insight into what's causing the problem.

Best regards,

Log Name: Application
Source: Application Error
Date: 27/10/2024 11:56:57
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: BABSOFT\joe
Computer: Joe-CTO.babsoft.co.il
Description:
Faulting application name: RemoteDesktopManager.exe, version: 2024.3.15.0, time stamp: 0x66e80000
Faulting module name: mstscax.dll, version: 10.0.27729.1000, time stamp: 0x46937feb
Exception code: 0xc0000409
Fault offset: 0x0000000000001d91
Faulting process id: 0x2374
Faulting application start time: 0x1DB2856633793CF
Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: c7f82706-0d23-4f4a-bcb7-75077c9602a1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-27T09:56:57.9150974Z" />
<EventRecordID>2679</EventRecordID>
<Correlation />
<Execution ProcessID="9904" ThreadID="8480" />
<Channel>Application</Channel>
<Computer>Joe-CTO.babsoft.co.il</Computer>
<Security UserID="S-1-5-21-65501096-312519704-984555049-1141" />
</System>
<EventData>
<Data Name="AppName">RemoteDesktopManager.exe</Data>
<Data Name="AppVersion">2024.3.15.0</Data>
<Data Name="AppTimeStamp">66e80000</Data>
<Data Name="ModuleName">mstscax.dll</Data>
<Data Name="ModuleVersion">10.0.27729.1000</Data>
<Data Name="ModuleTimeStamp">46937feb</Data>
<Data Name="ExceptionCode">c0000409</Data>
<Data Name="FaultingOffset">0000000000001d91</Data>
<Data Name="ProcessId">0x2374</Data>
<Data Name="ProcessCreationTime">0x1db2856633793cf</Data>
<Data Name="AppPath">C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\system32\mstscax.dll</Data>
<Data Name="IntegratorReportId">c7f82706-0d23-4f4a-bcb7-75077c9602a1</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>

Log Name: Application
Source: Windows Error Reporting
Date: 28/10/2024 11:46:45 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: MNABCBPG1B3
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: RemoteDesktopManager.exe
P2: 2024.3.13.0
P3: 66960000
P4: 230d
P5: 67247104
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d1140ca-8077-4e50-907e-89f5d9fdd243
Report Status: 524390
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-28T00:46:45.9594368Z" />
<EventRecordID>63427</EventRecordID>
<Correlation />
<Execution ProcessID="47900" ThreadID="43544" />
<Channel>Application</Channel>
<Computer>MNABCBPG1B3</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Bucket">
</Data>
<Data Name="BucketType">0</Data>
<Data Name="EventName">AppHangB1</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">RemoteDesktopManager.exe</Data>
<Data Name="P2">2024.3.13.0</Data>
<Data Name="P3">66960000</Data>
<Data Name="P4">230d</Data>
<Data Name="P5">67247104</Data>
<Data Name="P6">
</Data>
<Data Name="P7">
</Data>
<Data Name="P8">
</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">0d1140ca-8077-4e50-907e-89f5d9fdd243</Data>
<Data Name="ReportStatus">524390</Data>
<Data Name="HashedBucket">
</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

here for the same issue as well.. RDM's been crashing several times a day and not just after adding machines.. see above logs

Hello,

Thank you for providing the logs. Based on the information, it appears the crash is related to the mstscax.dll module, which is a component of the Microsoft Terminal Services ActiveX control used for Remote Desktop connections.

Could you confirm the full version of Windows you are currently using? Additionally, could you try running the command `sfc /scannow` as an administrator to see if it resolves the issue?

Best regards,

I have the same proble - after update to last versions

Nome da aplicação com falha: RemoteDesktopManager_x64.exe, versão 2024.3.15.0, carimbo de data/hora: 0x66e80000
Nome do módulo com falha: mstscax.dll, versão: 10.0.27729.1000, carimbo de data/hora: 0x46937feb
Código de exceção: 0xc0000409
Deslocamento com falha: 0x0000000000001d91
ID do processo com falha: 0x27B4
Hora de início da aplicação com falha: 0x1DB296E482494AD
Caminho da aplicação com falha: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager_x64.exe
Caminho do módulo com falha: C:\WINDOWS\system32\mstscax.dll
ID do relatório: ee193606-9c3b-461b-86e8-9379eaaf5a2f
Nome completo do pacote com falha:
ID da aplicação relativa ao pacote:

Edition Windows 11 Pro Insider Preview
Version Dev
Installed on ‎19/‎10/‎2024
Evaluation expires on ‎16/‎09/‎2025 0:16
OS build 27729.1000
Experience Windows Feature Experience Pack 1000.26100.29.0

running the sfc /scannow did not fix the problem.

Hello,

Thank you for providing the logs. Based on the information, it appears the crash is related to the mstscax.dll module, which is a component of the Microsoft Terminal Services ActiveX control used for Remote Desktop connections.

Could you confirm the full version of Windows you are currently using? Additionally, could you try running the command `sfc /scannow` as an administrator to see if it resolves the issue?

Best regards,

hey Carl,

I'm running Windows 11 Version 23H2 (OS Build 22631.4317)

just before I ran sfc /scannow this morning, RDM crashed again and the logs are below. I'm currently running RDM as of this writing and will see if it still crashes after the scan.

Log Name: Application
Source: Windows Error Reporting
Date: 29/10/2024 9:05:27 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: MNABCBPG1B3
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: RemoteDesktopManager.exe
P2: 2024.3.13.0
P3: 66960000
P4: 230d
P5: 67247104
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d1140ca-8077-4e50-907e-89f5d9fdd243
Report Status: 524390
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-28T22:05:27.3174756Z" />
<EventRecordID>63659</EventRecordID>
<Correlation />
<Execution ProcessID="12384" ThreadID="8332" />
<Channel>Application</Channel>
<Computer>MNABCBPG1B3</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Bucket">
</Data>
<Data Name="BucketType">0</Data>
<Data Name="EventName">AppHangB1</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">RemoteDesktopManager.exe</Data>
<Data Name="P2">2024.3.13.0</Data>
<Data Name="P3">66960000</Data>
<Data Name="P4">230d</Data>
<Data Name="P5">67247104</Data>
<Data Name="P6">
</Data>
<Data Name="P7">
</Data>
<Data Name="P8">
</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">0d1140ca-8077-4e50-907e-89f5d9fdd243</Data>
<Data Name="ReportStatus">524390</Data>
<Data Name="HashedBucket">
</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

Could you try setting "Enable API hooking" to Disabled in Settings / Sessions / Remote Desktop (RDP)? We would like to isolate if the issues you are seeing are related to this option or not.

https://docs.devolutions.net/rdm/kb/troubleshooting-articles/rdp-session-troubleshooting/#disable-rdp-api-hooking

thanks Sebastien. just did that and I'll continue to monitor

@joe4 As an aside, the Windows 11 Pro Insider Preview Dev channel is a pre-beta version of Windows. This version is not recommended for production use as stability issues can be more common.

Could you try setting "Enable API hooking" to Disabled in Settings / Sessions / Remote Desktop (RDP)? We would like to isolate if the issues you are seeing are related to this option or not.

https://docs.devolutions.net/rdm/kb/troubleshooting-articles/rdp-session-troubleshooting/#disable-rdp-api-hooking

hey Sebastien,

it unfortunately froze again

Log Name: Application
Source: Windows Error Reporting
Date: 29/10/2024 11:52:40 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: MNABCBPG1B3
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: RemoteDesktopManager.exe
P2: 2024.3.13.0
P3: 66960000
P4: 230d
P5: 67247104
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d1140ca-8077-4e50-907e-89f5d9fdd243
Report Status: 524390
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-29T00:52:40.0618216Z" />
<EventRecordID>63715</EventRecordID>
<Correlation />
<Execution ProcessID="15456" ThreadID="10948" />
<Channel>Application</Channel>
<Computer>MNABCBPG1B3</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Bucket">
</Data>
<Data Name="BucketType">0</Data>
<Data Name="EventName">AppHangB1</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">RemoteDesktopManager.exe</Data>
<Data Name="P2">2024.3.13.0</Data>
<Data Name="P3">66960000</Data>
<Data Name="P4">230d</Data>
<Data Name="P5">67247104</Data>
<Data Name="P6">
</Data>
<Data Name="P7">
</Data>
<Data Name="P8">
</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\Users\P816637\AppData\Local\Temp\WER.9b58c0e9-6ce8-4a0c-8dcb-8cd787405f46.tmp.version.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.21f98807-03af-4106-b087-f2a1caf6336c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.efbf2b81-35b8-425b-af8e-d96270b862a2.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a00e3613-4a9f-4311-b9d4-f3287fccff0a.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7a039bd-1f49-4e1e-8efc-f8d5413b3a64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a04115e6-90e5-4380-9a67-57f344641bcd.tmp.txt
\\?\C:\Users\P816637\AppData\Local\Temp\WER.3afe1ac4-6d89-409f-a459-743a83b77646.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1a6f3ad3-ff85-486b-bee0-6b44febb5ad6.tmp.xml
WERGenerationLog.txt</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_RemoteDesktopMan_5aaff1288e9af06648af6bd14f392a708bba482f_5e95f839_cab_a895b046-46e9-4e3a-bf49-060579a754f9</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">0d1140ca-8077-4e50-907e-89f5d9fdd243</Data>
<Data Name="ReportStatus">524390</Data>
<Data Name="HashedBucket">
</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

hey Sebastien,

I've got the MsRdpEx_RDM.log but unable to upload it. lemme know if there's any specific info from the logs you need.

Thanks!

@joe4 As an aside, the Windows 11 Pro Insider Preview Dev channel is a pre-beta version of Windows. This version is not recommended for production use as stability issues can be more common.

yes I know, but the windows version was updated 10 days before updating RDM and it still worked fine. After updating RDM things went south...

Just updated to the latest version. No Change.
Updated Enable Api Hooking, Still no change.

Joe

Hi,

Looking at the version of mstscax.dll (10.0.27729.1000) in the error reports, it corresponds to a Windows Insider Preview build. These builds can have regressions and bugs that never get fixed before the related changes make it to a stable release of Windows. In this case, the RDP ActiveX also causes similar crashes in mRemoteNG, which also uses the RDP ActiveX, just like Remote Desktop Manager: https://github.com/mRemoteNG/mRemoteNG/issues/2647

A workaround would be to install MSRDC and use it instead of the built-in RDP ActiveX which is affected by the problem:
https://docs.devolutions.net/rdm/kb/knowledge-base/msrdc-support-rdm/

Just to clarify: the problem isn't with Remote Desktop Manager. Microsoft obviously broke something into the RDP ActiveX DLL (mstscax.dll) in the recent Windows Insider Preview builds. MSRDC contains an out-of-box copy of the RDP ActiveX, and is likely unaffected by the same bug, so it can be used as a workaround.

Best regards,

A new Windows Insider Preview canary build came out today: https://blogs.windows.com/windows-insider/2024/11/06/announcing-windows-11-insider-preview-build-27744-canary-channel/

In the changelog, it says "Fixed an issue causing remote desktop connection (mstsc.exe) to crash in the previous flight.". I assume this is probably the bug that affected build 27729 previously. Can anyone confirm if the issue is gone with build 27744?

Unfortunately, the problem persists, at least for me. It's almost worse than before – now the application closes reliably when I try to open a second simultaneous connection. Before, it often closed, but not always.

It's not a production machine. :)

It looks like whatever Microsoft fixed for mstsc didn't cover the RDP ActiveX with multiple connections - mRemoteNG confirmed the crash remains on their side, and that manually copying mstscax.dll from a stable Windows build works around the issue. I've been trying to figure out how to report this to Microsoft, and I've been told users enrolled in the Windows Insider Program should be doing it themselves through the Feedback Hub. Have you reported the issue already? Can you see if others have reported the same?

I tried to submit a suggestion once, but I don't think it helped. It's more of a statistical analysis.

I like MSRDC though. If I understand it correctly, it's better than MSTSC in terms of functionality anyway. The disadvantage is the additional installation, but in my case it doesn't matter.

A user on the mremoteNG project reports that the crashes stopped with build 27754.

https://github.com/mRemoteNG/mRemoteNG/issues/2647#issuecomment-2490122981