4.4 KiB
title, weight, description, keywords
| title | weight | description | keywords | |||||
|---|---|---|---|---|---|---|---|---|
| Windows Portable Elevation | 49 | Elevate the RustDesk portable app on Windows so remote sessions can handle UAC prompts, Task Manager, and other administrator-level windows. Compare startup elevation, controlled-end elevation, and requested elevation. |
|
Use portable elevation on Windows when the RustDesk portable client needs administrator privileges to handle UAC prompts, elevated apps, and full input control.
Windows portable programs do not have administrator privileges, which can lead to the following issues:
- The screen cannot be transmitted when the UAC (User Account Control) window pops up.
- When an elevated window, such as the Task Manager, pops up, the mouse becomes unresponsive.
By elevating privileges, RustDesk can create a process with administrator privileges during startup or a session, enabling it to perform screenshotting and mouse operations, thereby avoiding the above problems.
When do you need portable elevation?
You need portable elevation when the RustDesk portable client must interact with administrator-level UI on Windows. The most common signs are blocked UAC prompts, missing screen transmission during elevation dialogs, or no mouse control over elevated windows such as Task Manager.
Portable elevation quick answers
- Elevation is only needed when the portable build must interact with admin-level Windows UI
- Startup elevation is best when no one is available on the controlled side
- Controlled-end elevation is best when the user can click
Accept and Elevate - Control-end requested elevation still requires someone on the controlled side to accept the UAC prompt
- Installing the full program is still the better option when you do not specifically need the portable workflow
Elevate at startup
This way, remote users don't need to request elevation when connecting. There are two methods:
-
Method 1: Change the name of the portable program to include
-qs-or-qs.exeor_qs.exe(>= 1.4.6), or end withqs.exe(1.2.0 ~ 1.4.5). Click the left mouse button to run, clickAcceptin the UAC window. -
Method 2: Right-click and run as administrator.
Elevate at the controlled end
The controlled end can directly click Accept and Elevate when connecting, or click Elevate when already connected.
| Connecting | Connected |
|---|---|
![]() |
![]() |
Request elevation at the control end
After selecting Request Elevation from the action menu, the following dialog box will appear. If you choose Ask the remote user for authentication, you won't need to input a username and password, but the user on the remote computer must have administrator privileges. If you select Transmit the username and password of administrator, the user on the remote computer only needs to accept in the UAC window. After sending the request, please wait for the user on the other side to accept the UAC window. Upon confirmation, a success message will appear. Note that both methods require someone on the controlled end to accept the UAC window. Therefore, if there is no one available on the other side, elevation should not be requested at the control end.
| Menu | Dialog |
|---|---|
![]() |
![]() |
| Wait | Success |
![]() |
![]() |
How to Choose
| Scenario | Method |
|---|---|
| No elevation required | Install the program |
| No user available at the controlled end | Rename or Run with administrator |
| User available at the controlled end and Immediate elevation when connected and Accept-via-click connection |
Click Accept and Elevate when receiving the connection at the controlled end |
| User available at the controlled end and Elevation as needed |
Click Elevate on the connection management window at the controlled endor Request elevation at the control end |





