Mstsc 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 Windows Server > Remote Desktop Services (Terminal Services) mstsc ntdll.dll error Question 0 Sign in to vote I am having a strange problem with
Remote Desktop Connection Has Stopped Working
MSTSC, everytime a user tries running MSTSC it comes up with application error and closes on all the machines they are
Remote Desktop Connection Stopped Working Windows 7
using. They do have a roaming profile, so I am wondering whether the profile is corrupt but how can it affect running MSTSC? I have logged onto the machine and tried running MSTSC
Remote Desktop Connection Has Stopped Working Windows 10
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 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 - remote desktop has stopped working windows 10 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 local Application Data. If the above does not help you may be forced to give them a new profile.Thanks.-TP Wednesday, September 23, 2009 4:22 PM Reply | Quote Moderator 0 Sign in to vote Hi, I have tried deleting the two TS bitmap files and the same err
Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Hi I have a user who is, since last night, no longer able to connect to our terminal server... remote desktop crashing windows 10 she is now getting the following message: The instruction at "0x4d86bcfa" referenced memory at "0x00000000". The memory remote desktop stopped working windows 10 could not be "read" She has been able to connect by using the 'run as' option and putting her own network credentials in - but remote desktop crashes windows 10 does not want to do this as a long term solution. Any ideas? Thanks in advance! Reply Subscribe View Best Answer RELATED TOPICS: MSTSC.EXE: How much memory should it be using? Application error Application Error?   6 Replies https://social.technet.microsoft.com/Forums/windowsserver/en-US/07628215-fa88-4fda-ba63-fba3a06a8216/mstsc-application-error?forum=winserverTS Pure Capsaicin OP akp982 Apr 8, 2010 at 4:57 UTC akp982 is an IT service provider. Is this error on the terminal server or her machine? Looks like a memory problem, try recreating her profile or changing out the memory. 0 Serrano OP Patrick Louis-Jean Apr 8, 2010 at 6:13 UTC I she can runas administrator, it sounds like it is a permissions problem. What OS is she running? How is she logging on to the machine - local https://community.spiceworks.com/topic/94810-mstsc-exe-application-error account or domain? Is it just her or do other users on that machine have the same problem? 0 Sonora OP Clare1904 Apr 8, 2010 at 6:38 UTC Hi Thanks for your replies..... the user is using an XP SP3 laptop, connecting to a 2003 Terminal Server - and I'm told it worked fine last night! The error message appears to be on the laptop as it will not open the RDP session. I'm confused as to why it won't work in the normal manner, but it will work when using the 'Run as another user' route with her own network credentials logging on to the domain (it isn't just restricted to admin credentials).... surely if it is a memory problem wouldn't the 'run as' way in also be affected? Apologies if this is a stupid assumption! 0 Sonora OP Clare1904 Apr 8, 2010 at 6:39 UTC Sorry - forgot to say - it is just her, the other users in the same office connecting to the same server are not having any problems.... 0 Sonora OP Best Answer Clare1904 Apr 8, 2010 at 8:37 UTC Hi - the user was complaining so much about having to access via 'run as' I decided to restore machine back to Tuesday - this has resolved the issue.... for the time being! Thank you so much for your help and suggestions though! 0 Serrano OP Patrick Louis-Jean Apr 8, 2010 at 10
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get https://www.experts-exchange.com/questions/24603073/mstsc-exe-Application-Error.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > mstsc.exe Application Error Want to Advertise Here? Solved mstsc.exe Application http://www.bleepingcomputer.com/forums/t/398498/pc-with-mstscexe-bad-image-error-when-using-remote-desktop-connection/ Error Posted on 2009-07-27 Windows XP 2 Verified Solutions 3 Comments 5,843 Views Last Modified: 2012-05-07 When logging out of any server or when exiting the mstsc application my customer gets an application error. "The remote desktop instruction at "0x00e802b7" referenced memory at "0x00000008". The memory could not be "read". Click on OK to terminate the program. He has XP SP3 with mstsc version 6.0.6001.18000 (longhorn_rtm.080118-1840) I have tried to rename the files mstsc.exe and mstscax.dll to .bak, and rebooted, but that did not help. I also deleted the bcache2.bmc file as well. I also tred to reregister the dll file. Should I remove XP3 to use an stopped working windows older version of RDP? Thanks for any help! 0 Question by:cstallings Facebook Twitter LinkedIn Google LVL 66 Best Solution byjohnb6767 Delete the following from c:\windows\system32\dllcache mstsc.exe mstscax.dll mstsmhst.dll rdpdd.dll rdpsnd.dll rdpdr.sys rdpwsx.dll rdpclip.exe Then rename them to *.old in c:\windows\system32 Then Go to Solution 3 Comments LVL 63 Overall: Level 63 Windows XP 17 Message Expert Comment by:SysExpert2009-07-27 1) It could be a hardware issues, especially RAM, so run a RAm diagnostic for a few hours 2) Not sure if t is worthwhile to uninstall SP3. Did it work previous to the SP3 update ? I hope this helps ! 0 LVL 66 Overall: Level 66 Windows XP 49 Message Accepted Solution by:johnb67672009-07-27 Delete the following from c:\windows\system32\dllcache mstsc.exe mstscax.dll mstsmhst.dll rdpdd.dll rdpsnd.dll rdpdr.sys rdpwsx.dll rdpclip.exe Then rename them to *.old in c:\windows\system32 Then replace them from the most recent versions in C:\WINDOWS\$NtServicePackUninstall$. If needed you might need to unregister them if possible, and then reregister them. This will basically rebuild the files needed for RDP. 0 LVL 1 Overall: Level 1 Message Assisted Solution by:rldavis2009-08-18 Just one comment on Johnb6767's excellent solution above. The mstscax.dll date needs to match the mstsc.exe date. On one machine where I corrected this there was a newer mstscax.dll an
List Welcome Guide More BleepingComputer.com → Security → Virus, Trojan, Spyware, and Malware Removal Logs Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. BLEEPINGCOMPUTER NEEDS YOUR HELP! BleepingComputer is being sued by Enigma Software because of a negative review of SpyHunter. A case like this could easily cost hundreds of thousands of dollars. If we have ever helped you in the past, please consider helping us. To learn more and to read the lawsuit, click here. CONTRIBUTE TO OUR LEGAL DEFENSE All unused funds will be donated to the Electronic Frontier Foundation (EFF). If you accept cookies from this site, you will only be shown this dialog once!You can press escape or click on the X to close this box. Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. PC with mstsc.exe bad image error when using Remote Desktop connection Started by rocko411 , May 20 2011 12:31 PM Page 1 of 2 1 2 Next This topic is locked 15 replies to this topic #1 rocko411 rocko411 Members 8 posts OFFLINE Local time:05:18 PM Posted 20 May 2011 - 12:31 PM In advance, thank you for the assistance in defining if I have a virus. Maybe I have a virus.. maybe not. When trying to use the remote desktop connection on my PC, I am experiencing: The application or DLL C:\WINDOWS\system32\aaclient.dll is not a valid Windows Image. Please check this against your installation diskette. Maybe this is just a install issue? It worked in the past... months ago. Also, when trying to open really any file, if I right click to define a program to open it with, it takes 30 second and never displays the window access to define what program I want to use... if I right click again while still on the file, it then allows me to select from my "open with" prog