Rdp Mstsc.exe Application Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MSTSC Application Error mstsc ntdll.dll error Windows Server > Remote Desktop Services (Terminal Services) Question 0 Sign in
Remote Desktop Connection Has Stopped Working Windows 7
to vote I am having a strange problem with MSTSC, everytime a user tries running MSTSC it comes remote desktop stopped working windows 7 up with application error and closes on all the machines they are using. They do have a roaming profile, so I am wondering whether the profile is corrupt but how remote desktop connection has stopped working windows 10 can it affect running MSTSC? I have logged onto the machine and tried running MSTSC and it works but I do have admin rights. The OS is Windows XP SP3 and trying to connect to Server 2000. Wednesday, September 23, 2009 2:35 PM Reply | Quote Answers 0 Sign in to vote Hi,I got round the problem by creating a
Remote Desktop Has Stopped Working Windows 10
new profile and all seems fine now it must have got corrupted.The information from the Application Log just after it crashes in order:1 - ERROR: Faulting application mstsc.exe, version 6.0.6001.18000, faulting module mstscax.dll, version 6.0.6001.18266, fault address 0x0015bcfa.2 - INFORMATION: The application, C:\WINDOWS\system32\mstsc.exe, generated an application error The error occurred on 09/24/2009 @ 12:22:02.515 The exception generated was c0000005 at address 4D86BCFA (mstscax)3 - ERROR: Faulting application mstsc.exe, version 6.0.6001.18000, faulting module mstscax.dll, version 6.0.6001.18266, fault address 0x0015bcfa. Marked as answer by Fayraz Tuesday, September 29, 2009 8:30 AM Friday, September 25, 2009 3:03 PM Reply | Quote All replies 0 Sign in to vote Hi, The RD Client references some things in the user's roaming profile. For example, if you rename HKCU\Software\Microsoft\Terminal Services Client\ registry key in the problem user's profile and then have them launch mstsc does the problem remain?Another thing that roams is the default.rdp file, but I doubt that would cause crashing.It does not roam, but have you tried deleting their TS bitmap cache files? They are named bcache2.bmc, bcache22.bmc and are located under the user's
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 computer. Very strange. remote desktop connection has stopped working windows 7 ntdll dll What had changed to suddenly cause this? The Application log in the Windows faulting module name ntdll.dll remote desktop Event Log showed the error was related to the remote audio functionality. Apparently, Remote Desktop Connection is using the Ogg Vorbis
Remote Desktop Connection Has Stopped Working Server 2012
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: 0.0.3.6 Exception code: 0xc0000005 Fault https://social.technet.microsoft.com/Forums/windowsserver/en-US/07628215-fa88-4fda-ba63-fba3a06a8216/mstsc-application-error?forum=winserverTS 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: Renaming vorbis.acm in C:\Windows\System32 fixes the issue on https://tommynation.com/fix-remote-desktop-connection-stopped-working-error/ 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 actually works! Shaunn Diamond Thanks for sharing this. Much appreciated! Renaming vorbis.acm in c:windowssystem32 solved it. Al
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://superuser.com/questions/450569/remote-desktop-connection-works-fine-but-rdp-file-crashes of this site About Us Learn more about Stack Overflow the company Business http://serverfault.com/questions/758919/rdp-crashes-after-entering-password Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is 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 remote desktop a question Anybody can answer The 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 has stopped working user's pc with the exception of one machine. 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 vo
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 RDP Crashes After Entering Password up vote 3 down vote favorite 1 Recently I've been trying to login to various machines via RDP and am getting the following error my Windows 10 workstation: Faulting application name: mstsc.exe, version: 10.0.10586.0, time stamp: 0x5632d1d8 Faulting module name: ntdll.dll, version: 10.0.10586.103, time stamp: 0x56a8483f Exception code: 0xc0000374 Fault offset: 0x00000000000ee71c Faulting process id: 0x3eac Faulting application start time: 0x01d16d6d340f9399 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll After debugging with VS 2015 it seems like a heap corruption issue. rdp windows-10 share|improve this question asked Feb 22 at 13:03 Mike Averto 1967 I had/have "CSR Harmony Wireless Software Stack" version 2.1.63.0 installed. I believe that all versions of Windows (Vista and higher) are susceptible to being messed up by this thing. I had this issue on Windows 7 Pro. –William Jul 13 at 0:19 add a comment| 2 Answers 2 active oldest votes up vote 4 down vote accepted The problem was from the recent CSR harmony bluetooth driver I installed. The drivers try to add some bluetooth tag authentication which was causing the issue and RDP crashes regardless of a good or bad password. The simple fix is