mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
Filetransfer not available if remote system got a custom shell instead of standard explorer.exe #2426
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#2426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @avsaponchik on GitHub (Jan 17, 2024).
Bug Description
Issue name^.
Tested on Windows 11 (master) machine (PC that is connecting to another machine) and Windows 7 (slave) machine (which we connect to).
How to Reproduce
On the machine with Windows 10 LTSC (not tested on any other OS type), if we activate advanced shell settings and change our desired shell to something else (windows will not boot explorer.exe upon startup) - when we connect to it there will be no disks or folders and filetransfer from or to that machine is not available.
Expected Behavior
Filetransfer should work no matter what shell is executed upon startup.
Operating system(s) on local side and remote side
Windows 11 x64, No matter actually
RustDesk Version(s) on local side and remote side
1.2.3 (2023-10-13 10:57) > 1.2.3 (2023-10-13 10:57)
Screenshots
Additional Context
If we manually start an explorer.exe and then reconnect with rustdesk then filetranfer will be available again
@rustdesk commented on GitHub (Jan 17, 2024):
#763
@avsaponchik commented on GitHub (Jan 17, 2024):
actually, this exact system is running windows 10 LTSC