Mstsc.exe Application Error 1000
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site mstsc ntdll.dll error About Us Learn more about Stack Overflow the company Business Learn more about remote desktop connection has stopped working windows 7 ntdll dll hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is remote desktop connection has stopped working server 2012 a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The
Remote Desktop Has Stopped Working Windows 10
best answers are voted up and rise to the top Remote Desktop Connection works fine but RDP file crashes up vote 1 down vote favorite We don't want to give users remote desktop access to the server so we have published applications on the surver and created RDP files that the users run. This works great on every user's pc with the exception of one machine. remote desktop stopped working windows 7 Each time this one machine runs the RDP file it crashes after about 10 -15 seconds. Here is the error message from the event viewer: Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 07/18/2012 Time: 10:07:26 AM User: N/A Computer: (X'D OUT) Description: Faulting application mstsc.exe, version 6.1.7600.16722, faulting module ntdll.dll, version 5.1.2600.6055, fault address 0x00010ef4. The weird part is... we can run the Remote Desktop Connection from the start menu and it connects to the server just fine. Has this happened to anybody and what did you do to fix it? remote-desktop share|improve this question asked Jul 18 '12 at 16:07 Michael Riley - AKA Gunny 186118 migrated from serverfault.com Jul 18 '12 at 17:20 This question came from our site for system and network administrators. add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted Solved the problem by removing an invalid Printer on the client machine. share|improve this answer answered Jul 19 '12 at 20:53 Michael Riley - AKA Gunny 186118 add a comment| up vote 0 down vote I have seen this error a couple of times with mstsc.exe. I
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 21:56:54 GMT by s_wx1062 (squid/3.5.20)
Guide to Using Google Chromewindows-10-fast Home > How I fixed the "Remote Desktop connection has stopped working" error in Windows 8.1 How I fixed the http://www.fixedbyvonnie.com/2014/12/fixed-remote-desktop-connection-stopped-working-error-windows-8-1/ "Remote Desktop connection has stopped working" error in Windows 8.1 Posted on December 19, 2014 by vonnie — 55 Comments ↓ Let me tell you a story about a http://serverfault.com/questions/704650/remote-desktop-connection-stops-working-when-connection-is-closed troubleshooting incident I encountered a few weeks ago. I live in New York City. The other day I was trying to use the Microsoft Terminal Services Client (mstsc.exe) to remote desktop remotely connect to a PC in Los Angeles, California but for some inexplicable reason I couldn't connect. Well that's not entirely true; the client actually crashed on connect. After entering my credentials and clicking Connect, the remote computer would log me in but then would invariably flash and crash with this troublesome message: The Remote Desktop connection has stopped working. has stopped working The error is pretty lame if you ask me. Here's the thing: it's already obvious that the Remote Desktop connection stopped working because the client was completely locked up. Therefore, why does Microsoft need to rub it in my face by telling me what is already undeniably true? So yes, I was perturbed. I tried immediately connecting again (just to see if the error would go away) but I got the same result. Rebooting didn't fix anything so I asked a friend to attempt to connect to the same remote computer. Guess what? He didn't have any issues. He connected fine and looked at me like I was stupid. So there was something on my computer that was causing the Remote Desktop application to quit unceremoniously. But what was it? When I looked in the event logs I could see mstsc.exe was the faulting application name. But I already knew that. There was also something in there about vorbis.acm. Faulting module name: vorbis.acm How odd… what is that? Wait a second… I thought to myself: Vorbis
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Remote Desktop Connection stops working when connection is closed up vote 1 down vote favorite I just started using a new HP laptop with Windows 8.1 using the same domain account I've used for years. I can remote desktop to any server / VM on the local network, however when I disconnect the session from my laptop (close the window) the RDP client crashes with the typical "has stopped working" message. This only happens with RDP connections to Windows 8 / Server 2012. Windows XP and Server 2003/2008 doesn't cause this. In the event log on my laptop I get the following error (Event ID 1000): Faulting application name: mstsc.exe, version: 6.3.9600.17415, time stamp: 0x5450434f Faulting module name: ntdll.dll, version: 6.3.9600.17736, time stamp: 0x550f4336 Exception code: 0xc0000005 Fault offset: 0x000000000003d85e Faulting process ID: 0x2164 Faulting application start time: 0x01d0ba5205a5c537 Faulting application path: C:\Windows\System32\mstsc.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 9f129310-2645-11e5-826b-3ca82a837a3a Faulting package full name: Faulting package-relative application ID: Googled a lot and only found instances where the RDP connection failed when trying to connect. Some solutions involved unchecking remote printers, audio, etc which I also tried. As a final note, RDP works so it's not a major problem, just irritating having to constantly close the "has stopped working" boxes as I RDP quite a lot. remote-desktop rdp windows-8.1 share|improve this question edited Jul 9 '15 at 15:08 asked Jul 9 '15 at 14:54 Andrie Schoombee 913 Are you saying when you disconnect your session on the server (and not your desktop) crashes? Or do you mean RDP crashes? Please provide more info. Are you using RDP on the local network? Or are you using it remotely over VPN? –CIA Jul 9 '15 at 14:59 On local network, when I close the session from my laptop (client side) remote desktop crashes. I updated the question. Also, I've used RDP in the past on Windows 8.1 without problems, it's only on the new HP l