Windows 10: MSTSC RDP crashes shortly after launch

Shortly after launching a remote app on a single computer other machines work just fine the program crashes. It shows that it is connected to the server then does not show the app and crashes.


Here is the info from the event viewer:

Faulting application name: mstsc.exe, version: 10.0.18362.752, time stamp: 0x64062c86

Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0

Exception code: 0xc0000374

Fault offset: 0x00000000000f92a9

Faulting process id: 0x2fb8

Faulting application start time: 0x01d62d48f044a33e

Faulting application path: C:\Windows\System32\mstsc.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: dee6d851-f8de-421c-a7ec-8d79380c8ac9

Faulting package full name:

Faulting package-relative application ID:

_________________________________________________________________________

And:

Fault bucket 2081841460730338595, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0



Problem signature:

P1: mstsc.exe

P2: 10.0.18362.752

P3: 64062c86

P4: StackHash_a93f

P5: 10.0.18362.719

P6: 64d10ee0

P7: c0000374

P8: PCH_3F_FROM_ntdll+0x000000000009CC14

P9:

P10:



Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF5DA.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF752.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF762.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF772.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF792.tmp.txt



These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_372ceec8cb2e794ff4c25976c010cedec6be6_564341b6_28c6c4f9-7099-4eff-a4e8-87ea74a2d1ff



Analysis symbol:

Rechecking for solution: 0

Report Id: 0211195b-a1ef-4f43-a0eb-02eb84c59ba8

Report Status: 268435456

Hashed bucket: 464a66b7afcb329bace42fc749831d23

Cab Guid: 0

_____________________________________________________________________________


Steps I’ve taken:

1. Removed 3 recently installed updates
2. Checked in event viewer for reason codes for the crash
   1. Googled two of them and found one resolution was to:

i. regsvr32.exe /u ntdll.dll this will uninstall the file

ii. regsvr32.exe ntdll.dll and press this will reinstall the file.

1. Logged into my own account on computer
   1. Opened remote application
   2. It crashed the first time
   3. It crashed the second time
   4. It worked the third time through the sixth times.
2. Reopened it on the local profile

1. 1. It crashed and would not successfully open.
2. After recreating the profile, I am briefly able to see the app and type some text to log into it the actual application, but it crashes again.

:)

 

mstsc vs rdp

hi

I wish to buy a new laptop with windows 10,

I need to communicate with a remote server, now I am using MSTSC and I was told that there is another option, app called RDP,

I will appreciate to know if they are the same considering speed system recourses etc. and is there any limitation regarding operating system to work smoothly with them.

regards

 

Unable to launch applications in RDP session

Issue: User is unable to launch applications when connected to a device through RDP

To clarify:

RDP connection itself is successful. User is can access device. But when user clicks an application, it does not launch.

User IS able to launch applications when signed into destination device directly.

Other users are not encountering issues opening applications when connected via RDP on the same devices.

Issue seems to occur only on this users specific profile.

Any suggestions?

 

CLI mstsc errorlevel

I have an issue trying to connect to a remote system with mstsc. Occasionally it times out. I have a rough outline of a decent bat to try to connect, then try again if mstsc fails. The issue that's complicating matters is that once mstsc is executed even
if it fails to connect I get errorlevel 0.

As an experiment, I tried to connect to a non-existent system. I got the popup re: Remote Desktop can't connect to the remote computer for one of these reasons: but the bat thought it was successful. As an experiment I tried a more direct test with the
test code below from my beta bat, which displayed IT SAYS IT DID WORK.

start /WAIT mstsc %srv%.rdp /h:1280 /w:1024 /v:%srv% /prompt && echo IT SAYS IT DID WORK

if I tried the reverse, it did NOT return the expected error message.

start /WAIT mstsc %srv%.rdp /h:1280 /w:1024 /v:%srv% /prompt || echo IT SAYS IT FAILED

Of course I also echoed the errorlevel, and it's 0 whether or not I actually connect/log in.

Am I missing something? Does anyone have a non-powershell method to actually determine if mstsc fails?