Install RustDesk on Windows 11 and Steam Deck

Oct 13, 2025 by sorusgentrification.com 27 views

Windows 11 + Steam Deck (SteamOS) File Transfer: Resolving the "No active console user logged on, please connect and logon first" Error

In this article, we will explore the issue of file transfer between Windows 11 and Steam Deck (running SteamOS) using RustDesk, a remote desktop and file transfer application. The problem arises when attempting to transfer files from Windows 11 to Steam Deck, resulting in the error message "No active console user logged on, please connect and logon first." We will delve into the bug description, provide a step-by-step guide on how to reproduce the issue, and discuss the expected behavior.

When using RustDesk to remotely control the Steam Deck from Windows 11, file transfers fail with the error message "No active console user logged on, please connect and logon first." This issue occurs even when the user is logged in to the Steam Deck in Desktop Mode, with the user account set to "deck." It is worth noting that file transfers from the Steam Deck to Windows 11 work without any issues.

To reproduce the issue, follow these steps:

Install RustDesk on Windows 11 and Steam Deck: Download and install RustDesk on both Windows 11 and Steam Deck.
Run and set up RustDesk: Launch RustDesk on both devices and set them up to connect to each other.
Attempt to open TRANSFER FILE on the Windows 11 side: On the Windows 11 side, navigate to the file transfer feature and attempt to initiate a file transfer to the Steam Deck.
Observe the error message: The error message "No active console user logged on, please connect and logon first" will be displayed.

The expected behavior is that the file transfer screen opens correctly, and the transfer system works without any issues. The user should be able to initiate and complete file transfers between Windows 11 and Steam Deck without encountering any errors.

The operating systems and RustDesk versions used in this scenario are:

Windows 11: The local (controlling) side
SteamOS 3.6.22: The remote (controlled) side
RustDesk Version 1.3.8: Both local and remote sides

A screenshot of the error message is provided below:

Unfortunately, there has been no response to this issue, leaving users to find alternative solutions or workarounds.

While the issue is not resolved, there are a few workarounds and solutions that can be employed:

Use a different file transfer application: Consider using a different file transfer application that does not rely on RustDesk's remote desktop functionality.
Log in to the Steam Deck user account: Although the user is already logged in, try logging in to the Steam Deck user account again to see if it resolves the issue.
Check for updates: Ensure that both Windows 11 and Steam Deck are running the latest versions of their respective operating systems and RustDesk.

The "No active console user logged on, please connect and logon first" error when attempting to transfer files from Windows 11 to Steam Deck using RustDesk is a frustrating issue that can be resolved by exploring alternative file transfer applications or workarounds. We hope that this article has provided valuable insights and solutions for users experiencing this issue.
Windows 11 + Steam Deck (SteamOS) File Transfer: Q&A

In our previous article, we explored the issue of file transfer between Windows 11 and Steam Deck (running SteamOS) using RustDesk, a remote desktop and file transfer application. We discussed the bug description, provided a step-by-step guide on how to reproduce the issue, and discussed the expected behavior. In this article, we will address some of the frequently asked questions (FAQs) related to this issue.

Q: What is the cause of the "No active console user logged on, please connect and logon first" error?

A: The exact cause of the error is not clear, but it is believed to be related to the way RustDesk handles remote desktop connections and file transfers.

Q: Why does the error occur only when transferring files from Windows 11 to Steam Deck?

A: This is a known issue, and it is not clear why the error occurs only in this direction. It is possible that the issue is related to the way RustDesk handles file transfers in the opposite direction.

Q: Can I use a different file transfer application to resolve the issue?

A: Yes, you can try using a different file transfer application that does not rely on RustDesk's remote desktop functionality. Some popular alternatives include FileZilla, WinSCP, and Resilio Sync.

Q: Will RustDesk release a patch to resolve this issue?

A: Unfortunately, there is no official word from RustDesk on when or if a patch will be released to resolve this issue. However, you can try checking the RustDesk website and forums for updates.

Q: Can I use a self-hosted relay to resolve the issue?

A: Yes, you can try using a self-hosted relay to see if it resolves the issue. However, this may not work in all cases, and you may still encounter the error.

Q: Is this issue specific to Steam Deck or can it occur on other devices as well?

A: This issue is specific to Steam Deck, but it is possible that it can occur on other devices as well, especially if they are running a similar operating system and file transfer application.

Q: Can I contact RustDesk support for help with this issue?

A: Yes, you can try contacting RustDesk support for help with this issue. They may be able to provide additional guidance or workarounds to resolve the issue.

Q: Are there any known workarounds or solutions to this issue?

A: Yes, there are a few known workarounds and solutions that can be employed to resolve the issue. These include using a different file transfer application, logging in to the Steam Deck user account, and checking for updates.

We hope that this Q&A article has provided valuable insights and answers to some of the frequently asked questions related to the "No active console user logged on, please connect and logon first" error when attempting to transfer files from Windows 11 to Steam Deck using RustDesk. If you have any further questions or concerns, please don't hesitate to reach out.