Mstsc.exe Error Windows 7
Contents |
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 "Remote Desktop connection has remote desktop connection has stopped working windows 10 stopped working" error in Windows 8.1 Posted on December 19, 2014 by
Remote Desktop Has Stopped Working Windows 10
vonnie — 55 Comments ↓ Let me tell you a story about a troubleshooting incident I encountered a few remote desktop stopped working windows 7 weeks ago. I live in New York City. The other day I was trying to use the Microsoft Terminal Services Client (mstsc.exe) to remotely connect to a PC in Los
Remote Desktop Connection Has Stopped Working Windows 7 Ntdll Dll
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. The error is pretty lame if you ask me. Here's faulting module name ntdll.dll remote desktop 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… vorbis… where have I heard that before? Isn't that an audio codec or something? I started Googling around and noticed t
computer regularly. This has worked flawlessly for months. Suddenly I started to experience that Remote Desktop would crash whenever I clicked on a folder in Windows Explorer on the remote
Remote Desktop Connection Has Stopped Working Server 2012
computer. Very strange. What had changed to suddenly cause this? The Application log
Remote Desktop Crashes Windows 10
in the Windows Event Log showed the error was related to the remote audio functionality. Apparently, Remote Desktop Connection is remote desktop crashing windows 10 using the Ogg Vorbis ACM codec for remote audio, and this was related to the crash on my local Remote Desktop Connection client. Faulting application name: mstsc.exe, version: 10.0.10049.0 Faulting module name: vorbis.acm, version: http://www.fixedbyvonnie.com/2014/12/fixed-remote-desktop-connection-stopped-working-error-windows-8-1/ 0.0.3.6 Exception code: 0xc0000005 Fault offset: 0x0000000000001f4f Faulting process id: 0x2478 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\system32\vorbis.acm The Fix and the Workaround I recently installed FL Studio by Image-Line for music production. As it turns out, this was the culprit that caused the issue to appear. Because FL Studio installs a copy of vorbis.acm file into C:\Windows\System32, this interferes with Remote Desktop Connection. The fix: https://tommynation.com/fix-remote-desktop-connection-stopped-working-error/ Renaming vorbis.acm in C:\Windows\System32 fixes the issue on 64-bit Windows. The file The permission The fix Note: The file is also present in C:\Windows\SysWOW64 on 64-bit Windows, but didn't need to be renamed on my system for this fix to work. If you can't live with this fix for some reason, you can also try the following workaround: The workaround: Disable remote audio playback in Remote Desktop Connection settings. Click settings Disable the audio That's it, folks! Please leave a comment below if this helped you in any way, or if you found related issues and workarounds that may help others who experience Remote Desktop Connection crashes. Also remember to follow TommyNation.com on Facebook. Remote Desktop Connection has stopped workingApplications, How To Guides, Windows 10, Windows 7, Windows 8 ItsPeet Great workaround! Renaming the file in System32 works like a charm. I see no consequences for FLStudio either… Tommy Stephansen Sweet, thanks for the feedback ItsPeet. Lance Powers Thank you so much for posting this! I have not been able to get RDP to work for 6 months, despite trying the other workaround you cite, plus other suggestions that I have found online. This actu
Forums Rules Donation More Activity Unread Content Content I Started My Activity Streams All Activity Search More Subscription Orders Manage Purchases Support More Donations Contact http://www.msfn.org/board/topic/172136-mstscexe-crashing-on-auto-reconnect/ Contact MSFN Submit News More More Existing user? Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign Up All Content All Content This Topic This Forum Advanced Search Facebook Twitter remote desktop Google All Activity Home Microsoft Software Products Windows 7 mstsc.exe crashing on auto-reconnect Sign in to follow this Followers 0 mstsc.exe crashing on auto-reconnect Started by billypylgrym, June 25, 2014 crash dump windows 7 mstsc.exe APPCRASH Error 1000 troubleshooting frustrated 8 posts in this topic billypylgrym 0 0 2 posts June 25, 2014 OS: Windows 7 x64 Posted has stopped working June 25, 2014 I have several users connecting to our main office via Terminal Services Gateway. One user specifically is having issues daily with APPCRASH errors on mstsc.exe. She is running Windows 7 64 bit, all updates installed. Gateway is on a SBS 2008 server. No other users are having this problem. After running the crash dump, it seemed that the issue was upon auto-reconnect. Doing some research, I found that her HKEY_Local_machine\ system\currentcontrolset\control\terminal server entry fDenyTSConnections Key was set to 1. I changed to 0 with no effect. I'm not sure what the next steps to take are. Can anybody analyze this dmp file better than I have done? Application Log Event Detail: Faulting application name: mstsc.exe, version: 6.3.9600.16415, time stamp: 0x524b5b3dFaulting module name: mstscax.dll, version: 6.3.9600.16503, time stamp: 0x52c5f878Exception code: 0xc0000005Fault offset: 0x0000000000439b7aFaulting process id: 0x10c8Faulting application start time: 0x01cf8fc6ce6ffa2dFaulting application path: C:\Windows\System32\mstsc.exeFaulting module path: C:\Windows\System32\mstscax.dllReport Id: 88b5f942-fbc6-11e3-8332-0023245c063b Crash Dump Detail: Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\mforsyth\Desktop\mstsc.exe.4420.dmp]User Mini Dump File with Full Memory: Only application data is available Symb