Back to Client Overview
Install the FSRdp Client on Windows
From the downloaded setup file to your first working session, including all required settings and permissions.
Need Help Setting Up?
Ask an AI chatbot of your choice using the following prompt:
Please help me set up my FSRdp client on Windows using this guide:
https://www.fssoft.de/FsRdp/en/InstallingClientWindows.md
Guide me step by step, only one step per response, and wait for my feedback after each command. Never ask me for a password.
The link points to the plain-text version of this page, which a chatbot can read in full rather than the shortened content it often retrieves from HTML pages.
1. Prerequisites
- Windows 10, Windows 11 or Windows Server, all 64-bit.
- No separate .NET installation; the package includes everything.
- Permission to install programs on this PC.
- The server name and ports of your FsRdpServer (default
8888 and 8889).
- For voice transmission: a microphone. A headset is strongly recommended – see section 7.
You do not need to open any ports on the client. The client always initiates the connection to the server. No Windows Firewall configuration or router port forwarding is required. Only the server must be reachable.
2. Installation
1
Download Setup
Download Setup_FSRdpClient.exe and save the file in any folder, for example “Downloads”.
Download Windows Installer
2
Start Setup
Double-click the downloaded file. The installer guides you through a few steps; you can keep the default settings.
3
If a Blue Warning Appears
Windows displays a SmartScreen message for less widely used programs (“Windows protected your PC”). Click More info and then
Run anyway. This is not a malware report; it indicates that the file has not yet been downloaded often enough.
4
Start the Program
After installation, you will find FSRdpClient in the Start menu and on your desktop.
Do not run from a network drive. If the program runs from a UNC path such as
\\server\freigabe\FsRdpClient.exe , Windows silently blocks microphone and camera access without an error message. Always install the client locally.
Only one client instance runs per sign-in. Launching it again only brings the existing window to the foreground. This is intentional: two instances would share the same microphone, and the second would record audio played by the first, creating feedback that no echo cancellation can prevent.
3. Allow Microphone and Camera Access
This is by far the most common cause of “I cannot hear anything” or “others cannot hear me”. Traditional desktop programs on Windows receive no permission dialog; you must enable access yourself once.
1
Allow Microphone Access
Settings → Privacy & security → Microphone . Two switches must be on:
Microphone access and, further down,
“Let desktop apps access your microphone”. The second switch is often overlooked.
2
Allow Camera Access
Likewise under Settings → Privacy & security → Camera, including “Let desktop apps access your camera”. Only required if you want to transmit your camera.
Changes to these switches take effect after restarting the client.
4. Settings: Server, Name and Language
Open settings using the gear icon. In the
Personal Settings tab, enter:
Your name |
Your display name, shown to other participants in the list. |
Server address |
Your server's DNS name, e.g. server.ihrefirma.de. Do not use an IP address : the server certificate is issued for the name, and verification fails with an IP address. |
Main port / Audio port |
Normally 8888 and 8889. Change these only if your server operator specifies different ports. |
Spoken language (for live subtitles) |
Your own language. This determines the language in which your speech is recognized and the language in which you read other participants' captions. Only relevant if your server offers live captions. |
Only device settings are available during an active session. You can change your name, server address and ports only while not in a room; changes would only take effect on the next connection anyway.
5. Test Your Microphone, Speakers and Camera
In the Device Settings tab, select and test your devices directly to avoid troubleshooting during a session:
- Microphone – select a device and start the test; the level indicator should move when you speak.
- Speaker – select a device and play the test sound.
- Camera – select a camera and check its preview.
6. Join Your First Room
A room is a virtual meeting place. Everyone entering the same room number joins the same session.
1
Enter a Room Number
You receive the number from the person helping you, or provide one yourself if you have a supporter key.
Connecting to a Server without a License?
During its 30-day trial period, a server accepts exactly one
room number: 123456789. Any other number is rejected with an explanatory message. The room can remain open for up to 24 hours and can be reopened immediately afterwards; all participants see a watermark. On a licensed server, this particular number is blocked instead.
2
Click Connect to connect
The client connects, checks the server certificate and then displays the participant list.
3
Wait for a Second Participant
While you are alone in the room, screen sharing, chat and file sending are disabled, since there is no one to receive them.
7. Features in the Room
Share Screen |
Shares your screen. First select a monitor and area; a red border continuously shows what others can see. Click again to stop sharing. Only one person can share at a time; starting a new share replaces the current one. |
Camera |
Transmits your camera image. Several participants can send their cameras simultaneously, displayed as tiles. |
Microphone |
Mutes your microphone. This is entirely local; the server is not informed. |
Sound |
Mutes room audio for you. |
Send file |
Sends a file to the room. The recipient must confirm acceptance before anything is saved. |
| Chat |
Text messages and images to everyone in the room. |
| Remote Control |
The person sharing can grant another participant mouse and keyboard control and revoke it at any time. Clipboard copying and pasting works in both directions. |
| Recording |
The room owner can record the session as a video file if the server offers this feature. While recording, all participants see a persistent notice that cannot be disabled. |
Subtitles |
The room owner enables live captions for the room. This also displays a persistent notice to all participants. |
Without a headset, take turns speaking. When audible room audio plays through your speakers, the client briefly pauses your microphone. Otherwise it would pick up other participants' audio and everyone would hear a delayed echo of themselves. With a headset, this does not occur and both sides can speak simultaneously.
8. Supporter Keys and Reserved Room Names
Anyone providing support receives a personal
supporter keyfrom the server operator. Enter it in the
License Settings tab under Supporter license
to become the owner of rooms you create.
As a supporter, you can also use:
-
Reserved room names (up to 10) – permanently reserve room names so no one else can occupy them.
-
Account owner-secret – a password for opening your own rooms as the room owner in a browser.
A supporter key belongs to exactly one person. It cannot be used by two installations simultaneously. If someone else signs in with it, you lose your session. Do not share it.
9. Updates and Uninstallation
At startup, the client checks for a newer version and asks before installing. Downloaded packages are verified against a cryptographically signed manifest before execution; file size and SHA-256 checksum must match.
Uninstall the client like any other Windows program via
Settings → Apps → Installed apps.
10. Common Problems
“Others Cannot Hear Me”
- Is the
Microphone switch on the toolbar active, rather than muted?
- Under Privacy & security → Microphone , is access for desktop apps enabled as well? (Section 3)
- Does the microphone test level indicator move in Device Settings ?
- Is the client running from a network drive rather than locally?
“I Hear the Others Twice, with a Delay”
This is feedback through open speakers. Use a headset or reduce speaker volume considerably.
The Client Does Not Connect
- Is
Server address exactly correct, without https://or trailing spaces?
- Did you accidentally enter an IP address instead of the name?
- Are both port numbers correct?
- Does a company proxy or strict firewall block outgoing connections to these ports? Ask your IT department about outgoing connections to
8888 and 8889.
- Is the server running at all? Only the server operator can answer this.
“The Client Says It Is Already Running”
An instance is already running, possibly in a background window. Starting again brings the existing window to the foreground; this is intentional (section 2).
A Certificate Message Appears
The entered server name does not match the server certificate, or your PC does not trust the issuing authority. Contact the server operator. The client intentionally does not offer a way to bypass this.