Terms of Use For FixedByVonnie

By proceeding to access fixedByVonnie.com, you expressly acknowledge, and agree to, all of the following:

fixedByVonnie.com is a personal website and blog owned by Security Plus Pro LLC, which is being presented for informational purposes only. The views on this website are solely those of the website owner (and not those of any employer or of any professional associations affiliated with the website owner).  Any views expressed in this website and any information presented on this website, or in any of its blog entries, should not be relied on for any purpose whatsoever other than as the personal opinions of the website owner.  The website owner expressly disclaims any and all liability for any information presented on this site.  The owner of this website and its blog posts shall not be held liable, and shall be held harmless, for any errors or omissions in any information or representations contained in this website, or in any of its blog entries.  The website owner also expressly disclaims any liability for the current or future availability of any such information. The website owner makes no representations as to the accuracy or completeness of any information on this website or which may be found by following any link on this website. The website owner shall not be held liable for any losses, injuries, damages, claims, or causes of action, from the display or use of any information on this website or in any of its blog entries. If you use the information on this website, or on any of its blog entries, you do so solely at your own risk.

How I fixed the "Remote Desktop connection has stopped working" error in Windows 8.1 - fixedByVonnie

How I fixed the “Remote Desktop connection has stopped working” error in Windows 8.1

Let me tell you a story about a troubleshooting incident I encountered a few weeks ago.

I live in New York City.

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.

Well that’s not entirely true; the client actually crashed on connect.

After 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 error is pretty lame if you ask me.  Here’s the thing: it’s already obvious that the Remote Desktop connection stopped working because the client was completely locked up. Therefore, why does Microsoft need to rub it in my face by telling me what is already undeniably true?

So yes, I was perturbed.  I tried immediately connecting again (just to see if the error would go away) but I got the same result.

Rebooting didn’t fix anything so I asked a friend to attempt to connect to the same remote computer.  Guess what?  He didn’t have any issues.  He connected fine and looked at me like I was stupid.

So there was something on my computer that was causing the Remote Desktop application to quit unceremoniously.

But what was it?

When I looked in the event logs I could see mstsc.exe was the faulting application name.  But I already knew that.

There was also something  in there about vorbis.acm.

Faulting module name: vorbis.acm

How odd… what is that?

mstsc.exe application error; this application stopped responding

Wait a second…

I thought to myself:

Vorbis… vorbis… where have I heard that before?  Isn’t that an audio codec or something?

I started Googling around and noticed that vorbis, sometimes called Ogg Vorbis, is an open source audio coding format.  But it wasn’t obvious to me what an audio codec and the Remote Desktop Client had in common.

How are the two related?

I started searching for clues through the Remote Desktop client tabs:

  • I perused the General tab… nope nothing here.
  • I scrutinized the Display tab… nothing relevant here
  • I clicked through the Local Resources tab…

Oh wait.. what is this?

Remote audio… configure remote audio settings?

Remote Desktop Local Resources

I mused to myself:

Ah, maybe there’s something in here I need to disable?

When I clicked in the Remote audio playback settings I noticed Play on this computer was selected.

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.

Remote Audio Settings in Windows 8.1

And guess what?

That fixed it!  I connected without any issues and the Remote Desktop client stopped crashing.

If you’re having a similar issue try poking around in the Remote Desktop settings to see what you can disable.  I know some people were able to fix the Remote Desktop client problem by disabling Printers under Local devices and resources.

Maybe that will work for you?

Local devices and resources in Remote Desktop Connection

P.S., one last thing:

You might be able to to solve the problem by backing up the cached bitmapped images of previous remote sessions.


Basically, 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.

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.

I have to be real with you though: I haven’t tested this bmc thing so I can’t tell you any expected outcomes!

Backup the bcachebmc files in Terminal Server Client

Please let me know what worked for you.


Connect with Vonnie on Twitter

