How to fix RDP/FL Studio audio conflict crashes


Do you use Windows’ Remote Desktop Protocol (RDP) to connect to headless or remote Windows machines or servers? Have you installed Image-Line’s FL Studio (formerly known as Frooty Loops)? Does your RDP client crash whenever you use an invalid character when naming a folder or file or when anything on the system would make a sound?  This guide will help you fix this issue once and for all!

I’ll preface this by saying if you actively use FL Studio then this guide may not help you. I am writing this under the presumption that you have removed FL Studio from your machine. If that is the case, there is a workaround at the bottom of the guide that you can use until a better option is available.


Step 1:  Check your event logs

This is easiest done right after the crash, as it will appear near the top of the Windows logs by default. It should be the one that reads “Error” with a red exclamation icon. This will give us our first clue.

Faulting application name: mstsc.exe, version: 10.0.10586.0, time stamp: 0x5632d1d8
Faulting module name: vorbis.acm, version:, time stamp: 0x50a51541
Exception code: 0xc0000005
Fault offset: 0x0000000000001f4f
Faulting process ID: 0x6f8
Faulting application start time: 0x01d1a0e7990d969d
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\vorbis.acm
Report ID: ac549ede-9aa3-4321-919f-80ef7c3fb110
Faulting package full name:
Faulting package-relative application ID:

Vorbis.acm? As in the Ogg Vorbis (*.ogg) codec? So this must have to do with audio then, right? Bingo! This is when it clicked for me. RDP would crash whenever the server system would do something that would have audio playback (most often the annoying “bing” sound when typing an invalid character when naming files or folders), but it also happened when I accidentally started playing a video file on the server. Now it makes sense as to why.

It turns out that FL Studio installs the vorbis.acm codec file, and for whatever reason RDP doesn’t like it. At all.

Step 2:  Deal with that pesky vorbis.acm

If you no longer use FL Studio, navigate to C:\Windows\system32 and locate the file. You have two options available to you: rename or remove. I elected to rename mine to vorbis.acm.old. You may need to restart your PC before it works, but this was not the case for me.

If you still use FL Studio you can either disable RDP audio playback, or you can move vorbis.acm to FL Studio’s installation directory (thank you to J R Stevens for letting me know about this!)

Moving vorbis.acm to FL Studio’s directory 

  • In C:\Windows\system32 right-click on vorbis.acm and click on Cut (alternatively hit CTRL-X)
  • Navigate to your FL Studio’s installation directory (default is C:\Program Files\Image-Line\FL Studio – if using the 32-bit application substitute Program Files with Program Files (x86))
  • Ensure you’re in the same directory as FL Studio’s executable (EXE) files
  • Right-click on empty space and click on Paste (alternatively hit CTRL-P).
  • Done! You should now be able to RDP crash-free while still retaining the ability to use FL Studio without issue!

Disable RDP audio playback

  • Launch the RDP client application.
  • Click on the Local Resources tab (click on Show Options if the tabs are hidden)
  • Under Remote Audio, click on Settings
  • Select Do not play and click on OK
  • Done!



6 thoughts on “How to fix RDP/FL Studio audio conflict crashes

  1. Hello Brian. You are indeed correct about the vorbis.acm file. It not only causes problems with RDP but causes crashes to many of the Windows 8/10 apps. I initially came across this info while trying to fix crashes with MS Solitaire Collection. Renaming the vorbis.acm also fixed a crash in Magix Music Maker Jam when clicking on the record button. Unfortunately, I like other musicians, use FL Studio on a regular basis. So the fix for me has been to rename vorbis.acm to vorbis0.acm whenever I want to use a Windows 10 app. Then I have to change it back to vorbis.acm when I want to use FL Studio. I informed Magix support about this and am waiting to hear back from them. I will be contacting Image Line (FL Studio) to let them know about this issue as well. What I’m hoping is that the programmers of FLS will provide a fix for the vorbis codec that will allow all these apps (RDP included) to live together in peace. Of course, I may be hoping for too much, but at least it’s worth a shot.

  2. Follow-up to my previous post:
    I came across an easy fix to the discussed problem. It seems that FL Studio doesn’t need the vorbis.acm file to stay in the System32 directory. It can actually be moved to the FLS folder that contains the executable for the program and FLS will find it there and use it. So for those like me that need to use FLS, just move the file. This way FLS continues to work correctly and the crash problem in Windows 8/10 apps goes away. I personally tested this and found that all works perfectly now. I hope your readers find this helpful.

  3. Thanks a bunch, man! Need to use RDP for work (and FL Studio in my spare time :P) and ran into this issue. This was an easy fix 🙂

  4. Many thanks for this… removing vorbis got my sound back up and running from my virtual desktop to my real RDP client in Windows 10

  5. Man this is so awesome!!! it worked perfectly !!
    I’ve been searching for almost a year how to fix my music maker jam prob on when I tried to record and it’s working again!!
    So helpfull.
    Thank you so much!!!!.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.