Mstsc Exe Error Msvcrt Dll
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 00:13:57 GMT by s_wx1157 (squid/3.5.20)
Update Deployment You know Java: It's always being updated to fix security flaws! Pre-commissioned the "Iwo Jima"
Remote Desktop Connection Has Stopped Working Server 2012
LHD-7 Maintained a 1000+ mixed OS computer network that included: servers, workstations, faulting module name ntdll.dll remote desktop network test equipment, switches and routers TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a remote desktop connection has stopped working when printing few minutes. Join Now I have been struggling with this all morning. Trying to launch RDP on a Win 7 PC 64-bit with all the latest updates including the new http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/remote-desktop-connection-has-stopped-working/b3eb27f1-ed3f-40d4-8cb1-72b6f2a57b3b RDP 8.0 client updates. Getting the Microsoft Visual C++ error that a runtime is causing problems. I have checked the logs and its showing that msvcrt.dll is the faulting issue. I have logged in with every account I can including domain admin and cannot rename or remove that file. I have unjoined the PC from the domain, renamed the PC, joined https://community.spiceworks.com/topic/775057-win-7-rdp-crashing-with-ms-visual-c-error it back to the domain, deleted the users profile and associated .bak file from the registry, and still cannot open RDP on that users profile. I can login as another user or admin on the PC and launch the RDP just fine. Its only for this one user. So I thought permissions...I added the user to the admin group, remote users, remote desktop users, vpn users, etc etc. and still no RDP access. Can anyone tell me what this is and how to resolve please??? Screenshot attached and log entry below.Faulting application name: mstsc.exe, version: 6.3.9600.16415, time stamp: 0x524b5b3dFaulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeb033fException code: 0x40000015Fault offset: 0x000000000002a84eFaulting process id: 0xc8cFaulting application start time: 0x01d0409f054f0943Faulting application path: C:\Windows\system32\mstsc.exeFaulting module path: C:\Windows\system32\msvcrt.dllReport Id: 624a090c-ac92-11e4-a7f0-7446a0b3d2ed RDP.png (26.3 KB) Reply Subscribe RELATED TOPICS: Anyone using RDP 8 on Win 7?? RDP Win 7 RDP to Win 7 VM over different subnet issue.   10 Replies Pimiento OP rjsmith Feb 4, 2015 at 5:31 UTC Sometimes when I am faced with these issues I run: sfc /scannow That verifies
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 http://superuser.com/questions/450569/remote-desktop-connection-works-fine-but-rdp-file-crashes this site About Us Learn more about Stack Overflow the company Business 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 a question remote desktop 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 user's pc has stopped working 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 vote 0 down vote