Remote Desktop crashes on launch.

Hi all,
I'm stuck as to why I'm getting this problem: when I launch Apple Remote Desktop, it crashes right away. I trashed the old ARD app, emptied trash, rebooted my Mac, installed ARD 3 from CD, updated ARD 3 to the latest version available today, repaired permissions on my local HD using Disk Utility, but no change.
In Console, I get:
09/04/30 17:56:20 com.apple.launchd[175] ([0x0-0x2c02c].com.apple.RemoteDesktop[400]) Exited abnormally: Bus error
And also:
09/04/30 17:56:32 com.apple.launchd[175] ([0x0-0x2d02d].Remote Desktop[407]) Exited abnormally: Bus error
Any ideas?

You might try removing the copy of ARD you've installed using the instructions here and reinstalling. Make sure you update to the latest version before you attempt to launch ARD for the first time, particularly important if your disk of ARD installs a version prior to 3.2.
Hope this helps.

Similar Messages

Windows 10 Remote desktop crash

Almost every time when connecting to W10 Preview build 9860 the remote desktop crashes with the following message:
Faulting application name: svchost.exe_TermService, version: 6.4.9860.0, time stamp: 0x5436329a
Faulting module name: rdpcorets.dll, version: 6.4.9860.0, time stamp: 0x543626df
Exception code: 0xc0000005
Fault offset: 0x000000000002b4c9
Faulting process ID: 0x3e8
Faulting application start time: 0x01d00ef1ef145db3
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: C:\Windows\system32\rdpcorets.dll
Report ID: ca08b2a1-7ae7-11e4-95fd-0023549b70e3
Faulting package full name:
Also some services werde stopped due to this crash, like cryptsvc, workstation and others..
The connection was established from Windows 8.1. Any Solutions available?

What Remote Desktop options have you chosen on the client (i.e., system where you're making the connection from) when making the connection? Have you tried varying them?
For what it's worth, I seem to be able to make a remote desktop connection to my Win 10 TP 9879 test system just fine. In my case I happen to be making the connection at the same screen size (1920 x 1200 pixels) as my local console uses.
Also, how are you breaking the connection? Are you selecting "Disconnect" on the remote system, or are you just closing down the Remote Desktop application? That could make a difference.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Remote Desktop Crashes When trying to log-in after changing password on the remote computer

Hi.
I use cisco VPN to connect to my work computer.
I can use RDC to connect to any computer on home network without issue.
Yesterday I changed to password on my work computer and now every time I try to log from my home computer RDC crashes.
I've disabled printing/clipboard on local devices and resourses, and I've deleted all the RDC cache files on the computer but I continue to have the same issues.
please help
Faulting application name: mstsc.exe, version: 6.1.7601.18540, time stamp: 0x53c72529
Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b864
Exception code: 0xc0000374
Fault offset: 0x00000000000bf922
Faulting process id: 0x44c
Faulting application start time: 0x01d078d866a9ba25
Faulting application path: C:\Windows\system32\mstsc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 65a988c9-e4cc-11e4-8a77-f46d04eedf8b
http://answers.microsoft.com/en-us/windows/forum/windows_7-winapps/remote-desktop-crashes-when-trying-to-log-in-after/cc45b7be-62ee-4f83-b50b-db028ee32a7f

Hi hg,
I didn’t found relevant settings in remote desktop connection manager, I checked the “Use multiple monitors when necessary” under tools->options, but seems like it is used for span a full screen over multiple monitors. For now I’d suggest figuring out
why your remote session keeps crushing.
I suspect the crash is not related to password changing, similar cases normally occurs after some local device driver, please try to disable the local printer in Remote desktop connection local resources first.
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote Desktop crashes when disconnected on Lenovo Carbon X1

Hello everyone,
We ordered about 10 new Lenovo Carbon X1 Touch (Model 20A70037US) machines at work and all seem to suffer from a similar issue. If an RDP (Remote Desktop) connection either times out or is closed for any reason, the remote desktop application crashes. This is incredibly annoying as we are a cloud based software company and regularly have multiple remote desktop session up at all times. All windows and lenovo updates are up to date. My Surface Pro 2 with the same Windows 8.1 pro OS and it doesnt have this problem. Any ideas?
Thanks,
Steve
Solved!
Go to Solution.

Click on someotherguy then look for "Send this user a private message" in small print in the mid/upper right of the page.
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

MS Remote Desktop crashes Mac OS X when trying to add a certificate

As written in the headline, when trying to permanently add a certificate, the window where I am supposed to enter my password produces the rainbow wheel of doom.
Steps to reproduce:
- Open MS Remote Desktop 8.0.8 (Build 25010)
- Connect to a server
- in "verify certificate", press "show certificate", then tick "always trust...."
- click "continue"
- password window opens, Mac crashes.
Steps to avoid the crashing:
- instead of "show certificate", just press "continue" - it works fine, it just doesn't store the certificate.

Hi,
The version 8.0.9 is released, please try the latest one and see how it works.
https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417
Best Regards.
Jeremy Wu
TechNet Community Support

Remote Desktop crashes windows pc - HELPPPPP

I have white macbook (dec 08) and I use the microsoft remote desktop connection for mac to connect to my xp machine. It always reboots my xp and causes it to have a serious error. I can connect most of the time but it does this once or twice per day. Any ideas?

Since RDC and your PC are not Apple products, please post your quesiton on Microsoft's own forums for their Mac products, as Apple discussions only provide support for Apple products:
http://www.officeformac.com/productforums

PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html)
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Windows 8.1 pro Remote App crashes connecting to 2012 Remote Desktop Web Access published application

Using 2012 Remote Desktop Web access to gain access to published applications. The workstation was a Windows 8.1 (home) upgraded to Windows 8.1 Pro with the Media Center add on. Launching the url to the login page for the RDW works fine. When the app is
clicked on to launch the Remote App crashes. How do I get it to properly connect. Other Windows 8.1 pro workstations work. Although none were upgraded from the 8.1 (home) Here is the event.
Faulting application name: mstsc.exe, version: 6.3.9600.16384, time stamp: 0x5215e2b5
Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x530895af
Exception code: 0xc0000005
Fault offset: 0x0000000000065e8e
Faulting process id: 0xab4
Faulting application start time: 0x01cf5f2ed029e83f
Faulting application path: C:\Windows\System32\mstsc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 21a471d6-cb22-11e3-8263-a0886933dd25
Faulting package full name:
Faulting package-relative application ID:

More info.
The computer is brand new HP.
Windows 8.1 pro with media center
processor Intel i7-4700mq - 12gig ram -64bit
Full windows touch support with 10 touch points
The computer is connecting to a 2012 Server hosted on Microsoft's Azure platform. Trying to access applications hosted by this server with Remote Desktop Web services. The computer can RDP using just the mstsc.exe to other computers and to the server with
no problem.
The computer presents the following msg box Body: Remote Desktop Connection has stopped working. I have tried the following to resolve this and narrow the scope:
-Created a new user account for the computer with admin rights, rebooted and logged in as the new user.
-Tried a different user account for the portal, that does work. The user does not show up as connected.
-All MS updates were loaded.
-Added these changes to the registry to keep alive the connection: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Gateway\Transports\Rpc-----HttpKeepAliveTimeout=dword:00000001
And HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client----RDGClientTransport=dword:00000001
Loaded this update http://support.microsoft.com/kb/2919394/EN-US
-Removed all printers
-Removed Antivirus
-Added the server to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default
-Disabled everything in MSCONFIG startup
-Ran sfc /scannow as administrator - no integrity violations
Any suggestions?

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

Windows 8 crashes when trying to connect to a Remote Desktop or a VPN

