![]() bmc.old and then retry your terminal services connection efforts. It’s located here: %USERPROFILE%\AppData\Local\Microsoft\Terminal Server Client\Cache You might be able to to solve the problem by backing up the cached bitmapped images of previous remote sessions.īasically, if you repeatedly connect to the same computers that have the same desktop setups, the terminal service client will save a cached copy locally on your system so you don’t have to keep downloading it from the remote computer. I know some people were able to fix the Remote Desktop client problem by disabling Printers under Local devices and resources. If you’re having a similar issue try poking around in the Remote Desktop settings to see what you can disable. That fixed it! I connected without any issues and the Remote Desktop client stopped crashing. Since I don’t care about the audio at the destination playing back on my local computer, I selected Do not play and attempted to reconnect. When I clicked in the Remote audio playback settings I noticed Play on this computer was selected. Remote audio… configure remote audio settings?Īh, maybe there’s something in here I need to disable? I clicked through the Local Resources tab….I scrutinized the Display tab… nothing relevant here.I perused the General tab… nope nothing here.I started searching for clues through the Remote Desktop client tabs: But it wasn’t obvious to me what an audio codec and the Remote Desktop Client had in common. ![]() I started Googling around and noticed that vorbis, sometimes called Ogg Vorbis, is an open source audio coding format. Virtual machine connect-to-console support Smart groups Support for credential encryption with certificates Windows 8 remote action support Support for. Vorbis… vorbis… where have I heard that before? Isn’t that an audio codec or something? There was also something in there about vorbis.acm. When attempting to type on the AS400 Green Screen (ibm iseries access 5. When I looked in the event logs I could see mstsc.exe was the faulting application name. Hello, Im using the iOS version of Microsoft Remote Desktop, connecting to my win 10 workplace pc. So there was something on my computer that was causing the Remote Desktop application to quit unceremoniously. He connected fine and looked at me like I was stupid. Rebooting didn’t fix anything so I asked a friend to attempt to connect to the same remote computer. I tried immediately connecting again (just to see if the error would go away) but I got the same result. Therefore, why does Microsoft need to rub it in my face by telling me what is already undeniably true? Here’s the thing: it’s already obvious that the Remote Desktop connection stopped working because the client was completely locked up. Well that’s not entirely true the client actually crashed on connect.Īfter 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 other day I was trying to use the Microsoft Terminal Services Client (mstsc.exe) to remotely connect to a PC in Los Angeles, California but for some inexplicable reason I couldn’t connect. Let me tell you a story about a troubleshooting incident I encountered a few weeks ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |