That was the answer for me!!!! the lady said "oh, well that was easy", and I wanted to smack her lol Sure the last click of removing the corrupt driver you have, for a printer you don't After upgrading the driver, printer share was back to normal. Your post solved it. navigate here
David Hervieux Clock3 yrs essaymPosts: 16 Share I understand that David - as in my original I have been updating the software every month on average now with the 'latest fixes' It has done this twice. After you do find the "Faulting module name", I suggest googling it to find out what it is and go from there. I'll have to look into it more in depth later on, but for now I'm at least able to keep on working. https://social.technet.microsoft.com/Forums/windowsserver/en-US/00e498b4-3763-4c4c-b41e-6f7e71c80990/remote-desktop-crash-on-connect?forum=winserverTS
worse yet it also crashed the print spooler service on the server, making printing unavailable for anyone else. 11 Serrano OP Helpful Post paul4170 Jul 9, 2013 at Instead, tools like R-HUB remote support servers, gosupportnow, logmein etc. Clock3 yrs essaymPosts: 16 Share So you are aware - with the first error that has always existed - I am able to replicate this by doing the following: RDP with
To run event viewer, just hit the Start button and start typing in "Event Viewer." You should be able to see in the "Summary of Administrative Events" any Errors (under "Event Clock3 yrs Stefane LavergnePosts: 1363 Share Hi Sam,Are you running RDM Agent on the destination machine?Regards, Stefane Lavergne Clock3 yrs essaymPosts: 16 Share No - RDM Agents do not run on Do you put it in search or in the browswer> wuafri Go to your local hard drive then find the username you are looking for then also you need to enable Remote Desktop Connection Has Stopped Working Windows 7 Ntdll Dll Faulting module name: vorbis.acm How odd… what is that?
View this "Best Answer" in the replies below » Challenge × Join Now or connect with Connect with Facebook LinkedIn Already have an account? Remote Desktop Keeps Crashing Windows 7 Huh? When is a proof or definition formal? This solved my seperate issue.
LH This actually worked perfectly the first time! Reinstall Remote Desktop Windows 10 I looked through the event log on the server and found a 4105 and several 1103 errors each time he tried to connect. The 4105 states: The Remote Desktop license server This happens when I try to connect via RDP to Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 2008, Windows 2012… And it's intermittent on all of them. Deleting that .bmc file in %USERPROFILE%AppDataLocalMicrosoftTerminal Server ClientCache didn't work but deleting the other 3 Cache files in that dir fixed the crash for me that just randomly started happening today.
Leave a Reply Cancel reply Post navigation Previous Previous post: How to setup a virtual DD-WRT Router with Hyper-VNext Next post: Update AD-Users with new Phone-number and Pager via Powershell Search http://www.isolation.se/mstsc-and-rdcman-crashing/ This has worked flawlessly for months. Remote Desktop Crashes Windows 10 at least temporarily. In my case the user had an old corrupt printer driver that would crash her session when connecting to the terminal server.... Remote Desktop Connection Crashes Windows 7 As soon as I played a file, the Remote Desktop crashed.
It's located here: %USERPROFILE%\AppData\Local\Microsoft\Terminal Server Client\Cache You could rename the .bmc files to .bmc.old and then retry your terminal services connection efforts. windows-xp rdp terminal-server mstsc share|improve this question asked Jun 23 '09 at 13:39 rotard 2381314 Rotard- Can you post the event log that corresponds with the crash? this just fixed my RDP issues that has plagued two of my home systems. Usually you just get spam in the log saying the printer could not be installed. Remote Desktop Connection Has Stopped Working A Problem Caused The Program To Stop Working Correctly
It all worked perfect with Win 7, now my kids need to enter passwords…they even want them to get a Microsoft account… also Microsoft's own Family Safety doesn't run any more remove content of C:\Documents and Settings\user\Local Settings\Application Data\Microsoft\Terminal Server Client\Cache For more details, please check this post: MSTSC crash on connect Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Thanks for sharing! Boris Cuber Ohhh lord, killing %USERPROFILE%AppDataLocalMicrosoftTerminal Server ClientCachebcache64.bmc did the trick.
I have not yet connected successfully with Remote Desktop. Windows 10 Remote Desktop Fix I mused to myself: Ah, maybe there's something in here I need to disable? Much appreciated!
Have a great day :-) TommyNation.com © All Rights Reserved Twitter Facebook Back to Top
No problem to connect to my server using Windows 8 Remote Desktop from my laptop. finally after figuring it out... David Refoua To test if the problem really was about the Vorbis codec, I opened a Media Player on the remote computer. share|improve this answer answered Aug 4 '09 at 18:29 subvip7 add a comment| up vote -1 down vote The issue has not come up again to my knowledge, but I think
Faulting module would be facredprov2.dll.