How to Fix a Corrupt RDP File and Enable Remote Audio Settings

@July 9, 2024

Here’s a common problem with editing RDP files that is easily fixed: As soon as an RDP connection file is edited (either with Remote Desktop Client or a text editor like Notepad), the file becomes corrupt when it’s loaded by Remote Desktop Client.

The reason behind this is that the RDP file is signed and the properties are part of the signature. The fix is to simply remove the signature by removing the last two lines with a text editor. Follow this simple guide to fix the issue:

Instructions to Remove RDP File Signature

Open the RDP file with Notepad

Delete the two lines starting with signscope: and signature: (the selected text in the screenshot)

Save the file and open it with Remote Desktop Client.

Full RDP File

For reference, here’s a full RDP file without signature. It’s been adapted to

• Not connect local drives and printers
• Forward local audio, microphones and webcams for usage of e.g. MS Teams on the remote desktop

redirectclipboard:i:1
redirectprinters:i:0
redirectcomports:i:0
redirectsmartcards:i:0
devicestoredirect:s:*
drivestoredirect:s:
redirectdrives:i:0
session bpp:i:32
prompt for credentials on client:i:1
server port:i:3389
allow font smoothing:i:1
promptcredentialonce:i:1
videoplaybackmode:i:1
audiomode:i:0
audiocapturemode:i:1
redirectdirectx:i:1
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:1
gatewaycredentialssource:i:0
full address:s:TS01.MYSERVER.COM
gatewayhostname:s:ts.myserver.com
workspace id:s:ts01.myserver.com
use redirection server name:i:1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.Full_Desktop_Ses
use multimon:i:1
alternate full address:s:TS01.MYSERVER.COM