Hello,
When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network
machine).
Useful PC specs:
- i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board)
> All latest drivers and Windows updates installed.
> Ran Memory Diagnostic. No errors.
Event Log:
Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a
Exception code: 0xc0000005
Fault offset: 0x00000000000027ee
Faulting process ID: 0x994
Faulting application start time: 0x01cdf16f9b46e882
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\DUI70.dll
Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a
Faulting package full name:
Faulting package-relative application ID:
WinDbg: (RDP Crash dump with procdump)
Loading unloaded module list
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(994.1118): Access violation - code c0000005 (first/second chance not available)
dui70!DirectUI::Element::_SetValue+0xe:
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
0:000> .ecxr
rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000
rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0
rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000
r8=0000000000000001 r9=000000989f3afa28 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=00000098a1d29401
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010200
dui70!DirectUI::Element::_SetValue+0xe:
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
0:000> !analyze -v
* Exception Analysis *
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
FAULTING_IP:
dui70!DirectUI::Element::_SetValue+e
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
DEFAULT_BUCKET_ID: NULL_POINTER_READ
PROCESS_NAME: mstsc.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
dui70!DirectUI::Element::_SetValue+e
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx]
MOD_LIST: <ANALYSIS/>
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
FAULTING_THREAD: 0000000000001118
PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ
LAST_CONTROL_TRANSFER: from 000007fec5be7db8 to 000007fec5be27ee
STACK_TEXT:
00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe
00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98
00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689
00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e
00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20
00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37
00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69
00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2
00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66
00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135
00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8
00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56
00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7
00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242
00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc
00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113
00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56
00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b
00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151
00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc
00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310
00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b
00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159
00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5
00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4
00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af
00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f
00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104
00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc
00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6
00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20
00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19
00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7
00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219
00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113
00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56
00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69
00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168
00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12
00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec
00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7
00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9
00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63
00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135
00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8
00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56
00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72
00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a
00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b
00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695
00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f
00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375
00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dui70!DirectUI::Element::_SetValue+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dui70
IMAGE_NAME: dui70.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 50108e6a
FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue
BUCKET_ID: X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
Followup: MachineOwner
Any ideas what could be the problem and how to resolve this?

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.
I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that
provides a program that'll hash the password for you. I used it so I can say its safe:
http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/
I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for
those in a bind this will work for you.
This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

Remote Desktop to servers crashes on Windows 8.1 Pro

Hi All,
I have done a search for this issue previously, but have been unable to find any information relating to my specific issue.
I have a Windows 8.1 Lennovo workstation with a pretty fresh install, and about 50% of the time I connect to our Windows 2003/2008R2 servers using remote desktop connection, it hangs, and tells me it has stopped responding.
I then have to force close the application and try again.
Having a look in the event viewer, I can see the below entries:
First, an event ID 1001, which is Windows Error reporting, containing the below info:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0
Problem signature:
P1: mstsc.exe
P2: 6.3.9600.16384
P3: 5215e2b5
P4: bced
P5: 134217729
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\edmonds\AppData\Local\Temp\WERB565.tmp.appcompat.txt
C:\Users\edmonds\AppData\Local\Temp\WERB576.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\edmonds\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_mstsc.exe_85bb93ec22754eb0631313fedba5dc3f456c90_4012f314_1a43c12d
Analysis symbol:
Rechecking for solution: 0
Report ID: ed4f9264-425c-11e4-be89-00173f416a8b
Report Status: 97
Hashed bucket:
This is followed by id 1002, which is an application hang, containing the below info:
The program mstsc.exe version 6.3.9600.16384 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 18d8
Start Time: 01cfd6693706de0c
Termination Time: 16
Application Path: C:\WINDOWS\system32\mstsc.exe
Report Id: ed4f9264-425c-11e4-be89-00173f416a8b
Faulting package full name:
Faulting package-relative application ID:
Interestingly enough, I had the same issue on my previous Fujitsu PC, which was also running Windows 8.1 Pro x64. I suspect it is some application I have installed on the machine causing the issue, but I don't have anything unusual installed.
If the above sheds any light on this, I will thank you in advance for any advice you can offer.
Thanks
Eds