Posted in Windows, Windows 8, Windows 8.1 Tagged with: , ,
  • Valentin Badea

    Yes, I have the same problem and your solution works for me ! Thank you very much !!

    • Whoohoo! I wasn’t the only with this issue – glad you’re working now

  • Fonzie Squaccuara

    Filter out the sh*t next time you write a troubleshooting article, nobody cares about your feelings and inner thoughts during the process …..sheeesssh

    • rawbyrtt

      Fonzie.. seeing his thought process as he walked through the problem can help others follow a similar process for related, but different issues. You’re one guy, so you’re in no position to speak for everyone else.

      Filter out the sh*t next time you write a comment.

      • Oh yes, RawByrtt to the rescue! Thanks for having my back lol

    • Hehe Fonzie thanks for the feedback. I like to write this way because I want people to get inside my head with the problem. Besides, stories are more interesting than just a long list of facts. If you just want bottom-line answers you won’t find them here! Thanks for telling me about your feelings and inner thoughts about this issue though – lol

    • Whoever

      It’s a year ago, but jeeze…….stfu. It’s a short article, and there’s nothing wrong with his style. FU Fonz, from the future.

  • LH

    This actually worked perfectly the first time! And funny thing is, this had my tech support stumped. They tried all sorts of things. Goes to show my first step should ALWAYS be a basic google search. I think I am going to just bookmark your page. thanks! (enjoyed your writing style as well. Fonzie Squacaca is straight trippin’. lol)

  • Brian O’Donnell

    worked for me thanks

  • SirLoinCloth

    Ran into this problem today, this fixed it. Sort of strange, it was working until today.

  • Foo Ken Oath

    Tried the audio fix – no go
    Renamed the files .bmc files The connection then worked
    Thanks for the tip !

  • Rahi


    Even i am facing this same issue. Have tried all the options mentioned above, but still getting same error. Any suggestions.

    Faulting application name: mstsc.exe, version: 6.3.9600.16415, time stamp: 0x524b5b3d

    Faulting module name: unknown, version:, time stamp: 0x00000000

    Exception code: 0xc0000005

    Fault offset: 0x0000000000000000

    Faulting process id: 0x1c54

    Faulting application start time: 0x01d0c909e3004c7f

    Faulting application path: C:Windowssystem32mstsc.exe

    Faulting module path: unknown

    Report Id: 2bae4aae-34fd-11e5-9c8a-54ee751eae02

  • J Cafeolai

    Had the same problem with Windows 10 and this solved my problem !! tick ‘Do not play’ and untick ‘Priters’ worked !!! Thank you 🙂

  • none of above solution worked for me,
    i found my answer when i disable AutoLogin for last user in Windows 10, OR 8, 8.1 remote desktop will closed on showing credential,

    just restore registry value and problem solved

    Enable = 0

    • efwww fewewf

      Thank you so much it helped created an account here to upvote you my friend 😉

    • Dus Shel

      Deleting the cache and disabling sound/printers alone didn’t work for me, but after I corrected the registry..NO MORE Remote Desktop crashes!!! Thanks 🙂

      • Melody McAfee

        How do you correct the registry

        • Dus Shel

          Refer to @Mahdi Yousefi answer that I originally replied to

      • mnchstr

        Disabling sound didn’t work for me but disabling local print did the trick.

    • Md. Saidur Rahman

      Here is already value are set 0 at enabled location. Where I change the value at default or Enabled location?

  • Erik Howard

    Had the same issue. Your post solved it. Greatly appreciated!

  • Derek Sunshine

    mother effer… that worked… wow. lol

    • Derek Sunshine

      i should add… this worked for windows 10 as well.

  • Boris Cuber

    Ohhh lord, killing

    %USERPROFILE%AppDataLocalMicrosoftTerminal Server ClientCachebcache64.bmc did the trick. It took me 3 weeks to use the correct search keywords in google to find that easy solution on your site.

    Hoorrrraaay! Next beer is on me. Thanks a f**king lot!

    • Yay! 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.

      Thank you!

    • Melody McAfee

      How do you get here. 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 hidden folders. do this by going to “View” on windows 10 . Then you will see AppData and from there it should be simple. Let me know if you have any more questions.

  • Stuart McGill

    Steps seems to be too technical. Instead, tools like R-HUB remote support servers, gosupportnow, logmein etc. are user friendly and easier to use.

  • Jeff Everett

    nailed it, mark another one up for audio redirection bork’d on windows 10. RDP audio redirection from a windows 7 target works great on the iOS app for iPad but not mstsc.exe in windows 10 destkop. welcome to 2015 and mobile/web 1st. i guess i do use the iOS app more but really?!?!

  • George Lennon

    Renaming the cached files worked for me. Thank you.

  • Eric Vest

    Thank you for the “Do Not Play Audio” tip. That was the answer for me!!!!

  • Tong Nattachai

    disabling printers works for me. Thanks for sharing!

  • Tobias Migge

    Thanks for the workaround, works like a charm for me!

  • SamuraiJ

    OMG! Thanks! This was bothering me for several months. You just made my day.

  • mikeym0p

    Disabling printer sharing worked for me, thank you so much!

  • Victor

    I believe the key to solving this issue specific to each case is looking in the event viewer. Look at not just the “Faulting application name” but also the “Faulting module name.” For me the faulting module was “dlxcrjdm.dll” which is an old Dell Printer Driver dll that I am guessing isn’t compatible with Windows 10 (which I just upgraded to). Anyway, after uninstalling the Dell printer, my problem was resolved. This type of approach may also solve the issue for those looking to use printers or audio as a local resource in the remote environment.
    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 Type”) in the last hour and then find the one related to your issue. After you do find the “Faulting module name”, I suggest googling it to find out what it is and go from there.

    • Drew

      Victor makes a good point – definitely check the event viewer. sdrdp5.dll was the cuplrit for us. Simple fix.

  • Mutungi Joel

    Thanks a lot

  • Smoke

    I had the same issue and none of the above fixes helped so I simply created a new user and that fixed my problem.

  • Naïke Van Damme

    Thanks!! Worked for me!

  • David Orensanz

    Amazing. I’ve been trying to fix during several months and it worked out (the audio off option) and this was in Windows 10, so I wrote to let you know that it also works in W10. Thanks a lot!!

  • Kiumane Kiumane

    I’m on Windows 10 and this worked for me – disabled audio. Thank you!!!!

  • Melody McAfee

    I am not computer literate so how do I disable autologin and how do I find registry value as the other steps did not correct the problem?

  • Gaurav Kohirkar

    Amazing solution man. Same problem of the Audio and it fixed for me.. Thanks a ton

  • Gaikoku Tamashi

    Audio setting worked for me. Thanks bro.

  • Mike

    Excellent that worked perfectly. Thanks for working out the problem and sharing the solution.

  • Davey

    worked , thankss

  • Nick Rodgers

    I had a similar problem solved by deleting C:Program FilesCSRCSR Harmony Wireless Software StackBLEtokenCredentialProvider.dll

    • Karl Berger

      It is solution for my problem – thank you.
      How did you find it ?

    • Ryan Hawk

      Thank you! This solved my problem.

    • Chief Aries

      This. It fix my wifi log in windows explorer crash problem. Thank you!

    • AB

      tried literally everything else, only this worked! Thanks!!!

    • Robert Larrance

      Great Solution! I deleted the CSR software and Remote is running again. I have had other problems with that software, should have dumped it months ago. Thanks, Nick!

    • If the crash happens in ntdll.dll (as was in my case), the chances are high it is related to the mentioned BLEtokenCredentialProvider.dll (just renaming it is enough to avoid crashes).
      The real cause of the crash can be tracked down by analyzing the dump file like mstsc.exe.6804.dmp (for Windows 7 they are accumulated in ?:UsersXXXXAppDataLocalCrashDumps by default).

    • Very Nice Person

      THANK YOU! It solved my problem too!

  • pdimitar

    I didn’t have that Vorbis error but I just went on a limb and tried disabling audio. Worked immediately! Thank you!

  • To test if the problem really was about the Vorbis codec, I opened a Media Player on the remote computer. As soon as I played a file, the Remote Desktop crashed. I set the Audio to Do Not Play, and it fixed for me.
    Googling tells me that Vorbis.acm is not compatible with 64-bit mtsc.exe version.

  • PaulM8

    In the Windows Application event log I found it was a newly installed HP printer on the network causing my RemoteApp RDP session to crash within seconds of starting. I disable Printers as a shared resource.

  • anthony abhilash

    that worked…Thanks

  • TONY

    worked perfect thanks! nice story btw xD

  • Daniela Antoniades Jordan

    Didn’t work with disabling the audio, but it worked by disabling the printer. Thank you so much for such a simple solution to an annoying new problem!

  • raf

    Disabling printer share worked for me! Thank you.

  • Joe Meyer

    Brilliant, this worked for me on Win 10 Pro, thanks so much.

  • Johny Piston

    Worked perfectly! Thanks!

  • This post pointed me in right direction.
    Found out user was using old printer driver that was responsible for crashing RDP connection.
    Win7 driver working on Win10 – compatible but not best solution!
    After upgrading the driver, printer share was back to normal.

  • Knútur Óli Magnússon

    Had the same thing in event log and this solution worked for me! Thanks 🙂

  • Angela Burdsall

    God bless you!

  • Veronika L. Tchesnokova

    Thank you for this post! I had same problem, and it was fixed after I disabled the printers!

  • Ryan MacIntosh

    Wanted to chime in as i was having the same issues, i had “Faulting module name: ntdll.dll” in my event log.

    Got onto here by Googling https://www.lifewire.com/how-to-fix-ntdll-dll-errors-2624474

    After disabling UAC, no more crashes!

    Hope it helps someone

  • Kaiser

    I’ve had continuous disconnection problems with Remote Desktop from a Win10 to a Win7 machine, where the connection dropped every time I used windows explorer on the host machine.

    I turned remote audio playback to ‘do not play’ and I also disabled ‘Printers’ under local devices and resources. No more disconnecting now!

    Thanks for the article

  • Adam Parker

    Works like a charm on Windows 10, thanks.

  • fluxtatic

    Beautiful. All I found on technet was an MS MVP giving up and saying, “sorry, you’ll need to reinstall Windows”

  • gfkBill

    Thank you! I had to turn off printers and clipboard too (not sure which did the trick).

  • Rômulo (ch4c4r – Xbox 360)

    You saved my life with audio config!!!!!!!!!!!!!!!!!!!!!!!!
    Thanks a lot dude!!!!!

  • Marco Floriano

    Thanks man, in my case it was the printer

  • Hikari

    This fixed my issue. . . FINALLY… I haven’t been able to log into ANYTHING via either remote desktop or just the shares on other computers in general because of this…

    Note: I’m referring to deleting the cache files. NOT the audio.

  • Barbara Waller

    Thats great. Thank you for sharing such wonderful information of fixing remote desktop connection in Windows. Uptill now I was using 3rd party tools like R-HUB remote support servers, Logmein, Teamviewer etc, for remotely accessing computers, Will try Windows RDP as well.

  • qanmber abbas

    toasters & toaster ovens at Target, in a variety of colors, finishes and brands. Shop a wide selection at cuisinart toaster

  • qanmber abbas

    the section of Kitchen & Bar Faucets in the Kitchen Department at The Home Depot Canada. home depot kitchen faucets