Hi,
According to your description, since system is just fresh installed, it should not other application cause this problem. It is most probably caused by Certificate or Firewall problem, please try to disable Firewall or upgrade your RDP Certificate for test.
Certificate Requirements for Windows 2008 R2 and Windows 2012 Remote Desktop Services:
http://blogs.technet.com/b/askperf/archive/2014/01/24/certificate-requirements-for-windows-2008-r2-and-windows-2012-remote-desktop-services.aspx
In addition, for RDP client crash problem, I would like to suggest you follow Andre's suggestion in the link below to colect RDP crash dump file, then upload the dump file to your OneDrive and post the sharing link here.
http://social.technet.microsoft.com/Forums/systemcenter/en-US/07b758db-7bba-4624-9bb4-d51b5e95e64a/windows-81-rdp-crashes-very-frequently-after-upgrade-from-windows-8?forum=w8itpronetworking
Roger Lu
TechNet Community Support

Apple Remote Desktop asks to setup every launch

I was trying to fix the crashes I was having running UNIX commands and deleted everything Apple Remote Desktop related except the app itself.
Now, everytime I open the app - it asks to be setup.
Anyone else having this issue? Anyone know of a fix?

Remote Desktop will do that if you are logged in with a user that does not have admin privileges.

Remote Desktop Services Manager Hangs / Crashes

Hi,
I have windows server 2008 R2 based remote desktop environment. When i access remote desktop services manager to manage domain users session, it hangs / crashes. I am not unable to add any other computer to manage as well. Same was working fine in Windows
server 2003.
Any valuable suggestion????
Regards
Rox_Star

Hi,
As a test, please create a new domain admin user account, log on to the server with it, and then open RDS Manager. Do you see the same issue with the new account?
Thanks.
-TP

Remote Desktop MAC version 8.0.5 crashing when opening format panel in Excel

Remote Desktop MAC version 8.0.5 crashing when opening a format panel in Excel. Attempt to reconnect via RDC do not work until you log into Windows direct and close the formatting window. I'm running Windows 7 Pro, Service Pack 1 and using Microsoft
Remote Desktop version 8.0.5 on a Mac running OS X 10.9.2. Reproduced error 3 times. Has also twice caused Excel to crash, so error does seem specific to the Windows environment and/or interaction with RDC (i.e. - not Mac related).

Hi,
Would you please provide us the log file for check after issue occurs.
Microsoft Remote Desktop -> About Microsoft Remote Desktop -> Send log via email -> Copy and paste the log here.
Thanks.
Jeremy Wu
TechNet Community Support

Crashing Remote Desktop while using Excel

This will crash remote desktop application.
On remote machine with Excel try this:
- open existing excel workbook or create new one
- right click - add comment
- right click on outside of comment box (grayed field) - colors and lines - fill - color - click on drop down combo box
that's it.
Host machine macbook pro 13 retina late 2013, os x mavericks 10.9.2
remote machines affected Windows
Server 2003, Windows Server 2003R2, Windows Server 2008

Here you go:
[2014-Mar-12 10:49:41] RDP (0): Final rdp configuration used: screen mode id:i:0
desktopwidth:i:1600
desktopheight:i:900
use multimon:i:0
session bpp:i:16
full address:s:192.168.1.167
audiomode:i:2
username:s:domain\user
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com"font-family:Monaco;font-size:13px;line-height:normal;" />bookmarktype:i:3
use redirection server name:i:0
[2014-Mar-12 10:49:41] RDP (0): --- BEGIN INTERFACE LIST ---
.... deleted by myself .....
[2014-Mar-12 10:49:41] RDP (0): --- END INTERFACE LIST ---
[2014-Mar-12 10:49:41] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Mar-12 10:49:41] RDP (0): client version: 8.0.24308
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Mar-12 10:49:42] RDP (0): Resolved '192.168.1.167' to '192.168.1.167' using NameResolveMethod_DNS(1)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Mar-12 10:49:42] RDP (0): Exception caught: Exception in file '../../librdp/itotlayer.cpp' at line 847
User Message : Security negotiation Error: NotAllowed(2)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Mar-12 10:49:42] RDP (0): Resolved '192.168.1.167' to '192.168.1.167' using NameResolveMethod_DNS(1)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Mar-12 10:49:42] RDP (0): **** User ACCEPTED connection to basic security host
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Mar-12 10:49:42] RDP (0): Protocol state changed to: ProtocolActive(5)

Remote Desktop crashes on launch.

Similar Messages

Maybe you are looking for